Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Lilo not able to boot Windows
Message
Information générale
Forum:
Linux
Catégorie:
Problèmes base de données, installation et Admin
Divers
Thread ID:
00622631
Message ID:
00623254
Vues:
19
>>I have two machines set up with hda/ running SuSE 7.3 Pro and hdc/ running Win98. Lilo cannot boot the Windows drive. Previously I had this working with older versions of SuSE (started with 6.1), and it even worked after updating the machines to SuSE 7.3, but I did a clean install of hda/. Now lilo says it is booting Win98, but nothing happens. The boot sector on hdc/ is fine. If I recable so it is C:\ on the primary ide, Win98 boots. Is this a problem with the newer version of lilo, or have I missed something. When I run lilo from the shell I get "bios drive 0xF86 may not be available". I haven't had time to research on line. I thought maybe Mr. Kreps might be aware of the issue.


>Oh ya! Just this last weekend...
http://www.linuxnewbie.org/nhf/intel/osbooting/lilo_dual.html explains pretty much what I did... Also, consult section 5.4 of the SuSE manual.

>But, try http://www.xosl.org/ first!

>The problem appears to be that the initrd file doesn't match the geometry of the HD. Also, be sure to check that the "lba32" line is in lilo.conf, and play with the linear checkbox to see if either on or off will help.

>lba32 # Use BIOS to ignore 1024 cylinder limit
>......
>### LILO Linux section (default)
>image = /boot/vmlinuz # Default
>label = linux
>root = /dev/hda7 # Root partition for the kernel
>initrd = /boot/initrd

>.......

>### LILO other system section (DOS/Windows)
>initrd = /boot/initrd.suse optional
>other = /dev/hda1 # Windows partition label = windows

My Win98 is on /dev/hdc. Will your suggestion still work? And why did it work in the past before I changed the version of lilo by performing a clean install of SuSE7.3?
--Matthew
Opportunity is missed by most people beacuse it is dressed in overalls, and looks like work --- Thomas Edison
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform