Quote:> Can anyone help. I have a coumputer that has LILO set up on it to boot
> Linux or Win95. (hda0- LINUX swap, hda1 - Win95, sda1 - linux). The
> system was working until now when I tried to boot into win95 and nothing
> happened (freeze). I can mount and work with the Win95 filesystem from
> Linux without a problem.
Okay, I see a few odd things here. For one, you have Win95 as hda1, and
the LINUX swap as hda0. How did you set that up? Is hda1 outside the
1024 cylinder limit? Did you use a partition manager to move your Win95
Win95 does not like to be anywhere other than hda0. By default it will
only install there. I have had problems putting it anywhere else, even
with a utility like System Commander, which is supposed to let it boot
from other partitions.
Quote:> Fdisk from linux says the system is FAT16 >32MB, but when booting from
> Win95 floppy disk I can not see the C: drive (can change drive, but it
> will not be able to read anything from it). FDISK from DOS says the
> partition is OK (C:) but is an UNKNOWN type.
What FDISK did you make the Windows partition with? Some FDISK utilities
set up the partitions in a way that specific versions of Windows can not
see. For example, if you use a Win95 OSR2 Large Disk Support partition
(FAT32) it will not be visible to DOS or Win95a. I have used both the
OS/2 and OpenLINUX partition programs to set up a FAT16 partition, and
then had DOS and Win95a FAIL to read that partition.
Quote:> Is there any way to fix this problem? Better yet, to fix it without
> re-installing the system?
The ONLY non-reinstall fix I can think of is if this is a BIOS
configuration issue. If your initial drive setup in the BIOS was as LBA,
and you changed it to LARGE, then the way the information is stored on the
drive will be changed. This makes partitions seem to disappear. However,
if you change back from LARGE to LBA, the LINUX swap partition may need to
Another problem I can think of is the "Active" partition bit. To be able
to boot from a partition, it must be set "Active." This is a feature of
FDISK. Due to your description, I DO NOT think this is your problem.
However, as a just in case I will mention it here. I have had a few
motherboards that deactivate the partitions on hda if ANY other hard drive
is used as the boot drive. On those boards, all OS boot areas MUST be on
------------------ Posted via CNET Help.com ------------------