Paduwan
asked on
Windows 2000 hangs during hardware detection
I have made 2 Ghost images and both have been tested on different machines successfully.
The problem I'm having at the moment is with two different machines:
- An ASUS P3V 4X
- A Soltek SL-85MIR2
I have tried each image on both machines. Since there is a hardware difference between the machines and the machine the image was built from, I receive a Blue Screen of Death Fatal error - Hard Disk Device Inaccessible.
To get around this, I run 2000 setup from the CD and then repair the installation so Windows can redetect hardware (I have done this before and it has installed fine).
However in this instance when Windows is detecting devices such as keyboard and mouse etc. the progress bar reaches about 30% and then freezes. In one case I left it for over 12 hours and no progress.
I have researched the Net with no luck. I have stripped the machines down to the bear essentials and still no luck. I have a big hammer which is starting to look like a feasible solution.
Any help is greatly appreciated. Thanks.
The problem I'm having at the moment is with two different machines:
- An ASUS P3V 4X
- A Soltek SL-85MIR2
I have tried each image on both machines. Since there is a hardware difference between the machines and the machine the image was built from, I receive a Blue Screen of Death Fatal error - Hard Disk Device Inaccessible.
To get around this, I run 2000 setup from the CD and then repair the installation so Windows can redetect hardware (I have done this before and it has installed fine).
However in this instance when Windows is detecting devices such as keyboard and mouse etc. the progress bar reaches about 30% and then freezes. In one case I left it for over 12 hours and no progress.
I have researched the Net with no luck. I have stripped the machines down to the bear essentials and still no luck. I have a big hammer which is starting to look like a feasible solution.
Any help is greatly appreciated. Thanks.
ASKER
We are currently using Sysprep 1.1 but haven't configured the sysprep.inf file.
Looking at the BSOD error:
0xC0000034
So you're right its' probably a mass storage problem. However the drive is a Seagate Barracuda IV (ATA) which you would think would be included in the Windows 2000 .inf list(?)
Anyway if I find a driver do I then reference it in mshdc.inf?
Looking at the BSOD error:
0xC0000034
So you're right its' probably a mass storage problem. However the drive is a Seagate Barracuda IV (ATA) which you would think would be included in the Windows 2000 .inf list(?)
Anyway if I find a driver do I then reference it in mshdc.inf?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The BIOS doesn't list UDMA as an option (AMI-BIOS 2003) and there is no anti virus.
I've searched the Net but I can't find information on which IDE controller is supported by the motherboard.
I have found a site that provides a list of entries that can be merged into the registry of the machine that the image will be taken from. It covers controllers such as atapi, compaq, intel, silicon, via etc. but I can't be sure that this will work on the board.
Anyway does the registry merge make sense?
I've searched the Net but I can't find information on which IDE controller is supported by the motherboard.
I have found a site that provides a list of entries that can be merged into the registry of the machine that the image will be taken from. It covers controllers such as atapi, compaq, intel, silicon, via etc. but I can't be sure that this will work on the board.
Anyway does the registry merge make sense?
ASKER
Tried the registry merge and it worked like a charm. Thanks zefiro for pointing me in the right direction.
For anyone else experiencing this problem, the instructions for the fix can be found at:
http://www.jsiinc.com/SUBJ/tip4900/rh4948.htm
For anyone else experiencing this problem, the instructions for the fix can be found at:
http://www.jsiinc.com/SUBJ/tip4900/rh4948.htm
When imaging Win2K with Ghost, are you using Sysprep? If not, download Sysprep 1.1 from Microsoft's site and check here for instructions on how to use it
http://www.microsoft.com/windows2000/downloads/servicepacks/sp2/deploytools.asp
You will want to follow instructions to use 'mass storage drivers' and you may also want to look into how to pre-load drivers using sysprep.
Mass Storage Drivers are basically hard drive drivers that Sysprep 1.1 (not 1.0) can load early enough in the imaging process to prevent almost all of the BSOD's caused by hardware. I cannot provide my list of drivers due to NDA's, but a Google search for mass storage drivers should get you some complete lists.
The nice thing about using sysprep is that, with some tweaking, you can completely automate the W2K install.
ABout detecting devices, using sysprep may just remove the problem by itself, or, if you can set-up the image with pre-loaded drivers and attempt to push that image down.
Other troubleshooting steps,
remove any USB devices especially mouse/keyboard,
if you find anti-virus listed in your BIOS anywhere, disable it,
turn off UDMA on your primary hard drive, (done in the BIOS),
while you are in the BIOS, turn off Advance Power Management features, probably not causing the problem, but should be turned off anyway,
I've seen ati video cards do this, but it sounds like you may have already tried removing it, if not, try it, if it is on-board, you'll need to get a PCI or AGP video card, then disable the on-board card
Could be RAM, but probably not. . .
If this is happening on both workstations, try to ID any common piece of hardware they may both have, if you find one, kill it off and try again,
otherwise, if you have another Ghost image handy, see if the problem occurs with it as well, if it does not, there may be something in the image that is killing you.
My best guess is the UDMA thing. . .but try Sysprep if you haven't already, you will like it.