SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I installed Lilo thinking it would see one of my NTFS partitions. It didn't, so when I used Partition Magic to boot into NTFS, Lilo came up and the only option I could do was to boot into DOS (Fat 32), so it made my hard drive freeze up. I used Partition Magic rescue disks to get back to my FAT32 partition and load Slackware. I don't know how to remove LiLo from the MBR now. Any help would.....help.
Originally posted by Nappa I installed Lilo thinking it would see one of my NTFS partitions. It didn't, so when I used Partition Magic to boot into NTFS, Lilo came up and the only option I could do was to boot into DOS (Fat 32), so it made my hard drive freeze up. I used Partition Magic rescue disks to get back to my FAT32 partition and load Slackware. I don't know how to remove LiLo from the MBR now. Any help would.....help.
Kinda hard to understand what you got going on there. If you have removed your Linux distro, and just want to run Windoze, simply use your boot disk to get to a DOS prompt and type ->
which will rewrite your master boot record, and that should fix you right up, removing LILO from your MBR and giving you the go with your Windoze OS.
On the other hand, if you are trying to dual boot Windoze and Slackware (I think this is what you're saying) and LILO is messed up, please post the output of ->
$ fdisk -l (lower case L)
$ df -h
$ pico /etc/lilo.conf
and perhaps we can get you going.
Please put your Linux distribution into your user cp (control panel) and let us know what OSes you're trying to run on this comp.
I feel stupid now, thank you for your help...all I had to do was to fdisk mbr and make sure that the fat32 was active. I'm trying to learn my way out of Windows so that I'm totally Linux dependent, but it's just going to take some time. I understand that the fdisk command in Linux works somewhat the same as the DOS fdisk righ??
The Linux version of fdisk is for the same purpose as the DOS one, and they are both command line programs, but the similarities don't go much further. For a more user friendly and less buggy version of fdisk under Linux try using cfdisk (a much better program in almost every way). One thing you will notice, however, is that there is no mbr switch for Linux fdisk (or cfdisk).
I just want to get confirmation on this topic. I installed Slackware on a scavenged 4gig drive in my WindowsXP computer. The system is dual-booting WinXP and Slackware. The Slackware drive seems VERY slow and might have problems associated with aging (it's about eight years old but was owned by a little old lady who only drove it on Sundays). I want to remove the Slackware drive and remove the dual-boot option. What I've been able to find in my search is that fdisk /mbr will remove the dual-boot from WinXP. Is this correct? It won't corrupt my drive? Has anyone encountered problems doing this?
Correct. The command: fdisk /mbr will overwrite your MBR and return it to a Windows-friendly/Windows-only state. Note that it will do nothing to the data on the Slack drive -- its only effect is to "reset" the MBR. After you perform this command and reboot, it should immediately boot into XP. As always, you should consider backing up any important data first, just to play it safe.
That being said, I've run the fdisk /mbr command a number of times when I was initially setting up my PC, with no ill effects at all. -- J.W.
This removes the bootloader from the partition table by writing zeros to the first 446 bytes on your first hard disk. If you have a SCSI disk, then you need to use the device name for a SCSI disk..eg /dev/sda.