🚀 go-pugleaf

In article <1992Jun9.000200.25752@honte.uleth.ca>, fengstad@alpha.uleth.ca (Grant Fengstad) writes:
|> A while back I posted a query as to the feasibility of running OS/2 2.0
|> requester and IBM's TCP/IP together using the same Network adapter.
|> 
|> The good news is "Yes" in a word.  Novell, smartly, has provided ODI
|> compliancy with the OS/2 requester.  In addition, it is possible through
|> the ODINSUP driver to run both ODI and NDIS based protocols on the same
|> adapter.  Using this specification, IBM's TCP/IP, which uses the NDIS
|> spec can co-exist with Novell's IPX/SPX services.
|> 
|> --
|> #====================================================================#
|> # Grant M. Fengstad               E Mail: fengstad@alpha.Uleth.CA #
|> # Manager, Network Operations             Voice:     (403) 382-6724       #
|> # RegionAir Information Systems           FAX:       (403) 327-1229       #
|> # A division of Canadian Regional Airlines Ltd.                           #
|> # 1921 Mayor Magrath Drive        Lethbridge, AB, CANADA T1J 3Z1  #
|> #====================================================================#

There may be problems here though.  It's my current understanding that
IBM's TCP/IP is not interacing w/ ZODINSUP properly.  If your net.cfg can
supply enough LSL buffers then it will work fine.  In my case net.cfg
tries to support both T/R and Enet via ODINSUP and I think I am running
out of buffers causing TCP/IP to hang after running OK for a short time.
I'm trying to resolve the problem w/ Novell and IBM currently.

-- 
David Kolb                    Opinions are my own not SAS'
SAS Institute, Inc.           EMAIL:      sasdxk@unx.sas.com
SAS Campus Drive - J206       Phone:      (919) 677-8000 x6827
Cary, NC  27513-2414 USA      FAX:        (919) 677-8123