Could not find kernel image: linux error? booting back to XP Pro

Bobmark8Bobmark8
edited February 2009 in Science & Tech
Could not find kernel image: linux error? booting back to XP Pro <hr style="color: rgb(255, 255, 255); background-color: rgb(255, 255, 255);" size="1"> <!-- / icon and title --> <!-- message --> I am one day into Linux and I will try to keep my issue brief. My wife's Dell 8400 which runs XP Pro is sick. icon_sad.gif
First problem (nothing to do with Linux);
Windows could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEMSoooo... I created a "bootable" from download and burn the Ubuntu Live CD Ubuntu 8.10 to run Linux to backup files before trying to restore anything. I was very successful in copying all the data files I need (just in case of a recovery glich icon_wink.gif). Ubuntu has a fantastic GUI!!!
Now here is the rub. I have removed the Ubuntu Live CD and have the MS WIn XP Pro CD in my CD drive to do recovery procedures per the MSs postings I have reviewed AND I now get the unexpected message;eusa_wall.gif
could not find kernel image: linux
boot: (blinking curser) :eek3:
Google had only 10 posts with this subject and all related to trying to get Linux running. Thats not my long term goal. My goal is to get MS Win XP Pro running again. And now I have joined this forum.
ANY HELP ON THIS WOULD BE MET WITH GREAT REJOICE. :respect:

Thanks, Bob

Comments

  • kryystkryyst Ontario, Canada
    edited February 2009
    You need to boot up into the recovery console with the windows cd and get to your c prompt and type FIXMBR that should resolve that problem. Though why it's looking for that boot loader is strange. Did you try installing linux?
  • Bobmark8Bobmark8
    edited February 2009
    I am really struggling with my wife's Dell 8400 which runs XP Pro

    Started with the error:
    Windows could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM

    So, I created a "bootable" CD with KNOPPIX_V6.0-ADRIANE_V1.1CD-2009-01-27-DE.iso to run Linux. I didn’t like the GUI: Soooo... I created a "bootable" CD with ubuntu-8.10-desktop-i386.iso to run Linux. This worked great. With this I am able to see and copy files; however I have discovered there is no valid restore points available in the System Volume Information folder.

    I re-confirmed this by placing the “bad” HD from the Dell 8400 into my Dell Inspiron 530 and it also confirms no valid restore points are available in the System Volume Information folder.

    I have tried to replace the 5 hives in the operating system /WINDOWS/SYSTEM32/CONFIG/folder; however this has not been successful and I have also managed to lose the ability to log in as an administrator in the To repair a Windows XP installation using Recovery Console, press R. (know I screwed that up because this is a machine with an OEM XP install, so you can please skip telling me how I screwed that up)

    So I finally decided to do the MS install repair, i.e.When you see the "Welcome To Setup" screen, you will see the options below.

    This portion of the Setup program prepares Microsoft Windows XP to run on your computer:
    • To setup Windows XP now, press ENTER. (Did this)
    • Accept the License Agreement and Windows will search for existing Windows installations. (Did this)
    • Select the XP installation you want to repair from the list and press R. (Did this)

    Now here is STILL the rub. I have removed all CDs and put the Boot order back the way is should be AND I STILL get this unexpected message on a black (DOS like) screen;

    Syslinux 3.71 Debian – 2008-09-06 EBIOS Copyright © 1994-2008 H. Peter Anvin
    could not find kernel image: linux boot (blinking cursor)

    Any and help would be appreciated very much. I have been at this for DAZE (DAYS)!

    Thanks,
    Bob
  • kryystkryyst Ontario, Canada
    edited February 2009
    Have you gone into recovery console yet from the windows cd and done a fixmbr yet?
  • Bobmark8Bobmark8
    edited February 2009
    Kryyst,<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p></o:p>
    <o:p></o:p>
    Yes Thank you for your previous tip and I apologize for neglecting to say I did attempt your idea and it didn't resolve the issue and as I said in my last posting I can not get into the recovery console anymore since I did try the recovery method of using restore points per MS KB Article ID: 307545 (my bad :-(). So I am back to the question in my last post on how to kill off this Linux boot message. I can't understand how Linux put something on my machine when my understanding was that it was to be a "bootable" CD to help troubleshoot Windows XP<o:p></o:p>

    What I believe I need to do is find and nuk the command that is looking for "kernel image: linux"

    If you agree do you have any ideas on how to do this? Or what would you do next besides throwing the machine out the window (not XP but HOUSE)

    Regards, Bob
  • LeonardoLeonardo Wake up and smell the glaciers Eagle River, Alaska Icrontian
    edited February 2009
    If you've already saved your important data, why not just format the drive and reinstall the OS of your choice, which you indicated was XP? Or, why don't you set the machine to boot from CD, and perform a Windows XP "repair" installation (not recovery console)?
  • Bobmark8Bobmark8
    edited February 2009
    Leonardo,

    Thanks for the response. It was the second thing you recommend "set the machine to boot from CD, and perform a Windows XP "repair" installation (not recovery console)?" that I have already done and I feel it may have taken; however on reboot still get the message:
    Syslinux 3.71 Debian – 2008-09-06 EBIOS Copyright © 1994-2008 H. Peter Anvin
    could not find kernel image: linux
    boot (blinking cursor).
    I have yet to do a scratch install as I wanted to try and avoid reinstalling all programs and data (which, I have but you never know what you may have forgotten to backup). So I think I am faced with three options
    1. get rid of or get SYSLINUS 3.71 out of the boot sequence some how and prevent a full reload.
    2. Fresh install of MS XP Pro, but don't know the best way to do this step by step :-( and of course will need to reload all apps and data.
    3. Try the DELL recovery which I am told will put this puppy back to factory settings and of course will need to reload all apps and data.

    Which would you do and how would you do it. Any additional help is appreciated.

    Cheers, Bob
  • LeonardoLeonardo Wake up and smell the glaciers Eagle River, Alaska Icrontian
    edited February 2009
    I have yet to do a scratch install as I wanted to try and avoid reinstalling all programs and data
    I know the feeling. I have no advice for overcoming the current problem. My Linux experience is only very basic and I have no experience with dual booting.

    It's your call - to perform a format and clean XP installation with the risk that you have not backed up everything.
  • Bobmark8Bobmark8
    edited February 2009
    Leonardo,

    Thanks, I am seaching through folders right now to try and find the Lunix File to nuck. I I can't find it I will call MS and DELL both before I commit to either method of fresh install; let's see what those brains tell us. Thanks for the responses. Bob
  • kryystkryyst Ontario, Canada
    edited February 2009
    I'm still puzzled with why your getting a linux error the live CD shouldn't have installed anything unless you told it to, but for some reason that sounds like a dual boot error message. Which would be from the GRUB installer that linux uses when it's installing the OS and it puts it in the MBR. FIXMBR normally (as in every time I've tried it) removes the GRUB boot loader, if that is what the problem is. One other command you can run from recovery console is FIXBOOT.

    But couple other questions. Do you have more then one harddrive or is your harddrive set with more then one partition? The reason I ask is that if this is a GRUB boot loader that you've got doing a clean install won't remove it even deleting the drive partition won't fix it as it's in the boot record which isn't touched by partitioning the drive.

    One other possibility is if this machine is a name brand machine (dell, hp etc...) they often have repair tools built into a small few gig partition that is sorta invisible. However they also use a boot loader to get into that partition. It's possible that whatever you did killed that partition and it's that boot loader, which is linux based that is causing the problem and has nothing to do with linux.

    If that sounds like the case, then I'm not sure how to fix it.
Sign In or Register to comment.