Re: Solutions for booting dual OS (separate HDs)
On Thu, 20 Jun 2002 01:06, David P James wrote: > [EMAIL PROTECTED] wrote: > > I am still booting from floppy and it takes ages so I look for help: > > > > I have hda with win2k on it. Boots if no cd-rom or floppies in drives. > > > > And then there is the hdb with debian. Boots from floppy (loads the > > kernel etcetc from floppy). > > > > So yes these are separate HD's. > > > > Now from previous experience I *know* that win2k is quite 'sensitive' > > when it comes to booting. I tried boot manager called GAG earlier, but > > managed on multiple attempts to lose the Master Boot Record to Win2k and > > had to reinstall from backup images... So no luck. > > > > AFAIK lilo will also overwrite win2k boot manager in a way that will make > > poor little win sulk and not ever be found again. So answer to any of the > > three below will solve my problems, II. or III. being more robust I > > suppose. > > > > I. > > How do I make an boot disk for the hdb/debian so that it only boots from > > the floppy, but loads kernel etc from HD? > > > > II. > > Is there such a thing as relatively foolproof and simple way (aside from > > BIOS ;) ) to install an boot manager that does not > > touch/corrupt/overwrite the Win2k? Any links and experiences welcome. Quote, "MCSE Windows 2000 Professional for Dummies." Page 75. "Problems have been reported with the partitioning code that runs as part of the Windows 2000 setup program. Therefore, only use the Windows 2000 Setup program to partition the volume onto which Windows 2000 is to be installed. Use Windows 2000 Disk Management console (I've still found this dodgy) to create or format other partitions, or use a third party partitioning tool such as Partition Magic. ...On a dual boot machine with Windows 9x, you may configure a Windows 2000 partition as NTFS, but the primary (boot) partition must be either Fat or( inthe case of Windows 95osr2+ and Windows 98) FAT 32." Unquote. If it's this much hassle with fat imagine the problems with ext2 or 3 ?? I've dual booted using lilo and Win 2000 and it was o.k. for a while then after a few days seemingly randomly the boot menu dissapears and it loads the old pre dual boot O/S. I tried it with Win 98 and Win XP Professioal lately Win 98 exixting on one disk and Win XP on another. It dual boots fine for a random number of days then no go. It wipes all the boot O/S selection menu and defaults to Win98. I'm about to try loading woody Debain 3.0 to dual boot with Win2K and will use lilo and see what happens to Win2k. I thought I did this a while back and had no problems but that may have been with XP Pro I'm not sure. Good Luck:-) >> > > > III. > > Now as I write this I started to wonder if it would be possible to > > add the lead to linux boot record into windows BOOT.INI ? For win2k > > boot.ini says: > > multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 > > Professional" /fastdetect Anyone ever try it 'the windows way'? > > > > Well any help much appreciated, > > > > Jani > > I'm not entirely sure if this is what you're looking for, > but you might want to take a look at this grub multi-boot > howto (the example system has all the OSs on the same hd, > though that shouldn't really matter as you have win on the > first hd). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Solutions for booting dual OS (separate HDs)
Regarding your third question, there's a mini HOWTO on how to use the NT loader to boot Linux that still applies to Win 2k: http://www.tldp.org/HOWTO/mini/Linux+NT-Loader.html >From reading this, I have been able to use the NT loader to boot Debian on a different partition -- I'm not sure if having them on separate drives would complicate the matter. If you already have things installed then I think it would be sufficient to follow sections 5 and 6. There's another one (http://www.tldp.org/HOWTO/mini/Linux+WinNT.html), which I haven't read, that you may find helpful as well. Andrew On Wed, 2002-06-19 at 07:44, [EMAIL PROTECTED] wrote: > I am still booting from floppy and it takes ages so I look for help: > > I have hda with win2k on it. Boots if no cd-rom or floppies in drives. > > And then there is the hdb with debian. Boots from floppy (loads the kernel > etcetc from floppy). > > So yes these are separate HD's. > > Now from previous experience I *know* that win2k is quite 'sensitive' when it > comes to booting. I tried boot manager called GAG earlier, but managed on > multiple attempts to lose the Master Boot Record to Win2k and had to reinstall > from backup images... So no luck. > > AFAIK lilo will also overwrite win2k boot manager in a way that will make > poor little win sulk and not ever be found again. So answer to any of the > three below will solve my problems, II. or III. being more robust I suppose. > > I. > How do I make an boot disk for the hdb/debian so that it only boots from > the floppy, but loads kernel etc from HD? > > II. > Is there such a thing as relatively foolproof and simple way (aside from > BIOS ;) ) to install an boot manager that does not touch/corrupt/overwrite the > Win2k? Any links and experiences welcome. > > III. > Now as I write this I started to wonder if it would be possible to > add the lead to linux boot record into windows BOOT.INI ? For win2k boot.ini > says: > multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 > Professional" /fastdetect > Anyone ever try it 'the windows way'? > > Well any help much appreciated, > > Jani > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Solutions for booting dual OS (separate HDs)
On Wed, 2002-06-19 at 06:44, [EMAIL PROTECTED] wrote: > AFAIK lilo will also overwrite win2k boot manager in a way that will make > poor little win sulk and not ever be found again. So answer to any of the > three below will solve my problems, II. or III. being more robust I suppose. Not entirely true. LILO will overwrite the w2k boot manager, but you can still boot into w2k using LILO. You can just set up LILO to be your primary boot manager and boot into Linux or w2k. In your /etc/lilo.conf just add: other=/dev/hda1 (assuming w2k is on disk a, partition 1) label=W2K > Is there such a thing as relatively foolproof and simple way (aside from > BIOS ;) ) to install an boot manager that does not touch/corrupt/overwrite the > Win2k? Any links and experiences welcome. > > III. > Now as I write this I started to wonder if it would be possible to > add the lead to linux boot record into windows BOOT.INI ? For win2k boot.ini > says: > multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 > Professional" /fastdetect > Anyone ever try it 'the windows way'? This is how I USED to do things, but as I found myself using Linux more and more and Windows less and less I did the above. If you want to do this, you can set up the NT bootloader to load LILO which will, in turn, load Linux. If you want a link, here it is: http://www.google.com/search?q=win2k+linux+boot+dd Otherwise, for the "quick and dirty" instructions: Make sure that you DO NOT install LILO into the MBR. If possible, make sure that your W2K boot partition is FAT32. Compile in VFAT support into your Linux kernel. Mount your W2K partition (for this example we'll mount it on /w2k). Assuming that your Linux partition is /dev/hdb1 (change as appropriate below) dd if=/dev/hdb1 bs=512 count=1 of=/w2k/linux.bin Then open up your /w2k/boot.ini and add a line such as: c:\linux.bin="Debian" Now, if your W2K partition HAS to be NTFS (mine did because I was concerned about at least pretending that my stuff in w2k was secure :), then you won't be able to do it so easily. If you have a FAT32 parition available somewhere then mount it, put linux.bin on it, boot into w2k, and then copy linux.bin to your c: drive. Keep in mind that anytime you have to re-run LILO (e.g. after a kernel update) you'll have to redo the dd above. If your w2k boot partition isn't FAT32 (like mine wasn't) you'll see why the first LILO-based alternative is a much better idea IMHO. :) Good luck. -Alex signature.asc Description: This is a digitally signed message part
Re: Solutions for booting dual OS (separate HDs)
[EMAIL PROTECTED] wrote: I am still booting from floppy and it takes ages so I look for help: I have hda with win2k on it. Boots if no cd-rom or floppies in drives. And then there is the hdb with debian. Boots from floppy (loads the kernel etcetc from floppy). So yes these are separate HD's. Now from previous experience I *know* that win2k is quite 'sensitive' when it comes to booting. I tried boot manager called GAG earlier, but managed on multiple attempts to lose the Master Boot Record to Win2k and had to reinstall from backup images... So no luck. AFAIK lilo will also overwrite win2k boot manager in a way that will make poor little win sulk and not ever be found again. So answer to any of the three below will solve my problems, II. or III. being more robust I suppose. I. How do I make an boot disk for the hdb/debian so that it only boots from the floppy, but loads kernel etc from HD? II. Is there such a thing as relatively foolproof and simple way (aside from BIOS ;) ) to install an boot manager that does not touch/corrupt/overwrite the Win2k? Any links and experiences welcome. III. Now as I write this I started to wonder if it would be possible to add the lead to linux boot record into windows BOOT.INI ? For win2k boot.ini says: multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional" /fastdetect Anyone ever try it 'the windows way'? Well any help much appreciated, Jani I'm not entirely sure if this is what you're looking for, but you might want to take a look at this grub multi-boot howto (the example system has all the OSs on the same hd, though that shouldn't really matter as you have win on the first hd). -- David P. James Ottawa, Ontario http://members.rogers.com/dpjames/ The bureaucratic mentality is the only constant in the universe. -Dr. Leonard McCoy, Star Trek IV -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Solutions for booting dual OS (separate HDs)
On Wed, Jun 19, 2002 at 02:44:54PM +0300, [EMAIL PROTECTED] wrote: > How do I make an boot disk for the hdb/debian so that it only boots from > the floppy, but loads kernel etc from HD? The significant line in /etc/lilo.conf is boot=/dev/fd0 Good Luck! -- Note that I use Debian version 3.0 Linux emac140 2.4.17 #1 sön feb 10 20:21:22 CET 2002 i686 unknown Hans Ekbrand pgpmf8Zgz3c64.pgp Description: PGP signature
Solutions for booting dual OS (separate HDs)
I am still booting from floppy and it takes ages so I look for help: I have hda with win2k on it. Boots if no cd-rom or floppies in drives. And then there is the hdb with debian. Boots from floppy (loads the kernel etcetc from floppy). So yes these are separate HD's. Now from previous experience I *know* that win2k is quite 'sensitive' when it comes to booting. I tried boot manager called GAG earlier, but managed on multiple attempts to lose the Master Boot Record to Win2k and had to reinstall from backup images... So no luck. AFAIK lilo will also overwrite win2k boot manager in a way that will make poor little win sulk and not ever be found again. So answer to any of the three below will solve my problems, II. or III. being more robust I suppose. I. How do I make an boot disk for the hdb/debian so that it only boots from the floppy, but loads kernel etc from HD? II. Is there such a thing as relatively foolproof and simple way (aside from BIOS ;) ) to install an boot manager that does not touch/corrupt/overwrite the Win2k? Any links and experiences welcome. III. Now as I write this I started to wonder if it would be possible to add the lead to linux boot record into windows BOOT.INI ? For win2k boot.ini says: multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional" /fastdetect Anyone ever try it 'the windows way'? Well any help much appreciated, Jani -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
