[comp.protocols.tcp-ip.ibmpc] TCP/IP from OS/2

craigs@cognos.UUCP (Craig Statchuk) (04/12/90)

I have been trying to dig up sources for TCP/IP TRANSPORT level support
under OS/2.  So far I have come up with 4 possibilities -- any of which
may or may not be suitable -- maybe someone can help:

1.  PC/TCP for OS/2 from FTP Inc.  This is a new product (just released this
    month) that provides APPLICATION layer support (ftp, telenet, et al.)
    Currently they DO NOT have a Programmer's Toolkit that provides TRANSPORT
    layer support (either 4.x BSD Sockets or NAMED PIPES is acceptable).
    Apparently they will be releasing such a product soon.

2.  TCP/IP for OS/2 from IBM.  Appears to have all neccessary development
    tools and libraries.  Questions:  Rumour has it that you need OS/2 EE to
    use this package -- does anyone know for sure?  Also, are any of the
    libraries usable in a DLL?

3.  Essex TCP/2 -- had some good recommendations on this package except
    that I don't know how to contact them (sorry but I've never heard
    of Essex Systems -- I have a feeling that this is about to change).

4.  Excelan/Novell for OS/2 --  Provides 4.3 BSD socket support as DLL
    (good!) and support for NDIS network cards.  Question: Is Novell LAN
    Manager Software required to run in a UNIX environment?  Does anyone
    have any experience with this package?


We intend to port some existing applications from SUN UNIX to OS/2
and would like to use a BSD Socket library.

Thanks in advance -- I will summarize responses for the net if I
find out anything interesting...

-- 
Craig Statchuk           P.O. Box 9707        uunet!mitel!sce!cognos!craigs
Cognos Incorporated      3755 Riverside Dr.   craigs%cognos.uucp@uunet.uu.net
HUMAN: (613) 738-1440    Ottawa, Ontario
FAX:   (613) 738-0002    CANADA  K1G 3Z4

schafer@rice.edu (Richard A. Schafer) (04/14/90)

The IBM version definitely *does* require EE 1.2; I would guess that means
it requires something in the Communications Manager section, presumably
the Ethernet interface drivers that I believe are part of Comm Manager.
 
IBM has stated that they recognize the need for TCP/IP to work with SE,
and plan to try to do that in the future.