Find the answer to your Linux question:
Page 2 of 2 FirstFirst 1 2
Results 11 to 19 of 19
The live CD won't even start up, too slow. And I have already deleted the linux drive, The only drive I have on there now is C:\...
  1. #11
    Linux Newbie
    Join Date
    Mar 2008
    Location
    England, Manchester.
    Posts
    114


    The live CD won't even start up, too slow.

    And I have already deleted the linux drive, The only drive I have on there now is C:\

  2. #12
    Linux Guru
    Join Date
    Jan 2009
    Location
    Dover, NH
    Posts
    1,633
    Oh, I misread that part. Boot with a Win9x disk, at the A: prompt, type fdisk /mbr

  3. #13
    Linux Newbie
    Join Date
    Mar 2008
    Location
    England, Manchester.
    Posts
    114
    Thanks for your reply, I just tried it.

    It stalled for a second then shows A:\ again.

    I restarted to see what it done but its still the same.

  4. #14
    Linux Guru Jonathan183's Avatar
    Join Date
    Oct 2007
    Posts
    2,903
    As I put in post #10 I think you should boot from a Linux live CD to fix this ... if you only have a single hard drive Ubuntu should refer to this as /dev/sda and you can use the command in post #10 to erase bootloader code from the MBR. Provided you have Windows partition marked as active it should start when you reboot the system. Be careful to type command exactly as incorrect values will wipe other information from the hard drive !

  5. #15
    Linux Guru
    Join Date
    Jan 2009
    Location
    Dover, NH
    Posts
    1,633
    The MBR should be clear now. If it's still booting to grub, then something else is going on, and probably not good.

    I agree with Jonathan183. We should see the fdisk -l output in case something is still there that shouldn't. Perhaps it could be corrected first with the gParted CD, make sure the FAT partition is the only one there and it takes up the whole disk. If it still tries to boot with Grub, boot again with the Win9x Disk, and see if you can see the C: drive (dir C:). If so, it may be as easy as running sys C: . Otherwise, we may be looking more at a recovery operation.

  6. #16
    Linux User
    Join Date
    Dec 2007
    Location
    Idaho USA
    Posts
    340
    Your problem is you ran Win2000's "fixboot", puting the wrong boot code into the volume boot record. I do not know the command for ME, it might be the same as 98 "sys C". There is not a thing wrong with your current MBR boot code.

  7. #17
    Linux Newbie
    Join Date
    Mar 2008
    Location
    England, Manchester.
    Posts
    114
    Yes that's exactly it.

    I tried SYS C but it said bad command or file name

    The C drive is still there though

  8. #18
    Linux Guru
    Join Date
    Jan 2009
    Location
    Dover, NH
    Posts
    1,633
    Must not be on your boot disk. I hope this disk is the same version as on your hard drive if this is going to work. The SYS C: has to be run from A:\ to work right (it transfers the boot code from the current drive to the one specified)...

    PATH A:\;C:\Windows;C:\windows\command;

    SYS C:


    Good Luck!

  9. #19
    Linux Newbie
    Join Date
    Mar 2008
    Location
    England, Manchester.
    Posts
    114
    Quote Originally Posted by D-cat View Post
    Must not be on your boot disk. I hope this disk is the same version as on your hard drive if this is going to work. The SYS C: has to be run from A:\ to work right (it transfers the boot code from the current drive to the one specified)...

    PATH A:\;C:\Windows;C:\windows\command;

    SYS C:


    Good Luck!
    D-cat you are a genius!

    My Windows just booted up perfectly right now as I am typing this.

    I don't know how that worked but I have saved it for future reference.

    Thankyou, you really have helped me.

Page 2 of 2 FirstFirst 1 2

Posting Permissions

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