HDTenEightyP/NetNews huggingface dataset:
From: gts@UCLINK.BERKELEY.EDU (Greg Small)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Transfer Speeds from PC to SPARC 10
Date: 21 Dec 92 04:47:08 GMT
Reply-To: gts@uclink.berkeley.edu
Organization: The Internet

uclywss@ucl.ac.uk (Mr Warwick Smith) writes:
>We need to periodically copy 1 gigabyte files from a PC to Sun SPARC 1
>typically 85 - 160 kbytes/sec.
>The PC is a 486 33Mhz using a BICC 16 bit Ethernet card with MPS 4.2
>and PCNFS 4.0. File transfer speed on its local disk is 250 Kbytes/sec
                                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Looks to me as though your maximum possible rate is 250 Kbytes no matter
how fast the network is.  I suggest trying "COPY /B GIGAFILE.XXX NUL" on your
PC to measure the ultimate rate that it can deliver data to the network.
The speed may depend on just how fragmented your PC disk is (although that
may not be a problem on a 1 gigabyte disk ;-).

Greg Small                                           1-510-642-5979
Personal Computer Networking & Communications        gts@violet.Berkeley.EDU
Workstation Software Support Group, IST/WSS          216 Evans Hall
University of California, Berkeley, Ca 94720         1-510-643-5385 (Fax)
From: gnatowsd@mailgw.er.doe.gov (Dennis_Gnatowski)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: PING for NCSA
Date: 16 Dec 1992 10:04:40 -0600
Organization: UTexas Mail-to-News Gateway
NNTP-Posting-Host: cs.utexas.edu

Is there a PING executable that will work with NCSA Telnet?  If so, is it
available via Anonymous FTP?

-----------------
Dennis Gnatowski
gnatowsd@mailgw.er.doe.gov


Newsgroups: comp.protocols.tcp-ip.ibmpc
From: ricardo@ing.puc.cl (Ricardo Schmutzer von Oldershausen)
Subject: Packetdriver for IBM PS/2 Adapter/A ?
Organization: Universidad Catolica de Chile
X-Newsreader: TIN [version 1.1 PL8]
Date: Fri, 18 Dec 1992 14:10:37 GMT

We have been trying to connect a IBM PS/2 to the Ethernet.  I do not
know if there exists a Packetdriver for a IBM PS/2 Ethernet Adapter/A
(microchannel) or a ODI driver.  Any suggestions are welcome.

Thanks,
	Ricardo
--
+-----------------------+--------------------------------+--------------+
| Ricardo A. Schmutzer | Internet: ricardo@ing.puc.cl    | Conectividad |
| PUC, Santiago, Chile |           ricardo@lascar.puc.cl | Distr. Comp. |
+----------------------+---------------------------------+--------------+
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: jiliu@silver.ucs.indiana.edu (Jian Liu)
Subject: Re: NCSA Telnet for SVGA Monitor
Reply-To: tkolasny@scholia.wbme.jhu.edu
Organization: Indiana University
Date: Sat, 19 Dec 1992 01:00:28 GMT

Try auto

Jian
From: tony@scotty.dccs.upenn.edu (Anthony Olejnik)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Q: NUPOP over SLIP and where does it store the IP configuration
Date: 11 Dec 92 21:16:16 GMT
Distribution: usa
Organization: University of Pennsylvania

Q: How can I configure the IP address (assigned to the particular
   SLIP port that I dial into) into NUPOP?
 
   Using an MSKERMIT script and an AWK (for DOS) script, I'm able
   to extract the IP addresses presented to me by my SLIP server
   and redirect them to an ASCII config file.  Thus, any applications
   that obtains their configuration from an ASCII file (such as
   MSKermit v3.12, Trumpet, PCTCP, etc.) can be configured on the 'fly'.
   NUPOP doesn't seem to keep its configuration in an ASCII file.
   Thus, I'm assuming that its stored in the binary somewhere.  

Q: Does NUPOP store its TCP/IP configuration in an ASCII file? 
   If so, what is the name of the file.

Thanks in advance.

--tony
From: overberger@gw.wmich.edu
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Searching for TFTP server
Date: 18 Dec 92 10:41:16 EST
Organization: Western Michigan University

YourIn article <92352.122717HOLTZMAN@SJUVM.BITNET>, Michael S. Holtzman <HOLTZMAN@SJUVM.BITNET> writes:
> Greetings.  I am desparately seeking a TFTP server for a PC.  If anyone
> can point me in the right direction, etc.
> 
> Please respond directly.
> 
> My eternal gratitude....


You might give a company called SONIC SYSTEMS a call. They have a BOOTP nlm
and a TFTP nlm that is part of their Macintosh remote boot package, TDM.

Their # is 408-736-1900

Good Luck !
From: nelson@crynwr.com (Russell Nelson)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: TCP/IP and Windows for Workgroups 
Distribution: world
Date: Wed, 16 Dec 92 17:56:55 GMT
Organization: Crynwr Software

In article <1992Dec15.210651.28387@microsoft.com> jallard@microsoft.com writes:

   In article <723836303snx@crynwr.com> nelson@crynwr.com (Russell Nelson) writes:   >
   >James, here's my challenge to you: run an anonymous FTP server over
   >Microsoft's TCP/IP stack, put something popular on that server, and
   >announce it all over the Internet (don't forget comp.archives and
   >archie).  If your server serves all comers, it's worthy of the name
   >TCP/IP.  Until then...

   What an excellent idea!

Glad you like the idea.  If you *really* want to give it a stress
test, contract with Sports Illustrated to produce GIF images of the
swimsuit issue.  You could even make it a big PR deal, saying how
Microsoft was conducting research into image distribution over the
Internet.

:)

-russ <nelson@crynwr.com> What canst *thou* say?
Crynwr Software           Crynwr Software sells packet driver support.
11 Grant St.              315-268-1925 Voice  |  LPF member - ask me about
Potsdam, NY 13676         315-268-9201 FAX    |  the harm software patents do.
From: Greg.Reinacker@FtCollins.NCR.COM
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: PC/TCP 2.1 & Xvision 4.1
Date: 17 Dec 92 14:01:04 GMT
Reply-To: Greg.Reinacker@FtCollinsCO.NCR.COM
Organization: NCR Microelectronics, Ft. Collins, CO
In-reply-to: catcim@eig.unige.ch's message of 14 Dec 92 12:50:21 GMT

>>>>> On 14 Dec 92 12:50:21 GMT, catcim@eig.unige.ch said:


-> I have installed FTP's PC/TCP release 2.1

-> I also installed X-Vision 4.1, but unfortunatly I don't bring them to
-> work together. The local dealer tells me that the communication part of
-> X-Vision only supports PC/TCP release 2.05.

-> The schedule for a new release of the communication part is to vague,
-> has anyone a better experience or a clearer time schedule to solve the
-> problem.

I am using XVision 4.1 and PC/TCP 2.1 with no problems at all.

I used the VW Communications driver for PC/TCP 2.05, and everything
seems to work fine.

One big problem I had, tho -- if I used the ETHDRV -m command to load
the driver into expanded memory, Windows would lock up regularly when I
was using XVision...maybe this could be your problem also?

Feel free to e-mail me if you still have problems...

--
--------------------------------------------------------------------------
Greg Reinacker                          (303) 223-5100 x289
NCR Microelectronic Products Division   VoicePlus 464-1289
2001 Danfield Court                     Greg.Reinacker@FtCollinsCO.NCR.COM
Fort Collins, CO  80525
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: paulf@manor.demon.co.uk (Paul Fawcett)
Subject: Switch on your modem !
Distribution: world
Organization: UDI
Date: Sun, 20 Dec 1992 03:02:22 +0000





After quiting a Kermit Telnet session using a SLIP packet driver
any further attempt to persuade the modem to redial results in 
failure with the message 'Turn on your modem and redial'. This
will occur even if the SLIP driver has been removed with a RELEASE
TSR utility. Other comms software also refuses  to reconnect in
such circumstances.


My question is what has the SLIP driver done to persuade everything
else that the modem is *off*, and is there a fix other than a reboot.



Thanks. 


--------------------------------------------------------------------------
Paul Fawcett                 |      Internet: paulf@manor.demon.co.uk
London, UK.                  |                tenec@westminster.ac.uk
--------------------------------------------------------------------------  
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: mcgrath@ncifcrf.gov (Connon Mcgrath)
Subject: netmanage chameleon tcp-ip problems
Organization: Frederick Cancer Research and Development Center
Date: Fri, 18 Dec 1992 00:51:22 GMT

To users of the Netmanage Chameleon package.

I wonder if you have come across any performance problems.  We have.

On a basically VERY underused network segment, we see around a 100 kb/s
throughput using a variety of DOS-based FTP's (NCSA, Excelan), both incoming
and outgoing with respect to the DOS machine.  This is about the same as
some 386 and 486 SCO System V (unix) machines we have on this segment.
Out of Chameleon, however, this drops to between 8-20 kb/s, but only on the
outgoing side relative to the PC running Windows.  Incoming speeds are
comparable to the DOS-based or unix speeds. 

We have been in touch with Netmanage on this and have even been called
a beta-site.  They tell us that the TCP/IP buffers have been set up at
4KB incoming and 1KB outgoing and that this is not adjustable!  Of course,
it would be wonderful if this were allowed in a future release, but that
doesn't move a series of 10MB *.tif files off my pc any faster today.  We can,
and will, drop back to DOS for large data transfers like this, but it would be
nice to work on other things while that is going on.  In other words, I'd like
to stay in Windows all day if I could.

Is there anything in Windows that we can do to improve performance, i.e.
increase a priority or permanently allocate RAM to an application?  Our
knowledge in this area is lacking.  Any ideas?
###########################################################################
Connor McGrath                        #
Scientific Applications Analyst       #
NCI-FCRDC AIDS Vaccine Program        #      "Make up your mind."
Fort Detrick Bldg 560 Rm 32-93        #
Frederick, MD 21702                   #
mcgrath@avpvx1.ncifcrf.gov            #
301-846-1408                          #
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: maw@netcom.com (Martin Walker)
Subject: NCSA / KA9Q for OS/2?
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Date: Sat, 12 Dec 1992 15:19:50 GMT

Has anyone ported NCSA Telnet 2.3.05 or the latest KA9Q to OS/2?. If so,
please could you tell me how you did it, what changes were made etc.
I have written a full ANSI emulator for KA9Q with all the functionality
of an SCO console, and I would like to have this availible under OS/2
as well. I would prefer it if I could get NCSA to work on OS/2, as it is
so much faster, but KA9Q would do as well.

I gave the source for my emulator to Phil Karn, but I haven't had a reply
from him, nor have I seen any new versions which incorporate the changes
I made.

Any help at all would be appreciated. Basically, any TCP/IP package which
compiles under both DOS and OS/2, and for which the source is availible,
would do very nicely.

Thanks in advance,
Kean Johnston,

via ...

-- 
Martin Walker               |  "One way to stop a runaway horse
++27-12-344-3973 (w)        |   is to bet on him"
++27-12-998-7263 (h)        |   maw@netcom.com
Pretoria, South Africa      |   martin@paradigm.CO.ZA
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: pflaum@world.std.com (Greg M Pflaum)
Subject: Re: Winsock available?
Organization: The World Public Access UNIX, Brookline, MA
Date: Sun, 20 Dec 1992 04:36:18 GMT

In article <1gt994INNbnh@spool.mu.edu> John@Johns.FrontierTech.COM (John F. Moehrke) writes:

> We at Frontier Technologies have been shipping a Winsock compliant
> TCP/IP kernel for over a year now. And in January will be shipping 
> the Windows Sockets Version 1.1 compliant version just approved
> by the winsock committie.

Let me guess... Marketing?  It is disappointing to see Frontier join
some other WinSock vendors in truth-stretching.  Let's take a look at
appendix C of the WinSock spec v1.1 draft 2:

 C.  Background Information

            C.1 Origins of Windows Sockets
            The Windows Sockets project had its origins in a Birds Of A
            Feather session held at Interop '91 in San Jose on October
            10, 1991.  A committee was established, and an intensive
            debate via email resulted in the creation of a first draft
            specification, which was largely based on submissions from
            JSB and NetManage.  This draft, and issues arising from it,
            were debated at a committee meeting hosted by Microsoft in
            Redmond, WA on December 9, 1991.  Following further email
            discussions, a working group was established to develop the
            specification into its current form.

The result of that work was the Windows Sockets spec, the first 
official version of which was v1.0 Rev.A, dated June 11, 1992.  So, 
it would be very difficult to ship a "Winsock compliant TCP/IP kernel" 
over a year ago when the definition wasn't final until 6 months ago. 
(Of course, WinSock says nothing about _kernels_; it defines the API.)

Frontier _was_ the first vendor I know of to ship WinSock, so there's
hardly any need to exagerate the accomplishment.  (Though I do prefer
a revisionist history over another vendor who claimed for months to be
shipping WinSock, though no one seems to have received it until much
later.)

Why am I so touchy about this?  As an application vendor, I don't enjoy
hearing my customers say "Why don't you support WinSock yet?  I hear
it's been shipping for over a year."

Greg

Newsgroups: comp.protocols.tcp-ip.ibmpc
From: gwe@cbnews.cb.att.com (george.w.erhart)
Subject: Re: netmanage chameleon tcp-ip problems
Organization: AT&T
Date: Sat, 19 Dec 1992 01:39:14 GMT

In article <BzFJpM.E3I@ncifcrf.gov> mcgrath@ncifcrf.gov (Connon Mcgrath) writes:
>Out of Chameleon, however, this drops to between 8-20 kb/s, but only on the
>outgoing side relative to the PC running Windows.  Incoming speeds are

FYI, I have reviewed many Windows TCP/IP packages and the top performer for
FTP under Windows was Pathway Access for DOS, from Wollongong. It topped
out at around 34-35 KB/s. Generally, under Windows, FTP is SLOW. 

By the way, I am also seeing 30KB/s from Chamemleon ... you should check out
Windows NT ... same hardware, 200KB/s. Right now, I reboot to NT for any
really large file transfers (like PhotoCD image files, etc).


-- 
George Erhart
AT&T Bell Laboratories
Columbus, Ohio
att!archie!gwe or gwe@archie.att.com
From: john7@garfield.cs.mun.ca (John Mackey)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: SMC 8013EPC
Date: 20 Dec 92 01:12:58 GMT
Distribution: na
Organization: CS Dept., Memorial University of Newfoundland

This topic has been bounced around for some time now, but I am NOT sure
that a definitive answer has appeared (I hope to be corrected!):

What is the correct packet driver to use for a SMC 8013EPC card?
This is also referred to as an Elite 16 PLUS.

Here is the confusing issue:

SMC bought this design from Western Digital, who called the card
the 8013EP.  The correct packet driver for the WD card is the
commonly available wd8003e.com that you can get from just
about anywhere (up to Version 10.X, I believe).

HOWEVER, either SMC or WD changed the chipset on the board.  The old chip
(a 8390, if my memory serves correctly) is VERY common, and is used
in a variety of different ethernet boards.  The SMC version of the card
uses the 83C690 chip (again, don't quote me on the number).  In
a readme file on the "Superdisk" you get with the card, it says that you
should NOT use "older" drivers; only the "new" ones contain fully functional
support for the new chipset.

Our facility has a ~20 node LAN with a mix of DOS PCs and ISC UNIX boxes.
We are currently using the wd80003e.com packet driver in the DOS PCs (some
of which have real WD cards; others are SMCs; there are a small number of
cards from other manufactures).  The PCs with the SMC cards occasionaly
(once per week, on average) ALL go "deaf" to the network simultaneously
and need to be rebooted.  It is NOT the TCP/IP stack that is causing
this (tried a variety, including NCSA, B&W, FTP software, etc.).  Given
that we have UNIX machines using the SMCs with no apparent problems, I
suspect the packet driver.

My question is this: does the wd8003e driver support the new chipset found in
the SMC cards?  If so, what version introduced it?  If not, what is the
correct packet driver to use?

An incidental note:  the "Superdisk" contains a packet driver that I don't
like for two reasons.  First, it is "non-standard" compared with the other
packet drivers available in the public domain (different command line
switches, etc.)  Second, I have not been able to get RARP working with it.
"Hardcoding" the IP addresses at each PC is just not an option for me -
things are just too dynamic for that.

Comments or suggestions?
John
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: jiliu@silver.ucs.indiana.edu (Jian Liu)
Subject: Re: Packetdriver for IBM PS/2 Adapter/A ?
Reply-To: ricardo@ing.puc.cl
Organization: Indiana University
Date: Sat, 19 Dec 1992 01:04:37 GMT

ricardo@ing.puc.cl (Ricardo Schmutzer von Oldershausen) writes:
>We have been trying to connect a IBM PS/2 to the Ethernet.  I do not
>know if there exists a Packetdriver for a IBM PS/2 Ethernet Adapter/A
>(microchannel) or a ODI driver.  Any suggestions are welcome.

I have been using odi drivers on model 55sx and 50z all the time. In the
net.cfg, all you need to enter is the ethernet card driver type. Let me
know if you want to see a copy of our net.cfg.

Jian
From: nelson@crynwr.com (Russell Nelson)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: 3c509 PD Telnet/FTP SW ??? 
Distribution: world
Date: Fri, 11 Dec 92 18:32:52 GMT
Organization: Crynwr Software

In article <1992Dec11.204559.12617@scf.loral.com> andres@scf16.scf.loral.com writes:

   Pardon my ignorance, but where do i find the [3c509] packet driver

Well, there isn't a released one, but the Sixth BETA copy is
available by FTP from cheetah.ece.clarkson.edu.  It works for a lot
of people.  If you try a copy of it, please tell me if it works for
you.

   and what/how do I set-up the config.tel to look like ???

hardware=packet.  Comment out the other hardware-related parameters.

-russ <nelson@crynwr.com> What canst *thou* say?
Crynwr Software           Crynwr Software sells packet driver support.
11 Grant St.              315-268-1925 Voice  |  LPF member - ask me about
Potsdam, NY 13676         315-268-9201 FAX    |  the harm software patents do.
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: ih96@sol.acs.unt.edu (Yu Zhi)
Subject: Where I can ftp qvtnet 3.03?
Organization: University of North Texas
Date: Tue, 15 Dec 1992 21:30:45 GMT

Sorry if it is in FAQ, but I cannot find FAQ for this group. I have
qvtnet 2.3 for windows running here. I heard version 3.03 is available
, could someone tell me where can I get them? Another question, I want to
setup mail server but I don't know if there is any public domain POP3
server for windows available. Thanks for your time and kindness!
From: ashok@meds38956.cwru.edu (Ashok Aiyar)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: pop2/3 server for PC
Date: Mon, 14 Dec 1992 19:22:15 GMT
Organization: CWRU School of Medicine
Distribution: world
NNTP-Posting-Host: axa12-slip.dialin.cwru.edu
Summary: yes, POP2/3 servers exists for the PC!
Keywords: POP2 & POP3 servers, Ka9Q NET/NOS

In article <kurz.1.45.0@ipa.fhg.de> kurz.1@ipa.fhg.de (Hermann Kurz) writes:
>
>is there a pop2/3 *server* for the PC? 

Most Ka9Q NOS packages for the PC include POP2/POP3 *servers*.  For 
instance, Pa0GRI NOS 2.0m has both POP2 and POP3 servers.  In most of the 
NOS packages, the implementation of POP2 is faulty and leaves POP2 clients 
hanging as it abruptly disconnects.  In contrast, the implementation of POP3 
is robust, and works very well with both Mac and PC POP3 clients such as 
POPmail/PC, POPmail/MAC, Eudora, and NuPOP.

I am using WG7J NOS 1.06 as this version of NOS is extremely stable, and 
performs well.  It includes MX lookup for outgoing SMTP mail and has an 
internal POP3 server.  It works with Crynwr packet drivers.

This version of Ka9Q NOS (and others) is available from "ftp.ucsd.edu" in 
the directory /hamradio/packet/tcpip.  I believe that a newer version 1.07 
is being released by the author today.

For more information, contact me by e-mail.
----------------------------------------------------------------------
                              Ashok Aiyar 
                      Department of Biochemistry
                       CWRU School of Medicine
----------------------------------------------------------------------
From: nelson@crynwr.com (Russell Nelson)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Pocket Lan Adaptors and Packet Drivers... 
Distribution: world
Date: Wed, 16 Dec 92 17:41:53 GMT
Organization: Crynwr Software

In article <1992Dec16.145131.3169@magnus.acs.ohio-state.edu> GAYNOR@agvax2.ag.ohio-state.edu writes:

   Has anyone found and/or written a Packet Driver for the Solectec
   pocket LAN adaptor?  The manufacturer "claimed" to have one, which we
   later found out was simply a piece of code that requires PC/TCP (which
   we don't use).  Further calls to their Tech Support have resulted in
   the revised statement that they have not written a apacket driver for
   it.

Hmmm...  I've seen their driver disk, and they do indeed have a
packet driver for it.  I don't know why their tech support is so
clueless, but <ahem> that happens sometimes with tech support people. :)

   On a similar subject, does anyone have reccomendations on a pocket LAN
   adaptor (the kind that you attach to LPT1) for which a packet driver
   exists, and seems to work well with apps such as NCSA Telnet, POPmail,
   Gopher, and other packet-driver based apps?  Again, thank you.

Well, I wouldn't recommend Xircom because they distributed my packet
driver for a year in violation of the copyright.  I'd suggest one of
the following companies:

D-Link - 714-455-1688
Solectek - 619-450-1220
Accton - 415-266-9800
Compulan - 408-922-6888

Please tell them that Russell Nelson sent you because of their past
support for packet drivers and free software in general.

-russ <nelson@crynwr.com> What canst *thou* say?
Crynwr Software           Crynwr Software sells packet driver support.
11 Grant St.              315-268-1925 Voice  |  LPF member - ask me about
Potsdam, NY 13676         315-268-9201 FAX    |  the harm software patents do.
Xref: sparky comp.protocols.tcp-ip.ibmpc:6884 comp.protocols.pcnet:92
From: fn@junior.mathtok.polymtl.ca (Francois Normant)
Newsgroups: comp.protocols.tcp-ip.ibmpc,comp.sys.ibm.pc.net,comp.protocols.pcnet
Subject: packet driver for PC Network cards ?
Date: 11 Dec 92 22:21:43 GMT
Organization: Mathematiques Appliquees - Ecole Polytechnique - Montreal


Hi,


The subject says it all: Is there a packet driver for "PC Network" cards ?

Thanks in advance.


-- 
Francois Normant (francois_normant@mathappl.polymtl.ca)
Departement de Mathematiques Appliquees - Ecole Polytechnique
C.P. 6079 - succursale A
Montreal - Quebec - Canada - H3C 3A7
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: xiongtou@cda.mrs.umn.edu (Tou P. Xiong 1578973)
Subject: Need Communication Program
Organization: University of Minnesota - Morris
Date: Thu, 17 Dec 1992 18:30:10 GMT

I am in search for a simple communication program for poor folks.  Any
suggestion to what the program name and where to get it will be very
appreciative.  Looking for DOS and Windows freeware or shareware.

Thanks in advance.

Xy
From: nelson@crynwr.com (Russell Nelson)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Packet driver problem
Date: 11 Dec 92 18:21:03 GMT
Organization: Crynwr Software

In article <Dec.11.16.11.29.1992.11963@pilot.njin.net> ccoombs@pilot.njin.net writes:

First the packet driver:

   WD8003E.COM -n 0x60     [7688bytes  09-21-92]

   loaded in config.sys (in this order)

   wd8003.sys              [444bytes  03-03-92]

Then the version of PC/TCP that drives the wd8003 directly.  Nogo.
What you need is ethdrv.sys, which is the kernel of the PC-210
product that uses packet driver.

-russ <nelson@crynwr.com> What canst *thou* say?
Crynwr Software           Crynwr Software sells packet driver support.
11 Grant St.              315-268-1925 Voice  |  LPF member - ask me about
Potsdam, NY 13676         315-268-9201 FAX    |  the harm software patents do.