🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: comp.protocols.tcp-ip.ibmpc
1 messages
1 total messages Started by Jim Spink Wed, 30 Mar 1994 13:55
Re: IBM's DOS TCPIP over ODI?
#7360
Author: Jim Spink
Date: Wed, 30 Mar 1994 13:55
62 lines
3507 bytes
In article <Cn8LKK.J22@csfb1.fir.fbc.com> wrolf@csfb1.uucp (Wrolf Courtney) writes:
>In article <94074.214603U41602@uicvm.uic.edu> Rich Chong <U41602@uicvm.uic.edu> writes:
>>I'm trying to get IBM's TCP/IP for DOS  working on a Netware LAN.
>>Netware workstations talk ODI, that particular TCPIP talks NDIS.
>>The usual solution is to use a shim like ODINSUP. I can't seem to
>>get it working tho. It appears that a device driver needs to get
>>loaded, but after we've loaded other things on with autoexec.
>>For instance,
>>
>>CONFIG.SYS:                           AUTOEXEC.BAT
>>
>>      :                                    :
>>device=DXMA0MOD.SYS                   LSL
>>device=DXMC0MOD.SYS                   TOKEN
>>device=\TCPDOS\BIN\PROTMAN.DOS ...    ODINSUP
>>device=\TCPDOS\BIN\DOSTCP.SYS         NETBIND
>>                                      IPXODI
>>                                      NETX
>>
>
>This has one obvious problem - TOKEN.COM writes directly to the token-ring
>card, bypassing and stomping all over DXMA0MOD.SYS and DXMC0MOD.SYS.
>
>I am not familiar with IBM's TCP/IP for DOS, but let me suggest the following
>approach:
>
>a)  Check that IBM TCP/IP for DOS works OK, without the Netware LSL through
>    NETX.
>
>b)  Replace the TOKEN.COM with LANSUP.COM, and check that Netware works
>    OK.
>
>c)  Combine them, but make sure that whoever opens the adapter first, leaves
>    EXTRA.SAPs for the other protocol (probably just one.)  This parameter
>    is passed to the DXMx0MOD.SYS drivers by the first stack to run.  If
>    LANSUP.COM runs first, then put the parameters in the LANSUP section of
>    net.cfg.  Check Novell's manuals for exact parameters.
>
>This approach would have the multiplexing of the card handled by DXMx0MOD.SYS.
>If you instead want to have ODI handle it, then you could load TOKEN.COM,
>eliminate the "device=DXMx0MOD.SYS" statements, and again get them to work
>one at a time.  Right off the top of my head all you need for ODI itself is
>LSL and TOKEN.COM.  This approach may be 5-10% faster, and also works
>on non-token-ring networks (with substitution of the appropriate ODI driver
>for the card.)
>
>Wrolf
>
>
>-- 
>Wrolf Courtney               CS First Boston             My employer knows
>(212) 322-7017               Park Avenue Plaza           I'm crazy.
>wrolf@csfb1.fir.fbc.com      New York, NY 10055
>uunet!csfb1!wrolf

If you still have problems I suggest calling IBM support
at 1-800-237-5511.  They can help you with configuration
and open up a problem report if necessary to get your
problem fixed.

Jim Spink
IBM
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads