[H-GEN] Two questions: SCSI & Dodgy motherboard?

Steve Pinel stevep at ssc.qld.edu.au
Tue Jun 23 01:13:08 EDT 1998


Hello all.

Just added a second SCSI drive to  my machine, in order to install some
version of Linux at home (lets call it Brand X, to hold off the Holy
Wars), in addition to another OS that shall remain nameless.

The new drive is a 1.2Gb apple SCSI drive, fixed to ID 0 (don't think I
can change it).  Got it working fine with Win95.  The second drive is a
650Mb old (i.e. 1992 vintage)  Fujitsu thing that has worked fine till
now running both Win95 and Linux.  It is currently set up as SCSI ID 4.
I also have a SCSI CDROM on ID 2.  What I would like to do is set the
machine to boot by default on the 1.2Gb drive into Win95, and use LILO
on a floppy to boot into Linux, on the second drive.

Unfortunately, no matter what I seem to do, the computer wants to boot
off of the Fujitsu drive, even though it is not bootable (just returns
an error saying no ROM basic found).

Can anyone point me to something that says how PCs choose which is the
bootable drive in a SCSI chain, or point out the bleeding obvious that
I have somehow missed?



Second Qn:  I have a 486 motherboard that I would like to ifnd a use
for.  DOS installs fine, but if I try to install either WIndows 3.1 or
Linux, then it does a dummy spit.  Errors occur when it tries to use a
RAMDISK in Linux install, or gives an error in DOS extender in Windows
install.  Guessing the memory was at fault, I replaced it (8*1Mb SIMMS)
to no avail, as with every part including case & keyboard.  Anyone seen
this type of fault before?  I suspect the memory control on the
MotherBoard (as it only occurs with OSes that try to access above 640k),
but I'm open to suggestions on how to get around this problem.





More information about the General mailing list