RE: [newbie] Um...multi boot...NOT
At the Lilo prompt or Grub, type in or select DOS, and press the key. Roman Registered Linux User #179293 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jim Chiang Sent: Tuesday, September 19, 2000 11:03 AM To: [EMAIL PROTECTED] Subject: [newbie] Um...multi boot...NOT OK. I havea 20gB drive. I installed in this order: win98se Win2K Pro MDK7.1 After Win@K evertyhing was OK. I could still boot to 98 and 2k with the NT loader. I read a message a while ago with someone else running these same 3 OS's without Boot Magic. I'm in trouble. First of all, I thought 7.1 was supposed to use Grub, but when I boot I have Lilo not Grub. Also, at the boot: prompt when I hit Tab it shows: linux rescue WHERE IS WINDOWS I installed 7.1 by booting from CD and then choosing Advanced, Developer. What did I do wrong? Jim
RE: [newbie] Um...multi boot...NOT
I went into the Frak Config and clicked around a bit and didn't think I did anything but look around and then cancel... Next time I boot Grub comes up instead of LILO? They are both installed?? So confused I have the options now to boot to: linux failsafe windows floppy Problem is when I select windows and then get to the W2K loader, neither Win2K or W98 will boot. They both freeze up on the startup screens. What the? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Andrew Scotchmer Sent: September 19, 2000 6:23 PM To: [EMAIL PROTECTED] Subject: Re: [newbie] Um...multi boot...NOT > I'm in trouble. > > First of all, I thought 7.1 was supposed to use Grub, but when I boot I have > Lilo not Grub. > Also, at the boot: prompt when I hit Tab it shows: > linux rescue > > WHERE IS WINDOWS > Jim Did you install Lilo on the MBR or secondary boot header? In saying that how about entering Drak Config and placing the Windows option on the same partition as Lilo (hda 5 or where-ever) so that it would show when at the Lilo prompt. This should then enable you to boot Windows. Andrew
Re: [newbie] Um...multi boot...NOT
> I'm in trouble. > > First of all, I thought 7.1 was supposed to use Grub, but when I boot I have > Lilo not Grub. > Also, at the boot: prompt when I hit Tab it shows: > linux rescue > > WHERE IS WINDOWS > Jim Did you install Lilo on the MBR or secondary boot header? In saying that how about entering Drak Config and placing the Windows option on the same partition as Lilo (hda 5 or where-ever) so that it would show when at the Lilo prompt. This should then enable you to boot Windows. Andrew
Re: [newbie] Um...multi boot...NOT
- Original Message - From: "Charles A Edwards" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, September 19, 2000 2:09 PM Subject: Re: [newbie] Um...multi boot...NOT > > - Original Message - > From: "Jim Chiang" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Tuesday, September 19, 2000 11:03 AM > Subject: [newbie] Um...multi boot...NOT > > > > OK. I havea 20gB drive. I installed in this order: > > win98se > > Win2K Pro > > MDK7.1 > > > > After Win@K evertyhing was OK. I could still boot to 98 and 2k with the NT > > loader. I read a message a while ago with someone else running these same > 3 > > OS's without Boot Magic. > > > > I'm in trouble. > > > > First of all, I thought 7.1 was supposed to use Grub, but when I boot I > have > > Lilo not Grub. > > Also, at the boot: prompt when I hit Tab it shows: > > linux rescue > > > > WHERE IS WINDOWS > > > > I installed 7.1 by booting from CD and then choosing Advanced, Developer. > > > > What did I do wrong? > > >My guess would be that when the bootloader was installed you changed the > default location which should have been hda1 therefore Lilo was installed > instead of Grub or that for whatever reason Grub was not installed from the > CD. >I have more bad news. You will most likly have to fomatt your drive and > re-install all 3 OSes. >Were you using only Win98 or even Win98 and NT you could use fdisk/MBR to > remove Lilo and restore your Win bootloader but because you have Win2000 > this will not work. >If you have created a Win2000 Rescue disk you can possibly use it to > boot to your Win2000 installation CD and using the repair option restore > the Win bootloader. I say possibly because it has been my experiance that > the restore operation is either unable to find the Win2000 partition or if > it does find it, it reports that the partiion table is corrupt and it can > not repair. > Sorry to be the bearer of bad tidings. > >Charles > > > >
Re: [newbie] Um...multi boot...NOT
- Original Message - From: "Jim Chiang" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, September 19, 2000 11:03 AM Subject: [newbie] Um...multi boot...NOT > OK. I havea 20gB drive. I installed in this order: > win98se > Win2K Pro > MDK7.1 > > After Win@K evertyhing was OK. I could still boot to 98 and 2k with the NT > loader. I read a message a while ago with someone else running these same 3 > OS's without Boot Magic. > > I'm in trouble. > > First of all, I thought 7.1 was supposed to use Grub, but when I boot I have > Lilo not Grub. > Also, at the boot: prompt when I hit Tab it shows: > linux rescue > > WHERE IS WINDOWS > > I installed 7.1 by booting from CD and then choosing Advanced, Developer. > > What did I do wrong? My guess would be that when the bootloader was installed you changed the default location which should have been hda1 therefore Lilo was installed instead of Grub or that for whatever reason Grub was not installed from the CD. I have more bad news. You will most likly have to fomatt your drive and re-install all 3 OSes. Were you using only Win98 or even Win98 and NT you could use fdisk/MBR to remove Lilo and restore your Win bootloader but because you have Win2000 this will not work. If you have created a Win2000 Rescue disk you can possibly use it to boot to your Win2000 installation CD and using the repair option restore the Win bootloader. I say possibly because it has been my experiance that the restore operation is either unable to find the Win2000 partition or if it does find it, it reports that the partiion table is corrupt and it can not repair. Sorry to be the bearer of bad tidings. Charles
