Using LILO to boot win95 on 2nd IDE Drive.

Using LILO to boot win95 on 2nd IDE Drive.

Post by Neil Ricke » Tue, 12 May 1998 04:00:00




>My computer has Linux + LILO on first IDE and Win95 on Second IDE.

Is there anything other than linux on the first drive?

How did you get Win95 onto the second drive?

Quote:>other=/dev/hdb
>        table=/dev/hda
>        label=dos

The lilo installer should have complained about this.

Quote:>other=/dev/hdb1
>        table=/dev/hdb
>        label=dos

This is the closest, but won't actually work.

Quote:>None of them work, and after selecting the "dos" option from the LILO: prompt
>i keep getting the messages like "non-system disk or disk error......"
>or "SYSTEM CAN NOW BE REBOOTED" .

The messages suggests that the partition has not been properly
initialized.  You might need to boot from Win95 floppies, for the
same version of Win95, and run
  SYS C:
This assumes that your second drive shows up as C:.  If it shows up
as something other than C:, then you cannot boot Win95 from that
partition.

When all this is done, you will need to copy the partition boot record
to a file:

  dd if=/dev/hdb1 of=/boot/win95bootsect count=1

Then you will have to use a binary editor, such as 'bpe' to patch
that boot sector.  You need to change the byte at offset +24 from 80
(hex) to 81.  If you are using FAT32, then the byte you need to
change is at offset +40.  The purpose of this patching is to coax the
system into using the second disk (BIOS device 0x81) rather than the
first disk.  Finally, in your lilo.conf, you will need

  other = /boot/win95bootsect
     label = dos

 
 
 

Using LILO to boot win95 on 2nd IDE Drive.

Post by N. Emile Akabi-Davi » Tue, 12 May 1998 04:00:00



Quote:> Hello

> My computer has Linux + LILO on first IDE and Win95 on Second IDE.
> I have been Trying to make LILO boot from my second IDE drive without any
> luck.
> I have configured my lilo.conf with all the options one can think about
> without any luck.

> The most logical options to my opinion are:

> other=/dev/hdb
>         table=/dev/hda
>         label=dos

> or:

> other=/dev/hdb1
>         table=/dev/hda
>         label=dos

> or:

> other=/dev/hdb1
>         table=/dev/hdb
>         label=dos

> None of them work, and after selecting the "dos" option from the LILO: prompt
> i keep getting the messages like "non-system disk or disk error......"
> or "SYSTEM CAN NOW BE REBOOTED" .

The problem is DOS can only be booted from the first active
partition. Short of reinstalling everything, you will need
to amend the lilo.conf file so that the other=/dev/hda
and linux=/dev/hdb. Install this on a floppy by changing
the first line in the lilo.conf from /dev/hdXX to /dev/fd0.
Change the references in the fstab file from hdaX to hdbX
and hdb1 to hda1.

Open up your machine and switch the ribbon cables round for
connecting the hardrives. That is the ribbon cable to the first
harddrive should now connect to the second harddrive and
vice versa. Close the machine, power up and go into the
BIOS to reset the harddrive parameters. Save and reboot
with the lilo floppy.

If the system boots, you are fine and I have not missed any steps,
else I may have missed something. Should only take you 30 minutes
at the most.
Caio
N.Emile <DeR vInYl JuNkIe>
/* Standard disclaimer in place */
#include <disclaimer.h>

 
 
 

Using LILO to boot win95 on 2nd IDE Drive.

Post by Andrew Adam » Sun, 17 May 1998 04:00:00




> > Hello

> > My computer has Linux + LILO on first IDE and Win95 on Second IDE.
> > I have been Trying to make LILO boot from my second IDE drive without any
> > luck.
> > I have configured my lilo.conf with all the options one can think about
> > without any luck.

> > The most logical options to my opinion are:

> > other=/dev/hdb
> >         table=/dev/hda
> >         label=dos

> > or:

> > other=/dev/hdb1
> >         table=/dev/hda
> >         label=dos

> > or:

> > other=/dev/hdb1
> >         table=/dev/hdb
> >         label=dos

> > None of them work, and after selecting the "dos" option from the LILO: prompt
> > i keep getting the messages like "non-system disk or disk error......"
> > or "SYSTEM CAN NOW BE REBOOTED" .
> The problem is DOS can only be booted from the first active
> partition. Short of reinstalling everything, you will need
> to amend the lilo.conf file so that the other=/dev/hda
> and linux=/dev/hdb. Install this on a floppy by changing
> the first line in the lilo.conf from /dev/hdXX to /dev/fd0.
> Change the references in the fstab file from hdaX to hdbX
> and hdb1 to hda1.

> Open up your machine and switch the ribbon cables round for
> connecting the hardrives. That is the ribbon cable to the first
> harddrive should now connect to the second harddrive and
> vice versa. Close the machine, power up and go into the
> BIOS to reset the harddrive parameters. Save and reboot
> with the lilo floppy.

> If the system boots, you are fine and I have not missed any steps,
> else I may have missed something. Should only take you 30 minutes
> at the most.
> Caio
> N.Emile <DeR vInYl JuNkIe>
> /* Standard disclaimer in place */
> #include <disclaimer.h>

The above used to be true, but some late version of lilo that began
being distributed a year or so ago changed all that.  I discovered,
after searching all the LILO docs I could find to no avail, by
installing S.u.S.E 5.1 and letting YaST configure LILO, the following
fragment:

# DOS bootable partition config begins
other = /dev/hdb1
label = win
map-drive = 0x80
to = 0x81
map-drive = 0x81
to = 0x80
table = /dev/hdb
#
other = /dev/hda1
label = dos
table = /dev/hda
# DOS bootable partition config ends
#
As you can see there's pretty new stuff in there!  It worked
flawlessly.  

Andrew Adams

 
 
 

1. LILO+BM+Win95 mostly ok, 2nd LILO hosed by booting Linux?

(Okay, the Subject: line sucks.  Whatever.)

So here's the story: my system boots into the OS/2 boot manager; from
there I can select DOS 6.22, OS/2 Warp, Win95, or Linux (and I'd have
FreeBSD 2.1 on there if it supported extended DOS partitions).  Here's
the trouble: this is on two 2GB hard drives, with all but Win95 on the
first.

To boot the second, I can't use Boot Manager, because it doesn't do LILO's
wonderful trick of switching the C: and D: drives.  So I have the boot
manager invoke a copy of LILO installed on a dead partition, which has
a default setting to boot Win95.

Here's the problem: LILO lives in the first part of two different
partitions, not the MBR, since I want to boot into BM, not LILO (face it,
LILO hasn't got much of a UI).  I use it on Linux to switch kernels when
something hoses, and on an otherwise empty partition on D: to boot Win95.

Whenever I boot Linux though, it rebuilds a data file, and I end up
with "LIL-" (hang) the next time I try to boot Win95.  For some reason
LILO is referring to files back on the other drive, probably because
that's what I booted up on when I installed LILO.

I looked through the LILO docs, and have some idea of why this is
happening, but have no clue what to do about it.  I either need to prevent
LILO from reconstructing the data file, or find an alternate way to boot
Win95 (right now I just launch Linux, and tell LILO to boot Win95
instead).

I'm using the last 2.x slackware release.

(Hmm... I guess I could install LILO on the D: drive as well, but I was
hoping to put FreeBSD there... do LILO and FreeBSD work together?  Sorry,
but the latency in the Linux serial drivers isn't acceptable for what I'm
trying to do, otherwise I'd just use Linux.)

--

      Anyone can do any amount of work provided it isn't the work he is
        supposed to be doing at the moment.        -- Robert Benchley

2. Ethernet ca Cards (T base 10)

3. Linux on 2nd IDE drive on 2nd IDE controller?

4. Help Moving Data!!!

5. Configuring LILO to boot Win95 on additional SCSI drive, Primary is IDE?

6. Disk Mirroring WITHOUT Solstice?

7. using lilo to boot dos from 2nd scsi drive

8. Font problems with Netscape/XFree 3.1

9. Help: Using 1 gig IDE drive as 2nd drive

10. Booting DOS off 2nd drive, with 3 IDE drives

11. Lilo & 2 SCSI Drives - Won't boot from 2nd drive

12. Q:Boot linux from 2nd drive using Boot Easy?