HDTenEightyP/NetNews huggingface dataset:
From: gdennis@ntuix.ntu.ac.sg (Dennis Sng)
Subject: Wanted: CUTCP Key Map for IBM PC/AT 84key Keyboard
Organization: Nanyang Technological University - Singapore
X-Newsreader: Tin 1.1 PL4
Date: Thu, 10 Sep 1992 04:58:21 GMT

Pardon me if this is a FAQ ...

I have a user of an original IBM PC/AT with an 84-key keyboard.  
This user has been using DEC's PATHWORKS to get to our VAX which
is running VMS. 

He would now like to switch to using CUTCP instead of PATHWORKS.  
However, the keyboard mapping of the DEFAULT.TBL is not compatible
with DEC's ALLIN1 and Notes Conferencing applications.  

Does anyone out there know where I can get an suitable key map file?
Or if anyone out there has such a file, could you please post it here
or mail it to me.

Thanks in advance,
Dennis.

=========================================================================
Dennis Sng		 		Internet: gdennis@ntuix.ntu.ac.sg
GINTIC Institute of CIM				   Bitnet: GDENNIS@NTUVAX
Nanyang Technological University		       Fax: (65) 791-6377
Singapore 2263					       Tel: (65) 799-5548
From: karl@empirical.com (Karl Auerbach)
Subject: Re: PC/TCP 2.1 copy protection
Organization: Empirical Tools and Technologies
Distribution: usa
Date: Thu, 10 Sep 1992 01:56:30 GMT

I've been running the FTP 2.1 code with the serial number code for some 
months now.

John Romkey's summary is generally correct.  The serial number seems to be 
carried in ARP frames (in the unused part between the end of the true ARP 
packet and the end of the minimum size Ethernet frame.)

When there is a clash of serial numbers, there is the good old Romkey chirp 
and a fairly non-intrusive error message.  It only seems to appear 
occassionally and only at the DOS prompt.  (I haven't seen it under Windows.)

There is a special disk which has a serialized module.  The numbers on the 
disk has to be entered into the pctcp.ini file.  If the numbers are wrong
the kernel won't load.  If you just clone machines from a master machine 
like I tend to do, you only need to copy a:*.* c:\pctcp for the one special 
(360K) disk, not the entire set.

I've found it pretty painless to set up and not particularly intrusive
when a collision happens.  [I was part of the 2.1 beta test so I had lots of 
copies with the same serial number for quite a while.]

I just had to make adding the right serial number to the pctcp.ini file part 
of the ceremony of giving an IP address and name to a new machine.

			--karl--

>Unless it's changed since my last understanding of it (which I doubt
>but is possible), FTP Software's copy protection scheme will not
>require you to have a specific diskette per machine, nor will it
>generate any extra network traffic.
>
>Also, the serial number is
>piggy-backed on ARP packets, not in special broadcasts, so it doesn't
>cost you any extra traffic.
From: karl-boyken@uiowa.edu (Karl Boyken)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: SUMMARY:  NCSA Telnet & WINPKT
Date: 11 Sep 92 13:30:27 GMT
Organization: Dept. of Comp. Sci., U. of Iowa

Thanks to everyone who responded to my original question about why NCSA Telnet
was complaining that it couldn't find the packet driver vector.  I received
a number of replies, ranging from "you're doing everything correctly; it must
be a bug" to "use the decimal equivalent of the hex vector number" to "just 
let Telnet search for the vector".

One suggestion does seem to work: in CONFIG.TEL, use "ioaddr" to specify the
packet driver vector, not "interrupt".  When I use ioaddr=60, Telnet quits
complaining that it can't find the vector.  However, Chapter 7 of the Telnet
documentation states that the "interrupt" should be used to specify the vector.
Is this a bug in the documentation?

Unfortunately, I lost the original message that told me about using ioaddr, so
I cannot thank the sender directly.  So, thanks again--you know who you are.

*****        _My_ views, no one else's--except those I plagiarize         *****
Karl Boyken, system programmer |
Department of Computer Science | This is no social crisis
The University of Iowa         | Just another tricky day for you
karl-boyken@uiowa.edu          |                            -- Pete Townshend
From: phys169@csc.canterbury.ac.nz
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Problem with NCSA ftp <-> WinQVT
Date: 9 Sep 92 01:55:12 GMT
Organization: University of Canterbury, Christchurch, New Zealand

I have a problem with NCSA ftpbin hanging soon after connecting to a PC running
WinQVT, but is okay (well, 99%) when connecting to a VAX or Unix system. I can
only guess it has something to do with retries, timing, buffer sizes, etc or
that fact that the two PC's running 2.3.05 NCSA that fail are 286's with 3c501
cards (the one running WinQVT is a 386 with a WD8003e, if that is relevant).

I can open the connection, log in, find out the working directory, but as soon
as I transfer anything (even do a dir listing) it hangs.  I can log onto a VAX,
get the files to it, and then from VAX to the 286 without problems.

Do these symptoms indicate some obvious configuration error??

Mark Aitchison, University of Canterbury, New Zealand.
From: nelson@crynwr.com (Russell Nelson)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: NE2100 packet driver ?
Date: 14 Sep 92 11:59:29 GMT
Organization: Crynwr Software

In article <716179309snx@crynwr.com> nelson@crynwr.com writes:

   In article <1992Sep10.180834.17437@cti-software.nl> pim@cti-software.nl writes:   
      I've got hold of an ethernet card that seems to be a
      clone of a Novell NE2100 (?).

   Are you sure about that?  More likely it's a NE2000 clone.  What
   ethernet controller does your board use?

He told me via email that yes, indeed, it is a NE2100 clone.

-russ <nelson@crynwr.com>  I'm proud to be a humble Quaker!
Crynwr Software            Crynwr Software sells packet driver support.
11 Grant St.               315-268-1925 Voice
Potsdam, NY 13676          315-268-9201 FAX
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: ileicht@jarthur.claremont.edu (Spiff)
Subject: Is there
Organization: Harvey Mudd College, Claremont, CA 91711
Date: Thu, 10 Sep 1992 14:45:45 GMT

any way to use psuedo-packed drivers with OS/2?
From: ken@faculty.law.duke.edu (Ken Hirsh)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: thanks and more help with ip routing
Date: 10 Sep 92 13:49:07 GMT
Organization: Duke University School of Law

In article <ken.42@faculty.law.duke.edu> ken@faculty.law.duke.edu (Ken Hirsh) writes:

>Well, thanks to the help of many of you and the dedication of
>our staff in the law school and at Duke Network Operations, we
>have our IP routing working.  We are able to telnet all over the
>place, with one nasty exception.  When we try to Telnet to
>machines at North Carolina State University, net 152.1, we are

Well, we solved our own problem.  In our config.tel we set the subnet mask, 
which normally is set by the RARP request. However, that wasn't working for 
the connection to machines on 152.1.  Spelling out the netmask in config.tel 
fixed the problem.
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: dan@dribble.c-mols.siu.edu (Dan Ellison)
Subject: Re: NCSA Telnet & WINPKT
Organization: Southern Illinois University - Carbondale, IL (SIU-C)
Distribution: usa
Date: Fri, 11 Sep 1992 13:11:07 GMT

In <david.716115995@aim1> david@aim1.aztec.co.za (David Mason) writes:

>dan@dribble.c-mols.siu.edu (Dan Ellison) writes:

>>>In article <1992Sep4.184222.280@news.uiowa.edu> boyken@herky.cs.uiowa.edu (Karl Boyken) writes:
>>>>I've set up a number of PCs with NCSA Telnet and Windows, using WINPKT.

>>Also, you should probably create a pif file so you can set up background
>>processing or your sessions will die when they are not running in the 
>>forground.  you might also want to look at pktmux as it will allow more
>>than on session through the NIC (can run QVTnet and NCSA at the same
>>time!)

>What's this pktmux?  Can I run multiple telnet sessions with it over
>the same packet driver under windows - and make a simple x terminal?
>PD?  FTP'able?   More details please.

Yes. Yes. Yes.  It allows you to run multiple concurrent TCP/IP stacks
on a single NIC.  The methods for doing this are outlined in the docs
that come with the archive.  It is in the PD and it is ftpable from
numerous sites.  I think that I got it from gatekeeper.dec.com but
I'm not sure.  wuarchive.wustl.edu has it in mirrors2/msdos/pktdrvr
as pktmux11.zip.  Good luck with it.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| Dan Ellison, Network Team 	  -    	Computing Affairs, SIU-C 	| 
| Southern Illinois University 	  - 	Carbondale, IL 62901            |   
| FAX:      (618) 453-3459        -   	PHONE:    (618) 453-6149 	|
From: dsc3jfs@nmrdc1.nmrdc.nnmc.navy.mil (Jim Small)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: PC/TCP 2.1 copy protection
Date: 10 Sep 92 10:33:09 GMT
Distribution: usa
Organization: Naval Medical Research & Development Command

In article <gweil.85.716068151@ibeam.intel.com> gweil@ibeam.intel.com (Garry A. Weil) writes:
>>Subject: PC/TCP 2.1 copy protection
>>Message-ID: <1992Sep8.214208.41914@clinicom.com>
>>Date: Tue, 8 Sep 1992 21:42:08 GMT
>>Distribution: usa
>>Organization: CliniCom Incorporated, Boulder, CO
>>Lines: 43
>
>
>>I just got a call from someone at FTP Software informing me that our upgrade to
>>2.1 should ship in the next week or two. "Great!" says I -- I've been waiting
>>for some of the new features for a long time. But this is no mere notification,
>>I'm told, and sends out its signature onto my Ethernet, so all of my PCs'
>>kernels can tell if they have been installed on more than one workstation.
>
>This is just FTP playing catch-up with Sun. PC-NFS has had similar copy 
>protection since I started using it a year ago.

Don't you mean, 
"This is just FTP being just as stupid as Sun.  PC-NFS has been anal retentive
for the past year."

And to think the guys at FTP had the gaul to ask me why we were NOT going
to upgrade our current kernel.

well guys,  YOU HAVE A REASON NOW.

The last thing I want to do is monitor over 800 copies of a copy protected
kernel . . . 

-- 
I hate the 3B2
The 3B2 can bite me.
From: ken@faculty.law.duke.edu (Ken Hirsh)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: thanks and more help with ip routing
Date: 10 Sep 92 13:03:54 GMT
Organization: Duke University School of Law

Well, thanks to the help of many of you and the dedication of
our staff in the law school and at Duke Network Operations, we
have our IP routing working.  We are able to telnet all over the
place, with one nasty exception.  When we try to Telnet to
machines at North Carolina State University, net 152.1, we are
unable to open a connection.  A tech there monitoring a host
saw our request to open the connection, but apparently we are
not getting the response back to our machines.  Can you help?  I
am including the relevant portion of our autoexec.ncf.  It seems
strange that there is no problem with hosts on other networks.
load ne3200 slot=5 name=ne32ipx
bind ipx to ne32ipx net=1abc
load ne2000 int=2 port=300 name=ne2ipx
bind ipx to ne2ipx net=1000
load ne3200 slot=5 frame=ethernet_ii name=ne32ip
load ne2000 int=2 port=300 frame=ethernet_ii name=ne2ip
load tcpip forward=yes rip=yes
bind ip to ne32ip addr=152.3.95.254 mask=ff.ff.ff.00
bind ip to ne2ip addr=152.3.3.214
mask=ff.ff.ff.00 gate=152.3.3.250 arp=yes bcast=152.3.255.255
From: backman@FTP.COM (Larry Backman)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Named Pipes
Date: 8 Sep 92 18:13:41 GMT
Distribution: world
Organization: The Internet


 >> 
 >>     .... Still, this leaves the question, where are the RFC 1001/2 equivalents
 >>     for doing Named Pipes on TCP/UDP? Not worth the effort??
 >> 
 >> My personal opinion (which may be from way out in left field, since I've
 >> not done any actual named-pipes applications) is based on my understanding
 >> that Microsoft based named pipes on a Netbios-style flat namespace, with
 >> broadcast name defense implied.  This works badly in an internetworking
 >> environment, just like Netbios.  I think you can run at least some
 >> named-pipes applications with a glue layer that thranslates to Netbios calls,
 >> and that appears to be satisfying whatever demand there is...
 >> 
In past lifetimes I've implemented the named Pipes protocol.  Save your
energy Keith; it makes 1001/2 look pretty :-).

L>
From: krab@iesd.auc.dk (Kresten Krab Thorup)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Packetdriver for 3c503/16bit ?
Date: 14 Sep 92 14:27:43 GMT
Distribution: comp
Organization: Mathematics and Computer Science, Aalborg University

I just had a new 16 bit 3c503 ethernet card, but but but -- I have no
packet driver that can run with it in 16 bit mode, 8bit mode works
fine with the available driver... :-(

Anyone working on it?

/Kresten
From: geoff@tyger.Eng.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: PC/TCP 2.1 copy protection
Date: 13 Sep 1992 03:29:04 GMT
Organization: SunSelect
NNTP-Posting-Host: tyger.east.sun.com

As the evil person who coded the first of these serial number
broadcasting schemes, let me add a couple of words. First, as B&W and
FTP have stated, the pressure from overseas distributors to retain/
introduce such a mechanism is overwhelming. In view of the fact that
around 50% of our sales are outside the US, this is something that we
(SunSelect) cannot ignore. Although the situation is better in the US,
it would be naive (and costly) to assume that software license
violation does not take place here too. I used to be in favour of
eliminating serialization from PC-NFS, but real-world data which we
have gathered over the years convinced me some time ago that it would
be really dumb to do so.

Over the years, our customers have come up with extremely ingenious
(and often amazing) ways to rework the licensing model into something
that is easier to live with. One site blew the serial number into a
boot PROM on each PC and ran a little program to patch the number into
the local copy of PCNFS.SYS. Another customer with many thousands of
PCs worldwide built their own RPC-based installation mechanism:  they
reserve one PC-NFS serial for use in their "setup diskettes", of which
they have many copies. Booting off this diskette runs a program which
NFS mounts the master distribution area, copies down an up-to-date
distribution kit, requests a new serial number and IP address, patches
everything up, and restarts with the new, legal serial. We are
completely happy for people to do stuff like this: as long as they
conform to the spirit of the license (one actively used copy, one
serial number), they are free to use any mechanism they choose
to implement it.

Obviously the biggest problem with serial numbers is managing them, and
ensuring that you don't have valuable resources (licenses) going to
waste because they are tied to unused (or even defunct) systems.
Customers such as those mentioned above have created mechanisms to
track and manage licenses. Over time we hope to synthesize a generally
usable solution from these and other techniques.

Geoff

--
Geoff Arnold, PC-NFS architect, Sun Select. (geoff.arnold@East.Sun.COM)
-----------
News software that enforces a four-line .signature limit is responsible for
the fact that these postings just go on and on and on and seem to end in mid-
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: jallen@oat2.standard.com (John Allen)
Subject: Re: Desqview/X experience ?
Organization: Standard Insurance Company - Portland Oregon
Date: Tue, 15 Sep 1992 04:25:56 GMT

 just got Deskview X up and running and this is really slick,
I seem to be running out of memory from the under 640k area
on some apps, but this may be due to a networking configuration.
 
Deskview x is the slickest thing I have seen in a while,
Mess Windows does run underneath it with no problems;  A dos
window can be opened plus you can run X over a network.

The coolest thing is that this box can be an X host for standard
X terminals - you need a bit of horse power and ram.  I will be
reconfiguring my 486 this week to try this out.  It looks like this
thing has a multiuser X blackjack game that it can serve to X terminals.

This is really an original package - hats off to the DeskView people
now we dont have just "Windows" to look at!.

-- 
===============================================================================
John Allen  - Network Executive                   E-mail: jallen@standard.com
Network Services                               Telephone: (503) 243-6189
Standard Insurance, Portland Oregon                  FAX: (503) 321-3313
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: wright@lims01.lerc.nasa.gov (Ted Wright)
Subject: Re: PC/TCP 2.1 copy protection
Organization: NASA Lewis Research Center
Distribution: usa
Date: Thu, 10 Sep 1992 13:09:31 GMT

In article <1992Sep8.214208.41914@clinicom.com> john@clinicom.com (John Hensley) writes:
>From: john@clinicom.com (John Hensley)
>Subject: PC/TCP 2.1 copy protection
>Date: 8 Sep 92 21:42:08 GMT
> ......
>Is anyone else torqued about this, or am I letting my bias against copy
>protection cloud my judgment of a handy new network management feature? Any
>suggestions for how FTP could protect their software *without* catching hell
>from people like me? Just doesn't seem likely, given the nature of the product,
>but I'd sure like the current policy to change....

>-- 
>John Hensley           |
>john@clinicom.com      | "You think slower when you graze." -- Holling
>jhensley@nyx.cs.du.edu |

If you want to avoid copy protection, avoid "Distinct TCP/IP" as well.
Ted Wright (wright@lims01.lerc.nasa.gov)
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: martin (Martin Gren) <martin@axisab>
Subject: Re: TCP/IP printer server with LPD
Organization: Axis Communications AB, Lund Sweden
Date: Sun, 6 Sep 1992 21:07:48 GMT


Alan Luchuk> In article <16851C670.PA9690@utkvm1.utk.edu>, PA9690@utkvm1.utk.edu
Alan Luchuk>  (Alan Luchuk) wrote:
Alan Luchuk> 
Alan Luchuk> >Are special purpose devices available that do LPD?  Something
Alan Luchuk> >that plugs into an Ethernet on one side and a printer on the
Alan Luchuk> >other and doesn't require additional software/hardware.
Alan Luchuk> 

My company makes a TCP/IP printer server that supports lpd as well as many
other TCP/IP protocols. Further to this it also support Novell IPX
concurrently - with a lot of features. The box takes up to 4 printers.
If you have any further interest - please send me an email, or to
"info@axis.se" or "info@axisinc.com".

/ Martin

Martin Gren                email: martin@axis.se
Axis Communications AB     Tel: +46 46 19 18 38
S - 223 70 LUND,  SWEDEN   Fax:   +46 46 13 61 30
-- 
Martin Gren                email: martin@axis.se
Axis Communications AB     Tel: +46 46 19 18 38
S - 223 70 LUND,  SWEDEN   Fax:   +46 46 13 61 30
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: billy@sol.acs.unt.edu (Billy Barron - VAX/UNIX Systems Manager)
Subject: Re: Do most PC's use DNS or a local hosts file?
Organization: University of North Texas
Date: Tue, 8 Sep 1992 14:17:26 GMT

dmurdoch@mast.queensu.ca (Duncan Murdoch) writes:
>Very true.  This site has a name server, but it doesn't always work for me:  
>it looks like it'll be such a pain to track down exactly what's going wrong, 
>that I just put the few addresses I need right into the config file.

My site exclusively uses DNS for PCs (over 1200 last count).  We use BOOTP
to program all of our PC's configurations for IP and it works great.  We can
do a campuswide routing change or nameserver change in about 2 minutes.

Billy Barron, VAX/UNIX Systems Manager, University of North Texas
"More Power"
billy@unt.edu, billy@untvax.bitnet, THENET: NTVAX::BILLY
From: mark@noc.missouri.edu ()
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: U of Maryland's TCP/IP for dos?
Date: 10 Sep 1992 21:29:57 GMT
Organization: University of Missouri - Columbia
Distribution: world
NNTP-Posting-Host: noc.missouri.edu

I had previously been told that the University of Maryland might take up 
support of thier product that was previously distributed through the Wiscware
consortium.  Has any one heard any thing further on this?  Could someone give 
me a possible contact at Maryland?  Please reply via E-mail to 
ccmark@mizzou1.missouri.edu, thanks,

Mark 
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: eschwart@netcom.Netcom.COM (Eric Schwartz)
Subject: SLIP connection between a Sun and a PC..
Date: Tue, 08 Sep 92 00:39:50 GMT
Organization: Netcom Online Communications Service
Distribution: comp

I'm hoping someone can give me a rundown on what is involved to get a 386
running Windows 3.1 and Microsoft LAN Manager 2.1 to talk to a Sun (I
believe) via a SLIP connection.  We have a LAN Manager network set up
using 3Com Etherlink II boards (3C503), and goal is to gain FTP, telnet,
mail and news services, preferably with a Windows user interface.

Judging from the questions and answers I've read in the last several 
hundred posts here, I think this is the right place to ask.  If someone
could give me first a _general_ idea of whether or not this can be done,
that would be most valuable right now.  I would prefer to stick to
commercial software in the long run, but on the other hand, I would like
to implement a basic SLIP connection first (without LAN Manager and Windows)
as a first step.  Is there free software that does this on a 386 that is
_not_ running UNIX?  Should I get UNIX?

Please copy me via e-mail if you respond to the newsgroup.

Thanks,

Eric
--

Eric Schwartz
eschwart@netcom.com
work )408( 279-7191
FAX  )408( 279-7167
-- 

Eric Schwartz
eschwart@netcom.com
work )408( 279-7191
FAX  )408( 279-7167
Newsgroups: comp.protocols.tcp-ip.ibmpc