New system won't boot W2K...help!

tomstevens26

Senior member
Sep 21, 2001
700
0
0
Ok, here's the scoop...

Just finished migrating a friend's PC over from a Duron 800/MSI K7T Pro2A to a new Tbird 1.4 and ECS K7S5A. The rest of the system components are the same as the original configuration...just the mobo and CPU have changed. The system is setup for dualboot, W98 and W2K. Nothing was done to the hard drives...they were just pulled from the old system and reinstalled in the new. W98 booted fine, found the new hardware, etc...and is up and running without a hitch. W2K on the other is generating a STOP error message saying something about INACCESSIBLE DEVICE. I'm getting these errors even when trying to go into safe mode. Everything appears to run fine in W98 so I really don't think it is a hardware issue but I'm at a lost. The STOP error seems to point to hardware but why does it work fine in 98? Does W2K just not like having major hardware changes like that?

Thanks for any help/advice!
Tom
 

jcmkk

Golden Member
Jun 22, 2001
1,159
0
0
I don't see why it would be a hardware identification problem. One time I was having a very hard time installing Win2K on my athlon system, so I installed it on the same HD, but hooked up on my old celeron system. I switched the HD back over, and everything was fine.
 

obenton

Platinum Member
Oct 11, 1999
2,012
0
0
I've found that w2k generally handles the move better than win98. I assume you've used standard IDE33 controller on both computers, so that it's not an IDE controller issue. Run a w2k repair install from the w2k cd (or, using win98, copy its /i386 directory to the hard drive and run from the hard drive), and see if that fixes it. If starting the repair from within win98, use winnt32.exe.
 

Jiggz

Diamond Member
Mar 10, 2001
4,329
0
76
Thing I can see in here are those devices installed when you were using a Via based mobo and now cannot be found by W2K. If you made a good preparation on this upgrade you'll probably will not encounter this my removing all mobo related drivers first and then do the upgrade. Anyway, the probable fix is to reinstall as a repair. And if that does not fix it you will have to save your data and do a full re-installation.
 

Muadib

Lifer
May 30, 2000
18,124
912
126
Your problem was going from a VIA based board to a SIS based one. Try booting to safemode, and then deleting everything in your device
manager.
 

TCOMA

Junior Member
Dec 1, 2001
4
0
0
Reinstall W2K in Repair mode,insert the cd & follow the instructions....