HDTenEightyP/NetNews huggingface dataset:
From: jsanchez@polari.online.com
Subject: Re: Tandem term emulators on TCP/IP?
Keywords: Tandem Computers terminal emulator
Organization: Seattle Online Public Access Unix
Date: Wed, 29 Jul 1992 14:34:28 GMT

I think you want to talk to Crystal Point Software in Bothell Wa - sorry I
don't have the number with me.  They are 6530 experts and understand the
block mode of the 6530 better than anyone else.
Cheers
-- 
Jim Sanchez 
Hughes LAN Systems - Bellevue, WA (206)828-7417
Internet: jim@hls.com OR jsanchez@polari.online.com
UUCP: ..!uunet!polari!jsanchez
From: shiva@well.sf.ca.us (Kenneth Porter)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Adding a DOS lan to an NFS lan
Summary: Lantastic or Netware Lite?
Date: 29 Jul 92 20:22:17 GMT
Followup-To: comp.protocols.tcp-ip.ibmpc,poster
Organization: Whole Earth 'Lectronic Link

Our software/electronic design department network is a thinnet NFS-based
Ethernet comprising 2 Sun 386i's functioning both as development
systems and as file servers for a half dozen PC's, some running OS/2
(running FTP's PC/TCP for OS/2 1.2) and others running DOS (running
Sun's PC-NFS 3.1).

Our drafting department has 3 DOS PS/2's not networked and there has
been some interest in networking them together so that they can share
files, printers, and backup. They currently use sneakernet for file
sharing, a switch box for printer sharing, and move an external backup
unit from machine to machine for backup.

I can imagine that in the long run, we will want to connect the two
networks together and run a common protocol, but for now I think that
the desire is for an inexpensive peer-to-peer network for drafting, as I
don't think that there is funding available for a separate file server.

I've seen mention of Lantastic and Netware Lite in the literature, but I
don't know much about their capabilities or about what is involved in
administering them.  Are there other options?  What problems can I
expect if/when I connect the two networks together?  Will the DOS
protocols coexist peacefully with TCP/IP?  I expect this to be a
short-term (ie. one year) issue, as OS/2 or NT will probably replace
single-tasking DOS here, allowing a more sophisticated server-to-server
solution.

Note that cabling is not much of an issue, as all of the machines are in
adjacent rooms and we can just throw coax over the wall.

[For those who question the presence of the 386i's, we need the ability
to run multiple DOS sessions with access to an AT bus on a single desktop.
If Solaris 486 provides this capability, we may migrate that way, or we
may go with OS/2.]
Xref: sparky comp.protocols.tcp-ip.ibmpc:4474 comp.sys.novell:6118
From: ddl@burrhus.harvard.edu (Dan Lanciani)
Newsgroups: comp.protocols.tcp-ip.ibmpc,comp.sys.novell
Subject: Re: Help with Novell's ODI drivers
Date: 28 Jul 92 22:10:43 GMT
Followup-To: poster
Organization: Harvard University, Cambridge, MA

In article <92209.202057RBYAML@rohvm1.rohmhaas.com>, RBYAML@rohvm1.rohmhaas.com (Aengus Lawlor) writes:
| I used Manifest (it comes with QEMM) to see what interrupts
| ODIPKT used.

	My, the lengths people will go to to avoid reading the
documentation :)

| Unfortunately, ODIPKT isn't
| unloadable, and it locks in all the other ODI drivers loaded before it.

	ODIPKT unloads with the standard packet driver API function
defined for that purpose.  You can call this function with the "TERMIN"
program.

				Dan Lanciani
				ddl@harvard.*
From: jbvb@FTP.COM ("James B. Van Bokkelen")
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: TCP/IP and x.25
Date: 29 Jul 92 13:30:28 GMT
Reply-To: jbvb@ftp.com
Distribution: world
Organization: The Internet


    What hardware is supported to do this and does the support come in the
    form of compliance with RFC 877 regarding encapsulation of IP in x.25
    packets?

PC/TCP supports this via the 'generic' X25DRV kernel, and a board
vendor's Class 13 packet driver.  Frontier Technologies was the first
vendor to support this, I know a couple of others are in progress, I'm
not sure if they're shipping yet.
    
    I have been unable to determine if the product is capable of supporting
    an Ethernet and x.25 interface simultaneously. If it does, will it also
    act as an IP router between the two nets?

We only support one interface at a time, and don't act as a router.
    
    I need this router functionality (between Ethernet and x.25) for a large
    project so I would appreciate information that helps me build this either
    with FTP's product or another implementation.

Most of the commercial IP router vendors support both X.25 and Ethernet.
I'm pretty sure PCRoute doesn't, and the AX.25 used by KA9Q isn't what you're
interested in.

James B. VanBokkelen		26 Princess St., Wakefield, MA  01880
FTP Software Inc.		voice: (617) 246-0900  fax: (617) 246-0901

Newsgroups: comp.protocols.tcp-ip.ibmpc
From: ada@zip.larc.nasa.gov (Anthony Arviola)
Subject: Re: FTP's tcp/ip
X-Md4-Signature: 8fe00f2770929c5363209b1c86a91337
Organization: NASA Langley Research Center, Hampton, VA
Date: Thu, 30 Jul 1992 16:13:59 GMT

In article <9207291330.AA04971@ftp.com> jbvb@FTP.COM ("James B. Van Bokkelen") writes:
Path: news.larc.nasa.gov!uakari.primate.wisc.edu!ames!agate!ucbvax!FTP.COM!jbvb
   From: jbvb@FTP.COM ("James B. Van Bokkelen")
   Newsgroups: comp.protocols.tcp-ip.ibmpc
   Date: 29 Jul 92 13:30:27 GMT
   Sender: daemon@ucbvax.BERKELEY.EDU
   Reply-To: jbvb@ftp.com
   Distribution: world
   Organization: The Internet
   Lines: 12


       ....  does ftp/ips 2.03 kernel support BOOTP, or does anyone know where
       I can find a bootp client that will fire off the BOOTP packets and
       retrieve the appropriate information?

   We didn't add BOOTP until 2.04.  If you upgrade your 'generic' PC/TCP
>>>   to 2.1 (which is shipping as of today), you'll get BOOTP, a SLPDRV
   kernel (in addition to ETHDRV), our own serial line packet driver, and
   dialer utilities, which should make things a lot easier.

   James B. VanBokkelen		26 Princess St., Wakefield, MA  01880
   FTP Software Inc.		voice: (617) 246-0900  fax: (617) 246-0901

Did I read this right?  Version 2.1 PC/TCP is out!  I need to get a copy
to begin testing!...

This should be a post by itself if it is true!
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: eengelke@sail.uwaterloo.ca (Erick Engelke)
Subject: Re: Crynwr WD8003E-P 
Organization: University of Waterloo
Date: Thu, 30 Jul 1992 18:25:54 GMT

In article <712419634snx@crynwr.com> nelson@crynwr.com (Russell Nelson) writes:
>In article <712380314snx@exorcise.demon.co.uk> james@exorcise.demon.co.uk writes:
>
>Sure, the wd8003e driver works for many people.
>
>   I have tried the standard WD8003E driver without much success, although
>   it does appear to read the MAC address correctly.  The WD docs mention
>   significant differences with the 83C690 chip and the old software is
>   not compatible.
>
>Ahhh, yes.  You're one of the ones for whom the driver doesn't work.
>SMC is concerned about this driver not working for some people, and
>they sent me an Elite 16 to make it work.  Well, on my three
>machines, it does work.  Hard to fix it if it isn't broken.


The SMC driver we received with our NIC appeared to not block
succesive send calls when an earlier call was in progress and 
caused the card to timeout and appear to only send one or two
packets a second.  

To create this effect, you only need a program which can send
out back-to-back packets, and the packet length is important too.
Using the WATTCP FTP program on a 33 Mhz 386 appears sufficient.

We were able to get the programs to work by inserting a timed
delay loop between packets.  

So we worked backwards and created a small program to try
blasting out packets with the ability to vary the packet length
and the inter-send_call-delay and we were able to establish
that the delay had to be increased when larger packets were
sent.  So it's not hard to establish the cause of the problems.
or to reproduce them on demand.

I've placed a copy of the test program on sunee.uwaterloo.ca in
the file pub/wattcp/speed.exe though I think it now keeps packet
size constant.

speed.exe can also be used to test the performance of network cards,
but it may not be healthy for other machines on the subnet.

Erick

-- 
Erick Engelke					  Engineering Computing
						 University of Waterloo
Waterloo TCP Architect		 erick@development.watstar.uwaterloo.ca
From: leisner@eso.mc.xerox.com (Marty Leisner 311/? x?)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: deskview/X on 386...
Date: 20 Jul 92 01:14:29 GMT
Reply-To: leisner.henr801c@xerox.com
Distribution: world
Organization: Xerox


Has anyone had any experience with the new Quarterdeck/Deskview/X on 386?

It sounds ideal...from what I've read you can spawn DOS windows on X workstations, and run X applications on the PC...

Can this stuff integrate with NCSA or something like that?

Marty    leisner.henr801c@xerox.com 
          Member of the League for Programming Freedom 
 	Things should be as simple as possible, no simpler -- A. Einstein
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: eengelke@sail.uwaterloo.ca (Erick Engelke)
Subject: Re: wattcp building troubles...
Keywords: tcp/ip,wattcp
Organization: University of Waterloo
Date: Wed, 22 Jul 1992 03:08:02 GMT

 bmw@isgtec.com (Bruce M. Walker) writes:
>
>I think you'll find that if you compile everything with "Turbo C" (not
>Borland C), it will work OK.  

I believe BCC 3.0 will compile in Large mode (not small) or the other
way around.  I'm still using BCC 2.0 until I can upgrade to 3.1.  It
definately works with 2.0.

>There is also an assumption made
>about stack layout, which is probably necessary for the "tasking"
>portions of the code.

Actually, it's to circumvent programmers (like me) crashing their
pc's by placing 4.2 K data structures on Borland's 4 K stack.  So
what you are looking at is a stack overflow check.

>Wattcp is a pretty neat package, but it is not wriiten in C, it is
>written in "Turbo C"!

Or more accurately CI 86 C which is what I knew at that time back in
my youth.  C++ has forced a new awareness on me, but I still have to
work with pre-ANSI C for my job.   

Erick
-- 
Erick Engelke					  Engineering Computing
						 University of Waterloo
Waterloo TCP Architect		 erick@development.watstar.uwaterloo.ca
From: sgallowa@LETTERKENN-EMH2.ARMY.MIL (S_D_Galloway)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: CUTCP/CHARON list active?
Date: 22 Jul 92 11:39:22 GMT
Reply-To: sgallowa@letterkenn-emh2.army.mil
Distribution: world
Organization: U.S. Army Materiel Command, USAMC-SIMA

Hello all!

Is Clarkson University's CUTCP/CHARON still available *and* active?  It
used to produce about a dozen messages per week.  I have not received any
mail from this list in several months and have tried several times to
re-subscribe [to no avail].  If it is still active, would some kind soul
be willing to [automatically] forward me this list's mail until I get this
worked out with the list administrator?

BTW, we use CUTCP 2.2E and CHARON 3.4 and find them both incredibly
wonderful and stable programs!

Thanks!
Scott

==
Scott Galloway <sgallowa@letterkenn-emh2.army.mil>
     U.S. AMC, SIMA, Attn: AMXSI-TLS, Chambersburg, PA  17201   U S A
From: medalan@ubvmsd.cc.buffalo.edu (Alan M. Reynard)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: key mapping in telnet
Keywords: key, keyboard, mapping, telnet
Date: 28 Jul 92 19:02:00 GMT
Organization: University at Buffalo
News-Software: VAX/VMS VNEWS 1.41

I have an application (an Oracle database) running on a Vax 4000.  The
people who acess the application do so from IBM PCs running Digital's
Pathworks (formerly PCSA), and SETHOST.  When they log onto the VAX they
become captive VMS users.

We want to change their access method so that they log onto the VAX using
NCSA TELNET directly from their PCs.  In testing this we find that the
keymap under telnet is quite different from the PCSA-SETHOST keymap.  Is
there a way to alter the telnet keymap so they get to use their current
keystrokes for the application?

Thanks for any help with this.

Alan M. Reynard
SUNY SCH OF MEDICINE
BUFFALO, NY 14214
medalan@ubvms
From: dsc3jfs@nmrdc1.nmrdc.nnmc.navy.mil (Jim Small)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: tn3270 for slip
Date: 23 Jul 92 17:21:34 GMT
Organization: Naval Medical Research & Development Command

could someone direct me to a tn3270 that will run off a slip driver

-- 
I love the 3b2
The 3b2 is my friend.
From: pkershaw@dce.com (Peter Kershaw)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: News Readers for the Mac
Date: 28 Jul 92 14:40:59 GMT
Followup-To: comp.protocols.tcp-ip.ibmpc
Organization: DCE

In article <1992Jul27.191008.27641@usenet.ins.cwru.edu>,
trier@slc6.INS.CWRU.Edu (Stephen C. Trier) wrote:
> 
> In article <pkershaw-270792121157@192.94.50.51> pkershaw@dce.com (Peter Kershaw) writes:
> >A reasonably good PD Newsreader for Mac is Eudora, available from most of
> >the Mac ftp sites.
> 
> Ummmm...  Correct me if I'm wrong, but last time I checked, Eudora was
> a mail reader.

Yup, yur right 'bout that. The correct answer is NewsWatcher by Steve
Faulkenburg, once again available from many Mac ftp archives. Oh well,
helps to have the coffee before attempting to think!
> 
> You didn't mention that you appear to be associated with the company that
> makes the "excellent" TCP/Connect.  Hmmm...
> 
Yes, it should "appear" that I am in some way associated with this
"excellent" product, since I offered to send a brochure. That should be
self-evident. I don't make such offers for strictly magnanimous reasons.
That is not meant to in any way offend anyone, and in fact, I thought I was
already following the rules and etiquette of Internet use. If not, FLAME
me! Otherwise, don't make innuendo.

Peter

Peter Kershaw <pkershaw@dce.com>
Data Communication Engineering
2888 Bluff Street, Suite 161
Boulder, CO 80301
303-431-2233, 303-431-1140 fax, 303-829-5952 mobile
Newsgroups: comp.protocols.tcp-ip.ibmpc,comp.sys.laptops
From: pim@cti-software.nl (Pim Zandbergen)
Subject: Re: Packet driver for Zenith Z-Note 325L?
Organization: CTI Software BV, The Hague, The Netherlands
Date: Mon, 27 Jul 92 07:29:11 GMT

CSP1DWD@MVS.OAC.UCLA.EDU (Denis DeLaRoca 825-4580, 310) writes:

>>          Is there a packet driver avaiable yet for The Z-note?  If soow can I
>>  get it (preferably via BITNET or a BBS....don't have FTP access).  Iot, how
>>  I can I get the ODI drivers to act like a packet driver?  I need to  IPX and
>>  TCPIP (NCSA Telnet) at the same time.

> I understand that the Z-note's ethernet adapater interface is a clone
> of the NE-2000 (or Ne-1000) adapter so the NE-2000 pkt driver ought to
> job.

Has anyone gotten some UNIX with TCP/IP running with the Z-note's
built-in ethernet ? Specifically Interactive UNIX (which has
NE-1000 and NE-2000 drivers).
-- 
Pim Zandbergen                      domain : pim@cti-software.nl
CTI Software BV                     uucp   : uunet!mcsun!sun4nl!ctisbv!pim
Laan Copes van Cattenburch 70       phone  : +31 70 3542302
2585 GD The Hague, The Netherlands  fax    : +31 70 3512837
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: eengelke@sail.uwaterloo.ca (Erick Engelke)
Subject: Re: SLIP questions...
Keywords: nslookup, ping, wattcp, etc.
Organization: University of Waterloo
Date: Mon, 27 Jul 1992 15:23:54 GMT

 STEIN_A@mscf.med.upenn.edu (Alan D. Stein) writes:
>
>1)  I am working off a newly established SLIP service at my school.  I'm 
>interested in obtaining PC clients that support this device type (6, most 
>software seems to support only ether-type (1) devices).  

Try new ETHERSLIP, I believe it is available in the CRYNWR packet driver
collection.  It does slip, but packages it into a class one driver
(like Ethernet).

>2)  I'd like to write my own clients.  Can someone point me toward a TCP/IP 
>library that supports SLIP (I use SLIP8250)?  Borland C(++) is the language 
>of choice.  A PING client as a demo would also be incredibly helpful. 
>(WATTCP only seemed to support ether-type devices, is SLIP support 
>difficult to add?)

With ETHERSLIP, it already works.  The only thing you ought to do is
reduce the transmission size by adding the following line to your
WATTCP.CFG file: 
	mss=512

Be certain to download the latest WATTCP code from sunee.uwaterloo.ca
[129.97.50.50].  The latest version has a fix which pertains to the
smaller packet sizes of ETHERSLIP. 

>
>I'd use etherslip, but it seems to drop packets here and there with 
>occasional errors.  
>

The old ETHERSLIP was an excellent effort and first version.  Joe Doupnik
changed its operation so it no longer uses interupts and no longer 
drops data.  I think it was added to CRYNWR collection, but is otherwise
available from netlab.usu.edu with a little searching.

Erick
-- 
Erick Engelke					  Engineering Computing
						 University of Waterloo
Waterloo TCP Architect		 erick@development.watstar.uwaterloo.ca
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: beame@maccs.dcss.mcmaster.ca (Carl Beame)
Subject: Re: Can ""traditional"" comm programs talk TCP/IP?
Organization: McMaster University, Hamilton, Ontario, Canada.
Date: Mon, 27 Jul 1992 20:49:37 GMT

In article <2131@tymix.Tymnet.COM> billp@niagara.Tymnet.COM (Bill Putney) writes:
>
>I bought the new Procom+.  It has support for INT14 which has the
>potential for being a real nice feature.  I am also running FTP's
>PC/TCP which has an INT14 "server" called tnglass.
>
>Too bad you have to start tnglass in DOS before you start windows!
>The long and short of this is that you can get one session going
>to one destination.  If you want to disconnect and go to somewhere
>else you're hosed!  You have to quit windows and go restart tnglass.
>The other gotcha is that what tnglass really does is to start up
>a telnet session and just leave the display stuff hanging for the 
>INT14 emulator to attach to.  If you don't get windows up and the
>session going before the remote host gives up on the connection
>you're out'a luck again.
>
>If anyone has a MS-Windows INT14 telnet service routine I'm ready to 
>hear about it. :)

	Well we don't have an Windows INT14 emulator ... yet, but our
BWCOM14 package loads before Windows and provides a Hayes Modem emulator
interface. Therefore a Windows Terminal emulator which uses INT14 can use
standard ATDT commands to connect to a TELNET host. After the session is
terminated, the INT14 emulator returns to command mode and accepts additional
ATDT commands.

Carl Beame
Beame & Whiteside Software Ltd.
sales@bws.com
(416) 765-0822
From: chee@UHUNIX.UHCC.HAWAII.EDU (Brian Chee, UHCC 808-956-8316)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Exalan packet driver
Date: 21 Jul 92 18:19:07 GMT
Organization: The Internet

> Does anybody know if there is a packet driver for an Exalan(Exos)
> ethernet adaptor?
> 
> Thanks,
> ----------------------------------------------------------------------
> Mark Leber
> Systems Eng.
> Waterways Experiment Station
> Vicksburg, Ms.
> e-mail - mleber@darryl.wes.army.mil
> phone - (601)634-4607
> 
> 
Don't know about the packet driver, but an ODI driver certainly exists and
you can use the odipkt.com driver....works just fine...

As an FYI to the list....seems the "new" Novell Lanasyzer will only work
with a choice few ethernet boards....ODI drivers and windows 3.0+ is a 
must as is a board that can be put into "promiscuous(sp?)" mode....
The NE2000, NE2, NE2-32, and exos comes to mind right now....

/brian chee

~~~~~THESE ARE MY OPINIONS ONLY, an answer is only a good guess
University of Hawaii, Manoa              Microcomputer Services 
Brian Chee CNE/CNI, MicroComputer Lan Specialist
chee@uhunix.uhcc.hawaii.edu                      (808) 956-8316
From: jrd@cc.usu.edu
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Kermit TCP/IP help
Date: 30 Jul 92 20:47:54 MDT
Organization: Utah State University

In article <1992Jul31.002304.7024@organpipe.uug.arizona.edu>, kkc@con.nursing.arizona.edu (K.K.Chua) writes:
> 
> 
> When I tried to use the kermit built-in tcp/ip support on a Zenith Z-316/sx,
> I had the following error:
>     
>     ERROR releasing Packet Driver for ARP
>     ERROR releasing Packet Driver for IP
>     ERROR releasing Packet Driver for ARP
> 
> I am using a 3Com503 ethernet adapter.
> 
> I never have this problem when I used other brands of P.C.
> Can any kind soul out there please help?
> 
> Thanks in advance,
> 
> Kee
> College of Nursing
> Univ. of Arizona
-------------
	The messages are meant to be literal, in this case meaning that
Kermit could not disengage from the Packet Driver for each of the three
kinds of packets it has registered for. The cause of that is very likely
you loaded another piece of software which clobbered the Packet Driver and/or
board, say a Novell NetWare shell IPX generated for the board rather than for 
a Packet Driver. Another possibility is the 3C503 board was clobbered my 
memory management software. 
	In any case, the messages indicate the machine is in an unstable
state and should be rebooted. Afterward check the configuration carefully
for interference with the board or with the Packet Driver interrupt and
so on. There are so many ways of configuring machines that each case 
requires some study when matters fail. If you can, see if another person
nearby who knows about PCs can help go through the machine with you. It's
probably just some small mistake which is easy to overlook.
	Joe D.
From: JDONALD@LIUVAX.BITNET
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Charon 3.4 and IBM RS/6000 Aix 3.1
Date: 30 Jul 92 20:13:00 GMT
Distribution: world
Organization: The Internet

Hi,
Is anybody using Charon and Aix 3.1 for the RS/6000? I am looking
for a sendmail.cf file for examples. The one in the Charon appendix
is helpful but does not seem to work. Thanks. Also an example
of an MX entry in the named.data file is needed also. This is the
setup we are trying to configure....

Novell servers:
liunet1.liunet.edu
et1.liunet.edu

Charon
charon.liunet.edu       148.4.9.200

Aix host
ibm520.liunet.edu       148.4.29.2m

Tihaanks,i
Jleff Macdonald
Assist. Net Eng.
jdonald@liunvax.bitnet

Xref: sparky comp.protocols.tcp-ip.ibmpc:4444 comp.sys.novell:6087
Newsgroups: comp.protocols.tcp-ip.ibmpc,comp.sys.novell
Subject: Re: Help with Novell's ODI drivers
From: Aengus Lawlor <RBYAML@rohvm1.rohmhaas.com>
Date: Mon, 27 Jul 1992 20:20:57 EDT
Organization: Rohm and Haas Company

In article <BrzAx2.2x7@usenet.ucs.indiana.edu>, jiliu@copper.ucs.indiana.edu
(Jian Liu) says:
>
>For wnqvtnet (v 2.6), I had some problem first.  Before I had the odi
>drivers, I used wd8003e, where I could specify and irq number (0x60, etc), but
>the new odi does not give you this opportunity, and in the qvt_tcp.rc of the
>winqvtnet requires that packet_vector= to be filled with a value.  I posted
>a query in one of the newsnet groups, which I don't remember now, and thanks
>to someone, who I don't remember now as well, who told me that the odipkt
>uses 69 as the irq number, and I put 69 on that line, and wnqvtnet now runs
>like magic as well.
That was me. I used Manifest (it comes with QEMM) to see what interrupts
ODIPKT used.

One of the nice thing about ODI drivers is that they're all unloadable,
so you can unload them if you need the memory back, or if you want to
change your configuration (frame types, etc). Unfortunately, ODIPKT isn't
unloadable, and it locks in all the other ODI drivers loaded before it.

I never did like using MARK and RELEASE, so if anyone knows of a way to
gracefully unload ODIPKT, I'd appreciate it.
>
>Jian
>
Aengus
--
RBYAML@ROHMHAAS.COM                    Aengus Lawlor
RBYAML@ROHVM1.BITNET                   (who used to be ALAWLOR@DIT.IE)
"How about some of that famous Dublin wit, Barman?"
"Certainly, sir. Would that be Dry or Sparkling?"
Newsgroups: comp.protocols.tcp-ip.ibmpc