Re: [SLE] Dual Boot - Win98/SuSE8
Well I have dual boot of a sort, but I have to use a DOS floppy diskette with FDISDK to cahange the active partition. FDISK display partition information: Partition Status Type Vol Label Mbytes System Usage C: 1 A Pri-Dos Main 3757 FAT32 38% 2 Non-Dos 16 % 3 Non-Dos 5020 51% 4 Ext-Dos 973 10% If, as above, partition 1 is active then the system boots straight into Win98 If I set partition 2 active then re-booting brings up the LILO menu, if I select Linux then SuSE8 runs ok. If however I select Windows the system tries to boot from the LAN, then Floppy. I suspect partition 2 needs to be active but LILO does not know where to find Windows, so where and how can I edit LILO? Regards Keith Jacobs Researching the Baggarley Family History. Member of the Society of One Name Studies, East Surrey & London & Nth Middx Family History Societies.
On Thursday 23 May 2002 17.44, Keith Jacobs wrote:
Well I have dual boot of a sort, but I have to use a DOS floppy diskette with FDISDK to cahange the active partition. FDISK display partition information:
Partition Status Type Vol Label Mbytes System Usage C: 1 A Pri-Dos Main 3757 FAT32 38% 2 Non-Dos 16 % 3 Non-Dos 5020 51% 4 Ext-Dos 973 10%
May I suggest you use linux fdisk instead. It will give you a lot more useful information.
If, as above, partition 1 is active then the system boots straight into Win98 If I set partition 2 active then re-booting brings up the LILO menu, if I select Linux then SuSE8 runs ok. If however I select Windows the system tries to boot from the LAN, then Floppy.
I suspect partition 2 needs to be active but LILO does not know where to find Windows, so where and how can I edit LILO?
Edit /etc/lilo.conf. In the above scenario I'd put boot=/dev/hda and leave partition one as "active". That should probably solve your problems regards Anders -- I swear I do declare - how did you get that there?
Hi Anders May I suggest you use linux fdisk instead. It will give you a lot more useful information. I would but need FDISK on a floppy at present. Edit /etc/lilo.conf. In the above scenario I'd put boot=/dev/hda and leave partition one as "active". That should probably solve your problems Heres what I have in lilo.conf boot = /dev/hda change-rules reset read-only menue-scheme = Wg:kw:Wg:Wg prompt timeout = 80 message = /boot/message image = /boot/vmlinuz label = linux initrd = /boot/initrd root = /dev/hda4 image = /boot/vmlinuz.suse label = failsafe append = "ide=nodma apm=off acpi=off" initrd = /boot/initrd.suse optional root = /dev/hda4 other = /dev/hdb1 lable = windows image = /boot/memtest86 label = memtest86 I thought I had found the problem as hdb1 is my second drive on which I keep my data, so I edited /dev/hdb1 to /dev/hda1 but still can't get the dual boot to work. Regards keith
participants (2)
-
Anders Johansson
-
Keith Jacobs