Results 1 to 12 of 12
  1. #1
    2 Star Lounger
    Join Date
    Nov 2001
    Location
    Toowoomba, Queensland, Australia
    Posts
    112
    Thanks
    0
    Thanked 0 Times in 0 Posts

    ntoskrnl.exe (XP)

    I think I have a major problem and hope that someone here can prove me wrong.

    I am running XP Home on a Compaq Presario Laptop and have received an error message that stops windows from launching and refers to a missing or corrupted copy of NTOSKRNL.EXE

    I have tried using the restore disks that came with the laptop but they all warn about deleting ALL files before restoring the machine to showroom condition. I've located a copy of the file on the internet and thought I'd be able to copy it across via DOS but find that I can't boot into dos and the safe mode with the dos prompt is not available because of the missing file.

    Is there any way to boot the laptop in DOS?

    Thanks

  2. #2
    Gold Lounger
    Join Date
    Feb 2003
    Location
    Wardrobe Malfunction Junction, Derry
    Posts
    2,953
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: ntoskrnl.exe (XP)

    Why don't you hit the F8 key and see if at the Windows Advanced Options menu either Last Known Good will get you back to Windows or else System Restore? There are ways to boot from other disks if you have them and boot disks but this is the most straight forward and simple and easiest way I know.

    SMBP

  3. #3
    2 Star Lounger
    Join Date
    Nov 2001
    Location
    Toowoomba, Queensland, Australia
    Posts
    112
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: ntoskrnl.exe (XP)

    No success with 'last known'

    As an added complication, I'm using an external floppy drive (via USB) instead of the one that came with the laptop. I'm not sure whether the machine will see the floppy drive as the boot drive (it still appears as the a: drive in explorer) even if I have a floppy to boot from.

  4. #4
    Gold Lounger
    Join Date
    Feb 2003
    Location
    Wardrobe Malfunction Junction, Derry
    Posts
    2,953
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: ntoskrnl.exe (XP)

    Joe--

    Maybe if you can't use System Restore through Safe Mode by showing the nature of the error somebody will jump into show you how to fix the problem or you can fix what might be causing it.

    Missing NTOSKRNL.EXE Error:

    103673: Err Msg: Windows Could Not Start...(Missing Ntoskrnl.exe)

    314477: Error Message: Windows Could Not Start Because of a Computer Disk Hardware Configuration Problem

    I get the error "NTOSKRNL.EXE missing or corrupt" on bootup.

    Repair Missing or Corrupt Files

    One Answer:

    This is usually due to an error in the boot.ini file. The entry for NT is either missing or incorrect. Edit the boot.ini file and check the entry for NT is correct, for example for an IDE disk the entry should look something like

    multi(0)disk(0)rdisk(0)partition(2)winnt="Windows NT workstation"

    Check that disk and partition are correct. If you have recently added a new disk or altered the partitions try changing the disk() and partition() values. If you are sure everything is OK, then the actual file may be corrupt so copy NTOSKRNL.EXE off of the installation CD onto the %systemroot%/system32 directory.

    You may need to edit the boot.ini if Linux is installed onto a system. During installation DiskDruid (Red Hats disk configuration utility) may create a primary partition (depending on disk configuration) and although the extended NT partition was there first (and at the beginning of the disk), the primary partition affects the numbering of the partition() parameter of boot.ini. Changing it from (1) to (2) (for example) allows the successful boot of NT.[/i]

    SMBP

  5. #5
    Uranium Lounger
    Join Date
    Jan 2001
    Location
    Cincinnati, Ohio, USA
    Posts
    7,089
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: ntoskrnl.exe (XP)

    Well, forget DOS. It doesn't exist in Windows XP. You could try booting from floppies, but they won't get you anywhere (even the XP boot floppies as they require the XP installation CD) - and please don't slap a file you found on the Internet on the computer hoping that it will work. You could cause worse problems than you already have.

    At this point, without a full install CD, you may well be up a creek. Depending on how much data you stand to lose, you have a couple of options: 1) purchase a copy of Windows at a local retailer and use it to repair your installation, or 2) replace the hard drive and install Windows on the replacement. Then your data will still be readable from the old drive.

    I wish I had better news, but if you don't have a backup of your data, this is the kind of thing that will convince you to start making them.
    -Mark

  6. #6
    Gold Lounger
    Join Date
    Feb 2003
    Location
    Wardrobe Malfunction Junction, Derry
    Posts
    2,953
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: ntoskrnl.exe (XP)

    Joe--

    I think it would but you may have to check the boot order in your bios to make sure some other boot source isn't in the way of whatever you want to boot from--the A drive or the Hard Drive or a CD-Rom. You can get to dos prompts through boot disks and CDs from other operating systems, some people even use a 98 or ME disk and LKG doesn't work most of the time--it's only worked once for me with a crash after I put in InCD to a blue screen. We can track down this error for you and I will be glad to in a little while, but I don't think that will matter except for the future. We both know it has an excellent chance to be hardware induced probably driver by odds.

    How about giving System Restore a try from Safe Mode and some times if that won't work Safe Mode with a command prompt and running the System Restore command from there will get you back up to Windows.

    SMBP

  7. #7
    2 Star Lounger
    Join Date
    Nov 2001
    Location
    Toowoomba, Queensland, Australia
    Posts
    112
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: ntoskrnl.exe (XP)

    Thanks to everybody for your suggestions and advice. I've taken the option of going to a local repair shop to have the hard drive removed and copied. I'll then reinstall from scratch and reimport my data files.

    In future, I'll be more anal about backing up etc.,

    Thanks again

  8. #8
    Gold Lounger
    Join Date
    Feb 2003
    Location
    Wardrobe Malfunction Junction, Derry
    Posts
    2,953
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: ntoskrnl.exe (XP)

    Did you ever try an F-8 to Safe Mode and then System Restore Joe? And there is enough dos emoulation in XP to system restore from the safe mode command prompt sometimes when the first won't work.

    SMBP

  9. #9
    Uranium Lounger
    Join Date
    Jan 2001
    Location
    Cincinnati, Ohio, USA
    Posts
    7,089
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: ntoskrnl.exe (XP)

    Not to nitpick but I'm going to anyway...

    There is no DOS. Not even emulation. The safe mode command prompt is a command-line interface for the system which requires the kernel to be loaded, which brings me to my second point...

    NTOSKRNL.EXE is the Windows XP kernel. If it's missing or corrupted, the system won't get past the boot loader.
    -Mark

  10. #10
    Gold Lounger
    Join Date
    Feb 2003
    Location
    Wardrobe Malfunction Junction, Derry
    Posts
    2,953
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: ntoskrnl.exe (XP)

    That's not nitpicking at all, if I didn't look back at the boot mechanism enough to look at it and realize that. I don't want to look at the System Restore snapshot as some kind of panacea superficially and if predecessors to the kernel in the boot mechanism aren't working ( boot.ini or Ntdetect.com and they either can't load the kernel or enough of the kernel isn't there) than it's wrong for me to invoke using System Restore and I need to understand what it can and can't do. I'm not sure what caused this and all the things that can go into either not loading the kernel or the kernel getting in shape where it won't function. You'll see statements that say if you get that error the best thing to do is run the Windows XP Repair process, and I guess they're invoking a parallel or repair install when they say that maybe something else.

    I continue to get confused with the amount of information and tasks that can be accomplished though, outside this problem and this error with a dos prompt up in Windows XP and the XP has no dos statements. I know you understand this deeply. I wish I did and will continue to work on it on my own time. The other day I couldn't get one of their non-regression hot fixes in for a problem I kept having (mshtml.dll crashes with IE but maybe because of windows explorer or XP or all 3). The passwords for those self-extracting zips don't work half or most of the time, and their is a public KB download for that particular error but it doesn't work because like a lot of update/hotfixes downloads says you need XP SP1 when you have it so I used the dos prompt whatever it is to get the download in.

    When you say their is no dos do you mean for the purposes of booting into dos the way people talk about doing with prior OS's or just period, and then what do you call what is worked with when you put "cmd" or "command" in the run box? I'm not intending to be argumentative here, in the least, just trying to get past my confusion at learning commands and using them--thinking they are "dos commands" but knowing there is no dos.

    SMBP

  11. #11
    Uranium Lounger
    Join Date
    Jan 2001
    Location
    Cincinnati, Ohio, USA
    Posts
    7,089
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: ntoskrnl.exe (XP)

    Glad you didn't take offense. Understanding is half the battle (if not more). <img src=/S/smile.gif border=0 alt=smile width=15 height=15>

    There is an excellent explanation of the boot process, starting from when you press the power switch on up, here: http://www.qvctc.commnet.edu/classes...7/boot-xp.html This should help understanding what happens at boot time.

    When I say there is no DOS, I mean it's not there, period. DOS is an operating system in and of itself. You can boot to DOS and manipulate files if the file system can be read by DOS - FAT or FAT32. If the file system is NTFS, you won't be able to see the volume.

    XP's command line does have some of the same statements that DOS used, but I imagine it's because Microsoft wrote them both. It's a smaller learning curve for DOS jockeys. Incidentally, Unix was where MS cribbed some of their own DOS statements from, but the way the commands function is radically different in most cases. In any event it tends to blur the lines.

    When entering CMD in XP, you are using a "CLI" - Command Line Interface. DOS was a CLI operating system. The difference is that CMD has full 32-bit support and other extensions and is designed to work with the NT architecture. COMMAND is a 16 bit shell that can be run from within Windows, and exists for backward compatibility. It has severe limitations as to what it can do and is noticeably slower than CMD. They look the same but they aren't.

    Really, it's a matter of terminology. DOS looks for all the world like a command prompt in XP, but only because they are based on character input and output instead of whiz-bang graphics. Thus, it's easy to confuse the two unless you know what the fundamental difference is, and a lot of folks refer to the command line as a "DOS box." Myself, I'm a stickler for terminology but I'm just as guilty as the next person of using that term loosely....people know what you mean when you say it; it doesn't become important until you get to the low level stuff as this post did.

    Hope that helps!
    -Mark

  12. #12
    Gold Lounger
    Join Date
    Feb 2003
    Location
    Wardrobe Malfunction Junction, Derry
    Posts
    2,953
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: ntoskrnl.exe (XP)

    This is very helpful. The terminology is all important--that much I understand--and this is a good clear concise statement of some of the differences. It seems like some of these articles on dos in XP and the differences between cmd and command are afraid to come out and say what they really are which may be my rationalization for not understanding their terminology well.


    It would have been great to be toiling/hobbying with this stuff back in the day when Apple started and MS started and to know about some of the other OS's they borrowed from for a grip and a perspective on this, and to be able to watch them evolve. If I pretended I didn't have a few hundred learning curves with this box I would only be fooling myself and learn nothing.

    I have collected sites on dos and sites on dos commands used in XP, and books with good chapters on the use of the limited number of statements. Every time I read the explanations of the differences between "cmd" and "command" I end up trying to figure out what they really meant. It is interesting that the many sites that are beginning to talk about Longhorn components say that the command shell they released for developers to test is based on Unix.

    Thanks for the help. The terminology is a large part of the problem for me.

    SMBP

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •