Unsolved

This post is more than 5 years old

14 Posts

14682

June 8th, 2005 14:00

DELL 2300, W2K install, NTKRNLMP.EXE "The error code is 7"

Okay, trying to revive archaic machine that died with a corrution of the MFT after 7 years.

It's replacements are being configured by me and my colleague, but I'd like to get this one servicable and back in the cluster if possible, for added redundancy.

Previously it ran Windows NT4. And may do again.

Wondered if Windows 2000 is possible as Windows NT4 has serious bugs that NEVER got fixed for our application :(

Install gives an error on the first floppy disk loading NTKRNLMP.EXE. "The Error code is 7" apparently - thanks MS.

The MSKB says this is either BIOS or Memory (what not even possible it is software?).

As a quick test, and chance to check out the hardware, I installed Debian (which worked first time as usual), and have run memory checkers, and I'm pretty sure this machines hardware is working as well it has done for the last 7 years. And that the cause of the error is something else.

The machine (circa 1998) has SCSI disks, and SCSI CD, dual processor.

Am I right in thinking that as "boot from CD" is missing from the BIOS options it isn't possible. I thought everything was booting from CD by then?

Is there a known BIOS fix required? The DELL migration tools just went phut when asked about stuff this old.

11 Posts

July 13th, 2005 02:00

You said you had dual processors? NTKRNLMP.EXE is a special version of the Windows NT kernel that allows you to use more than one processor if your version of Windows permits -- and currently all versions of Windows except Windows XP Home Edition permit it.
 
Chances are, the copy of the multiprocessor kernel on the floppy disk got corrupted. That's what a 7 error usually means. So how to bypass this? At the beginning of the setup process, it asks you if you need to use any special SCSI drivers (scuzzy of them, I know:smileyvery-happy: ) by hitting F6. Two almost-entirely undocumented other features can be activated at that point. If you hit F7, then Windows Setup doesn't do any special detecting at all: it assumes your computer is single processor with no power saving features (you can change this later on from Device Manager) and no "wierd" SCSI drivers, just "normal" ones, and uses the appropriate kernel and drivers. If you hit F5, then you can select a specific Hardware Abstraction Layer and Kernel to use for the install.
 
When you start Setup and it asks you for SCSI drivers, hit F7. NTOSKRNL.EXE will get loaded instead of NTKRNLMP.EXE, and only a single processor will be used. Once Windows Setup is successful, and assuming you've got a Windows 2000 CD, you then open Device Manager, select the Computer object, select the item under it, and update the drivers to "ACPI-compliant Multiprocessor Computer." You will now regain your previous dual processor goodness.

Message Edited by TwelveBaud on 07-12-2005 10:01 PM

8 Posts

September 12th, 2005 09:00

I have this same issue. However, I can not be a corrupt disk. I have tried four different disks all with the same error being displayed. I have tried to get around it by using the F5 or F7. Once it goes around I get ftdisk.sys error code 7 and the install halts. I have updated the bios with the lates from the Dell website and I have tried to load XP Pro, Windows 2000 Pro, W2K Server and W2K Advanced server and they all give the same error.

Any suggestions?

11 Posts

September 12th, 2005 18:00

Unfortunately, in your case you can't try to get around it using F5 or F7; that trick is specific to NTKRNLMP.EXE, HALMP.DLL, and other special multiprocessor files. FTDISK.SYS is a filesystem and hardware driver and can't be skipped over.
 
If you're absolutely certain it's not a disk problem, then it could be a problem with your memory, hard disk, processor, or motherboard. Error 7 just means it couldn't read the file without explaining why. Try running a memory tester, reformatting your hard drive, and running something like SETI@Home or PrimeNet to check your processor.

11 Legend

 • 

47K Posts

November 8th, 2005 00:00

There is a 12 gig max boot partition size limit on the perc.
No other issues with 2000 or 2003 server that I am aware of.
No Events found!

Top