patg@impch.UUCP (Patrick Guelat) (04/10/89)
Hi there,
We're using SCO 2.3.1 with an ESDI-controller. We're suffering under
a serious problem: as soon we get a bigger disk, we fill it up and
need more diskspace... This takes no end, and that's a REAL problem. ;-)
We're now a the point where we need to install a second controller
to fulfill our needs ;-)). We have another two 70 MB hd's lying
around here with ST506 interface waiting to be filled up ;-)
SCO 2.3.1 now supports a second controller (as mentioned in the release notes).
Is there anyone out there using a second hd-controller under SCO2.3.1
who can give us some hints regarding the type of controller,
IO-base address, irq-vector ( 15 ? ) and so on ?
Pat
--
\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//
// Patrick Guelat, ImproWare Switzerland \ SMART: patg@impch.uucp \\
\\ SUB-NET: ..!altger!impch!{patg,boxdiger} \________ Wasting time is an //
// EUNET : ..!cernvax!impch!{patg,boxdiger} \ important time of\\
\\ OTHER : ..!uunet!acad!acadch!impch!{patg,boxdiger} \ living. //
//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\tif@cpe.UUCP (04/11/89)
Written 2:53 pm Apr 9, 1989 by impch.UUCP!patg in cpe:comp.unix.xenix >We're using SCO 2.3.1 with an ESDI-controller. We're suffering under >a serious problem: as soon we get a bigger disk, we fill it up and >need more diskspace... This takes no end, and that's a REAL problem. ;-) > >SCO 2.3.1 now supports a second controller (as mentioned in the release notes). >Is there anyone out there using a second hd-controller under SCO2.3.1 >who can give us some hints regarding the type of controller, >IO-base address, irq-vector ( 15 ? ) and so on ? Hint 1: (According to my documentation on a slightly different version) Systems with an ESDI controller can't add another controller. Hint 2: We have a purely pre-release system "running" with 1077 Meg(!) of HD space on one SCSI controller. (We have the potential -- today -- to run with over 2 Gig on one SCSI controller and we can still add a second!) Paul Chamberlain Computer Product Engineering, Tandy Corp. {killer | texbell}!cpe!tif
neese@cpe.UUCP (04/12/89)
> /* STUFF DELETED */ >Hint 2: We have a purely pre-release system "running" with 1077 Meg(!) > of HD space on one SCSI controller. (We have the potential -- > today -- to run with over 2 Gig on one SCSI controller and we > can still add a second!) Being a SCSI purist, I have to note a correction to my colleagues statement that he has 1077Meg on one SCSI adapter, not controller. Sorry tif. Roy Neese UUCP @ {killer,merch,texbell}!cpe!neese Tandy Computer Product Engineering
sl@van-bc.UUCP (pri=-10 Stuart Lynne) (04/13/89)
In article <141100016@cpe> tif@cpe.UUCP writes: > >Written 2:53 pm Apr 9, 1989 by impch.UUCP!patg in cpe:comp.unix.xenix >>We're using SCO 2.3.1 with an ESDI-controller. We're suffering under >>a serious problem: as soon we get a bigger disk, we fill it up and >>need more diskspace... This takes no end, and that's a REAL problem. ;-) >> >>SCO 2.3.1 now supports a second controller (as mentioned in the release notes). >>Is there anyone out there using a second hd-controller under SCO2.3.1 >>who can give us some hints regarding the type of controller, >>IO-base address, irq-vector ( 15 ? ) and so on ? Well Dave Dillabough (uunet!van-bc!dilltk!dave) has run two WD 1003 compatible controllers in SCO systems without too many problems. You do have to modify the second controller to interrupt at the appropriate interrupt vector. >Hint 1: (According to my documentation on a slightly different version) > Systems with an ESDI controller can't add another controller. He hasn't had any trouble with running a WD 1007 with another controller. Dave is out of town until next week. I'm sure he won't mind providing more information to those who ask, when he gets back. The biggest problem is modifying the hardware for the interrupt vector. Usually there are jumpers for selecting the second board address. After that you just mkdev hd 2. -- Stuart.Lynne@wimsey.bc.ca uunet!van-bc!sl 604-937-7532(voice) 604-939-4768(fax)
patg@impch.UUCP (Patrick Guelat) (05/14/89)
Hi there,
I would like to thank everybody who sent us ideas, pointers and hints
on how to use a second hd-controller with sco xenix 2.3.1.
Many thanks to Paul Zola (paulz@sco.uucp), Martin Stanley (mts@ai.toronto.edu),
Jim O'Connor (jim@tiamat.fsc.com) and a lot of others for their precious
help.
What has to be done
-------------------
If you want to install a second hd-controller you should look around for
a hd-only controller ( without floppydisk-controller ).
In our case this is a TNC RLL-controller, but an Adaptec 2370 would also
work and there are certainly a few more. ( also ST506 controllers )
It must be a controller that can be jumpered to a secondary
IO-address ( 0x170 - 0x177 ).
The second problem is the IRQ. You have to change it from 14 to 15. On a
few controller this can be done with jumpers, we had to do some hardware
hacks ( cut and paste ;-)
Additionally you should change the ROM address of the controller from
0xc800 to 0xcc00 if possible.
After that, you have to configure your xenix :
Run 'mkdev hd 0 1' to install the first drive on the second controller
Run 'mkdev hd 1 1' to install the second drive on the second controller
If you wish to mount these disks in /etc/rc ( you do ey ? ;-) you will
have to edit '/etc/default/filesys'. ( RTFM for more infos about that )
Be sure that the tunable kernel parameter 'NDISK' is set high enough
( 4 or 5 if you wish to use 4 HD's and a floppy ). This can be done
with /usr/sys/conf/configure.
If you have two hard disks on the second controller, it is necessary
to mount the filesystems on the first hard disk before mounting the
filesystems on the second hard disk.
--- Patrick Guelat
--
\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//
// Patrick Guelat, ImproWare Switzerland / SMART: patg@impch.uucp \\
|| EUNET : ..!cernvax!impch!patg | Wasting time is an ||
\\ OTHER : ..!uunet!acad!acadch!impch!patg \ important part of living. //
//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\