Subject: RE: About the QBus EIDE interface...
To: 'John Maier' <jmaier@midamerica.net>
From: David Woyciesjes <DAW@yalepress3.unipress.yale.edu>
List: port-vax
Date: 01/24/2002 10:27:09
> From: 	John Maier
> 
> > A better solution is what's already being discussed: an MSCP server on a
> > Qbus card. While I'd personally prefer SCSI to IDE, the ability to put
> any
> 
> Ummm...Actually SCSI vs. IDE argument goes away, in this case, because:
> 1) Qbus can't even hope to keep up with most any off the shelf EIDE drive
> made in the last
> few years.
> 2) Using a processor to talk to the IDE, for the VAX, is tantamount to the
> SCSI
> intelligent controller concept.
> 
> I.e. if I were really bent on it (and I'm not) I could make a controller
> to which you
> could connect an IDE drive.  On the other side, I could talk out SCSI,
> then you could hook
> it to any old SCSI bus. Thus you could us an IDE drive in any SCSI system.
> 
> The point here is implement MSCP which will give this board life under
> most any VAX OS.
> Additionally, because it will be an intelligent controller, it will take
> the load off an
> already very slow CPU.
> 
> The dumb IDE Qbus board is a great idea, but terribly inefficient, for a
> VAX, due to the
> high cost to the CPU for processing.  On the flip, at least it's
> something!
> 
> 
	Well, it would be a starting point for that intelligent controller,
wouldn't it? Basically, build a basic IDE controller, and then once it's
working solid, it can "evolve". I think it's best to start with a target
that's a little closer and easier to hit...

---   David A Woyciesjes
---   C & IS Support Specialist
---   Yale University Press
---   mailto:david.woyciesjes@yale.edu
---   (203) 432-0953
---   ICQ # - 905818