HDTenEightyP/NetNews huggingface dataset:
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Name this ethernet board . . .  Please?
From: markh@GHOST.MCS.stcloud.msus.edu (Mark Holden)
Date: 31 Dec 92 13:36:24 -0600
Distribution: world
Organization: Saint Cloud State University


	Hello all, I have a pair of ethernet cards which I'm trying to
find some information for.  Distinguishing characteristics follow:

	AT bus, 16-bit full length card
	BNC connector only, no DIX connector.
	Intel P82586 Ethernet chip
	Hordes of 7400 series TTL level chips
	part no (I think) 204927-501
	other numbers on the board include:
		204926-001
		204926-901A
		204926-902A
		204926-904A1
		204926-905A
		204926-906A
		204926-907A

	It may have been built by or for Compugraphics, a division of
Agfa (at least nowadays), as it was part of a Compugraphics Integrator
Series machine.  I've tried to contact these people, but it doesn't seem
that anybody much remembers these things :)

	Now, I couldn't swear to you it was ieee 802.3 Ethernet, but
Between the intel 586 and the fact that it connects to a 50-ohm RG58
bus type network, well, if it quacks like a duck . . .

	I've got all the i82586 based Crywnr packet drivers, but
not knowing irq settings, or base memory, or i/o ports, these are
like shooting in the dark.

	There are no jumpers on the board, but there are four banks of
switches, arranged as such:

-----------------------------------------
|               iP82586                |
|                                      |
|  SW1 SW2                             |
|                                      |BNC
|                                      |
|                     SW3 SW4          |
|                                      |
---------------------------------------- 
                    ||||||| |||||||||

	Note: the switches aren't labeled, that's my doing.

	SW1 = 1111
	SW2 = 0100
	SW3 = 00010000
	SW4 = 0000


So, any guesses, helpful hints?

--
Mark Holden
markh@ghost.mcs.stcloud.msus.edu   "Not only do we get to wear these cool
markh@scsu_2.mcs.stcloud.msus.edu  uniforms, but we are members of an elite
l00017@eeyore.stcloud.msus.edu     fighting force!  The Tank Paratroopers!"
"Happy, Happy!  Joy, Joy!"
From: cse0080@desire.wright.edu (John C. Hansen)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: NCSA doesn't work with my Novell setup
Date: 24 Dec 92 11:10:22 EST
Organization:  Wright State University 

I need some help.  I'm trying to use the NCSA telnet package and the
packet drivers associated with it.  My PC setup is shown below with 
copies of the net.cfg file I use, my "net.bat" file that loads all the
drivers, and the "network.log" file that shows what the software says
as it loads.  I can log onto my novell file servers and access the
network drives, both inside and outside of Win3.1, etc...  I can also
use novell's FTP and TnVT220 (telnet) programs without any problems.
But I can't get the NCSA stuff to work, nor trumpet or any of the other
free software programs that require packet drivers.  

What am I doing wrong?  Is there a news reader that would work with the
standard novell setup (i.e., without the packet drivers...)?  Please help!


Thanks in advance,
John Hansen

P.S. Also, once I get it working, how do I get a nntp server to allow me
to get news from it?

-----
NET.CFG:
--------
Link Support
	Buffers 8 1500
	MemPool 4096

Protocol IPX
    Bind NE2000
    Bind IPTUNNEL

Protocol TCPIP
      Bind NE2000
	ip_address      137.245.245.105
	ip_router       137.245.192.250
	ip_netmask      255.255.255.0
	tcp_sockets     8
	udp_sockets     8
	raw_sockets     1
	nb_sessions     4
	nb_commands     8
	nb_adapter      0
	nb_domain

Link Driver NE2000
    Int #1 5
    Port #1 340
    Frame Ethernet_802.3
    Frame Ethernet_II
    Frame Ethernet_SNAP
    Protocol IPX 0 Ethernet_802.3

-----
NET.BAT:
--------

lh lsl > network.log
\xln\ne2000 -n -w 0x60 0x05 0x340 >> network.log
lh ne2000 >> network.log
lh ipxodi >> network.log
lh netx >> network.log
lh tcpip >> network.log
lh telapi >> network.log

-----
NETWORK.LOG:
------------

NetWare Link Support Layer  v1.21 (920130)
(C) Copyright 1990, 1992 Novell, Inc.  All Rights Reserved.

Max Boards 4, Max Stacks 4
Buffers 8, Buffer size 1500 bytes, Memory pool 4096 bytes
Packet driver for NE2000, version 9.4.0
Packet driver skeleton copyright 1988-91, Russell Nelson.
This program is free software; see the file COPYING for details.
NO WARRANTY; see the file COPYING for details.


Packet driver is at segment 064B
Using 80[123]86 I/O instructions.
Interrupt number 0x5 (5)
I/O port 0x340 (832)
My Ethernet address is 00:00:1B:34:12:27
Novell NE2000 Ethernet MLID  v1.34 (910603)
(C) Copyright 1991 Novell, Inc.  All Rights Reserved.

Int 5, Port 340, Node Address 1B341227
Max Frame 1514 bytes, Line Speed 10 Mbps
Board 1, Frame ETHERNET_802.3
Board 2, Frame ETHERNET_II
Board 3, Frame ETHERNET_SNAP
NetWare IPX/SPX Protocol  v1.20 (911120)
(C) Copyright 1990, 1991 Novell, Inc.  All Rights Reserved.

GET LOCAL TARGET STACKS 3
WARNING: Specified MLID in "BIND" statement does not exist - Entry ignored
IPX protocol bound to NE2000 MLID Board #1.


-- 
John C. Hansen
hansen@logdis1.hq.aflc.af.mil		"... I am working on
cse0080@wsu.bitnet			a suitable quote..."
cse0080@desire.wright.edu		- John Hansen
From: wew@naucse.cse.nau.edu (Bill Wilson)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: QVT/net & Windows for WG
Keywords: tcp, windows
Date: 23 Dec 92 18:26:12 GMT
Organization: Northern Arizona University, Flagstaff AZ

Has anyone set up WIN QVT/net to work under Windows for Workgroups?
I'm currently using PC/TCP and would like to back off from it and 
get more base memory available.  Was there any mention of NFS being
added to QVT/net?

Thanks!

-- 
Let sleeping dragons lie........                    | The RoleMancer 
--------------------------------------------------------------------
William Wilson (wew@naucse.cse.nau.edu | wilson@nauvax)
Northern AZ Univ  Flagstaff, AZ 86011
From: bob@comlab.gatech.edu (Bob Baggerman)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: IBM TCP/IP for OS/2 Lanman 2.1a
Keywords: OS/2 Windows Lan Manager DOS IBM Microsoft
Date: 22 Dec 92 20:58:29 GMT
Distribution: usa
Organization: GTRI Communications Lab

Scott Lewis writes:
>Does anyone have any experience with running IBM's TCP/IP for
>OS/2 (including nfs add-on) on an OS/2 (1.3) machine that is
>also a Lanmanager 2.1a server?  How can IBM's tcp be used
>successfully over NDIS?  Any info on the config changes needed
>to make this work would be appreciated. 

Yea, I'm currently doing this.  It's neat and costs about 10 to 13 dB less
than Novell's product.  It took a lot of fiddling around to discover the 
correct pieces to keep but this is the general approach that ended up 
working.

1) Install LanMan and MS OS/2 1.3.
2) Comment out the LanMan related stuff in the CONFIG.SYS file
3) Install IBM TCP/IP.
4) Uncomment just the server, workstation, and other protocol statements
   in the CONFIG.SYS file.  Be sure to keep the IBM NDIS stuff instead of
   the Microsoft NDIS stuff.
5) "Merge" the IBM TCP/IP and LanMan PROTOCOL.INI files.
6) In STARTUP.CMD I start the LanMan stuff before the TCP/IP stuff.

I know this is a little general, especially the part about merging the
PROTOCOL.INI files.  If anyone is interested I'd be happy to send along
or post my CONFIG.SYS and PROTOCOL.INI files.  So far almost everything 
has been real stable and worked real well.  Our LanMan server now supports
ftp access and acts as an NFS server for our Suns.  The one piece I 
haven't gotten working yet is LPD.

I archive LanMan related utilities and documents on the LanMan server,
"lanman.gatech.edu".  The programmers libraries are there as well as a
number of issues of Microsoft NetNews.  I'd be interested in more LanMan
related utilities.  Contibutions can be put in the UPLOADS section.

Bob

-- 
Bob Baggerman                         !  bob.baggerman@gtri.gatech.edu
Communications Laboratory             !  bob@comlab.gatech.edu
Georgia Tech Research Institute       !  qseclrb@prism.gatech.edu
Atlanta, GA  30332  USA               !  404-894-3525
From: dtam@startek.com (David Tam)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: FTP packet driver spec.
Date: 28 Dec 92 21:56:27 GMT
Organization: The Internet


Does anyone know where can I get a copy of the Ethernet FTP packet driver spec(preferable via e-mail or ftp).
Any help will be greatly appreciated.

David M. Tam
DMT
dtam@startek.com
Organization: Penn State University
Date: Mon, 21 Dec 1992 17:09:12 EST
From: H. D. Knoble <HDK@psuvm.psu.edu>
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Switch on your modem !
Distribution: world

The HANGUP command of MS-Kermit 3.12 (latest release with MSKERMIT.PCH patch
file) does not properly hang up some modems;  I've never used a 9600 bps modem
it would hang up.  Thus what is needed is some code to issue an ATH command to
the modem.  This is possible via a DOS .BAT and companion MS-Kermit "init"
file; e.g., like one that follows this prose.  See DROPIT.INI for three
possible values of the DOS argument.  Note that issuing DROP * will attempt to
use the current serial settings as MS-Kermit doesn't change these if not asked
to.  Also note that DROPIT.INI may need a SET COMx statement activated if the
port isn't COM1.
-------------------------Code follows ----------------------------------
@Echo off
REM DROP.BAT
REM H. D. Knoble, Penn State University Center for Academic Computing
REM Hang up a 9600 bps modem by issuing the ATH command.
REM Port defaults to COM1, Speed defaults to 9600.
kermit -f dropit.ini, do drop %1

; DROPIT.INI
; Companion to DROP.BAT
; Attempts to drop the phone line using modem command ATH.
; called by issuing DOS commands;
; kermit -f dropit.ini, DO DROP [speed]             where "speed":
;   *     means do not set speed; use current serial port settings.
;   nnnnn means issue SET SPEED nnnnn
;   null  means issue SET SPEED 9600.
;
;   Port must be set with SET PORT COMn.
; SET COM3 \x3e8 4;  May be necessary to define port address and IRQ #.
; following checks DOS environment variable PORT (via SET PORT=) for a value.
if equal {"\$(PORT)"}  "" SET PORT COM1;   Default port to COM1.
if not equal {"\$(PORT)"}  "" SET PORT \$(PORT)
:Next
set take-echo on
DEF DROP if equal "\%1" "" SET SPEED 9600, -
  if not equal "\%1" "" if not equal "\%1" "*" SET SPEED \%1, -
  clear, output +++, input 3 OK, if success output ath\13, run cls, stop
From: tbenham@cybernet.cse.fau.edu (Tom Benham)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Winsock available?
Date: 23 Dec 92 03:15:53 GMT
Organization: Cybernet BBS, Boca Raton, Florida

trier@slc6.ins.cwru.edu (Stephen C. Trier) writes:

> Windows Sockets is for Windows while Berkeley Sockets is for BSD Unix.
> There are some significant differences caused by the different OS archi-
> tectures, but the spirit is meant to be the same.
> 
> The benefit is that you will be able to mix and match TCP stacks and
> applications from different vendors.  This means that ugly hacks like
Doesn't IBM offer BSD Sockets interface with their TCP/IP?
Also, I thought IBM has even announced Sockets of SNA.  Now
assuming (big ignorant assumption here so please correct me)
that these APIS are the same as or similar to BSD, then doesn't
the whole idea of Winsock introduce a new set of imcompatibilities?

Lastly: Is IBM participating in the development of the Winsock API?

Tom 
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: jallard@microsoft.com (James 'J' Allard)
Subject: Re: Winsock available?
Date: 29 Dec 92 18:41:45 GMT
Organization: Microsoft Corporation

In article <7kT8VB1w165w@cybernet.cse.fau.edu> tbenham@cybernet.cse.fau.edu (Tom Benham) writes:
>Doesn't IBM offer BSD Sockets interface with their TCP/IP?
>Also, I thought IBM has even announced Sockets of SNA.  Now
>assuming (big ignorant assumption here so please correct me)
>that these APIS are the same as or similar to BSD, then doesn't
>the whole idea of Winsock introduce a new set of imcompatibilities?

The goal behind Windows Sockets was to define a common interface that all
PC-based TCP/IP vendors could support under Microsoft Windows. Since the
interface is implemented as a DLL (regardless of the underlying transport
architecture), applications written to the specification will need to be 
aware of only a single API and can link to any vendor's compliant winsock.dll.

A couple of the reasons for basing it on Berkeley sockets was a) it was a good
start (why reinvent the wheel), b) almost all existing TCP/IP Windows
applications are written to some type of sockets interface. I believe that
IBM does currently offer a sockets interface. I believe that all of the
vendors involved in the Windows Sockets effort have in the past as well. For
backward compatibility, the old interfaces will continue to ship for some
time (either with applications or with vendors' stacks), but I think you'll
see that Windows Sockets will be the interface of choice.

I'm not sure what incompatibilities you're concerned about, but if you're 
worried that you can't port your favorite UNIX sockets application to 
Windows unmodified, the sockets changes will be minor compared to making
it work in Windows... Like I've mentioned before, Windows Sockets looks
a lot like Berkeley sockets+extensions. If you choose to ignore the 
extensions, you might manage to build a Windows-unfriendly application.
Your best bet is to take a look at the spec. Try microdyne.com or vax.ftp.com.

>Lastly: Is IBM participating in the development of the Winsock API?

I can't comment on their commitment in offering Windows Sockets support for 
their MS-DOS based stack or their Windows applications, but they have been
involved in the definition of the specification and are still on the mailing
list (e-mail winsockapi-request@microdyne.com to subscribe).
-- 
_______________________________________________________________
J. Allard                                 jallard@microsoft.com
Program Manager of TCP/IP Technologies    work: (206)882-8080
Microsoft Corporation                     home: (206)860-8862
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: "Tony C. Cheng" <tcheng@bronze.ucs.indiana.edu>
Subject: ODIPKT driver
Organization: Indiana University
Date: Wed, 23 Dec 1992 01:06:43 GMT


Can anyone tell me what the most recent version of ODIPKT driver is and 
where to find it?

Thanks./_Tony
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: usbill@ustores.missouri.edu (Bill Canning)
Subject: Token Ring ODI Packet Driver (ODITRPKT.COM)
Organization: University of Missouri - Columbia
Date: Mon, 21 Dec 1992 16:49:09 GMT

Does this program exist?  I read a posting that someone was nearly done with
this.  Are you done?  Do you need beta testers?

Thanks for the info,
Bill
-- 
Bill Canning                             usbill@ustores.missouri.edu (Internet)
(314) 882-2131                           usbill@muccmail.missouri.edu (cc:Mail)
[314] 882=4699 (Fax)                     CSPECWC@MIZZOU1 (BITNET)
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: weber@rhrk.uni-kl.de (Christoph Weber-Fahr [KIT])
Subject: Re: MS-Kermit v3.12 ODI work with token-ring?
Keywords: MS-Kermit, token-ring
Organization: University of Kaiserslautern, Germany
Date: Thu, 31 Dec 1992 11:29:09 GMT

ziegenfE@moravian.edu (Eric W. Ziegenfus) writes:

>Does the MS-kermit v3.12 (with ODI support) work with token ring odi drivers?
>Has anyone used MS-Kermit with a token-ring board?

Yes. It works perfectly here. I'd wish, more developers would give
that quality of media support.

Regards

Christoph Weber-Fahr

-- 
  Christoph Weber-Fahr                  |  E-Mail:  weber@rhrk.uni-kl.de 
  Universitaet Kaiserslautern,  KIT     |  S-Mail:  Postfach 3049
  Tel. 0631/205-3391                    |           D-6750 Kaiserslautern
--------------------------  My personal opinion only    ---------------------
Xref: sparky comp.protocols.tcp-ip.ibmpc:7202 comp.sys.novell:10979
From: holbrook@cic.net (Paul Holbrook)
Subject: Making BOOTP work with Cisco CS-516, FTP Inc 2.1 SLIP?
Organization: CICNet, Inc.
Distribution: comp
Date: Tue, 22 Dec 1992 16:59:00 GMT

I have a Cisco CS-516 running 9.1a(0.2), and I'm trying to connect via
async dialup SLIP using FTP Inc's PC/TCP V2.1.  I can get PC/TCP to
work if I statically configure in the address the Cisco has configured
in, but I can't get FTP Inc's BOOTP to dynamically discover the
address from the Cisco.  

I start the SLIP packet driver, use COMSCRPT to dial my cisco and put
it into SLIP mode, and then try BOOTP, but BOOTP fails to find a
server; I would have expected that the Cisco would see the BOOTP and
respond. 

I've been swapping messages with FTP about this problem, but I'm
curious to find out any anyone else has solved this problem with FTP
2.1 SLIP?

The real problem I'm trying to solve it to get FTP Inc's PC/TCP to
take a dynamic address when I dialup to my Cisco that is using static
fixed addresses for each serial line.  BOOTP seemed a logical way to
attack the problem, but I'm open to other suggestions.

--
J. Paul Holbrook
CICNet Technical Services Manager
holbrook@cic.net    (313) 998-7680
From: jbvb@FTP.COM ("James B. Van Bokkelen")
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: newsreader for PCs, nntp and vmail (PC/TCP)
Date: 21 Dec 92 19:24:31 GMT
Reply-To: jbvb@ftp.com
Distribution: world
Organization: The Internet


    >I suggest FTP software to make a GOOD newsreader (like "trumpet").
    >If you know any reason for using nntp and vmail, please reply to...

I do.  There's a tradeoff between server resources and PC-based resources.
If your site can afford lots of high-horsepower servers for NNTP, then
running NNTP interactively (let the user read the header of a message,
decide whether to get the text, etc. like Trumpet) is reasonable.  If you
can't have everyone connected to the NNTP server most of the day, then
you've got to run it in batch mode like VMAIL/NNTP.

An even better reason is if you need to read news when your PC's network
connection is down (SLIP, PPP or a portable).

    I agree with you.  I was sorely dissappointed in FTP's newsreader when
    my upgrade arrived. If you wish to follow more than 1 or 2 groups it is
    too unwieldy, too slow, and takes up too much disk space. 

Mileage obviously varies.  We've got people here following dozens of groups
with VMAIL/NNTP.  I follow 8 groups myself, and I had about 500Kb in my PC's
news hierarchy before I ran NNTP just now - it went down to 176Kb when the
queued deletions took effect and new messages were retrieved.
    
James B. VanBokkelen		2 High St., North Andover, MA  01845
FTP Software Inc.		voice: (508) 685-4000  fax: (508) 794-4488
From: trier@slc6.ins.cwru.edu (Stephen C. Trier)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: MIME compliant mailreaders for MS-DOS/Windows
Date: 30 Dec 1992 15:29:30 GMT
Organization: Case Western Reserve University, Cleveland OH (USA)
NNTP-Posting-Host: slc6.ins.cwru.edu
Keywords: MIME, Mail, SMTP

In article <1992Dec30.111958.19733@ulrik.uio.no> peterh@oslo.uninett.no (Peter Hausken) writes:
>We're starting to use MIME on UNIX machines, but I have not seen any 
>mailreaders for MS-DOS who is using MIME yet. Is there anyone working
>on implementing MIME on MS-DOS?

The metamail programs from Nathaniel Borenstein run on MS-DOS.  We integ-
rated these programs with a local mail reader, and they work well.  The
resulting user interface is clunky, as one would expect from the merger
of an vn/elm-style visual mail reader and a command-line MIME reader-
composer, but it does work.

It's relatively easy to adapt mail readers to use metamail.  In our case,
it took no more than a few dozen lines of code.

-- 
Stephen Trier                      "We want to offer you a price that you
Network software type               just can't afford to take advantage of."
Case Western Reserve University         - Sales blurb from HSC Software
trier@ins.cwru.edu
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: A1.MCL@isumvs.iastate.edu 
Subject: Re: Dos Lan Requester + Token Ring + Telnet(NCSA)
Organization: Iowa State University, Ames IA
Distribution: usa
Date: Thu, 24 Dec 1992 00:59:56 GMT

In article <1992Dec21.172534.9237@murdoch.acc.Virginia.EDU>,
tg2r@galen.med.Virginia.EDU (Todd P. Greenwald) writes:
>Is such a combination possible?  This would be our hospitals
>best route to the library literature searching software.
>Any help would be greatly appreciated.
>
>Todd Greenwald M.D.
>University of Virginia Hospitals

Yes, you should be able to do this.  We do this.

Mike Long
Iowa State University

Newsgroups: comp.protocols.tcp-ip.ibmpc
From: egntoh@ntuix.ntu.ac.sg (Toh Guan Nge)
Subject: Re: Intel Etherexpress Cards
Organization: Nanyang Technological University - Singapore
X-Newsreader: TIN [version 1.1 PL8]
Date: Wed, 23 Dec 1992 06:06:29 GMT

Does anyone know how to reach Intel Technical Support ?
Best if through Internet mail.


--
Toh Guan Nge, School of EEE,
Nanyang Technological University, Singapore
Internet Email: egntoh@ntuix.ntu.ac.sg
Bitnet   Email: egntoh@ntuvax.bitnet
Xref: sparky comp.protocols.tcp-ip.ibmpc:7103 comp.os.ms-windows.setup:2433
From: rnb@alsys1.aecom.yu.edu (Robert N. Berlinger)
Newsgroups: comp.protocols.tcp-ip.ibmpc,comp.os.ms-windows.setup
Subject: Use WFW with packet driver?
Date: 21 Dec 92 20:18:46 GMT
Followup-To: comp.protocols.tcp-ip.ibmpc
Organization: Albert Einstein College of Medicine, NY

Is it possible to use Workgroups for Windows with a packet driver
rather than NDIS?  I realize it may be possible to use an NDIS->packet driver
converter for other software, etc., but that's not really what I'm looking for.
From: aarond@xibm.StorTek.com (Aaron Dailey)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: A MCA Ethernet Card
Date: 21 Dec 92 16:03:09 GMT
Organization: StorageTek

In article <199212171818.AA21116@arwen.ics.muni.cs> ivos@arwen.ics.muni.cs (Ivo Cernohlavek) writes:
Path: stortek!csn!ncar!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!ucbvax!arwen.ics.muni.cs!ivos
   From: ivos@arwen.ics.muni.cs (Ivo Cernohlavek)
   Newsgroups: comp.protocols.tcp-ip.ibmpc
   Date: 17 Dec 92 19:49:38 GMT
   References: <143170@lll-winken.LLNL.GOV>
   Sender: daemon@ucbvax.BERKELEY.EDU
   Distribution: world
   Organization: The Internet
   Lines: 20
   X-Unparsable-Date: Thu, 17 Dec 92 19:18:52 CET

   Hi,

   > I found a MCA ethernet card  in one or our IBM Model 80 PC's. I do not know th
   e
   > manufacturer of the card and I don't know to obtain a driver that will work wi
   th
   >   PC/TCP.
   > Does anyone have any ideas?

   It may be Western Digital WD8003 "painted to blue". I have such one,
   it is in IBM's box, but has very small label "WD8003...". It works well
   with wd8003e.com from CRYNWR collection.

   Good luck (yo will need it with IBM products ! ;-)

					     Ivo Cernohlavek
					     Institute of Computer Science
					     Masaryk University
					     Brno, Czechoslovakia
					     ivos@ics.muni.cs

Also, some of the early 'IBM' ethernet cards are Ungerman Bass cards.
Sorry, I don't have the model.


--
Aaron Dailey Internet: Aaron_Dailey@stortek.com
StorageTek Corporation   Voice: (303) 673-4989, FAX: (303) 673-2570
Mail:  MS0242, 2270 South 88th Street, Louisville, C0 80028
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: david.hoisve@UUSERV.CC.UTAH.EDU
Subject: Ph client for DOS ...
Organization: University of Utah Computer Center
Date: Wed, 23 Dec 1992 17:52:15 GMT

Does anyone have a great PH (CSO NameServer) client for DOS?

Thanks in advance...

-- Dave.
David Hoisve
University of Utah Computer Center
HOISVE@CC.UTAH.EDU
Newsgroups: comp.protocols.tcp-ip.ibmpc