HDTenEightyP/NetNews huggingface dataset:
From: pcg@aber.ac.uk (Piercarlo Grandi)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: ka9q-nos
Date: 13 Sep 92 22:33:47 GMT
Reply-To: pcg@aber.ac.uk (Piercarlo Grandi)
Organization: Prifysgol Cymru, Aberystwyth

On 10 Sep 92 11:11:25 GMT, jandol@CS.FELK.CVUT.CS said:


jandol> My name is Jan Dolejs and I live in Prague in Czechoslovakia. At
jandol> moment I'm working for Czechoslovak firm called ZPA Cakovice, a
jandol> producer of control and computer equipment. [ ... ] My role in
jandol> this project is to develop the SW for the PC-AT386SX. I decided
jandol> to use the NET program (NOS version) and the corresponding
jandol> packet driver (Clarkson) for WD8003E or NE2000.

You cannot use NOS/NET for your project; it is copyrighted, and
copyright permissions allow copying only for use in educational
institutions or for packet radio people.

You should contact the author, as clearly indicated in the notes that
accompany the sources, for copyright permissions for commercial use.

Please don't abuse the generosity of people like Karn and his
coworkers...
--
Piercarlo Grandi                   | JNET: pcg@uk.ac.aber
Dept of CS, University of Wales    | UUCP: ...!aber-cs!pcg
Penglais, Aberystwyth SY23 3BZ, UK | INET: pcg@aber.ac.uk
From: "richard hajinlian" <richard.hajinlian@channel1.com>
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: ip options length?
Date: 14 Sep 92 01:20:26 EST
Reply-To: "richard hajinlian" <richard.hajinlian@channel1.com>
Distribution: comp
Organization: Channel 1 Communications

How do I find if there are IP options within the IP header?
Do you use the length fields or is there a field that will inform
you that there is an option list?

Thanks in advance.

Rich.
--
Channel 1 (R)   Cambridge, MA
From: TUB@CU.NIH.GOV (Bert Tyler)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re:  I NEED DG EMULATION FOR NCSA TELNET
Date: 16 Sep 92 01:06:25 GMT
Distribution: world
Organization: The Internet

(discussing adding terminal emulators to MS-Kermit...)

> The terminal emulation business is a difficult one: complex specs (only ~=
> hardware), clashes between dedicated terminal silicon and PC hardware, bulk,
> time/energy, etc). There would have to be really good incentives to consider
> another terminal which differed greatly from what is present now.

For what it's worth, we here at the National Institutes of Health have
plenty of incentive both in terms of wanting to make it easy to add
terminal emulators to MS-Kermit, and wanting to do so in a way that
gives us the ability to enhance and maintain those emulators rather than
forcing the "official" MS-Kermit folks to do so - our NIH8188 terminals.

The NIH8188 is a local-editing terminal with features not found in any
of the terminal emulators in either MS-Kermit or its commercial competitors
(a logical line width of over 1000 characters, for instance), and we
have lots of end users that are used to those features and don't
want to give them up.  We also have lots of programs that expect to
have an NIH8188 on the other side of the cable and send NIH8188-specific
escape sequences down the line.  On the other hand, NIH8188 terminals
basically don't exist outside of the NIH, and it would be unrealistic
to expect the Columbia releases of MS-Kermit to include an NIH8188
emulation mode.  Our solution has been to add a "loadable terminal
emulator" capability to our copies of MS-Kermit.

Our "loadable terminal emulator" code consists of a new command - "set
terminal driver <filename>" - and a number of hooks into MS-Kermit's
terminal emulator code.  The "set terminal driver ..." command looks for
the named file, verifies that it contains appropriate latch-up code at
the right places, allocates the required memory, loads the emulator code
there, and calls some initialization code to let the emulator start up.
After that, all communication to and from the emulator is through the
above-mentioned hooks and a single table-driven entry into the
emulator code.

(Yes, there's a performance penalty with using this sort of indirect
code.  No, it doesn't seem to be a noticable performance penalty on
today's hardware.)

The item with the single biggest impact on MS-Kermit was the fact that
we had to add 128 new "action" verbs (we called them "x1" through
"x128") to make room for all the extra function keys that are on
the NIH8188 in addition to the "normal" ones.  That puppy has a wiiiide
keyboard <grin>.

Adding a new terminal emulation is never easy, but at least this way
it's do-able - and in a way that doesn't force MS-KErmit to carry
the baggage of unneeded terminal emulators in everybody's copy of
the program.
From: yellowbd@eskimo.celestial.com (Andy Hubbell)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: ISO ppp driver for msdos based pc.
Date: 14 Sep 92 07:07:26 GMT
Organization: -> ESKIMO NORTH (206) For-Ever <-
X-Newsreader: Tin 1.1 PL3

Ok, I'm trying to find out if there is a ppp (like slip but better)
driver that has been ported to the IBM & compatible platform.  If anyone
out there knows where I might find it I would greatly appreciate the
information.  If I *have* to use slip I can, but would prefer to use ppp
instead.  Please reply via email, thanks.
  
BTW, I would also like to know where to find pd tcp/ip kernels for the
pc.  I am trying to set up DESQview/X over a slip/ppp link to my local
Sun system to play with X-applications and such.  Thanks!
  
                       --== Andy ==--
  
Email:  yellowbd@eskimo.celestial.com
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: skl@wimsey.bc.ca (Samuel Lam)
Subject: Re: NDIS driver for WD Elite board...
Reply-To: skl@wimsey.bc.ca (Samuel Lam)
Date: Tue, 8 Sep 1992 04:43:01 GMT

In article <Bu42pD.10B@usenet.ucs.indiana.edu>, "Tony C. Cheng"
 <tcheng@bronze.ucs.indiana.edu> wrote:
>Is there an NDIS driver for WD Elite board available?

There's one at sjf-lwp.corp.sjf.novell.com in the directory
odi/smc-wd/ethernet/ndis .

...Sam
-- 
<skl@wimsey.bc.ca>
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: waltje@cs.vu.nl (Kempen van Fred)
Subject: Re: PC/TCP 2.1 copy protection
Organization: Fac. Wiskunde & Informatica, VU, Amsterdam
Date: Tue, 15 Sep 1992 18:31:53 GMT

kb@jet.uk (Kenneth Blackler) writes:


>Those damned foreigners.....

Thanks.  I'm one :-)
But, seriously now.  I know several of the TCP/IP-for-DOS-package distributors
in The Netherlands, and most of them indeed would like to see _some_ way to
fight the piratism.  I used to work for a company that needed 170 PC's net-
worked.  I ordered PC/TCP 2.05Plus, with InterDrive 1.1.  I installed it on
some machine, to get a test setup.

Well, after it worked, I wanted to order a site license, as agreed with my
dealer.  What happens?  My boss simply tells me to call of any pending
orders, and install the stuff on _all_ machines.  Hell, it's my boss, so
I did.

I do not work there anymore (although I still use their PC/TCP, since I
took the original with me when I left :-)- they did not care), but this
is one of those situations that prove the "pressure" FTP, Sun and probably
B&W will be under from distributors in countries such as the Netherlands.

Now I come to think of it, this might also be the reason why I do not
get any of my e-mail messages sent to FTP back- they probably assume
that I have a pirated copy :-(  Guys?

I do understand that some way of protection is needed, since, in some
countries, signing some license agreement doesn't mean anything (sigh).
However, when installing a package (or, as it has been suggested, even
multiple kinds of packages) on a large network, the need for a filing
system for "which serial# is running where" seems a bit clumsy to me.

Indeed, it is quite easy to either forge this scheme, or to simply hack
the kernels to bypass the test completely.  In fact, any serial number
system could be bypassed :-(

Could this not be redirected towards the _distributors_ ?  If any onf
them observes a strange behaviour of a customer, then simply change
the license stuff to be lwafully binding.  Then, in case of doubt,
send a tech-guy over to check license data with actual installed-base
nubers...

A suggestion?

Fred.
-- 
--
Fred N. van Kempen                           | Home: waltje@uwalt.nl.mugnet.org
VU Amsterdam, Fac. Math && Computer Science  | Work: waltje@cs.vu.nl
From: wjr@FTP.COM (William J Rust)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: PC/TCP 2.1 copy protection
Date: 11 Sep 92 19:00:58 GMT
Reply-To: wjr@ftp.com
Distribution: world
Organization: The Internet

To anyone who is interested (I apologize to those who aren't), here
is the official FTP statement on serialization. Note, we don't call
it copy protection because it isn't. You can make as many copies as
you like and they will all run. If they are on the same LAN, you get
an annoying message every few minutes. That's all that happens. This
same discussion happened a few months ago and I hope that by sending
this out again, it won't be repeated in another few months.


ANNOUNCEMENT

FTP Software has added serialization to its PC/TCP product in version
2.1. We did this because we were asked to do so by our non US VARs
and OEMs and by customers who were concerned about corporate
liability for unauthorized copying. 

We worked hard to minimize the impact of serialization on our
customers. We decided on three criteria: 1) no additional traffic
would be added to the network, 2) software that was backed up and
restored would continue to work with no problems (ie, no key disks)
and 3) in an emergency a copy would work. We met these criteria.

We will be shipping the serialized version of 2.1 for all single
copies and upgrades from previous versions. Site licenses where a
contract has been signed, will be able to select either the
serialized or the non-serialized version. A new version of site
license, which does not require a signed license agreement, will be
available using the serialized kernel.

In operation, when a user runs the install program, it will prompt
for a serial number and a key. For single copy purchasers, the serial
number and the key are printed on the distribution disk. For
serialized site licenses, a printed list of serial numbers and keys
will accompany the master disks. All the user has to do is type in
the two character strings (about 12 characters each) when the
installation program prompts for them. If a valid serial number - key
combination is not entered, the kernel will refuse to load.  Because the
serial number is stored in the configuration files, rather than in
the kernel itself, the user never need enter the serial number again,
even when switching kernels or upgrading.

Serialization is implemented by each kernel sending its plaintext
serial number in every outgoing ARP request, in the "destination
hardware address" field. When a kernel hears its own serial number,
it will print a message on the screen and beep, but otherwise continue
to operate normally. If users encounter problems while running the
serialized kernel, FTP is prepared to remedy them quickly.

We invite your comments. Please send them to info@ftp.com. If you
would like more information on this or any other issue, contact your
salesperson or send mail to the above address.





--
William J Rust (aka, not-the-mama)                       Internet: wjr@ftp.com
FTP Software, Inc.                         (617) 246-0900, fax: (617) 246-0901


Newsgroups: comp.protocols.tcp-ip.ibmpc
From: kjetilo@bilbo.uio.no (Kjetil Otter Olsen)
Subject: PC-NFS Programmers Toolkit problem
Organization: University of Oslo
Date: Sat, 12 Sep 1992 10:09:53 GMT



Using PC-NFS Programmers Toolkit 2.0, a socket() call returns with
the error: Bad file number

/* Code-piece */

int iSock = 0;

if ((iSock = socket(AF_INIT, SOCK_STREAM, 0)) < 0) {
        tk_perror("Socket: ");
    }
/* End of Code-piece */

Since this very code-piece works in other programs, I suspect
a conflict of some kind between the toolkit and my program...

Can anyone tell me the reason why socket() returns with that error,
and some clues on what to look for in my program.

Thanks for any clues or hint!

Answers in E-mail please...

--Kjetil
-----
Kjetil Otter Olsen,   Senior Engineer,   M.Sc.,   C.Sc. (kjetilo@usit.uio.no)
Center for Information Technology Services (USIT), University of Oslo, Norway
From: trier@slc6.ins.cwru.edu (Stephen C. Trier)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: IBM's TCP/IP 1.2.1 for OS/2 Slip problem
Date: 11 Sep 92 19:13:24 GMT
Organization: Case Western Reserve University, Cleveland, OH (USA)
NNTP-Posting-Host: slc6.ins.cwru.edu

In article <ant.716104771@brolga> ant@brolga.cc.uq.oz.au (Anthony Murdoch) writes:
>...the slip IBM's TCP/IP doesn't seem to have any method of terminal
>interaction before the connection.

The solution under DOS is to open the serial port with a terminal program,
log in, then switch to the SLIP driver without dropping DTR (so the modem
stays online).

Is possible on OS/2?

-- 
"Beware of programmers who     Stephen Trier
 carry screwdrivers."          Network Services Engineering, IRIS/INS/Telecom
       Leonard Brandwein       Case Western Reserve University
                               trier@ins.cwru.edu
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: Sat, 5 Sep 1992 16:35:53 GMT

In <hippo.41.0@sonoma.edu> hippo@sonoma.edu (Michel Davidoff) writes:

>In article <1992Sep4.184222.280@news.uiowa.edu> boyken@herky.cs.uiowa.edu (Karl Boyken) writes:
>>Subject: NCSA Telnet & WINPKT
>>From: boyken@herky.cs.uiowa.edu (Karl Boyken)
>>Date: Fri, 4 Sep 1992 18:42:22 GMT
>>I've set up a number of PCs with NCSA Telnet and Windows, using WINPKT.
>>For the packet driver, I always use 0x62 for the packet interrupt, then use
>>
>>     winpkt 0x60 0x62
>>
>>to start WINPKT.  WINPKT says that it finds the packet driver and that the
>>new interrupt is 0x60.  I configure the config.tel thus:
>>
>>     hardware=packet
>>     interrupt=60
>>
>>But, when I start Telnet in Windows, I always get this message:
>>
>>     Warning, packet driver vector incorrect, using default search
>>
>>Telnet evidentally does find an interrupt, but I'd prefer that it didn't have
>>to search for it.
>>
>>If I don't load WINPKT and change the packet driver invocation to 0x60,
>>Telnet starts up without the warning.
>>
>>What am I doing wrong?  Thanks in advance.
>>
>Try in the config.tel interupt=62

Or better yet, try interrupt=0 and just let NCSA find the driver on it's
own.  I don't remember whether NCSA searches top down or bottom up, whichever
it is be sure to put the "new vector" for winpkt either above or below the
original driver so that NCSA will find it before the real packet driver.

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!)

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| Dan Ellison, Network Team 	  -    	Computing Affairs, SIU-C 	| 
| Southern Illinois University 	  - 	Carbondale, IL 62901            |   
| FAX:      (618) 453-3459        -   	PHONE:    (618) 453-6149 	|     
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: "Tony C. Cheng" <tcheng@bronze.ucs.indiana.edu>
Subject: NDIS driver for WD Elite board...
Organization: Indiana University
Date: Sat, 5 Sep 1992 15:22:16 GMT


Is there an NDIS driver for WD Elite board(uses WD8003E packet driver) 
available?  If there is, where can I find it?  I checked vax.ftp.com, didn't
find any NDIS driver there that I could relate to it.   

I need to use the card to work on n AT&T Lan Manager network, if no NDIS
driver is available for the card, or there's no need, how do I bind the 
packet driver in PROTOCOL.INI?

Any info. will be appreciated.

_Tony C. Cheng
From: george@ache.mad.adelaide.edu.au (George Travan)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Racal Interlan 5210 NI5210.sys
Date: 14 Sep 92 07:00:55 GMT
Reply-To: george@frodo.ua.oz.au
Organization: University of Adelaide
NNTP-Posting-Host: ache.mad.adelaide.edu.au
Originator: george@ache.mad.adelaide.edu.au


I have a problem with an interlan card using pcnfs4.0a. ftp from the
card to a sun host works, but from the sun to the card is very very slow.
too slow. something is wrong.
Two other pc's on the net have 3COM cards (no problems) and another ni5210
(not running pcnfs) work fine. One of the 3comms runs pcnfs.
I have checked the hardware/interrupts etc and even installed NCSA telnet.
NCSA telnet works fine!

My area of focus now is the card driver which came with the NI5210. Has anyone
any suggestions. Anyone got ni5210.sys  to work fully with PCnfs4.0a? 

I'd like to know.

/Geo



-- 
                  George Travan "A Rebel Without A Clue!"                   
                  E-mail: george@ache.mad.adelaide.edu.au                       
     Phone: (Australia) +61 08 228 5968   Fax: (Australia) +61 08 224 0464  
        University of Adelaide,G.P.O Box 498 Adelaide, AUSTRALIA 5001
From: ccaajmf@ucl.ac.uk (John Franks)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: NCSA Telnet & WINPKT
Date: 7 Sep 92 16:06:06 GMT
Organization: Bloomsbury Computing Consortium, London

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.
>For the packet driver, I always use 0x62 for the packet interrupt, then use
>
>     winpkt 0x60 0x62
>
>to start WINPKT.  WINPKT says that it finds the packet driver and that the
>new interrupt is 0x60.  I configure the config.tel thus:
 ... etc.

I could be very wrong (I'm currently setting something up along these lines - 
please tell me if I am!) but I thought winpkt was only for windows programs
and that DOS ones running under windows used the standard pktdrv interface -
and you just don't run more than one on each pktdrv. 

Please, please reassure me!


John Franks             I will arise and go now, for always night and day
ccaajmf@ucl.ac.uk       I hear lake water lapping with low sounds by the shore; 
& jmf14@phx.cam.ac.uk   While I stand on the roadway, or on the pavments grey,
   from Cambridge only  I hear it in the deep heart's core.
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: avdeyev@dsf58a.desy.de (Dmitry Avdeyev)
Subject: X client for DOS
Keywords: X11, client
Organization: Deutches Elektronen-Synchrotron (DESY)
Date: Thu, 10 Sep 1992 19:16:46 GMT

Hello !

Have anybody heard about shareware (or pd) X11 client for DOS.
I mean something like DesqView/X but non-commersial. Any 
suggestions will be appriciated.

	Thanks in advance, Dmitry.

--
---
Dmitry A.Avdeyev		+49-40-8998-2583
Computer networks analyst	USG DESY, Hamburg
From: romkey@asylum.UUCP (John Romkey)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: PC/TCP 2.1 copy protection
Date: 9 Sep 92 22:07:50 GMT
Distribution: usa


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.

The scheme requires each kernel to be stamped with a serial number at install
time. I believe site licenses will receive a list of serial numbers and keys.
If you have a 20 system site license, you get a master distribution and
20 serial numbers and keys, not 20 disks. Also, the serial number is
piggy-backed on ARP packets, not in special broadcasts, so it doesn't
cost you any extra traffic.
-- 
	- john romkey	  ELF Communications	 romkey@ELF.com
From: lcz@dptspd.sat.datapoint.com (Lee Ziegenhals)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Problems with KA9Q and ARCNET
Date: 9 Sep 92 02:24:14 GMT
Organization: Datapoint Corporation, San Antonio, TX

ddl@burrhus.harvard.edu (Dan Lanciani) writes:

>In article <1992Sep6.094826.15321@rhrk.uni-kl.de>, puder@rhrk.uni-kl.de (Arno Puder) writes:
>| 
>| I seem to have an old version of the KA9Q package. When I tried
>| to run it with my ARCNET (ATTACH PACKET...) it responded "un-
>| supported type class 8". Interesting enough the documentation
>| said that it should work. I logged on to Archie and got a couple
>| of dozens of references. Which one works with ARCNET?

>	It is my impression that most of the world has given up on
>class 8 packet drivers.  Correct me if I'm wrong, but doesn't the
>current ARCnet packet driver fake class 1?  I know that the general

Yes, indeed.  You are thinking of the "arcether" packet driver which does just
that.  I would recommend it to anyone thinking of using Arcnet via a packet
driver.  Another major advantage of arcether is that it supports RFC1201
instead of the older RFC1051.  This provides interoperability with other
Arcnet TCP/IP software such as Novell's or Datapoint's.

Lee
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: dirk@incom.de (Dirk Koeppen)
Subject: Re: Boot ROMs for Western Digital cards?
Reply-To: dirk@incom.de
Organization: Dirk Koeppen EDV-Beratung, D-6050 Offenbach, Germany
Date: Tue, 08 Sep 1992 08:07:26 GMT

John Franks writes
> Now, there's a little company
> in Germany (called "schasiepen", I think) that makes the things. 
> Unfortunately, someone's just borrowed the docs, but e-mail to
> support@unipalm.co.uk should get some info - that's the only address for them 
> I know, sorry. Unipalm is the UK distributor.

It's:
	Carl Schasiepen GmbH
	Harkortstr. 25
	4030 Ratingen 1
	Germany

	Tel. +49 2102-4906-0
	Fax  +49 2102-4906-15

--
  Dirk Koeppen  -  Holzwiesenweg 22  -  D-6050 Offenbach  -  Germany
  Phone: +49 69 89 3000 - FAX: +49 69 89 3004 - email: dirk@incom.de
  ---
  ** Phase 2 - Check Pathnames
  UNALLOCATED I=2 (NOT EMPTY) REMOVE?
From: ce1zzes@prism.gatech.EDU (Eric Sheppard)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: PC-NFS 3.5 to 4.0 Upgrade Problems
Keywords: PC-NFS RPC
Date: 15 Sep 92 19:27:03 GMT
Distribution: usa
Organization: Georgia Institute of Technology

In <1992Sep12.030127.25715@netfs.dnd.ca> boucher@ncs.dnd.ca (R. Boucher) writes:

>Here is my output when I start PC-NFS 4.0:

>The network.bat contains:
>NET START RDR CHENETTE *
>NET PCNFSD asimov
>NET NAME rob password

>and drives.bat contains:
>NET USE F: asimov:/tmp
>NET USE LPT2: asimov:panasonic
>NET USE Q: asimov:/var/spool/mail

first suggestion here is with the printer mount.  use '/fmt=r' to properly
print binary files across the network.  Raw mode is specific now:

NET USE LPT2: asimov:panasonic /fmt=r

another suggestion is to make sure you have a fairly recent pcnfsd daemon
running on your server.  We had some rough edges moving up to 4.0, but
the daemon I got from the site Geoff Arnold suggested made it easier.

Eric 
-- 
Eric Sheppard      Georgia Tech    |   "Of course the US Constitution isn't
Atlanta, GA                        | perfect, but it's a lot better than what
ARPA: ce1zzes@prism.gatech.edu     |             we have now." -Unknown
uucp: ...!{allegra,amd,hplabs,seismo,ut-ngp}!gatech!prism!ce1zzes
From: ddl@burrhus.harvard.edu (Dan Lanciani)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Anyone using Crynwr packet driver with PhoneNET
Date: 5 Sep 92 21:03:21 GMT
Article-I.D.: burrhus.1992Sep5.210321.17139
Organization: Harvard University, Cambridge, MA

In article <Bu1IK6.Ar7@wimsey.bc.ca>, skl@wimsey.bc.ca (Samuel Lam) writes:
| In article <1992Sep3.181611.14743@vax5.cit.cornell.edu>,
|  sbk@vax5.cit.cornell.edu wrote:
| >The key is to get your hands on PhoneNET Talk 3.0 (still in beta, I'm afraid). 
| >This is a fully ODI-compliant AppleTalk stack for DOS.  The, you load ODIPKT,
| >Dan Luciani's PDS-ODI shim.
| 
| ODIPKT has a run-time switch which makes it work with the older
| version of ODI which the current version (2.0) of PhoneNET Talk
| speaks.  So you should be able to get things to work now without
| waiting for PhoneNET Talk 3.0 to come out.

	Actually, it is an assemble-time switch and the alternate
executable is called ``odipktpn.com.''  Hmm, that's assuming you
are talking about my odipkt and not this ``Luciani'' person's
version :)

				Dan Lanciani
				ddl@harvard.*