Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Using RedHat 7.1 Seawolf on Compaq Presario 7000. Been using lilo for a couple of months with no problems using Linux or Windows ME. All of a sudden Linux works but Windows won't boot. None of the emergency cd's or diskette's provided by Compaq will boot. But Linux works wonderfully, as it always has. I don't use windows the rest of the family does and they say they haven't done anything other than email, aim, etc. I have tried changing the boot sequence in the bios but that didn't make any difference(a suggested remedy) I frankly don't have a bloody clue how this could be a linux problem but being a rank newbie I can only think to remove lilo to see if that helps. Why I should remove something that does apparently work to fix something that doesn't i.e. windows is, well, not very logical but I simply can not get windows to boot. Any help would be appreciated.
The 'default' and 'other' parts are important. What do they say? Is the 'other' section even there?
What about the time out? Is LILO actually prompting you or is it jumping straight to Linux? The timeout is in deciseconds, so 50 equals 5 seconds. Do you have enough time to type in the name of your secondary OS?
What else, what else .. hmm ..
Okay, while you are writing all that down, lets try mounting your Windows partition through Linux, to make sure it is still there. You know MS .. they're sneaky.
bash# mkdir /mnt/windows
bash# mount -t vfat /dev/hda1 /mnt/windows
Then 'cd' to the /mnt/windows and see what is there ..
WOW!!
I am truly impressed by the responsiveness of this open source world. I can't speak for results but if effort and community mean anything this is going to be or already is the 'new' age of computing. OK the following is my lilo.conf
I don't get any error message when i choose dos . The disk drive 'chugs' a few times then the machine locks up and has to be restarted with the on/off switch. ctrl-alt-del does nothing. On your previous message you said to mount hda1 but my dos is hde1 should I still follow the original instructions?
I tried the following lilo with no apparent difference. One question in the original lilo there are very small, what appear to be, periods on the extreme left of some of the lines. When I made the changes you directed a period does not get added. I was wondering where the periods came from and if they have any significance. I have included the altered lilo so you van verify I made the correct changes.
Thanks for your efforts.
boot="/dev/hde"
map=/boot/map
install=/boot/boot.b
prompt
timeout="50"
message=/boot/message
lba32
default=linux
Is the fat32 partition that windows is installed on set to active? Use Partition Magic if you can get it, to have a look. If not, use the DOS command fdisk.
Also you should try to check the drive for bad blocks on the HD. Your windows startup files could be on a corrupted / bad portion of the hard drive. Presario's are known to be POS's and I've worked on more than my share. I don't know what model numbers they were, but the one's that had the Quantum Bigfoot HD's seemed like I replaced gobs of those.
I have gotten my hands on a copy of partition magic, I hope I can check the HD over with that. The inventory says that the HD is a UltraDMA ATA66 40 GB.
boy this gets stranger and stranger. Partition Magic won't boot. It asks for the second diskette, throws the partition magic splash screen then goes to an hourglass and that's all she wrote. I have used these diskettes before on this machine so I doubt that the diskettes are the problem.
Here's something you can try to get windows working. Make sure that you have a disk that you can use to boot into linux. If you made one during the installation of RH 7.1, that will be fine. Boot into linux as you normally do, log in as root and run the command /sbin/lilo -u. This should restore the mbr back to its original state. Next, reboot the computer and see if it boots into windows. There are no guarantees that this will work. Good luck.
I believe that windows expects to be on the first partition of the first disk. Do you remember which drive it was on? Try booting with your Windows Startup Disk. Then run fdisk to see what the partitions look like and if the correct disk is active. I'm wondering if the partition information got whacked somehow.
Anyway, the 'hde' looks funny, because, unless you have an ide card added to your computer, you should just have 4 ide devices and 'hde' would be the fifth device.
One thing worth trying is:
A) Make sure you have a Linux Boot Disk
B) Boot up using your Windows Startup Disk
C) run the FDISK /MBR command to rewrite the
Master Boot Record
D) If windows boots up OK, use the boot disk to boot into
Linux
E) Reinstall the LILO loader.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.