HDTenEightyP/NetNews huggingface dataset:
From: landman@hal.physics.wayne.edu (Joseph Landman)
Subject: NDIS (ARRRGGGGHHHH!!!!) 
Summary: help me spock...
Keywords: pain....
Organization: Department of Physics and Astronomy
Date: Sat, 22 Aug 1992 20:05:12 GMT

Fellow Netmongers:

  I have been using the Crynwr packet drivers and NCSA telnet and other 
programs quite nicely on my 286 (blech) in my office.  Recently, I obtained 
a copy of the 2 user license network 10Net which uses NDIS.  I was able to 
get that up very easily, and it worked quite well.  However, my packet 
drivers cannot work with the NDIS drivers.  No problem (or so I thought).  I 
just downloaded a copy of DIS_PKT9.DOS from one of the handy-dandy archives, 
and installed it as per the instructions.

[frustration on]
For 2 <explitive deleted> days I have been trying to get this <really nasty 
explitive deleted> think to work.  It does not, claiming that the 10NET 
program has no driver to bind the PKTDRV$ to.  I was able to get rid of all 
of the other error messages, but that one.  I have the correct SMCMAC.DOS 
for my WD8013 board, and all of the 10net stuff installed.  If anyone out in 
Net.World has a clue as to what might help me (aside from a vacation), I 
would greatly appreciate a pointer.  Please email any suggestions, flames, 
etc to landman@hal.physics.wayne.edu

Thanks

Joe Landman
(Annoyed, and possibly unbalanced)
#,:::::::;,   ::            Joe Landman  Graduate Student (PhD),
#    ::       ::            Computational Solid State Physics.
#;:  ::       ::            Physics Dept., Wayne State Univ.   
#`::::; oe    ;:::; andman  666 Hancock Avenue, Detroit MI 48202 
#Internet: landman@hal.physics.wayne.edu landman@rhic2.physics.wayne.edu
#          kil@pandora.cs.wayne.edu  jland@ss0.eng.wayne.edu
#ATTnet: (313) 577-2720
From: exujlg@exu.ericsson.se (Jon L. Gauthier)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Will cutcp run under OS/2?
Date: 12 Aug 92 17:34:37 GMT
Organization: Ericsson Network Systems, Inc.

In article <1992Aug12.114547.14588@jupiter.sun.csd.unb.ca> dedourek@jupiter.sun.csd.unb.ca (John DeDourek) writes:
>From: dedourek@jupiter.sun.csd.unb.ca (John DeDourek)
>Subject: Will cutcp run under OS/2?
>Date: 12 Aug 92 11:45:47 GMT

>Is it possible to run the DOS tcp/ip applications from the cutcp package
>as DOS applications under OS/2 ver 2.0 while at the same time running
>the IBM LAN requester for OS/2 to access "network drives" from an
>OS/2 LAN server, with both using the same 16 MByte token ring adapter?

>Is anyone doing this now?

>Any hints, e.g. forget it, try this, etc. would be appreciated.

>E-Mail replies to:   dedourek@jupiter.sun.csd.unb.ca
>                    John DeDourek
>                    Faculty of Computer Science
>                    University of New Brunswick
>                    Fredericton, New Brunswick Canada

>If thought useful, a summary of replies will be posted to
>comp.protocols.tcp-ip.ibmpc.

I've tried, but couldn't do it unless I had a second ethernet board.
But, of course, I was using IBM's lan requester on a MS LanMan
workstation (I may not like MS, but Lan Manager works better for us than
Netware! - I can feel the heat already...)

Regards,
------------------------------------------------------------------------------
Jon L. Gauthier                                 Ericsson Network Systems, Inc
EXU/IS/TP Systems Programmer                                  P.O. Box 833875
+1 214 997-0157                                     Richardson, TX 75083-3875

Disclaimer:  "My opinions are my own - my employer would take the 5th on
             everything I say."  Surely it's been said before!...
------------------------------------------------------------------------------
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: cgh018@tijc02.uucp (Calvin Hayden x2254)
Subject: Re: EMail UNIX <-> DOS
Organization: Siemens Industrial Automation, Johnson City TN
Date: Thu, 20 Aug 92 16:37:11 GMT

From article <1992Aug14.191410.21924@siesoft.co.uk>, by xtest@siesoft.co.uk (xtest):
> Please feel free to flame me if this is the FAQ I think it is :-)
> 
> We have a network of UNIX servers. These run email, news etc. perfectly
> happily. We now have more and more DOS users coming on-line. Until now
> we have been happy for them to have an account on a UNIX host and read
> mail via a windows based emulator. It has now been decided that it
> would be a better idea if they could read mail from their local DOS server
> (be it OS2 or Novell).
> 
> The question is, what is the *easiest* (i.e. roughly equal parts cost
> and ergonomics) way to achieve this? For example, do we setup a Novell
> to UNIX gateway or OS2 to UNIX etc. etc.
> 
> I would appreciate it if somebody could list the available options and/or
> tell me where to look for best advice.
> 
> Please mail me directly and I will summarize responses...
> 
> Many thanks inadvance,
> 
> --
> bruce@siesoft.co.uk   Bruce C. Beadle, SNI, Bracknell RG12 8FZ England.
> Phone : +44-344-850485 (Desk).  |  +44-344-862222 (Switchboard)
> "Baldrick, your brain is like the great four headed haddock eating
> fish monster of Aberdeen - it doesn't exist!"  
We have a network of Sparcs, and a Novell network as well.  Our solution
was to grab "charon" off the net.  The Charon package (from Clarkson I think)
runs on a dedicated PC - a 286 is fine in our case.  It talks smtp to "talk"
to unix boxes and IPX to talk to the Novell queues.  We then got another
freebie off the net - Pegasus Mail  (pmail for short).  This package runs on
the novell nodes and interacts with the queues that charon uses.  Documentation
for it has a small cost, but online help is good enough to get started.

If you can get these two, take a look at them and see if it will solve some
of your needs - its def. low cost.  If you can reach uunet.uu.net, I think
that they have both.  Simtel may also have them.

Calvin

-- 
Calvin Hayden                   Uucp: uunet!tijc02!cgh018        
Siemens Industrial Automation   Inet: cgh018%tijc02@uunet.uu.net  
-- My opinions and mine alone --      cgh018@tijc02.uucp         
Newsgroups: comp.protocols.tcp-ip.ibmpc,news.software.readers
From: seant@sunfish.ratsys.com (Sean D. True)
Subject: Re: Trumpet Shell for FTP Software TCP stack.
Organization: Rational Systems, Inc.
Date: Thu, 20 Aug 1992 16:10:53 GMT

In article <kemp.713806943@convex.convex.com> kemp@convex.com (Phil Kemp) writes:
... 

>I tried over a slip connection and could not get this to work. Either
>from DOS or under DV/X.

>>run it in an ms-dos window under windows 3.1, but that does not work.
>>I keep getting "599 Command timed out". Changing parameters for

>That's the error I get too.

>>trumpnet and the PIF file had no effect until now.
>>The FTP software version is 2.05. Am I trying something that is
>>impossible or using the wrong setup? Other FTP commands work OK under
>>windows.

>Ditto under DV/X

>Any ideas?

I use Trumpet with the FTP wrapper under DVX at the office without trouble,
over a standard FTP Ibanyan driver. I haven't tried it over slip, although
I have run it from home using the asynch BANYAN network kernel and the same 
standard FTP Ibanyan driver. With DVX, you do have to install QOS network
support for DVX, remember to load the FTP kernel before loading DVX, and
not trying to load it again in your DOS window. (Sounds stupid, but I have
done it by accident a couple of times).

Is there any interest in a NEWSX style wrapper to run on top of DVX's network
support? 
================================================================
Sean D. True
Rational Systems, Inc.
seant@ratsys.com -- uunet!rational!seant
From: JOCELYN@novl1.ci.cuslm.ca (Jocelyn Nadeau)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: New readers for the Macs
Date: 21 Aug 92 19:56:59 GMT
Reply-To: jocelyn@cuslm.ca
Distribution: world
Organization: Centre univ. Saint-Louis-Maillet

How about Nuntius (also un SUMEX).  The best I've seen so far.

Jocelyn
------------------------------------------------------------------------
Jocelyn Nadeau                                   Jocelyn@cuslm.ca
Centre universitaire Saint-Louis-Maillet         506-737-5050 ext 5277
Edmundston, NB Canada                            fax 506-739-5373
E3V 2S8
------------------------------------------------------------------------
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: mikelle@vaxb.gbus.virginia.edu (Eddie Mikell)
Subject: ncsa telnet and the del 333p machine - does anybody's work?
Organization: Darden Center, University of Virginia
Date: Wed, 12 Aug 1992 21:19:46 GMT

Greetings:

I am experiencing a problem with getting NCSA telnet to work with a
Dell 333p 386 33mhz machine.

I am using an ibm token ring card, the ibmtoken software, and plain
vanilla telnet.  This same set up has worked on most clones I have 
used (treasure chest, dtk, alr, etc) without a hitch.

I have tried slowing the machine down, disabling the shadow ram, 
disabling all the serial ports, booting with a barren bootable
floppy disk, etc., with no luck.

Any suggestions?  I was somewhat appalled by the fact that none of
the Dell technicians had heard of the internet, let alone NCSA software, 
so they have been of no help.

Thank you.

Eddie 
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: DGH@herald.divinity.yale.edu (Duane Harbin)
Subject: 3C503 packet driver and SDLC
Organization: Yale Divinity Library
Date: Fri, 21 Aug 1992 18:03:23 GMT

Can anyone suggest some appropriate voodoo to make a 3C503 operated under 
the Clarkson packet driver co-habitate pleasantly with a Synchronous Data 
Link Controller?
The SDLC is apparently a pretty nasty piece of work. It insists on Interrupt 
3 and DMA channel 1. The packet driver addresses the issue of interrupt, but 
not the DMA channel. Actually, it looks as if the 3C503 packet driver isn't 
supposed to be using DMA at all.
Further info:
System: IBM XT/286, 640K RAM
OS:     DOS 3.30
NOS:    Netware 3.11
PD:     3C503.COM version 9.4.1 (Card is set for shared memory base DC000)
There is a particular application that utilizes the SDLC. The network and 
the application will both start out fine. However, if the SDLC application 
is running and attempts to access network services, e.g. printing, the 
system freezes up. If one shells out of the SDLC application and attempts to 
switch to a network drive, the system freezes.
Any suggestions welcome. Thanks.
Duane Harbin
Information Services Librarian
Yale Divinity School Library
203/432-5289
DGH@herald.divinity.yale.edu
From: nelson@crynwr.com (Russell Nelson)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: INT14 support for packet drivers 
Distribution: world
Date: Fri, 21 Aug 92 13:43:33 GMT
Organization: Crynwr Software

In article <p79mn+_.ian@netcom.com> ian@netcom.com writes:

   Is there an INT14 driver out there that will work with the
   Crynwr packet drivers?  I'd like to be able to use my own
   communications software instead of telnet.

The free Wattcp package has one (as do many commercial packages).
It's on sunee.uwaterloo.ca, in pub/wattcp.

-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,news.software.readers
From: GeraldR@sunfish.ratsys.com (Gerald Ruderman)
Subject: Re: Trumpet Shell for FTP Software TCP stack.
Organization: Rational Systems, Inc.
Date: Fri, 21 Aug 1992 03:36:47 GMT

In article <kemp.713806943@convex.convex.com> kemp@convex.com (Phil Kemp) writes:

>In <1992Aug14.083700.26995@kub.nl> mvw@kub.nl (Maarten van Wijk) writes:

>>I have been trying this out and it works great. But I would like to

>>run it in an ms-dos window under windows 3.1, but that does not work.
>>I keep getting "599 Command timed out". Changing parameters for

>That's the error I get too.

I can't get it to run under Windows either and I have the guy who wrote the 
shell right down the hall. Someone hear claims they did run udner Windows 
once, but I think they can't anymore.

Gerald Ruderman                                   geraldr@ratsys.com
From: crmcguffin@crmcg.com (Craig R. McGuffin)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Problem Running KA9Q Over Lantastic
Date: Sun, 16 Aug 92 23:58:54 EDT
Organization: C.R. McGuffin Consulting Services

Greetings all.

I'm trying to get TCP/IP to run over Lantastic.  (Why?  Because its there.)
Right now I'm just using 2 PC's, with the KA9Q package.  I've used it
with both AX.25 and SLIP connections, and been successful.  Unfortunately,
I can't seem to get things going over Ethernet.

The Ethernet cards are two of Artisoft's AE-3 boards.  I'm also using their
low-level drivers (AEX and AILANBIOS).  Lantastic has been working fine with
this configuration.  (However, for these tests, I haven't even loaded the
Lantastic redirector or server software.

I've obtained the NB packet driver, and it seems to load and talk to the
low level drivers.  On each machine, I load KA9Q, set the IP address, attach
the packet interface, start the servers, and start tracing to see what's
happening.

When trying to initiate a telnet session, the source machine's NB seems to
figure out the "fake" ethernet address of the target properly.  The KA9Q
ethernet, IP, and TCP level trace results look as I would expect them to.

On the target machine, the connection attempt seems to show up on the
interface, since trace shows packets being received.  I'm assuming that
means that the NETBIOS datagrams are going through between the NBs as they
should.  The IP and TCP level results again look ok (right address, ports,
etc.)  However, the target never picks up on the connection request.  It
just sits there with a silly look on its face, dumping trace results.

The only thing that looks out of place is on the ethernet trace...the
destination ethernet address shown on the target machine's trace results
is something weird, and it's different than the destination address shown
on the source machine's trace (which is the correct "plugged" IP address).
It looks like the address has been mangled by the target's NB driver somehow.

I've tried this both ways between the two machines, and get the same results.

If anyone has any suggestions on what's going wrong here, I'd appreciate
them via e-mail.  I can supply trace results and KA9Q configuration
information, if that would help.

Many thanks,

Craig McGuffin


-----------------------------------------------------------------------------
Craig R. McGuffin                                      Voice: +1.416.485.0623
Internet: CRMcGuffin@CRMcG.COM      (TORONTO, CANADA)    Fax: +1.416.489.1732
From: jrd@cc.usu.edu
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Kermit over NCSA Telnet(Using hardware=decnet)
Date: 20 Aug 92 01:44:30 GMT
Organization: Utah State University

In article <2220@sjfc.UUCP>, cpd1450@sjfc.UUCP (Craig Dufresne) writes:
> I have set up a PC to connect to a BSD4.3 Vax using NCSA Telnet 2.5.03,
> using the command hardware=decnet. I am also running pathworks with
> connections to Lat machines via the sethost command.
> 
> Now, I would like to add Kermit as an option. I can't use the packet
> drivers since they seem to screw up decnet. Is it possible to run kermit
> over the NCSA Telnet. The Kermit book talked about using Interrupt 14, is
> this related to the NCSA command net14 ??? Any help or explanations would
> be greatly appreciated ...
> 
> Craig Dufresne
> Internet: cpd1450@sjfc.edu
-----------
Craig,
	There's more than hope. First, Pathworks using NDIS and DECnet
packets can indeed run jointly with Kermit. What you need in this case
is a small protocol shim to provide a Packet Driver interface and use
NDIS as a substitute for a board. I happen to offer one named dis_pkt9.zip,
similar but not quite the same as dis_pkt.gup offered by FTP Inc though
they do the same basic job. Obtain dis_pkt9.zip by anonymous ftp to
netlab2.usu.edu, cd misc. There is a doc file in that archive. Also, MSK
v3.12 beta is in parallel directory kermit.
	Kermit has it's own internal TCP/IP stack for use with Telnet, as
well as working over other stacks by various methods. I have never gotten
NCSA's NET14 program to work here, undoubtedly a failure on my part, but
in any case performance will be much much better without this.
        As an added benefit, one time only, call now... is you can also
run Kermit on the top of Pathworks, replacing SETHOST. All this is handily
discussed in the user's manual, the paperbound book "Using MS-DOS Kermit",
2nd ed, Christine Gianone, Digital Press and Prentice Hall, 1991. A hint
is SET PORT DEC hostname; this will use either LAT (preferrably) or CTERM
automatically. And for calling right this minute... you can do both over
Pathworks and do Kermit's internal Telnet without rebooting etc. Nifty
slicing and dicing.
	Further queries on the Kermit part of this should be sent to me
at either jrd@cc.usu.edu or jrd@watsun.cc.columbia.edu. Please read the
docs and give things a try first however.
	Joe D.
From: galaad@broue.rot.qc.ca (Colin Surprenant)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: lpr on ISC 3.2 & PCTCP 2.05
Date: 21 Aug 92 18:22:07 GMT
Distribution: world
Organization: Groupe de Recherche Operationnelle en Telecommunication (ROT)
X-Newsreader: Tin 1.1 PL4


I am currently trying to configure lpr on ISC SVR3.2 and DOS workstations
using PCTCP R2.05. I can't get the damn thing working...

On the UNIX side I have lp configured properly with a printer called 'laser'.
Now, I'm trying to configure lpr with the /etc/printcap file. One way I have
lpr working localy only is like that:

lp|TI laser:\
  :lp=/dev/lp:sd=/usr/spool/lpd/lp:

Then I try to lpr.exe from PCTCP and it complains telling me :
error from server : 47 usr/lib/lpd: host name for your address (x.x.x.x) 
unknown

(x.x.x.x) being my PC IP address. 

So, browsing through documentation I find out I have to insert my workstation
name in the file 'hosts.lpd' which I did. I tried with the name 'PC2' or with
the complete domain 'PC2.syner.net' or even with the IP... no go.

I tried to configure /etc/printcap in this other way:

lp|TI laser:\
  :lp=:rm=isc1:rp=lp:sd=/usr/spool/lpd/lp:

isc1.syner.net being my UNIX server.

Like that when I try to lpr localy, it gets in the queue but nothing comes out
and when I issue a lpq to look at the queue, it gives me this message:
ISC1: waiting for queue to be enabled on isc1

But the queue is enabled when I look at the status using lpc.

HELP!
-------------------------------------------------------------------------------
galaad@rot.qc.ca     | Colin Surprenant
                     |
IP: 192.77.49.131    | ROT inc.
                     | Recherche Operationelle en Telecommunication
                     |
Voice: 514-685-7575  | Synerlogic (a Anderson Consulting Division)
Fax:   514-685-7692  | Montreal, Quebec
-------------------------------------------------------------------------------
From: nelson@crynwr.com (Russell Nelson)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Need information on Intel 16 bit ethernet card 
Distribution: world
Date: Fri, 14 Aug 92 18:14:56 GMT
Organization: Crynwr Software

In article <1992Aug13.190909.7965@crash> fpm@crash.cts.com writes:

   Can I get packet drivers for these?

I believe that Intel wrote a packet driver for this board...

-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
From: xtest@siesoft.co.uk (xtest)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: EMail UNIX <-> DOS
Date: 14 Aug 92 19:14:10 GMT
Organization: Siemens Nixdorf Information Systems Ltd.
X-Newsreader: Tin 1.1 PL4

Please feel free to flame me if this is the FAQ I think it is :-)

We have a network of UNIX servers. These run email, news etc. perfectly
happily. We now have more and more DOS users coming on-line. Until now
we have been happy for them to have an account on a UNIX host and read
mail via a windows based emulator. It has now been decided that it
would be a better idea if they could read mail from their local DOS server
(be it OS2 or Novell).

The question is, what is the *easiest* (i.e. roughly equal parts cost
and ergonomics) way to achieve this? For example, do we setup a Novell
to UNIX gateway or OS2 to UNIX etc. etc.

I would appreciate it if somebody could list the available options and/or
tell me where to look for best advice.

Please mail me directly and I will summarize responses...

Many thanks inadvance,

--
bruce@siesoft.co.uk   Bruce C. Beadle, SNI, Bracknell RG12 8FZ England.
Phone : +44-344-850485 (Desk).  |  +44-344-862222 (Switchboard)
"Baldrick, your brain is like the great four headed haddock eating
fish monster of Aberdeen - it doesn't exist!"
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Looking for a brouter
From: bartont@next2.msci.memst.edu (Tom Barton)
Date: 13 Aug 92 17:38:58 -0600
Distribution: world
Organization: Mathematical Sciences, Memphis State University
Summary: I've got one

In article <22081011003695@vaxb.acs.uwlax.edu> ABTSACS@UWLAX.EDU (Dan Abts - UWL System/Network Manager) writes:
>What are you using in a situation where you need to bridge Novell 
>ipx and route tcp/ip?  For ease of management, I am using bootp and 
>rip.  I have tried the following:
>
>PCRoute 2.24 works fine on a quiet network if you don't have more 
>than one brouter forwarding bootp.  I'm trying to connect 22 
>buildings on our campus.  So far I have 11 buildings connected and 
>most of the rest will only have a few pc's, but PCRoute hangs if 
>used as the brouter to isolate a building.  Older versions of PCRoute 
>don't hang up but still have the bootp problem.  
> ...

Hi Dan,

Sorry to post to the net, but mail to both of your email addresses bounced.

I have a patched version of PCroute v2.23 that both solves the bootp problem
and works fine in the brouter configuration. There are also some other
optional added features. I'm willing to send you context diff's based on the
v2.23 source if you'd like to look it over.

-- 
Tom Barton			       Internet: bartont@hermes.msci.memst.edu
Department of Math Sciences	       Internet: bartont@next2.msci.memst.edu
Memphis State University	         Bitnet: bartont@memstvx1
Memphis, TN 38152			  Phone: 901/678-2527
Newsgroups: comp.protocols.tcp-ip.ibmpc