re: Failed (non-boot) Hard drive halts windows bootup!?
Tuesday, September 27, 2005 at 9:45 am
Windows 2000 Annoyances Discussion Forum
Posted by C K
(6910 messages posted)
Moving the drives to a new motherboard (different HD controller) without proper prep
was your first mistake. Put them back on the old PC and see what happens. If they
work, good, and if they don't, you have some major problems to deal with. Read here:
http://support.microsoft.com/default.aspx?scid=kb;en-us;824125
http://support.microsoft.com/default.aspx?scid=kb;en-us;292175
Sometimes the HAL may be different but more often it's the HD controller on the motherboard
that is and that's what will stop everything cold. Hopefully, you haven't done other
damage such as to the hardware or data corruption. Any of these solutions assumes
that W2K has the necessary drivers for the new motherboard. As W2K is an old operating
system, it may be likely that you will have to put the new MBs drivers on a floppy
disk to add at the very start of the install. If you need to do that and don't,
the repair will fail and W2K will not start. Check to see if the new machine is
W2K compatible or may need new IDE drivers loaded from a support CD etc.. Can't
help on failed drives as that is a whole other issue...
On Tuesday, September 27, 2005 at 4:57 am, nick wrote:
>Hello, my win2k system has 2 hard drives, when I went to move both drives to a new
>PC I was setting up, the non-boot drive (data drive) failed due to a stiction problem,
>that's a whole other problem though...the boot drive with win2k (c: drive) is still
>OK, so I was hoping to be able to keep my PC the same (same windows setup, apps
etc)
>but just not have the data accessible. What happened was when the good drive starts
>to boot into win2k it gets through the OS selection screen and possibly the kernel
>load but halts with a blue screen that says 'drive not accessible' and to run a
virus
>scanner. So what's happening is the win2k loader is looking for something on the
>missing drive that is preventing it from starting windows. What I want to do is
break
>all of the links/pointers that point to that drive and let win2k boot from c:, but
>I'm not too sure what windows is looking for on that drive. I think the startup
>sequence is just getting to the reading the registry stage, there is a section of
>the registry that describes the drives in the system. Can I read this and see if
>it's looking for the other drive?? It may be looking for the MBR on the other drive
>but I'm not sure at this point...any help would be appreciated....what I'm hoping
>is I can go in and change a line or two in a file or the registry and be running
>like I was before....(fingers crossed) :) l8r...Nick
|
All messages in this thread [show all]
 |  | re: Failed (non-boot) Hard drive halts windows bootup!? (C K: Tue, Sep 27, 2005, 9:45 am) |
| |
| |
| |
Return to the Windows 2000 Discussion Forum
|
|
