Very Computer

by **Mark Nordstra** » Tue, 22 Jul 1997 04:00:00

Hi,

Sorry for the cross-post, but it seems appropriate to both.
Also, I may be a little to verbose and piece-meal here......

I originally had linux on a 1.2G drive and win95 on a 2.5G
drive. The 1.2G was the master and /dev/hda. The 2.5G was
a slave and /dev/hdb. (note that I'm omitting partitions
for the sake of my sanity). I've gone thru every FAQ, man-
page and HOWTO I thought related to (however remotely)
multiple boots.

For various reasons (hardware, mostly), I need a MS-DOS/Win
3.11 partition. This was a great excuse to get a large
drive. My intent is to use the new drive for linux and put
DOS on the 1.2G (95 seems more desperate for space, but that's
another issue).

By various means, I've managed to install DOS on the 1.2G.
Now, the new drive is /dev/hda (master on first chain), win95
is still /dev/hdb (also still slaved), and DOS is /dev/hdc
(master on the second chain, with the ATAPI cdrom slaved).
I'm pretty sure that LILO is gone from the 1.2G (did the
'dd' command, ran makedosfs, and even did FDISK /MBR).
I've added lines to lilo.conf, and ran /sbin/lilo. This
complains about /dev/hdc and I should MAKEDEV.ide. I do
and it doesn't make any difference, lilo still complains.
(Sorry, I haven't gotten a satisfactory news reader on
linux yet, and this is from 95. Any suggestions?).

When linux boots, everything's cool, both the win95 and the DOS
partitions are mounted where they should be, and look ok.

When 95 boots, I don't see the other DOS disk. I could probably
live with this, but it would be nice. Actually, I'm hoping this
might be an indication of other problems.

Attempting the to boot DOS (I know, lilo complained, but my data's
backed up, and I thought I might get something which helps),
complains that this isn't a bootable device (the hit a key one...).
When I press a key, it boots 95.

I would really appreciate any input on this.

Mark

by **Bob Niels** » Wed, 23 Jul 1997 04:00:00

>Hi,

>Sorry for the cross-post, but it seems appropriate to both.
>Also, I may be a little to verbose and piece-meal here......

>I originally had linux on a 1.2G drive and win95 on a 2.5G
>drive. The 1.2G was the master and /dev/hda. The 2.5G was
>a slave and /dev/hdb. (note that I'm omitting partitions
>for the sake of my sanity). I've gone thru every FAQ, man-
>page and HOWTO I thought related to (however remotely)
>multiple boots.

>For various reasons (hardware, mostly), I need a MS-DOS/Win
>3.11 partition. This was a great excuse to get a large
>drive. My intent is to use the new drive for linux and put
>DOS on the 1.2G (95 seems more desperate for space, but that's
>another issue).

>By various means, I've managed to install DOS on the 1.2G.
>Now, the new drive is /dev/hda (master on first chain), win95
>is still /dev/hdb (also still slaved), and DOS is /dev/hdc
>(master on the second chain, with the ATAPI cdrom slaved).
>I'm pretty sure that LILO is gone from the 1.2G (did the
>'dd' command, ran makedosfs, and even did FDISK /MBR).
>I've added lines to lilo.conf, and ran /sbin/lilo. This
>complains about /dev/hdc and I should MAKEDEV.ide. I do
>and it doesn't make any difference, lilo still complains.
>(Sorry, I haven't gotten a satisfactory news reader on
>linux yet, and this is from 95. Any suggestions?).

>When linux boots, everything's cool, both the win95 and the DOS
>partitions are mounted where they should be, and look ok.

>When 95 boots, I don't see the other DOS disk. I could probably
>live with this, but it would be nice. Actually, I'm hoping this
>might be an indication of other problems.

>Attempting the to boot DOS (I know, lilo complained, but my data's
>backed up, and I thought I might get something which helps),
>complains that this isn't a bootable device (the hit a key one...).
>When I press a key, it boots 95.

>I would really appreciate any input on this.

DOS and Win95 each want to have the other not visible to them. See the
Linux+DOS+Win95 and Win95+Win+Linux mini-HOWTOs for more information on
methods to make them all accessible.

Bob

--

http://www.primenet.com/~nielsen

by **Tom Dale** » Fri, 25 Jul 1997 04:00:00

> Hi,

> Sorry for the cross-post, but it seems appropriate to both.
> Also, I may be a little to verbose and piece-meal here......

> I originally had linux on a 1.2G drive and win95 on a 2.5G
> drive. The 1.2G was the master and /dev/hda. The 2.5G was
> a slave and /dev/hdb. (note that I'm omitting partitions
> for the sake of my sanity). I've gone thru every FAQ, man-
> page and HOWTO I thought related to (however remotely)
> multiple boots.

> For various reasons (hardware, mostly), I need a MS-DOS/Win
> 3.11 partition. This was a great excuse to get a large
> drive. My intent is to use the new drive for linux and put
> DOS on the 1.2G (95 seems more desperate for space, but that's
> another issue).

> By various means, I've managed to install DOS on the 1.2G.
> Now, the new drive is /dev/hda (master on first chain), win95
> is still /dev/hdb (also still slaved), and DOS is /dev/hdc
> (master on the second chain, with the ATAPI cdrom slaved).
> I'm pretty sure that LILO is gone from the 1.2G (did the
> 'dd' command, ran makedosfs, and even did FDISK /MBR).
> I've added lines to lilo.conf, and ran /sbin/lilo. This
> complains about /dev/hdc and I should MAKEDEV.ide. I do
> and it doesn't make any difference, lilo still complains.
> (Sorry, I haven't gotten a satisfactory news reader on
> linux yet, and this is from 95. Any suggestions?).

> When linux boots, everything's cool, both the win95 and the DOS
> partitions are mounted where they should be, and look ok.

> When 95 boots, I don't see the other DOS disk. I could probably
> live with this, but it would be nice. Actually, I'm hoping this
> might be an indication of other problems.

> Attempting the to boot DOS (I know, lilo complained, but my data's
> backed up, and I thought I might get something which helps),
> complains that this isn't a bootable device (the hit a key one...).
> When I press a key, it boots 95.

> I would really appreciate any input on this.

> Mark

It could be that your BIOS is only capable of recognizing two hard
drives. My system is this way (it is 6 years old). The README
has some info about this although I don't know how to tell if a system
has this limitation. Perhaps in the setup screens for the BIOS.
My setup screen only shows two drives. Here is an exerpt from
the lilo README:

More than two disks
- - - - - - - - - -

On systems with more than two disks, typically only the first two
can be accessed. The configuration choices are therefore the same
as with two disks.

When attempting to access one of the extra disks, LILO displays a
warning message ( Warning: BIOS drive 0x<number> may not be
accessible ) but does not abort. This is done in order to allow the
lucky few whose BIOS (or controller-BIOS) does support more than two
drives to make use of this feature. By all others, this warning
should be considered a fatal error.

Note that the two disks restriction is only imposed by the BIOS.
Linux normally has no problems using all disks once it is booted.

by **Geoff Winkles** » Sat, 26 Jul 1997 04:00:00

Quote:>Attempting the to boot DOS (I know, lilo complained, but my data's
>backed up, and I thought I might get something which helps),
>complains that this isn't a bootable device (the hit a key one...).
>When I press a key, it boots 95.

Sounds like you haven't set the dos partition as an "active"
partition.

Best way to do this is to remove the other disks completely, just boot
up off a floppy with only the DOS hard drive installed. Then run fdisk
off the dos floppy and set the drive as an active partition.

Should work then.

Geoff

Very Computer

LILO and multiple boots

LILO and multiple boots

LILO and multiple boots

LILO and multiple boots

LILO and multiple boots