[Ham-Computers] RE: Consequences of changing system boards

Hsu, Aaron (NBC Universal) aaron.hsu at nbcuni.com
Thu Oct 30 18:57:32 EST 2008


Robert,
 
When it comes to product activiation, WinXP/Vista monitor for hardware changes.  IIRC, the type of hardware monitored are systemboards, mass storage controllers (IDE, SCSI, etc), processors, hard drives, network adapters, and a few other items.  For processors and hard drives, the serial numbers are also monitored.  Each time there is a change to one of these devices, a number of points are added to a counter (I have a list of the points Vista assigns to each device, but I can't find it right now).  If the number of points within a certain timframe exceeds a fixed threshold (I think it was 10), Windows determines that it's now running on a different computer and will need to be re-activated.  IIRC, a systemboard change was 11 points, so it automatically triggered a re-activation.  However, if you replace the systemboard with an identical unit, then it wouldn't cost you any points.  CPU and hard drive changes cost something like 7 points.  If you change two components in a short period of time (such as a hard drive and video card), then the point total would exceed the threshold and would trigger an activation process.
 
Now, from a licensing perspective, Microsoft considers any type of systemboard replacement to be a "new computer" for which the license needs to be re-evaluated.  If your Windows license is a "retail" copy (bought in a "retail" box on a storeshelf), then the license is transferrable to the "new" computer.  If you have an OEM or "volume" license (such as "Select" or "Open"), then the license dies with the old systemboard and a new license needs to be purchased).  BTW, this applies to all Windows systems, not just ones where a component is replaced - "retail" licenses are transferrable to new hardware, OEM/Volume licenses are not transferrable.
 
As to your "clunk" problem.  I've seen this before.  Many newer systems these days will shutdown the system after making changes to the BIOS settings - this ensures that advanced chipset settings are properly enabled.  The "clunk" is often a "pop" comming from the speakers (turn on/off pop) or the hard drive actuators "parking".  One of my old motherboards started doing this and would not properly turn "off" when exiting from BIOS setup - I always had to "pull the plug" or throw a "hard" power switch to allow the power supply caps to discharge before the system would fully turn off and turn back on.  When I replaced the motherboard a couple years ago, I discovered leaky caps on the motherboard - the probable cause of the problem.  Remember, a few years ago, there was a global problem with bad electrolytic caps.
 
Anyways, I hope you were able to fix the networking problem.  Check the large caps on the motherboard for bulging and/or leaks - if you find any, it's definitely time to replace the motherboard.  For reference, these caps are part of the power regulation circuit and if they go bad, they can cause instability and eventual failure of the power supply.
 
73,
 
  - Aaron, NN6O

________________________________

From: ham-computers-bounces at mailman.qth.net [mailto:ham-computers-bounces at mailman.qth.net] On Behalf Of WA5CAB at cs.com
Sent: Saturday, October 18, 2008 2:42 PM
To: Ham-Computers at mailman.qth.net
Subject: [Ham-Computers] Consequences of changing system boards


At least when running WIN2000 or XP, I know that if you change the system board to a different one, you have to reinstall the OS.  If you replace the CPU with the same model you don't (I did that two years ago).  What about if you replace the system board with the same model?

The reason that I ask is that I seem to have damaged this system board.  I was switching from on-board ethernet controller to a PCI card after two solid days of fighting a connectivity problem (and that the port swap did not fix) and stupidly forgot to turn off the UPS after powering down the machine.  When I plugged in the PCI card there was a CLUNK and the fans momentarily came on.  Now it works the same when up and running but it comes out of system setup with a CLUNK and drops back to a black screen as though it were off.

Robert Downs - Houston
wa5cab dot com (Web Store)
MVPA 9480 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.qth.net/pipermail/ham-computers/attachments/20081030/204addc3/attachment.htm


More information about the Ham-Computers mailing list