Re: recovering from driver update
- From: Dan Seur <click@xxxxxxxxx>
- Date: Thu, 30 Mar 2006 11:44:33 -0500
As DL said there's no W2k rollback.
The slowdown may be due to bad mboard driver(s), or a failing HDD, or something else.
(1) See if the customer has the original driver(s) anywhere. CD? On the HDD? If not, talk to Abit tech support.
(2) Run the HDD manu's diagnostic against the hard drive.
(3) There's a chance the customer isn't telling you all the facts. There had to be a reason for installing new drivers; what was it? If the customer opened the case for any reason, it's probably a good idea to check all cabling connections and switches, including HDD jumpers.
wyocowboy wrote:
[note - this is a win2k Prof workstation, but since there is not a forum in the left-pane list for win2k under Windows - Older Versions, I am posting it here....]
A customer brought in a win2k prof workstation that had been working fine until he decided to load the latest motherboard drivers from Abit. Since doing the update, it takes about 45 min - 1 hr to get from power-on to the desktop. It takes slightly less than that in safe mode. Once it gets to the desktop, it is useless as it takes several minutes for the mouse pointer to move in response to mouse movement, so successfully doing something that requires a mouse click is like hitting the lottery.
When booting in protected (normal) mode, it spends a very long time at the colored win2k banner, with the progress bar stuck at "corporation" and when it finally moves on, it spends a very long time at "Applying security policy"
When booting in safe mode, it hangs for a long time after displaying the loading of \system32\drivers\ac2003.sys. I've been told that this is showing the last driver to successfully load, so I suspect the problem is with this driver, or the one that is loading after it.
I haven't yet enabled boot logging, but once I indentify the culprit, how do I roll back the driver, or disable it in such a way that I can get to the point that I can get around in the desktop - at least in safe mode?
Part two of the question is: if the culprit is some kind of essential driver that win2k needs to boot, does it automatically seek out an alternative base driver in the case that I need to disable the culprit by renaming, etc?
I did try a repair reinstall of win2k, but this did not change the symptoms.
---
avast! Antivirus: Inbound message clean.
Virus Database (VPS): 0613-1, 03/29/2006
Tested on: 3/30/2006 11:36:29 AM
avast! - copyright (c) 1988-2004 ALWIL Software.
http://www.avast.com
---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 0613-1, 03/29/2006
Tested on: 3/30/2006 11:44:33 AM
avast! - copyright (c) 1988-2004 ALWIL Software.
http://www.avast.com
.
- Prev by Date: Re: Windows 2000 Server problem with FTP.EXE
- Next by Date: Re: recovering from driver update
- Previous by thread: Re: recovering from driver update
- Next by thread: Re: recovering from driver update
- Index(es):
Relevant Pages
|
Loading
