>> Reno or dot something or other > 4.4-Reno is not NetBSD 1.anything. I _think_ Reno came before all NetBSD versions, but I wasn't involved with it that far back, and I don't recall what I've read of the history in enough detail. But I _think_ Reno was ancestral to 4.4-Lite, and I _think_ NetBSD was derived from 4.4-Lite (via the Jolitzes' work). But I could easily be wrong about either or both of those. Yes, some ancient dist -- I was looking at docs for creating bootable tapes that far back, because of the relation between systems -- Berkeley Networking Release 2 (Net/2), 4.4BSD-Lite, and 4.4BSD-Lite. However, I am unable to find the link in my history. I think the last (NetBSD) version I tried was tk50-file1-13A -- not that I tried anything earlier. >> It's probably the SCSI layer. Do I implement TMSCP(sp?) > TMSCP is not SCSI. TMSCP is the tuned-for-tapes version of MSCP, DEC's Mass Storage Control Protocol. MSCP is a protocol run between hosts and disks; TMSCP is an adaptation of it designed for tapes. > Given the questions you were asking, I would say it is highly unlikely you will need to implement TMSCP. The only cases I can see where you have a need to implement TMSCP are (1) building an emulator of some sort, (2) writing host code to speak to DEC tapes, or (3) building a glue layer, such as a board that speaks TMSCP to the host and SCSI to a drive. It does not strike me as likely that you would be taking on any of those while still having occasion to ask what you were asking. I wasn't asking if I should implement TMSCP, but rather whether my hardware and firmware do. I have a hunch that booting from MUA0 is breaking because of the SCSI board in the TKZ-50, but I can't be more specific and could easily be wrong -- it's just a hunch. -- KRJ/NODOMAIN.NET
Attachment:
smime.p7s
Description: S/MIME cryptographic signature