Sorry to post yet another dual boot question, but I'm a newbie and am really stuck here. I've searched the threads and my question has been addressed, but it doesn't look like it was solved (or maybe it was, but I'm too dense to figure it out). Anyway, the problem is that when I select a separate OS to boot using LILO, the system hangs. Here's the specifics:
I have a system (Athlon 850, 256 megs RAM) that had a Maxtor HD with Win98 installed on the secondary IDE master. I wanted to dual boot and had a spare HD lying around, so instead of dealing with partitioning my existing drive, I just added this new HD (Western Digital) and set about installing Red Hat 7.0 on it (had that lying around too). To be safe, I disconnected the Maxtor HD during installation, set the new HD to master and started installing.
Everything went fine and I was able to get Red Hat up and running. So, I reconnected the Maxtor HD (with Win98) and set it to be the slave on the secondary IDE. Then I edited lilo.conf to this:
- lilo.conf -------
- end -------
I then executed LILO as root and it gave me this:
It didn't give me any errors, so I figured it's fine. I then added this line to fstab:
- fstab ------
/dev/hdd1 /win vfat umask=002,noexec 0 0
- end ------
After a "mkdir win" I was able to access the contents of the Windows drive from within Linux, and was feeling pretty good about myself
Then, I tried rebooting and starting up win98 from LILO. LILO loads up and gives me a choice between linux and win98. If I choose linux, Red Hat boots without a problem. But if I choose win98, the system reads: "Loading win98" and then just hangs. However, if I open up my box and reset the Maxtor HD to master, Windows boots just fine.
One other thing that's strange and very possibly related is that when Red Hat boots, it gets to the "detecting new hardware" phase and something called Kudzu detects the Maxtor drive as a new piece of hardware. I don't know why this is happening, because the Maxtor mounts properly. Why would it detect it as new if it's mounted? Also, this Kudzu thing gives me the choice of Initializing the Maxtor drive, but I'm hesitant to do so because I don't know what "initializing" it entails. It just seems strange to me that I can access the contents of the Windows drive from within Linux, but during the boot, Linux says the Windows drive is new.
I'm at a loss as to what to do next... again, I'm a total newbie, so if anyone has any ideas, please let me know. I'm anxious to make the switch off Windows, but having to open my box and reset jumper settings on my HD is sort of a pain.