• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Problem loading up WIndows 2000...Help!

I recently built a computer using the CUSL2-C motherboard.

I am using my hard drive from my old computer,
which is a Maxtor Diamond Plus 40 ATA 100 running windows 2000.

I am receiving an error message when I boot up the hard drive.

The message is "STOP parameter, paramter, INACCESSIBLE_BOOT_DEVICE" with an entire blue background.

The bios detects the hard drive, but I can't seem to load up the operating system.

I tried using the "maxblast" disk, which is an install utility that came with the hard drive, but when I load it up, the whole system freezes.

Any ideas on how this error message occurred and how to get my hard drive to work?! Maybe I need to update my BIOS? please help! Thanks in advance.
 
If you used the Maxblast software to set up the drive the best way to get it to work would be boot from the maxblast disk and uninstall it, (I have had problems with drive overlay programs like Maxblast, EZdrive etc. when installing OS?s). Set your PC to boot from the CD drive, (boot order in the bios) and boot from your Win2k disk and go trough the setup routine that way, (of course that?s if you want to use all of the drive as C:\). If you want to divide the drive into partitions then uninstall the maxblast software and use fdisk

Gorgot to add make sure boot sector virus protection is turned off in the BIOS
 
Windows 2000 doesn't like it when you change the motherboard. Win2k is expecting one board, but sees another and it doesn't like it. if you have a ERD, you can find out the arc path of your win2k install, edit the setup file on the ERD, and try to do a repair from the recovery console. I've had your problem while transfering my HD from a onboard ATA/66 controller to a standard IDE channel. I think I ended up installing Win2k over itself. You might want to consider a clean install.
 
Got it up and running.

Just booted my computer up with win2k cd and ran a REPAIR.

Don't know exactly how it worked.

Thanks for your input everyone.
 
Back
Top