Re: dual boot

[bill jehle <billj brandx net>]

On Wed, 22 Dec 1999, Mark Wilson and Sharon Farr wrote:
> Bill
> 
> hda is your Master on your primary ide controller and hdb is the Slave on
> the primary ide controller. Your cdrom is on hdc which is the Master on your
> secondary ide controller.
> 
> hda is your IBM-DTTA-371010 hard disk. <<< Is this your Red Hat drive?--Yes
> 
> hdb is your WDC WD205BA hard disk.   <<< Is this your Windows drive?--Yes

Mark
Also I looked in BIOS and it was set to boot from HD 2 which was the Win disk
thats why it was booting Win. I changed it to boot HD1 now it boots only RH and
and I got the same msg from lilo -v as below..
Best Regards..
 --bill

> -----Original Message-----
> From: bill jehle <billj brandx net>
> To: Mark Wilson and Sharon Farr <markandsharon csi com>
> Date: Thursday, 23 December 1999 04:13
> Subject: Re: dual boot
> 
> 
> >
> >
> >Mark,
> > Here's what dmesg says... I changed the jumpers, I had them for hdo on
> >master-single, so I put it on master-dual and ran lilo again but I get the
> same
> >msg as below.
> >
> >PIIX4: IDE controller on PCI bus 00 dev 39
> >PIIX4: not 100% native mode: will probe irqs later
> >ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:DMA
> >ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:pio
> >hda: IBM-DTTA-371010, ATA DISK drive
> >hdb: WDC WD205BA, ATA DISK drive
> >hdc: CD-ROM 50X, ATAPI CDROM drive
> >ide2: ports already in use, skipping probe
> >ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> >ide1 at 0x170-0x177,0x376 on irq 15
> >hda: IBM-DTTA-371010, 9641MB w/465kB Cache, CHS=1229/255/63
> >hdb: WDC WD205BA, 19574MB w/1961kB Cache, CHS=2495/255/63
> >hdc: ATAPI 32X CD-ROM drive, 128kB Cache
> >Uniform CDROM driver Revision: 2.54
> >
> >shouldn't ide# say slave and master somewhere? I'll check the bios in setup
> >maybe I have something goofy going on there.
> >Thanks -
> >--bill
> >
> >> Bill
> >>
> >> Does your new lilo.conf look a little like this?:
> >>
> >> boot=/dev/hda
> >> map=/boot/map
> >> install=/boot/boot.b
> >> prompt
> >> vga = normal
> >> read-only
> >> timeout=50
> >> image=/boot/vmlinuz-2.2.5-15
> >>     label=linux
> >>     root=/dev/hda6
> >> other=/dev/hdb1
> >>     table=/dev/hdb
> >>     loader=/boot/os2_d.b
> >>     label=Win95
> >>     alias=w
> >>
> >> I wonder if your Win95 is really the slave? I say this because when you
> ran
> >> lilo it successfully added linux as a boot option but not Windows, but
> when
> >> you rebooted it went straight into Windows. I'm not sure what lilo does
> when
> >> it hits a problem like this, it may just exit, or it may go with it has
> got.
> >> I'm guessing it exits which would leave the Windows MBR - ie it will boot
> >> straight into Windows with no LILO boot: prompt.
> >
> >> Things to check:
> >>     Your lilo.conf
> >>     Run "dmesg | more" in linux to see which device was assigned to which
> >> disk (hopefully they are different)
> >>     Your bios boot options are correct. Some bios can tell you Cyl, Hds &
> >> Sects to help you id your disks
> >>     The Master - Slave jumper settings on your disks
> >>
> >> If the problem still isn't obvious let me know the above settings and
> I'll
> >> think of something creative to do with them ;-)
> >>
> >> Good luck
> >>
> >> Mark
> >> -----Original Message-----
> >> From: bill jehle <billj brandx net>
> >> To: redhat-install-list redhat com <redhat-install-list redhat com>
> >> Date: Wednesday, 22 December 1999 18:00
> >> Subject: Re: dual boot
> >>
> >>
> >> >
> >> >
> >> >>u can add the section below to
> >> >> your lilo.conf and rerun lilo.
> >> >>
> >> >> other=/dev/hdb1
> >> >>     table=/dev/hdb
> >> >>     loader=/boot/os2_d.b
> >> >>     label=Win95
> >> >>     alias=w
> >> >
> >> >OK enough with the bad edit job :=}
> >> > Mark I added that to lilo.conf and ran it. I now have RH6 as master on
> hda
> >> >just like your previous post, and Win 95 on hdb as slave. I ran lilo
> >> and -v -v
> >> >gets this message...
> >> >
> >> >Reading boot sector from /dev/hda
> >> >Merging with /boot/boot.b
> >> >Secondary loader: 8 sectors.
> >> >Boot image: /boot/vmlinuz-2.2.5-15
> >> >Setup length is 7 sectors.
> >> >Mapped 1208 sectors.
> >> >Added linux *
> >> >Boot other: /dev/hdb1, on /dev/hdb, loader /boot/os2_d.b
> >> >First sector of /dev/hdb1 doesn't have a valid boot signature
> >> >Removed temporary file /boot/map~
> >> >
> >> >What does this mean?
> >> >Also when I startup now Win boots immediately without giving me a lilo
> >> prompt.
> >> >(and then I have to do that incessant clicking to close it down, you
> know
> >> what
> >> >I mean :-) And linux will boot  only and fine and dandy With my boot
> disc.
> >> Why
> >> >won't it and Win boot from the boot prompt.
> >> >
> >> >> The "down" side of having the the Windows disk as Master is that the
> MBR
> >> is
> >> >> no longer a Windows one but the lilo one. This means that to boot
> either
> >> >> system you have to boot through lilo. This isn't really a problem -it
> >> just
> >> >> feels less conservative. As long as you have boot floppies for both
> >> systems
> >> >> you can access them in an emergency and undo any changes. If you want
> to
> >> go
> >> >> this route let me know and I'll suggest a way to achieve this. It was
> a
> >> >> little tricky the first time I did it. To my mind this is the better
> way
> >> to
> >> >> go as you get a little more functionality, ie you can reinstall Win95
> >> >> if/when necessary.
> >> >
> >> >I was thinking if that turns out to be a problem  I'll just unplug hda.
> >> >Thanks to you and to Jim for the help I hope you have a great Christmas.
> >> >Thanks--bill
> >> >
> >> >> It isn't as bad as it seems!
> >> >>
> >> >> Good luck
> >> >>
> >> >> Mark