3 Mar
2008
3 Mar
'08
2:12 p.m.
Allison Parent wrote:
Bob Armstrong
wrote:
The question is who is the interface for. Is this like the SCB1620 interface to provide
a hard drive to a small system that may not have any other major storage device,
or is this for a commercial system that has a *Standard* I/O allready?
For commercial you have to deal with the holder of the MSCP intellectual rights.
The other issue is MSCP is an intelligent system that has DMA and is able to run
linked lists for queued IO.The pro for MSCP is most all of the DEC OSs had drivers
for it. The minus is complex, firmware intensive, DMA and temporary bus master
and it would try to do some of the buffering that IDE drives already do well.
For RT11, the DD (tu58) driver would make a good
prtotype as would the HX previously
mentioned. The RT-11 docs cover creating new drivers and VMS docs too.
I would like to suggest as an alternative to MSCP, use John Wilson's HD:
device
definitions from Ersatz-11. The RT-11 device driver will be rather
easy. In
addition, if I am provided with the code for the RK05 and RL02 device
drivers
for other OSs, I can probably make a good effort to provide the changes
needed
for the HD: device. But someone else would need to debug the code.
NO, I don't volenteer, way too much going on right
now.
I will provide a suitable HD(X).SYS device driver over and above what
John Wilson
has already done for RT-11 with a translation table that will handle a
2 TB disk drive. Just
send me a test board for a Qbus system.
Sincerely yours,
Jerome Fine
--
If you attempted to send a reply and the original e-mail
address has been discontinued due a high volume of junk
e-mail, then the semi-permanent e-mail address can be
obtained by replacing the four characters preceding the
'at' with the four digits of the current year.