HDTenEightyP/NetNews huggingface dataset:
From: geoff@hinode.East.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Information on PC-based NFS clients
Date: 8 Apr 92 22:05:45 GMT
Reply-To: geoff@east.sun.com (Geoff Arnold @ Sun BOS - R.H. coast near the top)
Organization: Sun Microsystems PC-NFS Engineering
NNTP-Posting-Host: hinode.east.sun.com

Quoth backman@FTP.COM (Larry Backman) (in <9204072008.AA03163@ftp.com>):
#[detailed analysis]
#Geoff; please chime in if I have misrepresented anything :-).

Looks good to me, Larry :-) The only other suggestion I'd make
is that the operation of file locking over the net is a fairly
abstruse topic, and I would recommend that anyone who wants to
understand it should read the appropriate X/Open specifications.
Here's the relevant portion of my "suggested reading" file:

===========================cut===========here==================
There are also a number of standards documents covering this technology.
The most comprehensive are from X/Open:

X/Open CAE Specifications: PC Interworking - NFS.
X/Open CAE Specifications: Protocols for X/O Interworking - XNFS.

These documents are available directly from the X/Open Company. As the time of
writing, the phone numbers were:
   USA:    +1(415)323 7992 or +1(703)876 0044
   Europe: +44 734 508311
   Japan:  +81 3 3251 8321

The X/Open specifications are based in part on the following RFC
(Request For Comments) documents:

RFC 1094 - NFS Network File System Protocol Specification
RFC 1057 - RPC: Remote Procedure Call Specification Version 2
RFC 1014 - XDR: External Data Representation Standard
========================cut===========here====================

Geoff

------------------------------------------------------------------------------
--         Geoff Arnold, PC-NFS architect (geoff.arnold@East.Sun.COM)       --
--                SunConnect, A Sun Microsystems Business                   --
------------------------------------------------------------------------------
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: eengelke@sail.uwaterloo.ca (Erick Engelke)
Subject: Re: FTPBIN buggy 
Organization: University of Waterloo
Date: Mon, 6 Apr 1992 07:12:25 GMT

 braner@THEORY.TC.CORNELL.EDU (Moshe Braner) writes:
>
>I was running FTPBIN on 3 or 4 PC's.
>If one opened a connection and held it open while another client tried to 
>open a connection to the server, the second client hung.  I cannot tell 
>whether it hung completely or got into a retry loop, from my point of view 
>it was hung and had to be rebooted.


A new experimental FTP client is available from sunee.uwaterloo.ca in 
pub/wattcp/ftp.zip.  After a few weeks of testing it will join the regular
WATTCP program collection.

Enough of my users complained about the other free FTPs either hanging, 
slowing to a standstill, or trashing files larger than a few hundred kbytes.

The new FTP gives excellent performance, even when going through multiple 
gateways or reading from a network drive.  FTPing a file from my network
disk through a fileserver doubling as a bridge, through PCroute out to
my UNIX box yields an average of about 130 kbytes/s.  Oh, and that's with
only an 8 bit network card on my 386.

+---- file -----+  +----------------- ftp ----------------------+

FILESERVER -----> PC -----> FILESERVER -------> PCROUTE -----> UNIX
              (8 bit 
             network card)

On the PC the greatest slowdown comes from the time spent dealing with
DOS and the hard disk.  These have more of an effect than the preformance
degradation caused by intermediate gateways These have more of an effect than the preformance
degradation caused by intermediate gateways 

The common speed tests compare FTPing files from a ramdisk to a UNIX 
box on the same subnet.  Doing this with 1.5 Mbyte files I have reached
speeds of up to 540 kbytes/s.  (With smaller files it's hard to be as
precise with the measurements.) But you will find the speeds vary incredibly
with the type of network card, the network traffic, host loading, etc.

If you are interested in testing this program, just download it and Email me
if you find any problems.  Also available are new versions of the libraries
and the SMTPSERV program to handle inbound SMTP mail messages.


Erick 

P.S. Andrew Hardie, I can't reach you via Email.  Please mail me again so I
can trace a route back to you.
-- 
Erick Engelke					  Engineering Computing
						 University of Waterloo
Waterloo TCP Architect		 erick@development.watstar.uwaterloo.ca
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: dzubin@skorpio.usask.ca (Thomas Dzubin)
Subject: Re: PKTMUX issues
Organization: Saskatchewan Institute of Applied Science & Technology (SIAST)
Date: Tue, 7 Apr 1992 18:42:35 GMT

In article <1992Apr6.141237.54240@cc.usu.edu> jrd@cc.usu.edu writes:
>	A double ended TCP/IP stack has no problem with this because it
>does a full decode on all incoming material and recodes it for sending. It's
>a pseudo host servicing many clients and many exterior hosts. It just happens
>to communicate using TCP/IP to clients because that's what they speak. The
>problem to be solved is allocation and collision avoidance of ports and
>sequence numbers and the like, and the only way of achieving that is to 
>maintain the information in one spot. Per client translations occur between
>them and the exterior world, in a fashion compatible with normal TCP/IP
>usage and well known ports etc. A full decode is necessary to *understand*
>what's being said and translate accordingly; incrementing a few numbers is
>not the same thing. It's a software DELNI ("an Ethernet in a box"), an
>Internet in a program. Hmmm, "Pseudo Host Internet Program" for long.
>        I'm not advocating this thing, but rather pointing to what I think
>is the logical conclusion.
>	Joe D.


Just out of curiousity, does anyone want to estimate if there are going
to be any cycles left to do any useful processing once our CPU is done
doing all of these decodes?

Sure, it's nice to get the whole kitchen sink in here, but whatever
became of the Keep It Simple concept?

If we are going to be implementing a full TCP/IP stack, can it be done
on anything less in "power" than a '486?
It seems like everyone is proposing a solution that is greater and grander
than what even the 'commercial' vendors supply.

----------------------------------------------------------------------------
Thomas Dzubin
Networks person and general scape-goat
Saskatchewan Institute of Applied Science & Technology (SIAST)  CANADA
dzubin@skorpio.usask.ca  or  dzubint@sask.usask.ca
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: floydb@rpi.edu 
Subject: re: WinQVTnet & 3.1 No Worky!
Reply-To: floydb@rpi.edu 
Organization: Rensselaer Polytechnic Institute - Admin. 
Distribution: world 
Date: Tue, 7 Apr 1992 14:41:07 GMT

In article <1992Apr6.195135.39088@kuhub.cc.ukans.edu> lassa2@kuhub.cc.ukans.edu writes:
>Bug Report For WinQVTnet
>
>
>I DOES NOT WORK WITH WINDOWS v3.1
>
>I used my same w3.0 setup and run it on v3.1 and all i get is a 
>network initialization error!  but the .rc file checks out 
>
>I am sure not every one has v3.1 yet but is any one else getting this
>
>or is the author reading these nets?
>
>
>Todd A. Phillips
>Systems Development
>Univesity Of Kansas
>TPHILLIP@RESEARCH.RGSPS.UKANS.EDU
 
What version of WinQVTNet are you using?
 
barry
From: jbvb@FTP.COM ("James B. Van Bokkelen")
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Packet driver question
Date: 13 Apr 92 20:36:44 GMT
Article-I.D.: ftp.9204132036.AA21411
Reply-To: jbvb@ftp.com
Organization: The Internet


    3. Poll after a network card interrupt by chaining to the network card's
       ISR.  I don't recommend this, but it is better than some other options.

If the driver supports v1.09, the get_parameters() function allows you to
determine which interrupt to chain to.  The DIS_PKT we ship with PC/TCP
(1.13 or greater) supports this.

James B. VanBokkelen		26 Princess St., Wakefield, MA  01880
FTP Software Inc.		voice: (617) 246-0900  fax: (617) 246-0901
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: apple@drvax3.msfc.nasa.gov (Kathleen Applegate)
Subject: Re: de201 and de212 packet drivers
Organization: NASA/MSFC
Date: 16 Apr 92 13:15:33 GMT

WAHL@UWSTOUT.EDU writes:


>I am trying to find packet drivers for Digital DE210 and DE212 Ethernet
>boards.  All I have been able to find is drivers for DEPCA.  Is this the
>driver to use for these cards?  I have tried this driver for the DE201
>but haven't had any luck as yet.  The card does work with Pathworks and 
>the packet driver shim, but a department here is planning to use Novell
>only.  Any guidance will be appreciated.

>Thanks
>----------------------------------------------------------------------------
>Douglas J. Wahl                            INTERNET:	WAHL@UWSTOUT.EDU
>Systems Programmer                           BITNET:	WAHL@UWSTOUT.BITNET
>University of Wisconsin - Stout            
>Administration Building Room 18
>Menomonie, WI  54751

We use the Digital DE200 NICs and have successfully used packet
drivers with FTP Software Inc.'s PC/TCP as well as NCSA Telnet.
There is a file relating to DEPCA.COM that says this driver is for
the newer generation (i.e. DEnnn) boards, not the old "DEPCA" 
boards ... so the .COM file is a bit of a misnomer.

My DEPCA.COM command look like this:  DEPCA 0x60 10 0x300 0xd000

As far as PathWorks support?  DEC Tech Support said that they were
looking at the issue of supporting packet drivers as recently as
last fall, but that the decision was made to stick with NDIS and
the native DECnet driver.

-----------------------------------------------------------------
Kathleen Applegate                     apple@drvax3.msfc.nasa.gov
Senior Analyst
New Technology Inc.
Huntsville, AL  35802
(205) 544-7656
A
A
(205) 544-7656
From: FLOYD.R@FS.LIBRARY.WLU.EDU (Ruth Floyd)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: V.39.50 protocol?
Date: 9 Apr 92 19:22:25 GMT
Organization: The Internet

Has anyone heard of a new standard called V.39.50, supposedly
available as a transfer protocol to allow previously incompatible
devices to send and receive data?  The term has come up for us from
our Library System vendor, who has thrown development of V.39.50
support in their system as a solution for the use of TVI925 terminals
to a remote system that currently only supports VT-emulation.

I've never heard of V.39.50, and need to learn something about it
FAST.  Does anybody have any words of wisdom or sources for such
wisdom?

Thanks in advance.
Ruth W. Floyd               Head, Academic Computing
floydr@wlu.edu              University Computing
(703) 463-8847              Washington and Lee University
                            Lexington, Virginia 24450
Newsgroups: comp.protocols.tcp-ip.ibmpc,comp.protocols.tcp-ip
From: swhite@tybse1.uucp (William C. "Spike" White)
Subject: Re: Question: installing NCSA
Organization: Tybrin Corporation, Shalimar, FL
Date: Fri, 10 Apr 1992 15:06:18 GMT


I can probably help you out.  I administer  a TCP/IP LAN that currently 
includes FTP Software's PC/TCP running on one PC and NCSA Telnet running on two
other PC's.

And you're right.  It sounds like you inherited a lot of bogusity.  IFCUST.SYS
and IPCUST.SYS are used by the PC/TCP software -- they aren't needed by
NCSA Telnet.  I can check on ETHDRV, I forget which one uses that.

And I think you've got the best idea.  Remove all that crud and install
NCSA Telnet from scratch.  If you had complete docs, etc. to PC/TCP, I'd
say install it since it's a more complete implementation.

If you want more info, write.  I tried to send e-mail (USENET & Internet), but 
it bounced both ways.

-- 
Spike White
e-mail: swhite@afseo.eglin.af.mil uunet!sci34hub!tybrin4!tybse1!swhite
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: eengelke@sail.uwaterloo.ca (Erick Engelke)
Subject: Re:  PKTMUX issues
Organization: University of Waterloo
Date: Thu, 9 Apr 1992 20:49:35 GMT

 donp@novell.com (don provan) writes:
> RAF@cu.nih.gov (Roger Fajman) writes:
>>Is there any inherent reason why it can't be made to work if the
>>different TCP/IP stacks have different IP addresses?
>
>...  Iron a couple of details about broadcasts and ARP and you're
>in business.  Can't RARP, of course, since RARP depends on a
>one-to-one mapping between hardware address and IP address, but this
>type of configuration would probably too complicated for normal RARP
>or BOOTP to be much help anyway.

Actually it would be good to support BOOTP (or RARP) like Bruce Campbell's BOOTP
TSR which intercept's BOOTP requests and answers them from data inside the machine.
(download sunee.uwaterloo.ca: pub/wattcp/bootp for an example)

Suppose PKTMUX was told it could use IP numbers 129.97.20.2 through 129.97.20.10
and it managed those numbers.  When you run application X, PKTMUX would give an
unused IP number to that TCP and it would automagically configure for that address
using BOOTP. 

I'm not trying to add to Graham's workload, just hoping to show the potential.


>>Admittedly that's wasteful of addresses, but would it work?
>
>It's no more wasteful than the fairly typical practice of giving two
>different PCs in the same office two different IP addresses.

Nor any more wasteful than the average class B subnet with ten lowly addresses
in use.  

Since someone will probably ask, no it is not at all difficult for a PC to
have and use multiple IP addresses through the same Ethernet board.  In fact, 
if you PING 129.97.20.2 through 129.97.20.40, all are answerred by a single PC
running plain old DOS.  Most people won't have need for 39 IP addresses within
a PC, but I do.

Erick

-- 
Erick Engelke					  Engineering Computing
						 University of Waterloo
Waterloo TCP Architect		 erick@development.watstar.uwaterloo.ca
From: zmw@selu.edu
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Win 3.1 and FTP Softwares progs
Date: 14 Apr 92 15:39:00 GMT
Distribution: world
Organization: The Internet

I was unable to remove myself from this list by using the normal UNSUB cmd.
Please unsubscribe me.  Thanks.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
Mike Whisenhunt                |Internet: zmw@selu.edu   |How to tell if your
VMS System Manager/Postmaster  |Phone   : (504) 549-3643 |boss has used your 
Southeastern La. Univ, Box 430 |Fax     : (504) 549-5092 |Word Processor? Look
Hammond, La 70402  USA         |"Wise men still seek Him"|for whiteout on CRT.
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: tlm1@Ra.MsState.Edu (Terry Matula)
Subject: Re: NCSA Telnet w/ SLIP8250
Organization: Mississippi State University
Date: Fri, 10 Apr 1992 17:12:15 GMT

In article <1992Apr10.054116.16809@leland.Stanford.EDU> gjc@loki.Stanford.edu (George J. Chen) writes:

>Has anyone gotten the above combination of software to work together?
>Does anyone know it is impossible?  Thanks!

Hmmm..I don't know that it's impossible, but I did have trouble making them
work together.  My solution was to use the ETHERSL driver instead of
SLIP8250.
--
Terry Matula
tlm1@ra.msstate.edu
matula@ee.msstate.edu
From: courcel@cix.cict.fr (enseignement)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Need a Tektro emulator for PC
Keywords: Tektronix telnet BAPI
Date: 7 Apr 92 17:46:30 GMT
Organization: Centre Interuniversitaire de Calcul de Toulouse


We work here with HP's ARPA services 2.1 and Lan Manager/X (Lan Man 1.x
with TCP/IP transport layers).
Does someone know if there is (shareware or not) a terminal emulator
which could be used with HP Telnet (ie with BAPI interface)
emulating TEKTRONIX terminals ? We just use now the VT100 emulator
distributed by HP.
From: gts@MICA.BERKELEY.EDU (Greg Small)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re:  Win 3.1 and FTP Softwares progs
Date: 12 Apr 92 17:31:34 GMT
Organization: The Internet

= From pcip-request@louie.udel.edu Sat Apr 11 00:39:14 1992
= From: Bill Wilson <naucse!naucse.cse.nau.edu@arizona.edu>
= Subject: Win 3.1 and FTP Softwares progs
= Has anyone tried running FTP Software's programs under Windows 3.1 with
= FTP's 386 enhanced mode setup?

Worked fine for me under Windows 3.0 using PC/TCP 2.05 pl1 plus VPCTCP.386 
through ETHDRV and the Clarson version 8 UBNICPS2 packet driver.  Occasionally
TN (pl 3) would give "Violated System Integrety.." on 3270 connection attempts.
Hovever, I have a rather complicated setup, including a second UB NIUps2 running
UB TCP/PC and MS-Kermit 3.01 through the NetOne Telnet service.

It continues to work under Windows 3.1.  Do you have a specific problem?

Gregory T 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: VILLIELM@SNYNEWVM.BITNET
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: help
Date: 12 Apr 92 14:35:47 GMT
Article-I.D.: louie.9204121020.aa12222
Distribution: world
Organization: The Internet

help
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: aoelked@kirk.msoe.edu
Subject: Problems with Kermit 3.11 & IPX
Reply-To: aoelked@kirk.msoe.edu
Organization: Milwaukee School Of Engineering, Milwaukee, Wisconsin
Date: Tue, 14 Apr 1992 18:24:59 GMT

We are trying to get an WD8013 card to work with a packet driver so that 
we can talk to our Novell 3.11 file server with IPX and use Kermit 3.11
over TCP/IP at the same time on the same card.  The TCP/IP will (eventually)
be routed over to our ULTRIX and VMS systems.

It appears that the WD8003E packet driver just clobbers the IPX driver, but
Kermit can work with it just fine.  The 8003pkdr from SMC works fine with IPX
and NCSA telnet works, but when Kermit attempts to connect
to the host, it is able to find the packet driver, 
but unable to find the host.  

We are using Kermit over Telnet/FTP because that's what users are
familiar with, and IPX because that's what we've had around for some time.
We've also thought about going to ODI drivers, but have not investigated 
that avenue throughly yet.

Any help would be very much appreciated.


Below are some sample outputs from our attempts.  

8003pkdr: have used MANY different Int # combinations.

Packet Driver V2.03 (910814) for 8003/8013 Family LAN:
    *** RAM Base Addr:            C800 ***
    *** I/O Base Addr:            0320 ***
    *** IRQ Number:                  5 ***
    *** Pkt Drv Int # (Bluebook):   60 ***
    *** Pkt Drv Int # (802.3):      60 ***
    *** Max Multicast Addr's:        8 ***


WD8003E: 0x60 is used or kermit can't see the packet driver.

Packet driver for Western Digital WD8003 E EBT EB ET/A and E/A, version :.7.1
Portions Copyright 1988, Robert C. Clements, K1BC
Packet driver skeleton copyright 1988-92, Crynwr Software.
This program is free software; see the file COPYING for details.
NO WARRANTY; see the file COPYING for details.


Packet driver is at segment 0872
Using 80[123]86 I/O instructions.
Accessing the board using 16 bits of data.
Interrupt number 0x5 (5)
I/O port 0x320 (800)
Memory address 0xC800 (51200)
My Ethernet address is 00:00:C0:9E:1E:24


Dan Oelke                                              AOelkeD@kirk.msoe.edu
Academic Computer Services Department        Milwaukee School of Engineering
       The opinions within are mine and no-one else may claim them.
----------------------------------------------------------------------------
  VAX/VMS is like sex - if you've tried it, you can't get along without it,
     if you haven't you really have no idea what the fuss is about.
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: srl@sdf.lonestar.org (Steve Linebarger)
Subject: Std MsWin Socket API ? (was :... Tcp/ip API for Dos, Windows )
Summary:  Can you confirm, deny or massage someone into action?
Organization: SDF, public access unix. Dallas TX
Date: Thu, 9 Apr 1992 18:11:06 GMT

In article <9204070545.aa29219@louie.udel.edu> WEIJUN@ITIVAX.BITNET (WEIJUN WANG) writes:
>Greetings: all  [ Product info request Deleted ]
>BTW, there was a posting at the end of last year here about a standard
>TCP/IP socket interface standard for Window which supposed to come in
>March, is there any information about this?
>Thanks very much in advance. I'll summarize the answers I get.
>
>Regards,
>Weijun Wang
>Singapore

 I also need to know.  Is there or isn't there a discussion between MicroSoft,
 and other Vendors about a standard socket API for windows?

 Rumors, myths, hints 	, ANY KIND of info about it is needed.
 Is there anybody we can prod to help make this happen (Like  Wollongong
 , fr'instance)?

 Please post.
 Your particpation in this matter is truly appreciated.

Steve Linebarger 

-- 
srl@sdf.lonestar.org 73157,1323 aol:slinebarg GEnie s.linebarg 214.506.3990
From: WEIJUN@ITIVAX.BITNET (WEIJUN WANG)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Proxy ARP document
Date: 13 Apr 92 21:11:00 GMT
Distribution: world
Organization: The Internet

Hello,
Which document describe Proxy ARP?
Thanks in advance for any help.

Weijun (WEIJUN@ITIVAX.BITNET)
Newsgroups: comp.protocols.tcp-ip.ibmpc,comp.sys.mac.comm
From: karches@utdallas.edu (Tom Karches)
Subject: Re: what do I need to get a mac to talk tcp/ip?
Organization: Univ. of Texas at Dallas
Date: Tue, 7 Apr 1992 00:49:30 GMT

In article <167C1B24E.MUSANR01@tscc.macarthur.uws.edu.au> b.watson@uws.edu.au writes:
>Hi,
>   Sorry about asking this to a PC group, but ...
> 
>  < stuff deleted>
> 
>What is the easiest way to get FTP working on a mac plus?  (Once I get
>FTP working, I can get more software without having to find a mac that will
>read IBM disks|)
> 

First, you need a copy of MacTCP. A copy comes with the Eudora mail 
package (I'm not sure where from.) Once you have installed MacTCP,
you can then use NCSA Telnet (MacTCP version) for telnet, and for
FTP I reccomend Fetch from Dartmouth (publicly available).

> 
>Any hints or suggestions greatly appreciated.
> 
> 
>Also: can someone point me to a small text editor for the mac that I can use
>to change my config.tel.  Binary please,  I don't have stuffit or binhex
>and I have to walk to the other end of the campus to get to a mac that will
>read IBM disks.
> 

You could just use Teach Text. miniWRITER is a great text editor DA, if
that is more your style.

>---
>  Brian Watson
>  Teaching and Services Computer Centre
>  University of Western Sydney, Macarthur
>  Internet: b.watson@uws.edu.au


-- 
-------------------------------------------------------------------------------
Tom Karches          |"If rap music had been around when I was a kid,
karches@utdallas.edu | I would have become a musician instead of a politician."
---------------------'----------------------------------- Richard Nixon
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: santeew@dogmatix.cs.uoregon.edu (Wes Santee)
Subject: Please post FAQ file if it exists
Organization: University of Oregon Computer and Information Sciences Dept.
Distribution: usa
Date: Tue, 7 Apr 1992 00:16:07 GMT

'Lo

Is there a FAQ file for this newsgroup?  If so, could someone please
post it here (please don't send it e-mail, I don't want 50 copies of
it in my mailbox).

If not, could someone point me in the right direction on the different
ways to get my PC Clone talking tcp/ip on the Internet.


Thanks in advance,
-- 
Wes Santee			| "It all seems so stupid,
santeew@cs.uoregon.edu		|   it makes me want to give up.
				|  But why should I give up,        -Martin 
				|   when it all seems so stupid."      Gore 
Xref: sparky comp.protocols.tcp-ip.ibmpc:2898 comp.os.os2.apps:1500 vmsnet.networks.desktop.pathworks:1426