Path: utzoo!utgpu!watserv1!watmath!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!sdd.hp.com!spool.mu.edu!uunet!mcsun!ukc!acorn!unipalm!leo
From: leo@unipalm.uucp (E.J. Leoni-Smith)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Q: can LM/x and pc/tcp share tcp/ip stack?
Keywords: ndis, lan-manager, pc-tcp, tcp/ip
Message-ID: <1991Feb8.165239.6467@unipalm.uucp>
Date: 8 Feb 91 16:52:39 GMT
References: <1991Feb4.120459.15972@ulrik.uio.no> <1991Feb8.121444.4588@unipalm.uucp>
Organization: Unipalm Ltd., Cambridge, England
Lines: 110

leo@unipalm.uucp (E.J. Leoni-Smith) writes:

>edmbv@fiol.UiB.NO (Bjorn Asle Valde) writes:

>>My understanding of this setup leaves much to be done, hope
>>this isn't too stupid...

>>Have installed: HP lan-manager/x on an sco unix 3.2.2 box. The example
>>ms-dos client is  using tcp/ip to talk to the server, works nice. Now
>>I need to have a few programs to talk to a unix box over ftp's pc/tcp
>>tcp/ip implementation. Using the "dispktpm.dos" (ndis to packet converter)
>>and the generical kernel (ethdrv.exe) I can get pc/tcp to work *OR* 
>>lan-manager but not both it seems. Depending on what get loaded first it
>>seems like either l-m or pc/tcp will die from packet starvation. (?)

>>Can two tcp/ip stacks share an NDIS interface or am I trying to do something
>>impossible? I feel like taking a bath in aspirin, any help would be much
>>appreciated. Email responses prefered.

>Defintely YES, BUT some ndis drivers (notably current WD) break in this
>mode. 

>>PS: If it should turn out that this is indeed possible, then a copy of
>>"protocol.ini" and "lanman.ini" (and possibly config/autoexec) would
>>be helpful.

>>Regards, Bjorn Asle


>All part of the Unipalm Technical support service - you are lucky that
>England is covered in Snow today - so most of our real customers
>are staying at home!

>.................


>Sample CONFIG.SYS

>files=20 
>buffers=25 
>country=44,437,C:\DOS\country.sys 
>device=c:\ftp\ifcust.sys 
>device=c:\ftp\ipcust.sys 
>device=c:\lanman\drivers\dlc\protman.sys /I:c:\lanman 
>device=c:\ftp\dispktpm.dos 
>device=c:\lanman\drivers\elnkii\elnkii.sys 
>device=c:\lanman\drivers\netbeui\dosnetb.sys 
>lastdrive = v 


>Sample PROTOCOL.INI

>;**************************************************************************
>; %VER1.1d Protocol Manager Initialization File Template 
>; The following are default sections for various adapters and protocols 
>;**************************************************************************
>[protocol manager] 
>   DRIVERNAME = PROTMAN$ 
> 
>;************************ 
>;**     ADAPTERS       ** 
>;************************ 
>; WESTERN DIGITAL CARD 
>[WD8003XMAC] 
>  DRIVERNAME = MACWD$ 
>  IRQ = 5 
>  RAMADDRESS = 0XD000 
>  IOBASE = 0X280 
> 
>[ETHERLINKII] 
>    DRIVERNAME = ELNKII$ 
>    IOADDRESS = 0x300 
>    INTERRUPT = 3 
>    MAXTRANSMITS = 12 
>      XMITBUFS = 1 
> 
>;************************ 
>;**     PROTOCOLS      ** 
>;************************ 
>; NetBEUI ; works with DLC Protocol 
> 
>[NETBEUI] 
>  DRIVERNAME = NETBEUI$ 
>  BINDINGS = ETHERLINKII 
> 
>; FTP Packet driver 
> [PKTDRV] 
>  DRIVERNAME = PKTDRV$ 
>  BINDINGS = ETHERLINKII 
>  INTVEC = 0x65 
>  CHAINVEC = 0x66 

>Sample AUTOEXEC.BAT

>prompt $p$g 
>path=c:\;c:\dos;c:\lanman;c:\ftp;c:\lanman\drivers\dlc;c:\lanman\netprog 
>keyb uk,437,c:\dos\keyboard.sys 
>netbind 
>net start work 
>net logon user1 password 
>net use d: \\intl_server\users
>ethdrv  
>cd d:\user1 
>d: 


>This configuration was tested using a COMPAQ version of Lan Manager.
ARGGH I just realised you said LM/X! not straight Lan Manager.

All the above is of course irrelevant - sorry.