Hi.
        I've upgraded a system from DOS-W311+OS/2+W95-FAT16+Linux, using
Linux-Lilo on the MBR to multi boot, to OS/2+W95-FAT32+Linux, also using
Lilo to multi boot. Two observations:

        1. I had observed that partitioning for FAT32, one or two whole
disk tracks are left (appear as unused space under Linux fdisk, or at low
level inspecting the partition table) at the end of the disk. Someone knows
why? I have manually changed the space used by the FAT32 partition to
include this lost space, but not sure of consequences (only the stupid
Windows 95 fdisk reports 101% disk usage). I'd appreciate if someone
knows, before losing data.

        2. On Linux, on /etc/lilo.conf are defined the booting options,
which are made known simply running /sbin/lilo. When incorporating the
FAT32 partition (on /dev/hda3) a message appears: "/dev/hda3 has not a
valid boot signature". The result is that I cannot boot to W95 from
Lilo, and have to do it other ways. What is the solution? (This happens
whether or not the manual correction above).

        BTW, my Linux lilo/fdisk/cfdisk are just a bit more recent that
OSR2 appearance, so may be don't contemplate too well FAT32.

        TIA, Javier Vizcaino.

************************************
Javier Vizcaino. Ability Electronics. [log in to unmask]
  Starting point:        (-1)^(-1) = -1
  Applying logarithms: (-1)*ln(-1) = ln(-1)
  Since ln(-1) <> 0, dividing:  -1 = 1     (ln(-1) is complex, but exists)