Someobe here wrote: > > I've got two drives in a machine. One has Win95 on it, the other has WinNT > > and Linux. Using LILO, I can boot Linux and whichever Windows OS is on the > > first hard drive. I am unable, however, to boot the one on the second > > drive, hdb. > > > > My lilo.conf looks like: > [snip] > > other=/dev/hdb1 > > label=95 > > loader=/boot/chain.b > > table=/dev/hdb > > > > Using this config, I can boot Linux or NT, but not 95. If I try, I just get > > "Loading 95" (issued by LILO) and then nothing.
Likely not lilo's problem. Both DOS and Windows assume they start in "drive C"-- the lowest numbered partition on the very first disk in your system, regardless of where you think you have placed them-- and if they aren't there, when booted up they will look for files and try to write files in that partition. You might put a tiny little partition on your first disk-- just enough for command.com, autoexec.bat, msdos.sys, and so forth-- which functions as the active partition when you boot your second Windows system. Windows doesn't insist on being installed in Drive C, just so long as it owns it. (Note that windows will also try to use drive C as the home for its 15 Megabyte swap file-- possibly the problem that wouldn't let it startup on your system-- but you might be able to override this in win.ini or system.in. My take on your problem anyhow. ------------------------------------------------------------------------------ [EMAIL PROTECTED] Mike Shupp California State University, Northridge Graduate Student, Dept. of Anthropology http://www.csun.edu/~ms44278/index.htm
