Heya gang, I just installed W98 on a second hdd for a few games *only*. The way I did it, was open case, unhook Linux hdd and made second hdd hdd0, installed M$, rehooked everything back to normal. Then I tried to use YaST to setup my LILO so I had the choice of windows also to choose from in the boot screen. Unfortunately, it's not writing all the things it apparently needs to boot the windows hdd. All fstab has is /dev/hdb1 and 'other'. Anyone mind showing me their fstab if they're dual-booting or giving me a hint how to have YaST set it up? Thanks, John
John B wrote:
Heya gang,
I just installed W98 on a second hdd for a few games *only*. The way I did it, was open case, unhook Linux hdd and made second hdd hdd0, installed M$, rehooked everything back to normal. Then I tried to use YaST to setup my LILO so I had the choice of windows also to choose from in the boot screen. Unfortunately, it's not writing all the things it apparently needs to boot the windows hdd. All fstab has is /dev/hdb1 and 'other'. Anyone mind showing me their fstab if they're dual-booting or giving me a hint how to have YaST set it up?
The fstab has absolutely nothing to do wiht LILO or any other boot manager. By the time you get to the fstab, which is used by the "mount" program, the boot manager has long since exited, stage right. I do believe that Win98, being just M$-DOS 6 with a GUI, does not know about modern things such as booting off something other than the master on the primary IDE -- hda aka. hd0 To make things worse, this being DOS, there can only be one primary partition on the boot device. (Someone please correct me if I am wrong, but I believe this limitation does no longer exist in Win2K or XP, but both still must boot from the primary/master.) Now we have a bit of a problem, because I believe LILO also cannot boot off anything except the master on the primary IDE -- but at least we can have more than one primary partition, 4 of them in fact (or 3 plus an extended partition, in case you need more). You can put a primary partition on the first drive and hide it whenever you boot DOS (also you have to mark the DOS partition "active"), or you can leave things as you have them and swap the hard drives in the BIOS (using the boot manager, of course). LILO can do all this for you, but GRUB is much easier to configure and maintain. LILO at times seems to me to be cryptic and unintuitive; GRUB is straightforward and intuitive. It's up to you, but I do suggest you install and use GRUB instead of LILO. Either way, your fstab is irrelevant for now, and probably will need modification only if you want to access the Win98 stuff from Linux.
Form your e-mail, it seems that you installed Win98 after installing SuSe.
From my experience, you need to exactly the contrary, i.e installed first Win98 then SuSe which will make the dual boot configuration for you.It will never work the other way, even with WinXP
Darryl Gregorash
John B wrote:
Heya gang,
I just installed W98 on a second hdd for a few games *only*. The way I did it, was open case, unhook Linux hdd and made second hdd hdd0, installed M$, rehooked everything back to normal. Then I tried to use YaST to setup my LILO so I had the choice of windows also to choose from in the boot screen. Unfortunately, it's not writing all the things it apparently needs to boot the windows hdd. All fstab has is /dev/hdb1 and 'other'. Anyone mind showing me their fstab if they're dual-booting or giving me a hint how to have YaST set it up?
The fstab has absolutely nothing to do wiht LILO or any other boot manager. By the time you get to the fstab, which is used by the "mount" program, the boot manager has long since exited, stage right.
I do believe that Win98, being just M$-DOS 6 with a GUI, does not know about modern things such as booting off something other than the master on the primary IDE -- hda aka. hd0 To make things worse, this being DOS,
there can only be one primary partition on the boot device. (Someone please correct me if I am wrong, but I believe this limitation does no longer exist in Win2K or XP, but both still must boot from the primary/master.)
Now we have a bit of a problem, because I believe LILO also cannot boot off anything except the master on the primary IDE -- but at least we can
have more than one primary partition, 4 of them in fact (or 3 plus an extended partition, in case you need more). You can put a primary partition on the first drive and hide it whenever you boot DOS (also you
have to mark the DOS partition "active"), or you can leave things as you
have them and swap the hard drives in the BIOS (using the boot manager, of course).
LILO can do all this for you, but GRUB is much easier to configure and maintain. LILO at times seems to me to be cryptic and unintuitive; GRUB is straightforward and intuitive. It's up to you, but I do suggest you install and use GRUB instead of LILO. Either way, your fstab is irrelevant for now, and probably will need modification only if you want
to access the Win98 stuff from Linux.
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
g.lams@itcilo.org wrote:
Form your e-mail, it seems that you installed Win98 after installing SuSe.
From my experience, you need to exactly the contrary, i.e installed first Win98 then SuSe which will make the dual boot configuration for you.It will never work the other way, even with WinXP
Darryl Gregorash
wrote on 10/02/2005 08.50.29: <snip>
First off, it wasn't me who installed Win98; you should have replied to the original poster. Second, it will so work, in any configuration; it's merely a bit circuitous to install Linux first. In this instance, however, it is almost trivial, as the two systems were both installed to what was, at the time, the primary master drive. Thus, reinstalling the Linux drive as the master will allow us to boot into Linux, where it is a relatively minor task to edit lilo.conf and configure it to allow him to boot Win98 from the slave -- and yes, that can be done.
On Thursday 10 February 2005 7:50 am, Darryl Gregorash wrote:
John B wrote:
Heya gang,
I just installed W98 on a second hdd for a few games *only*. The way I did it, was open case, unhook Linux hdd and made second hdd hdd0, installed M$, rehooked everything back to normal.
<snip>
I do believe that Win98, being just M$-DOS 6 with a GUI, does not know about modern things such as booting off something other than the master on the primary IDE -- hda aka. hd0 To make things worse, this being DOS, there can only be one primary partition on the boot device. (Someone please correct me if I am wrong, but I believe this limitation does no longer exist in Win2K or XP, but both still must boot from the primary/master.)
Correction coming up. Your version is the simple version of the story. The original PC design provides for up to 4 primary partitions on a hard drive, as you state later. In the DOS world, only 1 primary partition can be active on a single hard drive. A FAT32 drive is type 0x0c, but when hidden it is type 0x1c. Similarly, NTFS is 0x07 and 0x17. To boot a DOS operating system [msdos 1.0 through MSXP] requires that the active primary partition on the first hard drive is booted. BIOSs which boot from other drives do this by presenting the other selected drive as the first drive. To boot different DOS os's on different primary partitions requires that the partition types are changed, to hide all but the required partition. fdisk will do this for DOS, but you need to know what you will boot next, before you shut down [or boot up, do fdisk and reboot]. GRUB and LILO manage the changing of partition types during boot. Booting MS98 from the second hard drive is 'unsupported' but possible with some limitations. The best is to make space for a tiny primary partition, with a boot sector, the hidden files and config.sys and edit whatever sets the windows directory [msdos.sys? so long ago, I have forgotten] to point to the windows directory of the installation on the second hard drive. Alternatively, I believe it may be possible to point GRUB to the boot sector on the second hard drive and boot that, even if the pc bios will not boot it, or if the bios is still set to boot from the first drive. Note that if the installation was done with this drive as C:, the registry may be confused, unless the installation partition is the first FAT partition on first and second drives, in which case it may be accepted as C:, even though it is on the second drive.
Now we have a bit of a problem, because I believe LILO also cannot boot off anything except the master on the primary IDE -- but at least we can have more than one primary partition, 4 of them in fact (or 3 plus an extended partition, in case you need more). You can put a primary partition on the first drive and hide it whenever you boot DOS (also you have to mark the DOS partition "active"), or you can leave things as you have them and swap the hard drives in the BIOS (using the boot manager, of course).
True, LILO and GRUB are subject to exactly the same rules as DOS. As above, LILO and GRUB can be configured to manage hiding and unhiding.
LILO can do all this for you, but GRUB is much easier to configure and maintain. LILO at times seems to me to be cryptic and unintuitive; GRUB is straightforward and intuitive. It's up to you, but I do suggest you install and use GRUB instead of LILO. Either way, your fstab is irrelevant for now, and probably will need modification only if you want to access the Win98 stuff from Linux.
LILO is prone to being broken if any of the files it uses are rewritten, because it only knows the files by hardware address on the disk [every time you change one of the key files, you must run a LILO config utility]. GRUB knows files by name, and can tolerate them being rewritten. Vince
Vince Littler wrote:
On Thursday 10 February 2005 7:50 am, Darryl Gregorash wrote:
I do believe that Win98, being just M$-DOS 6 with a GUI, does not know about modern things such as booting off something other than the master on the primary IDE -- hda aka. hd0 To make things worse, this being DOS, there can only be one primary partition on the boot device. (Someone please correct me if I am wrong, but I believe this limitation does no longer exist in Win2K or XP, but both still must boot from the primary/master.)
Correction coming up. Your version is the simple version of the story. The original PC design provides for up to 4 primary partitions on a hard drive,
Thanks for clarifying this. The point I was stumbling around, which you state in your third paragraph (and which is quite clearly explained, as I have seen, in the GRUB info file), is that all other primary partitions must also be marked as "hidden" --if-- they have some other DOS or Windows version installed on them. What I am not clear on then can be stated this way: if you have, let us say, XP and DOS 5 installed on a system, and you wish to boot XP, is it necessary to hide the DOS5 boot partition? The GRUB documentation suggests the answer is yes, but Linux documentation is often notoriously out-of-date.
Booting MS98 from the second hard drive is 'unsupported' but possible with some limitations. The best is to make space for a tiny primary partition....
Alternatively, I believe it may be possible to point GRUB to the boot sector on the second hard drive and boot that, even if the pc bios will not boot it, or if the bios is still set to boot from the first drive. Note that if the installation was done with this drive as C:, the registry may be confused, unless the installation partition is the first FAT partition on first and second drives, in which case it may be accepted as C:, even though it is on the second drive.
In fact, the solution in both GRUB and LILO is to remap the drives, exchanging the two drives in the BIOS tables. This is done with the GRUB "map" or LILO "map--drive" statements.
Now we have a bit of a problem, because I believe LILO also cannot boot off anything except the master on the primary IDE....
True, LILO and GRUB are subject to exactly the same rules as DOS. As above, LILO and GRUB can be configured to manage hiding and unhiding.
Here I am asking whether or not LILO can boot a Linux installation which is fully installed to, say, the primary slave drive. I said that I think the answer to this is "no", whereas GRUB certainly can boot such a Linux installation. OTOH, paying a bit more attention to the lilo.conf manpage and I dig up this: # global options: boot=/dev/hda <snip> image=/tamu/vmlinuz label=tamu root=/dev/hdb2 vga=ask # # other operating systems: other=/dev/hda3 label=dos other=/dev/hdb5 label=os2 loader=/boot/os2_d.b table=E: so it seems that the answer is "partly no". This is from LILO ver 22.3, and may or may not represent a change from earlier versions.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 John B wrote: <snip> | Anyone mind showing me their fstab if they're dual-booting or giving me a | hint how to have YaST set it up? Hi John, Ok, here's my fstab: /dev/hdc2 / reiserfs acl,user_xattr 1 1 /dev/hdc3 /home ext3 defaults 1 2 /dev/hdc4 /opt ext3 acl,user_xattr 1 2 (watch for wrapping!) /dev/hda1 /windows/C vfat iocharset=iso8859-1,users,gid=users,umask=0002 0 0 /dev/hda5 /windows/D vfat iocharset=iso8859-1,users,gid=users,umask=0002 0 0 /dev/hda6 /windows/E vfat iocharset=iso8859-1,users,gid=users,umask=0002 0 0 /dev/hdc1 swap swap pri=42 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 proc /proc proc defaults 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 sysfs /sys sysfs noauto 0 0 (watch for wrapping!) /dev/fd0 /media/floppy subfs fs=floppyfss,procuid,nodev,nosuid,sync 0 0 I think the procedure you'd probably want to use is this: Use YaST's partition editor [YaST->System->Partitioner] to set the unmounted drive up (mount point @ /windows/C, and so on.) Let it write the appropriate entries into fstab for you, using mine as a reference in case the editor picks the wrong character set (which it is prone to do.) YaST's Boot Loader Configuration module inspects fstab for changes each time you run it. If you just choose "reset" it'll recommend a suitable dual-boot configuration in the same way YaST did when you first installed SuSE. HTH & regards, - - Carl - -- ____________________________________________________________________ C. E. Hartung Business Development & Support Services http://www.cehartung.com/ carlh@cehartung.com Dover Foxcroft, Maine, USA Public Key #0x68396713 Reg. Linux User #350527 http://counter.li.org/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCCxfVusxgymg5ZxMRAs+1AKCD1Mdam+chxODROXYugdLpOZ+ZvgCdH33N 22pICruEMQxX4J91kw/yCoY= =JJH5 -----END PGP SIGNATURE-----
Carl E. Hartung wrote:
John B wrote: <snip> | Anyone mind showing me their fstab if they're dual-booting or giving me a | hint how to have YaST set it up?
Hi John,
Ok, here's my fstab: <snip>
Carl, For dual boot, we are interested only in the contents of lilo.conf (or preferably the grub menu.lst :-) ), not of fstab.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Darryl Gregorash wrote: | | Carl, | | For dual boot, we are interested only in the contents of lilo.conf (or | preferably the grub menu.lst :-) ), not of fstab. You get what you ask for at this shop. The OP's request was clear and concise: He wanted to see an fstab entry for a mounted Windows drive so he could mount it and deal with the boot loader. Did I miss something here? /*rant ON*/ And why the use of this ridiculous "we" crap, Darryl? Do you believe that patronizing complete strangers enhances your reputation? Or do you subconsciously rely on this manipulative technique to bolster a sense of superiority when, clearly, none is warranted? My advice? Don't waste the keystrokes next time. You added nothing to the discussion here and diminished your reputation in the process. /*rant OFF*/ Have a nice day! :-) - - Carl - -- ____________________________________________________________________ C. E. Hartung Business Development & Support Services http://www.cehartung.com/ carlh@cehartung.com Dover Foxcroft, Maine, USA Public Key #0x68396713 Reg. Linux User #350527 http://counter.li.org/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCC6rNusxgymg5ZxMRAj9RAJ9lqNS9gRJ1oDp7oDs1w8JUt73yRgCfar3G CRZl1eSbeNbtktC6vNiPMgM= =Tn4b -----END PGP SIGNATURE-----
Well, I stand corrected. *Almost* no one is interested in fstab when the question is how to configure a system to perform a dual-boot. Operative word here is "boot" which implies boot loader, not some OS specific file that only enters the picture an eternity later. Wasted keystrokes? What did your fstab contribute to the question of how he is to configure his boot loader? Nada, rien, empty set. Patronizing? I am never patronizing, hence the smiley -- I simply thought you had missed something significant.Next time I'll not make the mistake of "speaking" to you. Carl E. Hartung wrote:
Darryl Gregorash wrote: | | Carl, | | For dual boot, we are interested only in the contents of lilo.conf (or | preferably the grub menu.lst :-) ), not of fstab.
You get what you ask for at this shop.
The OP's request was clear and concise: He wanted to see an fstab entry for a mounted Windows drive so he could mount it and deal with the boot loader. Did I miss something here?
/*rant ON*/
And why the use of this ridiculous "we" crap, Darryl? Do you believe that patronizing complete strangers enhances your reputation? Or do you subconsciously rely on this manipulative technique to bolster a sense of superiority when, clearly, none is warranted?
My advice? Don't waste the keystrokes next time. You added nothing to the discussion here and diminished your reputation in the process.
/*rant OFF*/
Have a nice day! :-)
You too.
-----Original Message----- From: John B [mailto:yonaton@tds.net] Sent: Thursday, 10 February 2005 6:07 PM To: suse-linux-e@suse.com Subject: [SLE] Dual-booting...or trying, heh Heya gang, I just installed W98 on a second hdd for a few games *only*. The way I did it, was open case, unhook Linux hdd and made second hdd hdd0, installed M$, rehooked everything back to normal. Then I tried to use YaST to setup my LILO so I had the choice of windows also to choose from in the boot screen. Unfortunately, it's not writing all the things it apparently needs to boot the windows hdd. All fstab has is /dev/hdb1 and 'other'. Anyone mind showing me their fstab if they're dual-booting or giving me a hint how to have YaST set it up? Thanks, John -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com Hi John, This may help. I installed ME on a second hd without any fuss. I didn't detach the hd and It worked without a prob. I did use GRUB though, not lilo. I did not need to configure anything and ME was on the second hd and installed after suse. I was plesently surprosed by this. Chris
On Thursday 10 February 2005 03:06 pm, Chris wrote:
-----Original Message----- From: John B [mailto:yonaton@tds.net] Sent: Thursday, 10 February 2005 6:07 PM To: suse-linux-e@suse.com Subject: [SLE] Dual-booting...or trying, heh
Heya gang,
I just installed W98 on a second hdd for a few games *only*. The way I did it, was open case, unhook Linux hdd and made second hdd hdd0, installed M$, rehooked everything back to normal. Then I tried to use YaST to setup my LILO so I had the choice of windows also to choose from in the boot screen. Unfortunately, it's not writing all the things it apparently needs to boot the windows hdd. All fstab has is /dev/hdb1 and 'other'. Anyone mind showing me their fstab if they're dual-booting or giving me a hint how to have YaST set it up?
Thanks,
John
FSTAB has nothing to do with dual booting., FSTAB tells linux how to mount its partitions once *linux* is in the process of booting.
Bruce Marshall a écrit :
On Thursday 10 February 2005 03:06 pm, Chris wrote:
-----Original Message----- From: John B [mailto:yonaton@tds.net] Sent: Thursday, 10 February 2005 6:07 PM To: suse-linux-e@suse.com Subject: [SLE] Dual-booting...or trying, heh
Heya gang,
I just installed W98 on a second hdd for a few games *only*. The way I did it, was open case, unhook Linux hdd and made second hdd hdd0, installed M$, rehooked everything back to normal. Then I tried to use YaST to setup my LILO so I had the choice of windows also to choose from in the boot screen. Unfortunately, it's not writing all the things it apparently needs to boot the windows hdd. All fstab has is /dev/hdb1 and 'other'. Anyone mind showing me their fstab if they're dual-booting or giving me a hint how to have YaST set it up?
Thanks,
John
FSTAB has nothing to do with dual booting., FSTAB tells linux how to mount its partitions once *linux* is in the process of booting.
Hi all, Let me tell what I've understood since the question was not clear. I think that John has Linux installed on drive hda (partition hda1), and Windows 98 on drive hdb. He wants that his boot loader has two entries, one for Linux on hda and one for Windows on drive hdb. If it is your problem John, you have to know that the bios is unable to boot a second hard drive ! Nevertheless, you can do that with GRUB, I boot even from the third hard drive ! You need GRUB and not LILO, edit the file : /boot/grub/menu.lst so that it looks like below for the Windows 98 entry : # Modified by YaST2. Last modification on Fri Nov 26 09:41:53 2004 color white/blue black/light-gray default 0 timeout 8 gfxmenu (hd0,5)/message title Linux SUSE 9.2 kernel (hd0,0)/boot/vmlinuz root=/dev/hda1 vga=0x314 selinux=0 splash=silent resume=/dev/hda1 desktop elevator=as showopts initrd (hd0,0)/boot/initrd title Windows 98 map (hd0) (hd1) map (hd1) (hd0) root (hd1,0) chainloader +1 ........ The two map instructions are swapping hd0 and hd1 so that the Bios thinks that it is booting from the first hard disk !! The Linux entry is an example which supposes that you have only one partition, modify it in order to get your own configuration. Did I understand your problem, and is this a solution to it ? As far as I know, there is no solution with Lilo. Good luck. Michel.
Catimimi wrote:
Did I understand your problem, and is this a solution to it ?
I think the answers are going to be "yes" and "yes"
As far as I know, there is no solution with Lilo.
I thought so too, until I was preparing my first reply to the OP, when I found the "map-drive" statement in the lilo.conf manpages. It uses hexadecimal notation for the drives, hda corresponds to 0x80. The manpage description seems to imply that the statement is valid only in an "other" section. But GRUB still is much easier to install, and easier to reconfigure when you make changes -- even though sometimes you actually must edit the drive.map file too, which I think will be necessary in this case. Already OP's device.map contains the line "(hd0) /dev/hda", and he just needs to add a new line: "(hd1) /dev/hdb" (this will corresponde exactly to your example menu.lst). Also, some people might wonder why there is no "makeactive" line in your example file; of course, the reason for this is that partition was marked active when win98 was installed, and this has not changed.
participants (8)
-
Bruce Marshall
-
Carl E. Hartung
-
Catimimi
-
Chris
-
Darryl Gregorash
-
g.lams@itcilo.org
-
John B
-
Vince Littler