by (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