heh@duke.UUCP (Helen Harrison) (10/17/84)
Does anyone out there have a dup11 driver for 4.2? We have our own locally written rje software which has been running under version 7, using a dp11. We will shortly be getting a vax 750 on which to run 4.2. As our dp11 is thoroughly obsolete, we are getting a dup11. Unfortunately, I have found no 4.x driver for it. Ideally, the driver would talk IBM Bisync. Our package, "hasp", emulates a hasp workstation providing rje to an IBM computer running MVS. I would be interested in finding others who are doing UNIX to IBM communications. Any pointers would be greatly appreciated. Also, has anyone taken over the device driver list that Alan S. Watt used to maintain? Helen Harrison mcnc!duke!heh (919) 684-6058
long@ittvax.UUCP (H. Morrow Long) (10/22/84)
> Does anyone out there have a dup11 driver for 4.2? > There is a dup-11 driver included in a RSCS emulation package for Unix 4.2BSD called UREP (Unix RSCS Emulation Package). The software is available from Penn State University (psuvax1 on the net) for $150, but since you are affiliated with an academic institution you might be able to get them to send the driver for free. I would recommend the UREP package if you must communicate with IBM mainframes running "VM". We are still using the 4.1BSD version of the software so I can't comment on the quality of the 4.2 driver (which I am waiting for). > Also, has anyone taken over the device driver list that > Alan S. Watt used to maintain? > > > Helen Harrison > mcnc!duke!heh > (919) 684-6058 Alan S. Watt worked at this site until this spring, I have taken over many of his duties. I think we would be willing to support the device driver list for the USENET community if there is sufficient interest. H. Morrow Long {ucbvax!decvax, yale, ittral} !ittvax!long
chris@umcp-cs.UUCP (Chris Torek) (10/23/84)
* I would recommend the UREP package if you must communicate with
IBM mainframes running "VM". We are still using the 4.1BSD
version of the software so I can't comment on the quality of the
4.2 driver (which I am waiting for).
The 4.2 driver is really the same as the 4.1 driver (but the names have
been changed to protect the innocent, I mean, to comply with the 4.2
uio code). I've been told that the driver is actually pretty trivial;
the hard part is figuring out what the IBM software was sending over
the sync line (and it is NOT what is given in the IBM manuals, even if
you can get hold of them).
In other words, whatever the quality of the 4.1 software is, is the
quality of the 4.2 software.
--
(This mind accidently left blank.)
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (301) 454-7690
UUCP: {seismo,allegra,brl-bmd}!umcp-cs!chris
CSNet: chris@umcp-cs ARPA: chris@maryland