Setup error: ntkrnlmp.exe could not be loaded

[geekchik]

I have Win2k on an old 6GB drive. I recently bought a 40GB drive and wanted to install Win2k on it as the master drive so I can use the 6GB to play around with alternate OSs. However, every time I try, I get ntkrnlmp.exe could not be loaded. Error type is 4. Setup cannot continue.

The drive is formatted with NTFS and if I boot from the 6GB drive I can use the 40GB as a slave. That's not an acceptable permanent solution, though, as the small drive is old, sloooow, and already had a bad block turn up.

Any ideas, links etc. would be much appreciated.

Thanks,

geekchik

 

[PeteH2]

Hi,

Have master and slave jumpers have been correctly set ?
What partitions have you got set on each drive ?
What happens if you install W2k on the 40Gb without the 6Gb present ?

PeteH2

 

[geekchik]

Hi. )

The 40GB drive is master, and 6GB is slave, both at the appropriate place on the cable. (I don't even have to change them to boot from the smaller one, since my motherboard has a boot option that lets me manually select a device to boot from if I don't want to boot from the master. Nice, that.)

Each drive only has the one partition. At first, I had the large one partitioned further, but after several unsuccessful attempts to install, obliterated the partitions and reformatted, thinking there might be a problem with the partitions. It didn't help.

Installing without the 40GB drive yields the same error.

Thanks again from the frustrated,

geekchik

 

[geekchik]

Erm... I meant installing without the 6GB drive yields the same error.

Sheesh. lol geekchik

 

[Niv3k]

try doing an fdisk, and completely wiping out the 40 gb drive. Do not format. Then pull the 6 gb out of your computer, and leaving only the 40 gig in there, re-install the OS.

Kevin

 

[Guest_imported]

I had this same problem trying to install to a single processor system (with Error Type 7). It turned out the 4 bootdisk were created on a multiprocessor system. I ran makeboot from the target pc and the install worked no problem.

 

[Guest_imported]

Chances are that the hard drive needs to be fdisk and reformatted. We had the same happened to two different disk. One hard drive was really old and was used with Linux. The other was an old 4 gb. We ran the fdisk and reformatted with no problems afterward. Hope this helps.