Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!DBSTU1.BITNET!C0033003
From: C0033003@DBSTU1.BITNET
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: ind$file info required
Message-ID: <8906061038.aa24280@louie.udel.edu>
Date: 7 Jun 89 05:00:39 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 34
X-Unparsable-Date: Tue, 06 Jun 89 14:19:33 MEZ

well, hmm, maybe this has been asked b4, but:

does anyone have a description about the ind$file mechanism of IBM ?
Anyone tried to utilize this mechanism to supply a low level interface
to replace the TCP/IP drivers ?

We do have ind$file running here, it's a standard feature ( I guess )
for file xfer between hosts and remote machines at IBM, but I couldn't
even find a description of this mysterium until now.

Any info would be appreciated.

Thanx in advance.

Detlef
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

#include <disclaimer.std>


 Detlef J. Schmidt                +49  531  391 5514
 Computing center
 University Brunswick
 P.O.B. 3329
 D-3300 Braunschweig
 F.R.G.

C0033003 at dbstu1.bitnet
 C0033003%DBSTU1.BITNET@MITVMA.MIT.EDU
 c0033003%dbstu1.bitnet%cunyvm.cuny.edu@BRL.ARPA
 CUNYVM.CUNY.EDU!C0033003%DBSTU1.BITNET@ucbvax.Berkeley.EDU
 ..!mcvax!unido!DBSTU1.bitnet!c0033003
etc...
.