HDTenEightyP/NetNews huggingface dataset:
From: henri@mitre.org (Henri Bulterman)
Subject: Re: wattcp building troubles...
Organization: The MITRE Corporation, McLean VA 22102
Date: Tue, 21 Jul 1992 17:20:55 GMT

> [Various netters have told tales of trouble in converting WATTCP from
>  Borland C to other C compilers...]
 
Just last week I went through the exercise of porting some WATTCP source
files to Microsoft C7.  (There is a complete MSC port in one of the
directories on the Waterloo machine, but it is slightly out of date.)
 
There's one section in WATTCP.H that you have to be sure to change.
This code occurs in the definition of the "Internet Header" structure:
 
   Borland:   unsigned hdrlen :4;
              unsigned ver    :4;
              byte     tos;
 
   MSC:       unsigned hdrlen :4,    /* Note commas */
                       ver    :4,
                       tos    :8;
 
Until I made this change, Erick's excellent SMTPSERV program was
dead in the water.  I figured this out by comparing the new WATTCP.H
to the older version in the UofArizona MSC port.
 
Hope this information proves useful to somebody!
 
Henri Bulterman
The MITRE Corporation
henri@mitre.org
From: tim@mentor.cc.purdue.edu (Timothy Lange)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Mail/News w/ NFS.
Keywords: nfs mail news NNTP SMTP POP
Date: 21 Jul 92 14:57:04 GMT
Organization: Computing Center, Purdue University

I am using Beame & Whiteside NFS which also can appear to be PC-NFS
and FTP's nfs product (protocol stack emulators??).  Anyway, I'm
looking for a mail program that will allow me to read and send mail
via a POP server we have running on a unix box and news via NNTP while
I have my nfs shells loaded and running.  The machines we have nfs
exports on are NOT the machines that provide mail and news, I have to
use POP/SMTP and NNTP.

Let me know if you have heard of such a thing, thanks...

-- 
Tim Lange.

Purdue University Computing Center      1408 MATH Building
West Lafayette, IN  47907-1408          317-494-1787
Xref: sparky comp.protocols.tcp-ip.ibmpc:4412 comp.sys.novell:6026
From: srivasan@ucs.orst.edu (Anil Srivastava)
Newsgroups: comp.protocols.tcp-ip.ibmpc,comp.sys.novell
Subject: Help with Novell's ODI drivers
Date: 25 Jul 92 04:51:35 GMT
Article-I.D.: CS.1992Jul25.045135.21123
Reply-To: anils@prism.cs.orst.edu
Organization: Department of Computer Science - Oregon State

Hi folks,

This is probably a FAQ. I have just started the process of migrating
from Crynwr Packet Drivers to Novell's ODI drivers for reasons too numerous
to enumarate here, but I would really love to keep using my favourite PD
applications like WINQVTNET and Trumpet.  Is there a way to do that, and if
yes how do I go about it? 

Would really appreciate any responses, either to this group or by e-mail.

Thanks in advance...
-- 
Anil Srivastava                       *   anils@{prism,mist,storm}.cs.orst.edu
Grad(ual) Student in Computer Science *   (503) 737-3802  -  VOICE
Oregon State University               *   (503) 737-4890  -  FAX
From: rcq@FTP.COM (Bob Quinn)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Help needed with FTP's TCP/IP and 486DX/50
Date: 23 Jul 92 15:00:04 GMT
Reply-To: rcq@ftp.com
Distribution: world
Organization: The Internet

Hello Andrew!

>   Software:
>   FTP Software's TCP/IP pkg v2.15, using ipcust.sys and ifcust.sys
>     Adapters: STB QuickVGA combo card; includes SuperVGA, IDE controller,
>
>   Basically, everything works fine (eg, ping.exe, finger.exe, tnglass.exe,
>   etc) EXCEPT tn.exe (telnet) and rloginvt.exe (rlogin/vt100 protocol).
>   -- 
>   Andrew White                  |  Dod #0584
>   sabre@quantum.sas.upenn.edu   |  '82 Honda Sabre v45       

We at FTP are aware of the problem and have a fix.  The problem is
that the TSENG chipset in your STB Video card doesn't like the code
we use to detect what video card is in use.  We have versions of
these programs that have an option to suppress use of this video
detection code, thus avoiding problems.  You can call our support
department to get updated versions.

Regards,

--
 Bob Quinn                                             rcq@ftp.com
 FTP Software, Inc.                                  Wakefield, MA

Newsgroups: comp.protocols.tcp-ip.ibmpc
From: flog@open.ch (Florian Gutzwiller)
Subject: Who does TVP/IP over PC Broadband Cards ?
Reply-To: flog@open.ch
Organization: Swiss Federal Institute of Technology (ETH), Zurich, CH
Date: Mon, 27 Jul 1992 19:53:18 GMT


Does the media 'Broadband' itself allow something like TCP/IP to be run on ? If  
yes are there products Cards/Drivers that would allow to do so and make the  
broadband look like ethernet. If not are there low cost solutions to replace  
expensive Applitek equipment (Broadband-Ethernet bridge).

Thanks

--
Florian A. Gutzwiller	Phone:  +41-61-281-8600 
Open Systems AG		Fax:    +41-61-281-8603
Basel/Switzerland	E-Mail: flog@open.ch (NeXT)
Newsgroups: comp.protocols.tcp-ip.ibmpc,comp.protocols.tcp-ip,comp.dcom.lans.eth
From: femenia@power.ci.uv.es (Jose M. Femenia Herrero)
Subject: Re: Packet driver for BICC card?
Date: Fri, 31 Jul 1992 17:58:41 GMT
Organization: Universitat de Valencia, Spain
X-Newsreader: Tin 1.1 PL4

michel@neptunus.rivm.nl (Michel van Best) writes:
: Does anybody know where to find a packet driver for a bicc
: isolan card (4110 or 4110-2)?
:
: Thanks Michel
: --

Yes, you can find it in the Clarkson PD package available from
grape.ecs.clarkson.edu (/pub/ka9q) or in others archives.
The drivers name are ISOLAN.COM for the 9.1 PD version.
We have a oldest version (MBICCPD v.1.0) that seem work fine with NCSA tn3270
and with PC/TCP Software.
--
Jose Miguel Femenia Herrero        Internet: femenia@graf.ci.uv.es
Servei d'Informatica               EARN:     FEMENIA at EVALUN11
Universitat de Valencia            X400:   S=femenia;OU=vm;OU=ci;O=uv;P=iris;
46100 Burjassot (Valencia) SPAIN           A=mensatex;C=es
From: STEIN_A@mscf.med.upenn.edu (Alan D. Stein)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: SLIP questions...
Summary: HELP!
Keywords: nslookup, ping, wattcp, etc.
Date: 27 Jul 92 05:11:38 GMT
Distribution: usa
Organization: Club (Penn) Med


Apologies if any of this is repititious (I didn't see a FAQ) or otherwise  
idiotic:

1)  I am working off a newly established SLIP service at my school.  I'm 
interested in obtaining PC clients that support this device type (6, most 
software seems to support only ether-type (1) devices).  Notably, I'm looking
for NSLOOKUP.  Does this pc client exist anywhere?  What about a network 
time client (PDCLKSET only supports ether-type devices)? 

2)  I'd like to write my own clients.  Can someone point me toward a TCP/IP 
library that supports SLIP (I use SLIP8250)?  Borland C(++) is the language 
of choice.  A PING client as a demo would also be incredibly helpful. 
(WATTCP only seemed to support ether-type devices, is SLIP support 
difficult to add?)

Thanks for all help offered.  I will summarize replies in a post if they are 
email'd to me.
 
	Al

I'd use etherslip, but it seems to drop packets here and there with 
occasional errors.  Isn't the SLIP/SLIP8250 implementation cleaner than
the ETHER/ETHERSLIP pair anyway?
------------------------------------------------------------------------------
don't even think it...
------------------------------------------------------------------------------
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: donp@novell.com (don provan)
Subject: Re: Exalan packet driver
Organization: Novell, Inc., San Jose, California
Date: Tue, 28 Jul 1992 17:06:16 GMT

In article <9207281314.AA05292@ftp.com> jbvb@ftp.com writes:
>    ... it's convenient to overlook the fact that one of the first actions
>    taken by Novell when they bought Excelan was to sell off the EXOS205
>    product line....
>
>Two years is "one of the first actions"?

I'm sorry, but your information is incorrect.  Novell bought Excelan in
the summer of 1989 and the EXOS 205 product was sold to FTC in early
1990.  Pretty quick for selling off a hardware line, i'd say.  Perhaps
you're being confused because Novell continued to sell the EXOS 205 as
part of its LAN WorkPlace for DOS package until 1991.

						don provan
						donp@novell.com
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: eengelke@sail.uwaterloo.ca (Erick Engelke)
Subject:  several subjects on my mind
Organization: University of Waterloo
Date: Tue, 28 Jul 1992 04:12:34 GMT

Anyone in need of a fast freeware FTP program, get ours from
sunee.uwaterloo.ca [129.97.50.50] in pub/wattcp/ftp.zip
It's been tested with a plethora of other systems and has
features and speed unavailable on the other free FTPs.

Several people have mentioned having difficulty compiling/linking WATTCP
code.  Many more people have written in saying they found no difficulty
with any of the Borland versions and others found simple solutions to
what first seemed a difficulty.

The most common solution was to look at the options in *my* makefiles
(eg. apps/makefile) and copy them, or recompile the libraries with the
same options you plan to use.  But do not mix compiler options, that
don't work! 

The MSC incompatible things mostly stem from slightly different function
names (eg. bcopy), MSC's broken bitfields (that's why Ping didn't work
Joe), and MSC's weird un-C-like MK_FP macro.  If someone has a spare
license of MSC 6 or greater and wants to donate it, I will endevour to
make the source MSC compatible and keep it that way.  But I need all the
manuals and the compiler.

Erick
-- 
Erick Engelke					  Engineering Computing
						 University of Waterloo
Waterloo TCP Architect		 erick@development.watstar.uwaterloo.ca
From: jpc@avdms8.msfc.nasa.gov (J. Porter Clark)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Jumpers for Novell NE1000 board
Date: 21 Jul 92 14:12:13 GMT
Organization: NASA/MSFC

Help!  Our computer repair guys (don't get me started about them!)
substituted a Novell NE1000 board sans documentation for a 3Com 3C503
board.  They have not a clue about jumper settings on this board ("It
should work just fine like it is."  Aughh!!!) and I'm desperate.  I'm
trying to get this working with NCSA telnet with a ne1000 packet
driver.

Maybe we should CFD a "comp.hardware.jumpers" newsgroup?
--
J. Porter Clark    jpc@avdms8.msfc.nasa.gov or jpc@gaia.msfc.nasa.gov
NASA/MSFC Communications Systems Branch
From: cctr132@csc.canterbury.ac.nz (Nick FitzGerald, CSC, Uni. of Canterbury, NZ)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: 3COM503 & Clarkson
Date: 30 Jul 92 12:10:34 +1200
Organization: University of Canterbury, Christchurch, New Zealand

In article <1992Jul27.043024.17682@ddsw1.mcs.com>, karl@ddsw1.mcs.com
(Karl Denninger) writes:
> In article <1992Jul27.112627.6058@csc.canterbury.ac.nz>
cctr132@csc.canterbury.ac.nz writes:
[that's me]
>>Next, 16-bit VGA cards give the 3C503 card hell.  You either have to set
>>the VGA's jumper that forces it to 8-bit operating mode or put it in an
>>8-bit slot.
> 
> That's funny, I run a 3c503 in a 16-bit slot AND have an Orchid Fahrenheit
> 1280 card in the machine too (also in a 16-bit slot).  Works perfectly.  I
> am using the packet drivers V9.4.0 with shared memory enabled.
> 
> However, my WD8003 card DID NOT work in this same configuration.  That's why
> I pulled it and went with the '503.

What can I say? - "One man's meat is another man's poison" ??

For the record, most of the machine's I deal with are "cut price,
el-cheapo" clones, which mostly have Trident chipset based VGA cards. 
Recently it has become a virtual necessity to put such cards into 8-bit
mode to get 3C503's to work in the same machine, regardless of shared
memory base address settings (except I haven't tried "disabled"). 
Limited experience with WD/SMC cards suggests that often this is
unnecessary in the same machine.

Oh to get my hands on an Orchid Fahrenheit!!!   8-)

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 Nick FitzGerald, PC Applications Consultant, CSC, Uni of Canterbury, N.Z.
 n.fitzgerald@csc.canterbury.ac.nz    (64)(3)  642-337 Voice,  642-332 FAX
From: brian@Novell.COM (Brian Meek)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: How to install FTP kernel with Desqview/X ?
Date: 31 Jul 92 01:52:31 GMT
Organization: Connectivity Products Group -- Novell, Inc

In article <Bs80xt.Fuw@helios.physics.utoronto.ca> stefan@helios.physics.utoronto.ca (Stefan Mochnacki) writes:
>From: stefan@helios.physics.utoronto.ca (Stefan Mochnacki)
>Subject: How to install FTP kernel with Desqview/X ?
>Date: Thu, 30 Jul 1992 21:27:29 GMT
>
>	We have a nasty problem in installing the FTP PC-TCP
>kernel which came with our DV/X distribution. The FTP stuff
>is on a seperate diskette but requires Quarterdesks INSTALL 
>programme to decrypt and install. But in order for that to happen
>INSTALL must detect the TCP/IP software to be already installed. ...
>Yes, Catch-22 !
>
>	If anybody has installed the Desqview/X with TCP/IP stuff
>as supplied by Quarterdesk, could you please let me know? I have
>some frustrated people here!
>
>	Am I correct in presuming that PC/TCP as supplied by
>Quarterdesk will support packet drivers?

I'm afraid you're incorrect in presuming that the PC/TCP kernel
is supplied by Quarterdeck at all.  Your "Network support option"
disk does not include any TCP/IP kernel code, only the drivers
that interface to pre-installed TCP/IP kernels from FTP Software 
or Novell.

Sorry.  

Tell you what...  since I feel pity for you in this predicament -- 
I'll let you in on a secret.

If you FTP to sjf-lwp.novell.com, and take a peek in the following
directory...

	~/lwp4dos/tcpip/*

...and combine those files with a proper ODI driver from ~/odi/dosup5.zip,
you should be able to puzzle out how to run DESQview/X with what you 
already have.  Call it a "test-drive" since the TCP/IP kernel found in
sjf-lwp.novell.com: ~/lwp4dos/tcpip/tcpup1.zip is really there as an 
update to people who already have a license to it.  If you like it...
buy it later and I promise not to sick our lawyers after you.

-- brian
___________________________________________________________________________
Brian Meek                      Novell, Inc. -- Connectivity Products Group
                                Internet mail:  brian@Novell.COM
From: dsc3jfs@nmrdc1.nmrdc.nnmc.navy.mil (Jim Small)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: FTP's tcp/ip
Date: 29 Jul 92 22:47:21 GMT
Organization: Naval Medical Research & Development Command

In article <9207291330.AA04971@ftp.com> jbvb@ftp.com writes:
>
>    ....  does ftp/ips 2.03 kernel support BOOTP, or does anyone know where

>dialer utilities, which should make things a lot easier.


Well, a little too late.  I've already found etherslip, slipdial, and
the wattcp bootp code and have them functioning as a unit.  
(It's not that I wouldn't like having your new kernel, it's just that 
this project is going to be used under the old site liscence of about
800 pcs, and by a site liscence for 800 pc's for even just your slip
kernel is going to be about what, $70 a pop?)

a month of summer hire salary is much cheeper even if the liscence 
was only $10 a pop

Not that the government is cheap or anything , (The scum only hired me
as a GS-4 Clerk typist salary)

-- 
I love the 3b2
The 3b2 is my friend.
From: ddl@burrhus.harvard.edu (Dan Lanciani)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Maximum UDP packet size
Keywords: UDP PCTCP packet size
Date: 30 Jul 92 03:36:02 GMT
Organization: Harvard University, Cambridge, MA

In article <1992Jul29.025917.1452@maccs.dcss.mcmaster.ca>, beame@maccs.dcss.mcmaster.ca (Carl Beame) writes:
| 	FTP's PCTCP is unable to IP fragment packets bigger than the network
| mss (~1400 over ethernet). Beame & Whiteside Software Ltd. TCP-IP contains
| an small PCTCP emulator which allows programs written for FTP's software
| library to run over BW-TCP/IP. Since BW-TCP supports fragmentation up to 
| ~16K, your program MIGHT run without modification over our TCP and use large
| UDP packets.

	Our TCP/2-DOS also includes an INT61 emulator and supports
larger-than-MTU IP packet sizes, so you have two possibilities of
running without modification.  (Odds are looking up :)  For further
info, contact Essex Systems (508) 532-5511 or send email.

				Dan Lanciani
				ddl@harvard.*
From: bharad@ASTRO.OCIS.TEMPLE.EDU (Bharadwaja Palakodety)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: (none)
Date: 24 Jul 92 22:40:01 GMT
Distribution: world
Organization: The Internet

I compiled netwatch and is running for sometime when the keyboard freezes for no
reasons. (sometime could be >30minutes <= 3hours)

Is there any similar bug you encountered ?

from: bharad@astro.ocis.temple.edu
From: cowen@acsu.buffalo.edu (Michael Cowen)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: News Group for tcp-ip.macintosh
Date: 31 Jul 92 14:01:58 GMT
Organization: UB

There is a newsgroup comp.sys.mac.comm which discusses tcp-ip related
matters for the mac.

	Mike Cowen
From: rocks@pyrope.NMSU.Edu (David C. Rocks)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: TN3270-e
Date: 22 Jul 92 01:07:53 GMT
Distribution: comp
Organization: NMSU Small Systems


	What is the difference between the "D" and "E" versions of Clarkson's
TN3270 packages?

			Dave Rocks
			rocks@nmsu.edu
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: swhite@tybse1.uucp (William C. "Spike" White)
Subject: Re: Can ""traditional"" comm programs talk TCP/IP?
Organization: Tybrin Corporation, Shalimar, FL
Date: Wed, 22 Jul 1992 05:22:19 GMT

In article <19JUL92.12414681@sklib.usask.ca> scott@sklib.usask.ca writes:
>I use NCSA Telnet on my PC to connect to remote sites for both telnet
>and ftp, but I miss having the features of my "traditional"
>communications packages i.e. ProComm, Telemate, Telix etc. For example I
>find not having the Telemate editor/backscroll/view windows available,
>with their cut and paste abilities, to be painful.
>
>So, I was wondering if anyone has adapted these programs to run with
>their network cards. I am using a 3com503, by the way.
>
>I know that the new version of Kermit can use TCP/IP but I'm not a great
>fan.
>
>Peter Scott <scott@sklib.usask.ca>

This may help. I had to do some research on running Reflection, a terminal
emulator package, on TCP/IP.

In the pre-Windows days, terminal emulator programs could
be written to be well-behaved, meaning they did the std. comm port call to
the BIOS, invoking DOS' int. srv. rtn. to actually go out and read and write
from the comm port. I believe this interrupt was called int 14. 

Good TCP/IP packages, such as Novell's LAN Workplace for DOS or FTP's PC/TCP, 
provided int 14 support.  This meant that they had a TSR which allowed you to 
read and write to a network connection exactly as if you were reading and 
writing to a serial port.  And they slipped in the address of THEIR routines
into the int. vector table, so when your well-behaved terminal emulation 
program made its read or write interrupt call, it was *REALLY* reading and
writing to the network connection.  It was blissfully unaware that it was
going across the network.

I'm sure I'm simplifying, but if your terminal emulator is well-behaved
(i.e., doesn't muck directly with the serial ports) and your TCP/IP package
provides this support, it should be just a matter of configuration.

And in these days of Windows, I'd expect to see the same trick pulled soon
with DLL (Dynamicly Linked Libraries). 

Also, the new version of Procomm Plus is supposed to have network support.

-- 
Spike White     Tybrin Corporation, Shalimar, FL | Moderation in all things --
swhite@afseo.eglin.af.mil                        | and abstinence in none! 
Disclaimer: I speak only for myself, not my employer. 
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: pkershaw@dce.com (Peter Kershaw)
Subject: Re: tn3270 for slip
Followup-To: comp.protocols.tcp-ip.ibmpc
Organization: DCE
Date: Mon, 27 Jul 1992 18:00:11 GMT

In article <1992Jul23.172134.19356@nmrdc1.nmrdc.nnmc.navy.mil>,
dsc3jfs@nmrdc1.nmrdc.nnmc.navy.mil (Jim Small) wrote:
> 
> could someone direct me to a tn3270 that will run off a slip driver

Frontier Technologies has an excellent DOS and integrated Windows TCP
application, that includes SLIP and TN3270, as well as all the other
Internet goodies. For further info or to receive a brochure, email
pkershaw@dce.com.

Peter Kershaw <pkershaw@dce.com>
Data Communication Engineering
2888 Bluff Street, Suite 161
Boulder, CO 80301
303-431-2233, 303-431-1140 fax, 303-829-5952 mobile
From: galew_a@cactus.org (Andy Galewsky)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Maximum UDP packet size
Keywords: UDP PCTCP packet size
Date: 28 Jul 92 21:45:07 GMT
Organization: Capital Area Central Texas UNIX Society, Austin, Tx


Hi,
    We have a system that is built on FTP software's PCTCP development kit
that uses UDP. Our problem is that we need to send packets larger than
the (apparent) 1400 byte limit for UDP packets under FTP's implementation.
So I have a couple of questions:
    * Does anyone know of a way to up this limit (FTP tech support says no)
    * Does anyone know of a library similar to FTP's that would permit us
      to have larger UDP packets?
    * Could we use some other network call to get packets that can be larger
      than this ?

			Thanks ever so much
		 	The Galewsky Brothers
  		        dan@crs.com
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: beame@maccs.dcss.mcmaster.ca (Carl Beame)
Subject: Re: FTP server needed
Organization: McMaster University, Hamilton, Ontario, Canada.
Date: Thu, 30 Jul 1992 02:48:52 GMT

In article <1992Jul29.174238.29258@murdoch.acc.Virginia.EDU> paw7w@fulton.seas.Virginia.EDU (Perry Alan David Wood) writes:
>I'm looking for an ftp server with the following features:
>
>1) Allow ftp login with a login id and password.  Once logged in, the usual
>   ftp commands should be available (get, put, binary, ascii, del, mkdir,
>   rmdir, etc.).
>
>2) Allow anonymous ftp login with access restricted to a directory or disk
>   partition.  The anonymous user should be able to "get" and "put" in
>   this directory.
>
>3) One login at a time is sufficient.
>
>4) Must work on a PC/XT.
>
>I currently use NCSA Telnet 2.3.  It satisfies #1,3,4, but not #2.
>
>Thanks!
>--
>Perry A. D. Wood            Bitnet: paw7w@Virginia
>University of Virginia      Internet: paw7w@Virginia.EDU

	Version 3.0 of BW-TCP due out in August does all of the above. The
password file has restrictions for up to 10 directory trees  per user with 
full Read, Write, Create, Modify, Delete and Execute permissions.

Carl Beame
Beame & Whiteside Software Ltd.
sales@bws.com
From: jbvb@FTP.COM ("James B. Van Bokkelen")
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Exalan packet driver
Date: 23 Jul 92 13:11:36 GMT
Reply-To: jbvb@ftp.com
Distribution: world
Organization: The Internet


    > Does anybody know if there is a packet driver for an Exalan(Exos)
    > ethernet adaptor?

    Don't know about the packet driver, but an ODI driver certainly exists and
    you can use the odipkt.com driver....works just fine...

Long ago, when it was politically correct (i.e. when they were doing business
with Microsoft and Novell hadn't bought them yet), Excelan did an NDIS driver
for the EXOS205.  It's known to work with DIS_PKT, and is available from
vax.ftp.com.  Since a packet driver would require loading code onto the board
somehow, and Excelan's support for vendors that used their "nx" OEM down-load
module vanished in 1988 or so, no direct-to-the board Packet Driver exists.

James B. VanBokkelen		26 Princess St., Wakefield, MA  01880
FTP Software Inc.		voice: (617) 246-0900  fax: (617) 246-0901