Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!amdcad!ames!ucbcad!ucbvax!OSWEGO.OSWEGO.EDU!beadel
From: beadel@OSWEGO.OSWEGO.EDU (Edward.F.Beadel@oswego.oswego.edu, Jr.)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Need TCP/IP on RSTS/E
Message-ID: <8801072342.AA14610@oswego>
Date: 7 Jan 88 23:42:39 GMT
References: <8801050739.AA01158@GAAK.LCS.MIT.EDU>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 22

>> 					... The problem with RSTS is
>>    that DEC has never done anything to ease user-written device drivers,
>>    and there was nothing like the VMS XE driver to allow user programs to
>>    get at the raw ethernet the last I knew.
>  I heard rumors (shortly after you left the RSTS community James, and
>  shortly before I did) that such an interface was in the offing.  I
>  have not heard what came of that.

In the RSTS/E V9.4 Programming Manual (DEC Order Number AA-EZ09A-TC {
including AD-EZ09A-T1,T2}) the aboved problem is addressed: " In order to
increase the flexibility of Ethernet on RSTS/E, DIGITAL has provided a
direct interface to the Ethernet data link layer for RSTS/E users. This 
interface resembles the interface provided for the DMC/DMR communications
devices, and can be programmed with or without DECnet/E on the system."
(page 11-3)

This allows use of both UNIBUS controllers (DELUA and DEUNA) as device XE:
and the Q-bus controller (DEQNA) as device XH:.

		Edward F. Beadel, Jr.
		RSTS SIG Steering Committee
		UNIGIG rep to DECUS PDP-11 Task Force