Help! An associate of mine is determined to use IBM TCP/IP for DOS under the
DOS box in OS/2. Yes, he does have a copy of TCP/IP for OS/2. No, for various
reasons, he won't use it for this purpose. When he tries to open a DOS box, he
gets an error during the NETBIND. Any helps, suggestions, reasons this simply
won't work? An IBM rep said it would, though not the preferred method, but
alas, he was on the OS/2 TCP/IP team and could not give details on how to set
up the DOS product to work.
Thanks, Blaine p.s. How can I get my copy of TCP/IP for OS/2 to work in the
DOS box? I have read of an "access kit" and have been told about installing
virtual drivers, but need some more details. Thanks on this one, too!
I am not sure if this is supported. In any case, you will need the
TCP/IP for OS/2 2.0 DOS access kit. Does your associate have it ?
************************************************************************
* Stefan Zollner, Assistant Professor and Associate Physicist *
* Iowa State University/Ames Laboratory, A205 Physics, Ames, IA 50011 *
* zol...@iastate.edu Phone: (515) 294-7327 FAX: (515) 294-0689 *
************************************************************************
I do not believe you will be able to get TCP/IP for DOS/Windows to
run in a VDM in OS/2. The biggest reason is that there isn't a virtual NDIS
driver. The TCP/IP for DOS/Windows will not be able to get to any lan adapters.
Not also that there are probably some other reasons that it won't work, so I wouldn't
get my hopes of even a slip only install working...
As for VDM support for OS/2 TCP/IP, you have to install the DOS/Windows Access Kit.
It will allow you to run any application written to winsock, or to our TCP/IP for DOS/Windows
Programmers Toolkit v2.0 or later.
Jonathan (Jon) Rosen <jro...@vnet.ibm.com>
IBM TCP/IP Development
I submitted the entire text of your post to IBM's TCP/IP for DOS development
team. Here is the answer I got back:
>This person needs to use OS/2 TCP/IP's DOS Windows Access kit,
>which will provide the stack connectivity.
Craig Weeks
IBM Corp.
Austin, Texas
These opinions are mine, not IBM's.