HDTenEightyP/NetNews huggingface dataset:
From: pkarrer@bernina.ethz.ch (Peter Karrer)
Subject: Re: ODIPKT and Token Ring
Organization: Swiss Federal Institute of Technology (ETH), Zurich, CH
Date: Tue, 13 Oct 1992 21:10:47 GMT

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

>In article <718895298snx@childsoc.demon.co.uk>, mike@childsoc.demon.co.uk (Michael Bernardi) writes:
>| >I've just been thinking some more about this. Given that few if any
>| >applications support TR. Also that ODIPKT (and the NDIS Packet Driver?)
>| >produce Token Ring packets. Then a ETH2TR "shim" would seem a good solution?
>| >This would assume applications were using Ethernet and card were using TR.
>| >Then IBMTOKEN would need re-writing as TOKEN.COM or LANSUP.COM or renaming to
>| >LANTRPKT.COM? :-)
>| 
>| Are there ANY TCP/IP application that understand Token_Ring packets? Apart
>| from FTP's TCP/IP Package.

>	Yes, of course.  My TCP/2-DOS stack (also commercial) supports
>Token Ring.  If it didn't, I wouldn't have been able to develop ODIPKT :)

Would ETH2TR be difficult to write, or, as I suspect, almost trivially
simple? That is, trimming incoming ARP packets to 28 bytes and expanding
outgoing ones to 60, plus fiddling with the ARP hwr field (see IBMTOKEN.ASM).
Or is the source routing problem still involved on this level?
-- 
Peter Karrer                                   pkarrer@bernina.ethz.ch
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: tyers@rhea.trl.OZ.AU (P Tyers)
Subject: Re: Help with ODI and QVTNET27/NCSA Telnet
Organization: Telecom Research Labs, Melbourne, Australia
Date: Tue, 13 Oct 1992 23:22:57 GMT

From article <davidw.718919455@auck.irl.cri.nz>, by davidw@auck.irl.cri.nz (David White):
> In <1992Oct12.155002.7358@welchgate.welch.jhu.edu> dv@welch.jhu.edu (Deepak Vaidya) writes:
> 
> 
>>Hello,
> 
>>Can anyone help with getting NCSA or QVTNET27 running under windows 3.1.  I am 
>>able to run NCSA from dos using odipkt but every time that I run it under
>>windows I am kicked out to the dos prompt.

This is a familiar error I recently encountered. I found that in the
"qvt_tcp.rc" file there is a definition (mandatory) of the packet_driver
interrupt vector. The supplied default is 60 which works with ipxpkt etc.
ODIPKT.COM has a default vector of 105 according to the supplied doco, when
I used this the program stopped dropping out to DOS prompt. That is within
file qvt_tcp.rc set the packet vector to 105 and hopefully you will not drop
out to dos. However, I now have a different problem (see my posting of 14
Oct.) which I have yet to resolve re packet class.

Hope this helps

P Tyers, Tel. +61-(0)3-2536794   JANET: p.tyers%trl.oz.au@uk.ac.ucl.cs
ACSnet:	p.tyers@trl.oz   UUCP:{uunet,hplabs,ukc}!munnari!trl.oz.au!p.tyers
CSnet: p.tyers@trl.oz.au   ARPAnet: p.tyers%trl.oz.au@uunet.uu.net HAM: VK3KTS 
MAIL: Telecom Research Laboratories,P.O. Box 249,Clayton,VICTORIA 3168,AUSTRALIA
From: JEFF@sand.liunet.edu (Jeff Macdonald)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Slip packet driver for dial in
Date: 16 Oct 92 16:54:33 GMT
Distribution: world
Organization: Long Island University

Hi,
Looking for anyone who uses the slip packet driver for dial in ...
what I am trying to do is to setup a slip dial-in for users to dial
in and get files from a FTP host. The packet driver does not have a
dial string option. I guess I'm asking how to send a phone number to
the phone for a remote user, using slip.


Thanks in advance.


Jeff Macdonald
Assistant Network Engineer
Southampton Campus
Long Island University
Southampton, NY 11968
(516)283-4000 ext 352


    Concerto (n): a fight between a piano and a pianist.
From: garyng@gnct.com (garyng)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: KA9Q Telnet Server
Date: Tue, 13 Oct 92 07:30:01 HKG-8
Organization: Global Network Communication Technology Co.

ivor@lhc.nlm.nih.gov.nlm.nih.gov (Ivor D'Souza) writes:

> I have setup my KA9Q IPX-router on PC-AT running version NOS 920603.
> I would like to be able to setup the TELNET server to accept logins.
> I have been able to setup /ftpusers for use of the FTP server but have
> had no luck in figuring out what it takes to enable a login account for
> use with the TELNET server.  Any assistance will be greatly appreciated.
> Thanks.
> 
> --
>  =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>     Ivor L. D'Souza                                      INTERNET:        
>     System Administrator                            ivor@occs.nlm.nih.gov 
>     National Library of Medicine                    Tel: (301) 402-1742    
> 

I remember that it is very similar to setup a ftp user, it is only the number
in the ftpusers file. I have tried the following :

username password 87
                  ^^

well I use a 9106 version.

BTW, have you been able to use the dialer for 920603. I just can't make it work.

-gary
From: JOCELYN@novl1.ci.cuslm.ca (Jocelyn Nadeau)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: request bootpd program for MS-dos...
Date: 15 Oct 92 23:37:55 GMT
Reply-To: jocelyn@cuslm.ca
Distribution: world
Organization: Centre univ. Saint-Louis-Maillet

Look into 142.17.2.244 (anonymous) for public/network/bootpnos.zip.

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: mike@childsoc.demon.co.uk (Michael Bernardi)
Subject: PPP Packet Driver?
Distribution: world
Organization: The Children's Society
Date: Mon, 5 Oct 1992 10:42:28 +0000

I've just been reading the documentation supplied with the Crynwr Packet
Drivers and also with KA9Q. It appears that Phil Karn wrote the SLIP driver
for KA9Q and allowed it to be ported as a Packet Driver.

KA9Q currently has PPP support, I also understand that this code has been put
into the public domain. I'm not a programmer but how difficult would it be to
port this code as a Packet Driver?

After all there has been some considerable interest in this Packet Driver....
                 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
From: seth@gradient.cis.upenn.edu (Seth Bromberger)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: FAQ Request & Question
Date: 11 Oct 92 21:19:42 GMT
Distribution: na
Organization: University of Pennsylvania

Could some kind soul please send me a copy of the FAQ?

Thanks,

Seth Bromberger
seth@gradient.cis.upenn.edu

Newsgroups: comp.protocols.tcp-ip.ibmpc
From: mike@childsoc.demon.co.uk (Michael Bernardi)
Subject: ODIPKT and Token Ring 
Distribution: world
Organization: The Children's Society
Date: Thu, 8 Oct 1992 11:27:32 +0000

>What it seems is needed is a ODITOKEN.COM program. This would load talk to
>the NIC via the ODI drivers BUT talk to the application via ethernet paket
>driver. Of course the best solution would be for application to understand
>BOTH Class 1 and 3 packet drivers. However us Token Ring users seem to be
>second class :-) so this is unlikely.

I've just been thinking some more about this. Given that few if any
applications support TR. Also that ODIPKT (and the NDIS Packet Driver?)
produce Token Ring packets. Then a ETH2TR "shim" would seem a good solution?
This would assume applications were using Ethernet and card were using TR.
Then IBMTOKEN would need re-writing as TOKEN.COM or LANSUP.COM or renaming to
LANTRPKT.COM? :-)
--                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: pinesoft@netcom.com (Pine Software)
Subject: Re: Wanted: PC Email on Windows for Unix Mail
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Date: Thu, 8 Oct 1992 19:16:39 GMT

In article <1992Oct7.022053.25524@iti.gov.sg> jinho@iti.gov.sg (Tan Jin Ho) writes:
>
>I am looking for an MS Windows-based Email application program that runs on
>top of standard PC TCP/IP networks and uses SMTP and/or POP. (ie. it can
>read and send UNIX mail).
>
>Any pointers would be greatly appreciated.
>
>
>Tan Jin Ho
>jinho@iti.gov.sg
>

We at Pine software have developed a package which works with the three
most popular TCP/IP stacks, PCNFS, FTP's PCTCP, and Wollongong's WINTCP.
I will include the recent product announcement below

Date: 8/5/92 
PINE SOFTWARE
PO Box 3041 Stanford, CA  94309
(415) 962-8687 e-mail, pinesoft@netcom.com (Internet) 

Pine Software, Inc. is pleased to introduce Open Systems Mail(TM) 
for Microsoft(TM) Windows(TM).  Open Systems Mail is a fully 
featured, easy-to-use electronic mail application designed or IBM 
PCs and compatibles running Microsoft Windows/DOS-based TCP/IP 
client protocols.  This product is one of the only electronic mail 
products for MS Windows that truly conforms to open systems and 
standards (SMTP, TCP/IP, RFCs).


The following is a list of  planned future enhancements:


    - Program icon will indicate arrival of new mail while minimized

    - Tool and status bar for improved functionality and ease-of-use

    - Allow user to send and receive binary attachments in accordance
      with MIME specification

    - A new version designed for use with portable computers and modems

    - A Macintosh equivalent for MacTCP

Open Systems Mail_ is available now, directly from Pine Software.  
Please contact us for more information.
From: mcn@cfa203.HARVARD.EDU (Charley Noecker)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Help with ODI and QVTNET27/NCSA Telnet
Date: 15 Oct 92 13:12:51 GMT
Reply-To: noecker@cfa.harvard.edu
Organization: Smithsonian Astrophysical Observatory, Cambridge, MA,  USA

From article <1992Oct13.232257.20513@trl.oz.au>, 
	by tyers@rhea.trl.OZ.AU (P Tyers):
> From article <davidw.718919455@auck.irl.cri.nz>, 
	by davidw@auck.irl.cri.nz (David White):
>> In <1992Oct12.155002.7358@welchgate.welch.jhu.edu> 
	dv@welch.jhu.edu (Deepak Vaidya) writes:

>>>Can anyone help with getting NCSA or QVTNET27 running under windows 3.1.  I am 
>>>able to run NCSA from dos using odipkt but every time that I run it under
>>>windows I am kicked out to the dos prompt.
> 
> This is a familiar error I recently encountered. I found that in the
> "qvt_tcp.rc" file there is a definition (mandatory) of the packet_driver
> interrupt vector. The supplied default is 60 which works with ipxpkt etc.
> ODIPKT.COM has a default vector of 105 according to the supplied doco, when
> I used this the program stopped dropping out to DOS prompt. That is within
> file qvt_tcp.rc set the packet vector to 105 and hopefully you will not drop
> out to dos. However, I now have a different problem (see my posting of 14
> Oct.) which I have yet to resolve re packet class.

I believe it will prove more helpful to try either WINPKT or PKTMUX.
I didn't have any success with WINPKT, but I hear that's what Deepak
Vaidya used, apparently successfully.

Charley Noecker              Smithsonian Astrophysical Observatory
POINTS Group                 Mail Stop 63
noecker@cfa.harvard.edu      60 Garden St 
617-495-7329                 Cambridge, MA 02138
From: pozar@kumr.lns.com (Tim Pozar)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: int14 Redirector for FTP Software's kernel
Date: 9 Oct 92 05:39:37 GMT
Organization: Late Night Software (San Francisco)


   I remember a Int 14 redirector for FTP Software's PC/TCP kernel.  Could
someone mail me a pointer?

                                Thanks,
                                   Tim
-- 
Internet: pozar@kumr.lns.com               FidoNet:  Tim Pozar @ 1:125/555
UUCP:     ...!uunet!kumr.lns.com!pozar
Snail:    Tim Pozar / KKSF / 77 Maiden Lane / San Francisco CA 94108 / USA
Voice:    +1 415 788 2022
From: santeew@sisters.cs.uoregon.edu (Wes Santee)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: FAQ Request & Question
Date: 9 Oct 92 15:41:38 GMT
Article-I.D.: cs.1992Oct9.154138.28126
Distribution: na
Organization: University of Oregon Computer and Information Sciences Dept.

'Lo,

I just subscribed to this newsgroup so I'm not quite sure what the
realm of topics are.  Could someone please post the FAQ (if there is
one) so I can take a look at it?

On that note, let me explain my situation.  I'm trying to bring
up a package called PM NOS which is an OS/2 2.0 port of KA9Q for
DOS, for running SLIP sessions with my university.

The port does not include any documentation, so I'm using year-old
docs to try to figure it out.  If there are folks out there who
are using the DOS or OS/2 version, I'm calling on you for help.

First, I need to see copies of other peoples autoexec.nos (that is
what the OS/2 version calls it) startup files.  Some of the command
syntax is still throwing me for a loop and the documentation does not
give a lot of examples.  The commands are essentially the same as the
DOS version, so a DOS version of the file would be great too.

Second, for security reasons, my university issues an IP for SLIP
connections AFTER the call is established.  That is so no one
can use your IP.  Anyway, you may have a different IP every time
you call.  I'm looking for leads on new software, or hacked versions
of PM NOS that will allow me to input the IP AFTER I make the connection
(yeah, I know its a bitch for mail handling, but I see their point).

I've also been told about a mailing list called: tcp-group@ucsd.edu
that may have discussion of these topics, but I don't know
who to mail to join.

Thanks for any info.

-- 
Wes Santee             | "I think it's about time we voted for senators
santeew@cs.uoregon.edu |  with breasts.  After all, we've been voting
                       |  for boobs long enough."
                       |       -Claire Sargent on women senators
From: jrd@cc.usu.edu
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Kermit TCP/IP troubles
Date: 16 Oct 92 12:05:25 MDT
Organization: Utah State University

In article <1992Oct16.135407.17231@cfa203.harvard.edu>, mcn@cfa203.HARVARD.EDU (Charley Noecker) writes:
> From article <1992Sep30.143543.118@kenyon.edu>, by oursler@kenyon.edu:
> 
> One important problem you seem to be having is with the nameserver; it
> appears not to like the address you gave it.  We have also found that
> Kermit 3.11 didn't work properly with nameservers, even when we gave
> it the right nameserver.  This is fixed in Kermit 3.12 (available now
> from watsun.cc.columbia.edu); if you don't want to go get this now,
> you can try substituting the Internet node number in place of 'kcvax3'.
> 
> You may have other problems, too (it looks fishy that it can't release
> the packet driver; maybe you haven't got the right one).  This may
> prevent you from starting a later TCP/IP session.  I recommend: first,
> see if the direct Internet addressing works; if it does, then try the
> new kermit.  After that, you should check the packet driver.
> 
> Charley Noecker              Smithsonian Astrophysical Observatory
> POINTS Group                 Mail Stop 63
> noecker@cfa.harvard.edu      60 Garden St 
> 617-495-7329                 Cambridge, MA 02138
-----------
	A clarification. Kermit does work ok with nameservers but two things
can lead to trouble. One is that shim ODIPKT from Dan Lanciani allows register
DI to be modified and that upsets higher level C code, most commonly in the
DNS material of MSK 3.11. MSK 3.12 works around this item, plus it can go
straight to ODI rather than though the shim. The second item is DNS lookups
by Kermit are done with UDP packets, and there are always a few DNS servers
which are configured to work only with TCP rather than both TCP and UDP.
Check the SERVICES file on the DNS machine to ensure both protocols are
supported.
	As Charley says above, 95% of troubles are related to TCP/IP 
configuration either in the PC or along the network path. The network
administrator needs to be contacted on both items. The other 4.99% are
in configuring the lan adapter and avoiding hardware conflicts. This leaves
a generous 0.01% for my blunders in the code; after all, no one is perfect.
	Joe D.
Xref: sparky comp.protocols.tcp-ip.ibmpc:5611 comp.protocols.tcp-ip:4662
From: kratz@goofy.zdv.uni-mainz.de (Thomas Kratz)
Newsgroups: comp.protocols.tcp-ip.ibmpc,comp.protocols.tcp-ip
Subject: LPR-command with WINQVT-43
Keywords: LPR,WINQVT
Date: 7 Oct 92 20:15:41 GMT
Organization: Johannes Gutenberg Universitaet Mainz
Newsgroup: comp.protocols.tcp-ip.ibmpc

I have a problem with WINQVT version 43 on a 386 with 8MB and WINDOWS 3.1,
trying to use lpr on an UNIX-host. 
The entries in qvt_tcp.rc are - as far as i know - correct but after klicking
the OK-button in the LPR-window a window with the message
    
                      LPR-DEAMON refused 'send control file' command

My supervisor has checked his settings and the NCSA-Telnet-2.14-lpr.exe
works fine.
Has anybody similar problems or an idea how to solve them?
Please send me email to

    kratz@goofy.zdv.uni-mainz.de

or a RE: to that newsgroup          Thanks, Thomas
 
****************************************************************************
"Even a stopped clock gives the right time twice a day"
                                        source unknown, will be changed soon
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: morris@grian.cps.altadena.ca.us (Mike Morris)
Subject: Re: Is KA9Q still available for CP/M systems?
Organization: College Park Software, Altadena, CA
Date: Sat, 10 Oct 1992 06:06:34 GMT

tech@aupair.cs.athabascau.ca (Richard Loken) writes:

>fraser_h@eis.dofasco.ca writes:

>>Many times I've seen mention that KA9Q was originally developed for
>>Z80 CPM systems. Is that original distribution still available anywhere?

>If you should stumble across a copy I would dearly love to see it.

So would I.  I'm also looking for some routines that I can incorporate
into my Z80 (Z180 in the works) ham radio repeater controller software
that would allow passing messages to a packet radio TNC via a 2-way
link.

>Mr. Karn has a religious objection to CP/M and waxes rhetorical about 8 bits
>and TCP/IP when the subject comes up.  The song is to the effect that 8 bits
>are dead and gone and XT boards can be had loaded for $50.00.

Try $15.00 complete with 640k and a monochrome card.  I bought two at the
last ham swap meet.  They both work just fine...  Two handicapped hams
are going to get gift XTs (for packet, etc.)  as soon as I can find a
couple good MFM drives and a couple serial cards.

-- 
Mike Morris   WA6ILQ   | This space intentionally left blank.
PO Box 1130            | 
Arcadia, CA. 91077     | All opinions must be my own since nobody pays
818-447-7052 evenings  | me enough to be their mouthpiece...
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: mike@childsoc.demon.co.uk (Michael Bernardi)
Subject: ODIPKT and Token Ring 
Distribution: world
Organization: The Children's Society
Date: Mon, 12 Oct 1992 13:08:18 +0000

>I've just been thinking some more about this. Given that few if any
>applications support TR. Also that ODIPKT (and the NDIS Packet Driver?)
>produce Token Ring packets. Then a ETH2TR "shim" would seem a good solution?
>This would assume applications were using Ethernet and card were using TR.
>Then IBMTOKEN would need re-writing as TOKEN.COM or LANSUP.COM or renaming to
>LANTRPKT.COM? :-)

Are there ANY TCP/IP application that understand Token_Ring packets? Apart
from FTP's TCP/IP Package. I think I've installed the software correctly but
every application I try looks for an Ethernet packet driver, which it says
cannot be found :-(
--
 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: aml@world.std.com (Andrew M Langmead)
Subject: Re: Desqview/X over SLIP
Organization: The World @ Software Tool & Die
Date: Sun, 11 Oct 1992 14:15:47 GMT

ileicht@jarthur.claremont.edu (Spiff) writes:

>agghghg.. Is there any way I can get Desqview/X to recognize the current
>drivers I am using (slip8250). 

WARNING!! I HAVEN'T TRIED THIS YET!
Now Quarterdeck is distributing the driver that comes with Novell's
LAN Workplace for DOS,(but not any of the utilities that come with LWP)
 with the "X to other systems" diskettte. New copies of "X to other systems"
include a mail in coupon for the driver. If your package is early enough that
it didn't have the coupon, call QOS and they will send the driver to you.
(or at least promise to send it, I haven't seen mine yet.) One could use
   SLIP packet driver.
   (would pdether be needed here?)
   PD to ODI shim.
   LWP driver.
to get a SLIP system for DESQview/X.

-- 
|Andrew Langmead - A frustrated Mac/Unix programmer stuck in an MS-DOS job    |
|Usenet=aml@world.std.com      |S. O'Conner "We Live in a dangerous Age       |
|bix=a.langmead CI$=72411,1560 | To say how you feel is to lay your own grave"|
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: steven@gopher.dosli.govt.nz (Steven Brydon)
Subject: Is eXceed Plus 3.1 broken with FTP 2.11 generic kernel
Organization: Dept. of Survey & Land Information, NZ.
Distribution: comp.protocols.tcp-ip.ibmpc
Date: Thu, 15 Oct 1992 03:46:59 GMT


I have just recently received the FTP PCTCP 2.11 up grade.

However, since upgrading I can no longer run HCL's exceed Plus for DOS.
Are there known problems with using this combination of packages ?

The PC just crashes as soon as the grey X screen and mouse pointer appear.

I can easily revert back to my PCTCP 2.05 version and exceed runs fine ?

Heres my CONFIG.SYS and AUTOEXEC.BAT

	SHELL=C:\COMMAND.COM /P /E:512
	DEVICE=C:\DOS\SETVER.EXE
	DEVICE=C:\DOS\HIMEM.SYS
	DEVICE=C:\EMM386.EXE x=d000-d1ff noems
	DOS=HIGH,UMB

	PATH C:\DOS
	loadhigh c:\utility\gmouse.com
	loadhigh c:\dos\doskey.com
	loadhigh c:\pctcp\wd8003e.com -n 0x7c 3 0x280 0xd000
	loadhigh c:\novell\ipx.com
	loadhigh c:\novell\netx.com /c=c:\novell\shell.cfg
	c:\pctcp\ethdrv
	f:
	login

The PC is a 386SX 8Mbytes and a NE-3 network adapter. I am using the PC-210
generic kernel and the latest packet driver from the 2.11 unsupported software diskette.

The 2.11 application appear to run correctly.

		Regards
		Steven
From: cowboy@trans.csuohio.edu (Joe Rosenfeld)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Help with ODI please!
Date: 12 Oct 92 22:44:21 GMT
Organization: Cleveland State University

I have been able to get ODI working fine with all cards save David systems.
In fact, the most disturbing thing about this sordid episode is the lack of
assistance form DS themselves.  They apparently do not even read messages
to the Sysop of their own BBS.

According to someone from DS I need to use the netdev.sys and the
custom.exe file.  I have both, but truth to tell, I do not understand
custom.exe, how it works, what it does, and how to use it.

I would really like to use ODI for some DS cards I have, and if anyone can
shed any light on the way netdev.sys works with custom.exe, I would be
grateful.  Of course, if you have an ODI set up for DS MC and AT cards, I
would be doubly grateful.

Feel free to email me.  If I resolve this issue I would be more than happy
to post a summary on this group.

Thanks for your needed assistance,
Joe

--

________

Joe Rosenfeld                              cowboy@trans.csuohio.edu
Automation Librarian                      joer@inca.law.csuohio.edu
Cleveland State University Law Library