OS/2, eCS & ArcaOS - Technical > Web applications
The MicroWeb DOS web browser
Roderick Klein:
--- Quote from: Martin Iturbide on January 06, 2022, 02:01:23 am ---Hi
I got this reply from Mike, the mTCP author.
--- Quote ---I wrote mTCP to bring networking to my old computers. Think about machines like the original IBM PC (1981), the PCjr (1983) and the PC AT. mTCP works fine in an emulated machine, and possible even in a virtual DOS machine. But it needs a packet driver which has direct and exclusive access to a network card. And it provides its own TCP/IP implementation.
If you want to use the networking available in a DOS VDM the programs need to be rewritten to use those networking APIs directly. I don't think that is a huge problem, but some quick Googling did not give me any information on what that network API even looks like. Do you have any links on what the network API for DOS VDMs looks like?
--- End quote ---
Do you know by chance the API that the DOS VDM uses for networking?
Regards
--- End quote ---
Hmmm I do not know if this is even documented somewhere with some examples how to write code to acess this interface.
VDOSTCP.SYS is most likely the driver providing this interface...
https://www.betaarchive.com/forum/viewtopic.php?t=32026
Mentions:
IBM TCP/IP for DOS 2.1.1 Programmer's Toolkit
The very few times I used the WIN/OS2 TCP/IP stack it crashed my system most cases. So I am not 100% certain how stable it this VDM TCP/IP support.
Roderick
Martin Iturbide:
Hi
So, I need to find the documentation inside the "IBM TCP/IP for DOS 2.1.1 Programmer's Toolkit".
On the "IBM TCP/IP VERSION 2.0 FOR OS/2" announcement there are some references to something called "DOS/Windows Access Kit"
--- Quote ---DOS/WINDOWS ACCESS KIT: This facility allows DOS applications written to the IBM TCP/IP for DOS Version 2.1 programming interfaces, and Windows applications written to the Windows Sockets API Version 1.0 or Version 1.1 specifications to run in an OS/2 environment on top of IBM TCP/IP Version 2.0 for OS/2. This product requires the customer to have the OS/2 Version 2.1 operating system installed.
--- End quote ---
I'm still trying to find something on a package of TCP/IP 2.0 for OS/2, but I still haven't find that documentation.
Regards
Martin Iturbide:
Hi
Checking also this book: "gg243531 TCPIP 2.0 for OS/2 Installation and Interoperability", chapter 13.
I found these pages (attached), but still no API documentation.
Regards
Olafur Gunnlaugsson:
--- Quote from: Martin Iturbide on January 07, 2022, 03:33:20 pm ---Hi
So, I need to find the documentation inside the "IBM TCP/IP for DOS 2.1.1 Programmer's Toolkit".
On the "IBM TCP/IP VERSION 2.0 FOR OS/2" announcement there are some references to something called "DOS/Windows Access Kit"
--- Quote ---DOS/WINDOWS ACCESS KIT: This facility allows DOS applications written to the IBM TCP/IP for DOS Version 2.1 programming interfaces, and Windows applications written to the Windows Sockets API Version 1.0 or Version 1.1 specifications to run in an OS/2 environment on top of IBM TCP/IP Version 2.0 for OS/2. This product requires the customer to have the OS/2 Version 2.1 operating system installed.
--- End quote ---
I'm still trying to find something on a package of TCP/IP 2.0 for OS/2, but I still haven't find that documentation.
Regards
--- End quote ---
The OS/2-DOS TCP/IP interface is basically WINSOCK
Olafur Gunnlaugsson:
--- Quote from: Sean Casey on January 05, 2022, 04:44:02 pm ---
--- Quote from: Olafur Gunnlaugsson on January 05, 2022, 02:27:38 am ---It is possible to run DOS packet drivers in a DOS session if you disable the DOS/2 networking, but not recommended, FTP Software (the company) also sold a TCP/IP stack for OS/2 that had a VDD that allowed DOS sessions to use DOS packets via emulation, but alas that is impossible to get hold of these days. The Essex Systems stack also had some VDD trickery, but I cannot remember it it supported the FTPS packets specification.
--- End quote ---
Is it true these older OS/2 TCP/IP and NetBIOS over TCP implementations used proprietary APIs which limited their use to only the network applications/services that were distributed with these packages?
--- End quote ---
The stacks were mostly compatible when using the same protocols, the low level or packet interfaces on OS/2 1.x varied from provider to provider however, for OS/2 2x this matterred less since NDIS was provided as standard and most stacks just layered on top of that (NDIS was available for 1.x, but not supplied as standard, except possibly with 1.3).
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version