This area contains Wolfgang Moeller's remote magtape driver with mods for VMS 5.4 and up. This allows you to have a tape somewhere across your DECnet acting as though it were locally connected, so that you can perform copies, backups, etc., over the network. A driver, local control program that talks to the driver, and remote network server that talks to the magtape and the local control program (across the net) are present. My update to Moeller's driver is in ztdriverm.mar and ztserverm.mar which are attempts at a multi-unit driver. The server expects to translate a logical ZTAPE which must contain the name of the ZTAn: unit that it is expected to get to. The remote program that accesses the tape still does not get into kernel mode to read the tape position for the real tape. What I expect is that a DECnet object that runs each ZT unit on a machine does an assign to logical ZTAPE before running the ztns2 program so the server will find the correct zt unit on the machine that needs remote tapes. ZTdriver works nicely on VMS 5.4 and 5.5. Glenn Everhart 6/7/93 : Additional mods added by Bob Marshall : o Added RMT.COM to be run by the user on the "ZT" side (i.e., the side without the tape drive). Automates use of the software. o Added RMT_OBJECT.COM, and DECNET object that resides on the side with the real tape. RMT.COM communicates with RMT_OBJECT.COM. RMT_OBJECT does everything on the real-tape side, obviating the need for the user to log into the real-tape side. o Modified ZT2.C and ZTNS2.C to pass the name of the ZT device, since this is a variable piece of information (ZTA0, ZTA1, ZTA2, or ZTA3). o Added the FORTRAN (sorry) program ZT2_FORCEX which finds the process that is running ZT2 and does a $FORCEX on it. Installation instructions in INSTALL.TXT. Bob Marshall marshall@nebula.ssd.lmsc.lockheed.com