Hi Leonard,

     About "packet driver problem" of May 13:

LE> ...I've got an old DOS box on my LAN.  It's got an Intel NIC and is
LE> using IPX...  I need to get TCP/IP working on it, but I can't seem
LE} to get a packet driver to co-exist with the netware driver.
BI> www.crynwyr.com
LE> ...Intel's website has a packet driver.  But not one that'll co-
LE> exist with the IPX driver.

     I yet have a long way to go before i can pretend that i've acquired
enough experience about the subject to make sense so, please, be kind to
me for i may not put it correctly but, euh...  Some reading does mention
the possibility to run multiple protocols and multiple ~LAN~ adapters on
a single machine and this includes "logical network boards" like a ~PPP~
packet-driver, it would seem.  Multiple frame-formats can be used over a
same "network board" (and wire), etc...  Perhaps this will be useless to
you but since there's nothing wrong about sharing information, even if a
user doesn't have a full grasp of what this is all about, i believe that
the texts i found may very well shead some light on your accute problem:

          ftp.rz.uni-osnabrueck.de/msdos/networking/novell/odi/ 
 -->       odidoc.doc - The Novell ~ODI~ manual (75 Ko, 1994)
           odiinfo.doc - The ~ODI~ specification (24 Ko, 1993)

     I once had the opportunity to play with a minimal set from `LW4DOS'
(and/or `DR_WEB-Spyder' as well) so, indeed, i do vaguely remember about
multiple protocol "bindings", etc.  I suggest you refer to this material
before anything else;  to the least, this will boost your determination:

          ..."expand your network by using multiple protocols (such as
 -->      IPX/SPX, AppleTalk, LAT, or TCP/IP)"...  ..."use the NET.CFG
 -->      file to configure the LAN driver for any possible hardware
          configuration"...  ..."Driver files such as NE2000.COM...
          ...are also called MLIDs (Multiple Link Interface Drivers)"...
          ..."LSL directs information to the appropriate protocol stack,
          a user can use TCP/IP services as well as IPX and AppleTalk
          services"...  ..."BIND option forces the protocol to
bind"...

     Since you seem to need an ~MLID~ to bind to the ~TCP~/~IP~ protocol
stack or vice versa (?), euh...  i guess you could try `TCPIP.EXE v5.0',
unless your system uses .NLMs instead...  The first is found right here:

          ftp://ftp.hsh.no/pub/archive/ftp.novell.com/nwos/dsclnt12/
           tcp16.exe (167 Kb, 1996)

     Finally, supposing you have the Intel `EtherExpress' driver loaded,
chances are a section of your `Net.CFG' file would look a bit like this:
________________________________________________________________________
          PROTOCOL TCPIP
               BIND EXP16
          ...

          PROTOCOL IPX
               BIND 1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     Take notice that the various ~IP~ content will certainly have to be
made up-to-date or `TCPIP.EXE' won't work;  it's also possible that this
version might be incompatible with a given application, in which case it
could make sense to use `TCPIP.EXE v4.2' from the `LW4T3.EXE' archive...
One more reason for failure may be the absence of (or inability to find)
components which are required (like some .MSG file or such).  Good luck!

     As i've commented in the begining, that's only a wild guess here so
it's quite possible that none of this will get you back on tracks but my
impression was that one simply shouln't have to install a second packet-
driver in the 1st place:  a single working one would probably suffice!!!

     When you're satisfied that some application requiring `TCPIP' to be
loaded functions correctly, a short visit to www.danlan.com provides you
with support for more applications if these must have Class-1/~EtherNet~
`Waterloo ~TCP~' instead (Daniel Lanciani has given us `ODIPkt v3.0')...

     Unless i misunderstood the whole thing, it's more about having your
configuration right than finding a packet driver which can co-exist;  it
seems reasonable to expect "shims" to attach to a driver without causing
harm but i got my doubts about connecting two drivers to one same ~NIC~.

                                             Salutations,  :)

                                             Michel Samson
                                             a/s Bicephale


P.S.:  The matter of multiple ~NIC~s made me wonder...  Does anyone know
       if two ~NIC~s can be connected through an ~UTP~ cross-wired cable
       while `Win 2K Pro' manages the 1st ~NIC~ and ignores the 2nd one,
       *COMPLETELY*, yet leaving it accessible from a DOS box?  It seems
       ~NIC~s are unlikely to be accessible from DOS Boxes, unless there
       is a way to exclude the section of ~UMB~ (via `Config.NT'?) where
       they happen to have their ~ROM~ located...  DOS applications like
       `MS-Kermit' can simply connect to `TSNT14.COM' from `COM/IP v3.1'
       but some LEGACY SoftWare which must use a packet-driver interface
       could link to the 2nd ~NIC~ instead, given that `Win 2k Pro' does
       not make its ~ROM~ disapear;  this DOS ~NIC~ connected by a cable
       to the rest of the NetWork managed by `Win 2K' would benefit from
       any fire-wall, virus scanner or INet feed present (in the form of
       a ~PPP~ "Adapter Card" thru `ICS', or a High-Speed MoDem), etc!!!


... And then there were none, a footnote in the history of the InterNet.
--- MultiMail/XT v0.42 - Who wants to make TelNet OLMR BBSing UNIVERSAL?