HDTenEightyP/NetNews huggingface dataset:
From: heberlei@cs.ucdavis.edu (Louis Todd Heberlei)
Newsgroups: comp.protocols.tcp-ip
Subject: finding a host's ethernet address
Keywords: ethernet address
Date: 18 Aug 92 21:34:48 GMT
Reply-To: heberlei@cs.ucdavis.edu
Organization: Computer Science, University of California at Davis.

I am sorry if this in not quite the right news group,
or if this question is in a FAQ, but...

Is there a general system call to find the ethernet
address(es) of a host?  For example, if I am working
on a Sun, can I easily determine the ethernet address
(le0 => lance ethernet??) from within C code?

Thanks,

Todd Heberlein

heberlei@cs.ucdavis.edu
Newsgroups: comp.protocols.tcp-ip.ibmpc,comp.os.ms-windows.apps
From: brian@stan.xx.swin.oz.au (TEHAN B)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Trumpet Shell for FTP Software TCP stack.
Date: 21 Aug 92 05:29:17 GMT
Organization: Computer Centre, Swinburne University of Tech., Melbourne, Australia.

In <ADA.92Aug19160709@zip.larc.nasa.gov> ada@zip.larc.nasa.gov (Anthony Arviola) writes:

>As far as the generic kernel goes, I still can't get the newsx.exe to 
>work at standard dos using the bat file suggested.  What I get is a
>statement that the device is loading.  Then finally, I get a message that
>says, that the driver has been unloaded, and I'm back at the dos prompt
>again.

Ditto, we get exactly the same behaviour with the ibanyan FTP kernel. I also
used the batch file suggested. Are there some patches to 2.05 or am I missing
something really obvious? We also tried specifying DOS interrupts etc..

Brian Tehan
Data Communications
Swinburne University of Technology
Melbourne Australia
Email: brian@banyan.swin.edu.au
Newsgroups: comp.protocols.tcp-ip.ibmpc,comp.protocols.appletalk
From: par@nwu.edu (Pete Rodriguez)
Subject: HELP:PS/2 Model 55SX, NCSA Telnet, and DaynaDL/2 Microchannel
Followup-To: comp.protocols.tcp-ip.ibmpc,comp.protocols.appletalk
Organization: Northwestern University
Date: Fri, 14 Aug 1992 16:15:47 GMT

Hello.  I am having problems getting NCSA Telnet to work with a
Microchannel Localtalk card.  Has anyone been successful in getting this to
work?  

If not with NCSA Telnet, are there any other TCP/IP programs that work with
this configuration (exclude KA9Q; it doesn't have VT100 emulation).

Thanks.

____________________________________
Pete Rodriguez
Undergraduate Admissions
Northwestern University
E-mail:par@nwu.edu
       pete@casbah.acns.nwu.edu
From: jackson@acf3.NYU.EDU (Robert Max Jackson,269 Mercer 4th Fl,998-8352,)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Crynwr WD8003E v. 10 packet driver problem
Date: 18 Aug 92 16:18:00 GMT
Organization: New York University



     In response to my query about a problem using version 10 of
the Crynwr packet drivers for Western Digital cards (WD8003E.COM)
Hugh Redelmeier (Thanks Hugh) reposted a June message from Russ
Nelson describing a bug in the 8390 driver used by the packet
driver for this (and other) cards.  As I have neither the skill nor
time (after 7 months of time tracking this down) to figure out how
to reassemble the whole packet driver, I decided to see if I could
simply patch the existing v.10 driver.  It seems to me that it will
work and I am seeking confirmation (I tried it and it seems ok, but
who knows what time bombs await).
     Below, as best I can figure it, is the incorrect and corrected
code (a macro used to insert pauses in communications with the
board).

Actual Code
in Hex        Assembler
-----------   -------------
50            PUSH    AX
E561          IN      AX,61   <---WRONG
58            POP     AX

50            PUSH    AX
E461          IN      AL,61   <---RIGHT
58            POP     AX

This piece of code seems to appear nowhere else in the remaining
code used for the packet driver.  Therefore, a simple search and
replace of the first 4 bytes by the second 4 bytes would seem to
patch the buggy code.  

     IS THIS CORRECT???
Xref: sparky comp.protocols.tcp-ip.ibmpc:4716 comp.sys.novell:6478
From: chs@stan.xx.swin.oz.au (SILVA C)
Newsgroups: comp.protocols.tcp-ip.ibmpc,comp.sys.novell
Subject: Accessing TCP/IP (NCSA TElnet) and Netware - How to
Keywords: Telnet ODI
Date: 12 Aug 92 08:23:29 GMT
Followup-To: comp.sys.novell
Organization: Computer Centre, Swinburne University of Tech., Melbourne, Australia.

I've just managed to get NCSA Telnet working on our Netware 3.11 
network. We are connected to the university backbone. So I now 
know that TCP/IP works.

However my problem is that I am having to take ipx and netx
out of my autoexec so that my packetdriver will work.

I'm sure that this is a FAQ but could someone detail how
i might be able to access both telnet and netware at the same time.

I know its possible, what I'm after is a how-to and a where is it.
From: DVS@ZE8.RZ.UNI-DUESSELDORF.DE ("Wolfgang R. Mueller")
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Is there a free BOOTP answering shim above packet drivers ?
Date: 17 Aug 92 18:01:02 GMT
Distribution: world
Organization: The Internet
X-Unparsable-Date: Mon, 17 Aug 92 17:34:23 CET

Hello,
is there somewhere available a tsr, which intercepts the packet interrupt
to filter outgoing bootp requests and answer them from local information,
so that these informations need not be in many different config files for
different programs ?
Thanks for any hints,
Wolfgang R. Mueller <dvs@ze8.rz.uni-duesseldorf.de> .
From: ukankgs@kuhub.cc.ukans.edu
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Crynwr WD8003E v. 10 packet driver problem
Date: 20 Aug 92 15:57:24 CDT
Organization: Whollllly Mackeral

In article <1992Aug16.145219.28669@cmcl2.nyu.edu>, jackson@acf3.nyu.edu (Robert Max Jackson) writes:
> 
>      I seem to have encountered a problem using version 10 of
> the Crynwr packet drivers for Western Digital cards
> (WD8003E.COM) that does not exist with earlier versions.  As I
> have seen no reference to this problem, I infer it probably results
> from some special interaction that I cannot determine.  Here I
> describe the problem and some of the tests I have done to try and
> locate the source.  This is the conclusion of months of irritation so
> I am hoping that it will help anyone who has experienced anything
> similar.  Also, of course, I would be thrilled if a resolution could
> be found.
>      The problem appears as lost key strokes.  This is often
> referred to as the "sticky shift keys" problem, because it frequently
> results in the Shift, Control, or Alt keys being "stuck" on, ie. as


I also had this problem and reported it along time ago, I thought it
was just on zenith machines, glad to see someone else is also having
that problem, I went back to real early drivers and they work.

Tphillip@research.rgsps.edu
Newsgroups: comp.protocols.tcp-ip.ibmpc,news.software.readers
From: kemp@convex.com (Phil Kemp)
Subject: Re: Trumpet Shell for FTP Software TCP stack.
Organization: CONVEX Computer Corporation, Richardson, Tx., USA
Date: Fri, 14 Aug 1992 15:42:23 GMT
X-Disclaimer: This message was written by a user at CONVEX Computer
              Corp. The opinions expressed are those of the user and
              not necessarily those of CONVEX.

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

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?

PK
--
Phil Kemp, Systems Engineer         Voice:(403)-233-2815
CONVEX Computer Canada Ltd.           Fax:(403)-261-2029
Calgary, Alta.                  Internet:kemp@convex.com
From: PIRARD@VM1.ULG.AC.BE (Andre' PIRARD)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: NDIS packet driver in DOS window?
Date: 21 Aug 92 13:52:25 GMT
Organization: University of Liege (Belgium), SEGI (Computing Center)

[The original question is about using PDs, so forgive the Subject sliding]
On Sat, 20 Jun 1992 13:07:09 -0400 Larry Backman said:
>I'll make the same statement I made on comp.os.os2.xxx.
>
>The correct solution to this problem is to write an OS/2 Virtual Device
>Driver that takes packet driver requests from one or more DOS boxes and
>converts those requests into calls to an NDIS driver.
>...

This wouldn't allow several DOS apps to share the same IP address,
nor OS/2 TCP/IP's [ban PKTMUX], though.
Another approach is to encapsulate IP in a protocol already shared
by DOS, and NETBIOS is (with ES presently, but soon without, I am told).
So, one uses NB.COM with a different IP address in each DOS.
(I haven't tried NB under OS/2 yet, but I am using it under DESQview OK).
And, of course, a NB/IP gateway on the LAN.
PCROUTE does this nicely (I am using it with 2 PDs: IBMTOKEN and NB,
both on IBM's LANSUP).

Of course, the best idea would be to provide OS/2 TCP/IP's API in DOS.
It looks like IBM wants to do that.
So, isn't this the occasion to define the specs of the DosSocketAPI?

Andr'e PIRARD         SEGI, Univ. de Li`ege          139.165 IP Adm.
B26 - Sart Tilman     B-4000 Li`ege 1 (Belgium)      +32 (41) 564932
pirard@vm1.ulg.ac.be  alias PIRARD@BLIULG11.BITNET
From: CCDH001@UTXVM.CC.UTEXAS.EDU
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Telnetting to a PC
Date: 14 Aug 92 14:12:43 GMT
Organization: The University of Texas at Austin

I would like to thank all of the people who pointed me to TELNETD from
Waterloo.  It seems that everybody except me (and our PC consulting dept.)
knew about it.
 
My compliments to the developers.  Unlike many network-related programs
TELNETD is blessedly simple to install.  And, it worked the first time!
I haven't had a chance to test it extensively and when I did test it it
was running on a 286-based system so it was painfully slow.  But, for
what our user wanted it is very nice.  It would be nice if there was a
way for it to recognize that you were trying to get to it from a PC and
therefore allow more programs to be run remotely.  But I'm not complaining.
 
I'm thinking now I can run it at home and while at work pretend to be
doing something when I'm actually cleaning up my hard disc.  B-))
 
Again, thanks to all who helped.
 
                                     <@>
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: MLONG@isucard.card.iastate.edu
Subject: Re: Will cutcp run under OS/2?
Organization: CARD
Date: Wed, 12 Aug 1992 20:05:53 GMT

In article <1992Aug12.114547.14588@jupiter.sun.csd.unb.ca>                      
dedourek@jupiter.sun.csd.unb.ca (John DeDourek) writes:                         
                                                                                
>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.                                                   
>                                                                               
No, I don't think you can do this at the present time, because the Virtual 802. 
2 interface for OS/2 is not in place as of yet.  When that V802.2 is finished   
I think you should be able to do this by using the IBMTOKEN packet driver, and  
Os/2 LAN Req. at the same time on the same card.                                
Mike Long                                                                       
Iowa State univ
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: hugh@cs.toronto.edu ("D. Hugh Redelmeier")
Subject: Re: Crynwr WD8003E v. 10 packet driver problem
Keywords: Crynwr packet driver WD8003e Western Digital keyboard
Organization: Department of Computer Science, University of Toronto
Date: 17 Aug 92 02:58:49 GMT

jackson@acf3.nyu.edu (Robert Max Jackson) writes:
|      I seem to have encountered a problem using version 10 of
| the Crynwr packet drivers for Western Digital cards
| (WD8003E.COM) that does not exist with earlier versions.  As I
| have seen no reference to this problem, I infer it probably results
| from some special interaction that I cannot determine.
...
|      The problem appears as lost key strokes.

Read the enclosed extract from a June message in this group.  Since
Russ is the maintainer of the drivers, I'm surprised that he hasn't
fixed this.

Hugh Redelmeier
hugh@mimosa.com or {utcsri, yunexus, utzoo, scocan}!redvax!hugh
When all else fails: hugh@csri.toronto.edu
+1 416 482-8253

| ~Subject:   Bug in 8390 drivers.
| 
| Some people are having trouble with some of the 10.x packet drivers.
| Specifically, I have heard of problems with the wd8003e and 3c503
| drivers, but it will also be in the ne1000, ne2000, hppclan, and
| ethiie drivers.  Not all machines are susceptible to the bug.
| I was able to reproduce it on only one of my machines.
| 
| This bug changes the state of the caps lock key and otherwise
| interferes with the keyboard.  This is due to line 51 of 8390.asm,
| which is a word input instruction.  It should be changed to a byte
| input instruction "in al,61h".
| 
| -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: mike@childsoc.demon.co.uk (Michael Bernardi)
Subject: IPXPKT and Token Ring
Distribution: world
Organization: The Children's Society
Date: Wed, 12 Aug 1992 15:11:32 +0000

I've been trying to get the IPXPKT (Crynwr IP over Novell IPX packet) router
to work for a couple of months now, without success. I have recently managed
to get hold of BOTH PC Route for PAcket Drivers and KA9Q NET.EXE but neiter
of them worked.

Last week I got a new Madge Smart 16/4 PC Ringnode card which allowed me to
install IBMTOKEN and IPXPKT on the same card and network. With KA9Q's NET.EXE
I could connect to a *ix system via the IBMTOKEN driver and I could telnet to
a PC also running KA9Q via IPXPKT. BUT I could NOT get a connection through
the router itself. ie using NET on the router I could see both networks BUT I
couldn't get through the router. Any ideas how I could solve this would be
gratefully recieved.

Of course if I had a Wester Digital Token Card driver that would work either
with FTP's TCP/IP or with NCSA Telnet/MS-Kermit (Packet Driver) then I
wouldn't need to use this faking of IP over IPX.

Mike
--
 Michael Bernardi        mike@childsoc.demon.co.uk (Internet) | Making lives
 The Children's Society, Edward Rudolf House, Margery Street, | worth living
 London, WC1X 0JL, UK    Voice: +44 71 837 4299    Charity Reg. No. 221124
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: cro@socrates.ed.asu.edu (C. R. Oldham)
Subject: 3com 3c503-16 TP packet driver.
Keywords: 3com 3c503-16 TP packet driver
Organization: North Central Association, Commission on Schools
Date: Fri, 14 Aug 1992 14:42:42 GMT

Short and sweet:

Does anyone know if the Crynwr 3c503 packet driver version 10.5.1 will work
OK with 3com's new 3c503-16 card (16 bit version of the old 3c503
EtherLink II)?  Will the card function in 16 bit mode with it?  If not,
is there a packet driver for the 3c503-16?

Thanks in advance,

Charles R. (C. R.) Oldham | North Central Association, Commission on Schools
cro@socrates.ed.asu.edu or| Arizona State University, Tempe, AZ 85287-3011
aocro@acvax.inre.asu.edu  | 602/965-8700:800/525-9517 | #include <disclaimer.h>
"For the Lord is a great God, and a great King above all gods..." Psalm 95:3
From: nelson@crynwr.com (Russell Nelson)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: 3com 3c503-16 TP packet driver.
Date: 16 Aug 92 07:28:54 GMT
Organization: Crynwr Software

In article <cro.713803362@ennews!socrates.ed.asu.edu> cro@socrates.ed.asu.edu writes:

   Does anyone know if the Crynwr 3c503 packet driver version 10.5.1 will work
   OK with 3com's new 3c503-16 card (16 bit version of the old 3c503
   EtherLink II)?  Will the card function in 16 bit mode with it?  If not,
   is there a packet driver for the 3c503-16?

Short and sweet:

Yes, and yes.

-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: Rick.Ellis@ofa123.fidonet.org
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Novell and WinQVT/Net (Argggghhhh)
X-Sender: newtout 0.01 Jul 13 1992
Date: 16 Aug 92  17:41:25

On <Aug 14 17:41> Steve Lodin writes:

 SL>      odipkt.com
 SL>      winpkt 0x60 0x63

 SL> When I run this, it seems everything loads into RAM except winpkt, which
 SL> gives a message similar to "packet driver is at segment xxxx,
 SL> there is no packet driver at 0x63".  When I run windows 3.1 after this
 SL> sequence, my machine hangs.

odipkt defaults to 0x69 not 0x60.  Try "odipkt.com 0 105".

--- msgedsq 2.1a
From: gt@hprnd.rose.hp.com (Glenn Talbott)
Date: Wed, 19 Aug 1992 20:43:51 GMT
Subject: Re: problems with HPPCLAN packet driver
Organization: HP Roseville Networks Division
Newsgroups: comp.protocols.tcp-ip.ibmpc

>I have obtained two versions of HPPCLAN.COM and have been unsuccessful
>with both:
>
>version .1.1  at watsun.cc.columbia.edu:/packet-drivers/bin
>version 9.0.0 at bitsy.mit.edu:/pub/connkit/pc.clarkson/drivers
>
>I am using the HP PC LAN Adapter/16 TP Plus (circuit board says Rev. A).
>I have the card configued in an NCR PC with HPLANSET.EXE as such:

HPPCLAN.COM does not work with this card.  The packet driver for HP PC
LAN Adapter/16 Plus (both TP & TL) is HPPCLANP.COM and will be available
both from Crynwr Software and HP real soon now.

---

Glenn Talbott
HP PC LAN Card Diagnostic and Driver Development
Hewlett-Packard Roseville Networks Division
gt@hprnd.rose.hp.com
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: kchen@math15.math.umbc.edu (Kan Chen (GS))
Subject: Need help in packet driver
Originator: kchen@math15.math.umbc.edu
Organization: Department of Mathematics, University of Maryland Baltimore County
Distribution: usa, canada
Date: Mon, 17 Aug 1992 19:58:24 GMT

I  am writing a application using WATCOM's C386 in the DOS4G extender.
I fails to install a packet receive function by using access_type(). It
seems to me the problem is that the Packet driver was runing under real
mode and it can't address the receive function which is in protected
mode (offset > 1MB).

Is there any experienced  know how to registor a packet receive function
in the access_type()? Is there a way to force a receive function address
under 1MB in WATCOM C386, or install a protected mode function(I mean
address > 1MB) to a packet driver?

Thanks for your time  and helpness.

you may response to kchen@math15.math.umbc.edu, and I will post
instereted answers or, answer on the news group.

Kan Chen
kchen@math15.math.umbc.edu
Tel: (410)955-4320
From: keith@novell.com (Keith Brown)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Font usage in Lan Workplace for DOS
Keywords: font vt220 presenter
Date: 18 Aug 92 02:04:24 GMT
Organization: Novell, Inc. San Jose, California

In article <133663@lll-winken.LLNL.GOV> 445362@jester.llnl.gov (Grant Johnson) writes:
>We're in the process of configuring Host Presenter for use with Oracle
>on a Sun.  Running windows in 640x480, none of the standard fonts fit
>an 80x24 screen completely.  They all cut off 2 characters.

Clearly you weren't running Host Presenter when you typed your article.
You had way more than 80 characters a line on your post! :-)

Anyway, sounds like you have LWP v4.0. At the beginning of January the LWP
people did a minor maintenance release that stomped on a few annoyances.
This was one of them. LAN WorkPlace v4.01 does have some fonts that
happily let you have 80 characters on a screen. 

>One more note, we're not necessarily commited to Host Presenter, we're
>certainlly not impressed with the speed, documentation, etc.

Well, I can't comment on the documentation because I've never read it!
However, the blame for the poor scroll speed (which I myself complained
about to the LWP developers) lies mainly with Windows. The obvious
solution is to implement configurable multi-line jump scrolling.
Fortunately, they were way ahead of me on this one. I've seen our
latest HP running and it positively sings along (and it does lots of
other totally wicked new stuff too!).

When will the next release of LWP be in the shops? I don't know. You would
have to ask Novell. ;-)

Keith
-
Keith Brown                                      Phone: (408) 473 8308
Novell San Jose Development Center               Fax:   (408) 473 8990
2180 Fortune Dr, San Jose, California 95131      Net:   keith@novell.COM
From: tse@ra.nrl.navy.mil (Anthony Tse)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Telnetting to a PC (with FLAMES)
Date: 12 Aug 92 20:31:02 GMT
Organization: Naval Research Labratory, Washington, DC

In article <Bsvost.J2L@helios.physics.utoronto.ca> stefan@helios.physics.utoronto.ca (Stefan Mochnacki) writes:
>FLAME ON:
>
>An aside: All that hype from Microsoft, Lotus, Novell etc. about
>e-mail and WANs I think is ridiculous. Why are all these companies
>re-inventing what we in the Unix world have had for years? It's the
>same logic which  hypes up Windows and keeps MS-DOS alive as
>the primary PC OS (on 486's no less ... absurd !). And all this
>silly rubbish about Unix systems being "user-unfriendly" or
>"needing a guru to run": setting up the memory layout
>on a PC these days is far more esoteric than bringing up a
>Unix workstation. It reminds me of the absurdities of
>JCL (now who on this group knows what THAT is ?)
>
>FLAME OFF.

	Funny you should mention this.  I am a Unix person living in a PC
world, so when things don't work, they always blame it on Unix,
including networking.  Somehow, I think when the motta of a company is
"the network is the computer", they know their networking software
pretty well.

	Yeah, I though it was pretty funny when this guy who kept giving me
the same shit about how difficult it is to set up a Unix box can't get
TCP to work on his PC.  The packet driver that came with the ethernet
card will work on some PC, but not others.  While the packet driver I
pulled off the net will work on the other PCs but not the original set.
Or when you can't run TCP if you want to run MS Word under DOS because
of memory conflict.  Or when they can't put the TCP path in because they
ran out of room.  Or when he upgraded to Window 3.1, the TCP stuff
stopped working (of course, it's the SUN software that screwed it up
:)).

	Not only is it more esoteric to layout the memory in a PC, it's
different on each and every PC depending on how the other software
packages are set up.

-Anthony
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: mike@childsoc.demon.co.uk (Michael Bernardi)