Short in Motherboard - Final Update

  • Thread starter Thread starter Jeff
  • Start date Start date
J

Jeff

....thought I would start another thread on this and give the final update
for those interested. This was the issue where I had a problem after
drilling a mounting hole for an extra case fan.

....got a replacement board today and everything is back up and running.

It turns out that this motherboard has a bios feature that allows one to set
how the machine reacts after power is restored after being cut off. I
haven't messed with or built that many machines and I've never seen this on
the ones that I have. The default apparently was to return it to the state
prior to the power outage. Because I had turned off the power switch on the
back of the power supply when the problem began, the board immediately
turned on when the power was restored even when the case switch was not hit.
So all of those issues related to that behavior were completely irrelevant
to the real problem. I'm still not positive that I know precisely what the
problem was with the old board, and I'm not inclinded to spend the time to
find out. It could perhaps have been simply a matter of something going
wrong with the video as the issue started when I couldn't get any output to
the monitor. ...but I tried two different cards plus the on-board, so it
would have to be something more basic on the board.

....anyway the new board works fine and I didn't have to re-install any of
the OS, which was on hardware raid.

There was only one very minor quirk - everything on the new board was
considered a new piece of hardware even though the board was the same
model - so all of the drivers were re-installed. The only problem that this
caused was that when I enter the network connection properties to place in
IP and similar info, W2K3 claims that these settings are in use by the old
network connection that "is not physically in the computer." (obviously, it
is on the old motherboard) It then asks if I really wish to use these
duplicate settings. There is only one network adapter card listed in the
device manager (the one for the current board), and I see no where that I
can disable the old one. Can anyone point me in the right direction?

Jeff
 
Thanks for reporting back..
All those clever suggestions totally missing the fault !!!..which isn't a
fault anyway !
Lol !
Life Is Cruel, Computers Make it Worse.
Mouse
@@@
 
Jeff said:
...thought I would start another thread on this and give the final update for those
interested. This was the issue where I had a problem after drilling a mounting hole for
an extra case fan.

...got a replacement board today and everything is back up and running.

It turns out that this motherboard has a bios feature that allows one to set how the
machine reacts after power is restored after being cut off. I haven't messed with or
built that many machines and I've never seen this on the ones that I have. The default
apparently was to return it to the state prior to the power outage. Because I had turned
off the power switch on the back of the power supply when the problem began, the board
immediately turned on when the power was restored even when the case switch was not hit.
So all of those issues related to that behavior were completely irrelevant to the real
problem. I'm still not positive that I know precisely what the problem was with the old
board, and I'm not inclinded to spend the time to find out. It could perhaps have been
simply a matter of something going wrong with the video as the issue started when I
couldn't get any output to the monitor. ...but I tried two different cards plus the
on-board, so it would have to be something more basic on the board.

...anyway the new board works fine and I didn't have to re-install any of the OS, which
was on hardware raid.

There was only one very minor quirk - everything on the new board was considered a new
piece of hardware even though the board was the same model - so all of the drivers were
re-installed. The only problem that this caused was that when I enter the network
connection properties to place in IP and similar info, W2K3 claims that these settings
are in use by the old network connection that "is not physically in the computer."
(obviously, it is on the old motherboard) It then asks if I really wish to use these
duplicate settings. There is only one network adapter card listed in the device manager
(the one for the current board), and I see no where that I can disable the old one. Can
anyone point me in the right direction?
Click to expand...
Too bad about the board, delete (uninstall) the adapter in device manager remove any
software related reboot.
Expect to find other unexplained 'quirks'. this can happen with old OS install / new MB
(even if its identical).
 
In alt.comp.hardware.pc-homebuilt "Jeff said:
...thought I would start another thread on this and give the final update
for those interested. This was the issue where I had a problem after
drilling a mounting hole for an extra case fan.

...got a replacement board today and everything is back up and running.

It turns out that this motherboard has a bios feature that allows one to set
how the machine reacts after power is restored after being cut off. I
haven't messed with or built that many machines and I've never seen this on
the ones that I have. The default apparently was to return it to the state
prior to the power outage. Because I had turned off the power switch on the
back of the power supply when the problem began, the board immediately
turned on when the power was restored even when the case switch was not hit.
So all of those issues related to that behavior were completely irrelevant
to the real problem. I'm still not positive that I know precisely what the
problem was with the old board, and I'm not inclinded to spend the time to
find out. It could perhaps have been simply a matter of something going
wrong with the video as the issue started when I couldn't get any output to
the monitor. ...but I tried two different cards plus the on-board, so it
would have to be something more basic on the board.

...anyway the new board works fine and I didn't have to re-install any of
the OS, which was on hardware raid.

There was only one very minor quirk - everything on the new board was
considered a new piece of hardware even though the board was the same
model - so all of the drivers were re-installed. The only problem that this
caused was that when I enter the network connection properties to place in
IP and similar info, W2K3 claims that these settings are in use by the old
network connection that "is not physically in the computer." (obviously, it
is on the old motherboard) It then asks if I really wish to use these
duplicate settings. There is only one network adapter card listed in the
device manager (the one for the current board), and I see no where that I
can disable the old one. Can anyone point me in the right direction?
Click to expand...
Try booting up in "Safe Mode"
In Win-95, Me, 2000, and 98, device-drivers that are still active in the
system, but not for recognized devices, show up when running
device-manager in Safe Mode. You have to delete them while running in
Safe Mode. I haven't seen this type of thing (lately anyway) while
running Win-XP though.

This problem of having to delete extra drivers in Safe Mode is an old
one with Windows. I think they corrected it with XP.

While at it, go looking for old video drivers and other duplicate
drivers as well. Usually, if you have two drivers for any device, it's
a mistake and should be deleted. It doesn't usually hurt if you
accidentally delete a driver you wanted; as Windows will just load the
proper one next time you boot up in Standard Mode.

Well: Usually. Sometimes video drivers have to be reinstalled from the
disk or from online sources if you accidentally mash the wrong one. No
problem ... usually; as Windows will just load whatever driver that
seems to it to be passable. ATI video boards have the biggest problem:
THERE you should set straight-up VGA mode before installing. Also,
deleting *ALL* drivers labeled "ATI*.*" in the Windows/system and
Windows/system32 directories before installing a new ATI board (if
you've had another one in the machine before) often solves a lot of
problems even running their ATI software removal program doesn't fix.
For some reason their installation software does *not* replace ATI
drivers that are already in those two directories, even if what's in
there is for the wrong board or even for a different OS version. ;-{

You'd *think* their ATI software removal utility would ... but no.

I've found as many as *five* video drivers installed on a machine
running WIN-98 when in Safe Mode; while only the one showed up when
booting normally. That caused all sorts of crap to happen.
 
Frank McCoy said:
Try booting up in "Safe Mode"
In Win-95, Me, 2000, and 98, device-drivers that are still active in the
system, but not for recognized devices, show up when running
device-manager in Safe Mode. You have to delete them while running in
Safe Mode. I haven't seen this type of thing (lately anyway) while
running Win-XP though.
Click to expand...

....looks like you were close, but not complete. Safe mode did pull up
references to other devices, but not the old network adapter. I also
realized that device manager also has an option to show hidden devices that
looked alot like the ones that appeared in safe mode. There must be
something in the registry that I'll have to search for.

Jeff
 
Back
Top