Re: lynx-dev lynx for WIN 3.1?

[Jason F. McBrayer]

>>>>> "MS" == Michael Sokolov <address@hidden> writes:

MS>    The_guy_who_is_too_ashamed_of_himself_to_reveal_his_name
MS> <address@hidden> wrote:
   
>> 2. You have some kind of a Dos interface
>> to winsock.dll.
   
MS>    Or even better the other way around: have DOS software
MS> establish the network connection, load a DOS memory-resident
MS> TCP/IP stack, and then either run DOS network apps or load Windows
MS> and run Windows network apps, having a WINSOCK.DLL that's a
MS> wrapper around the DOS TCP/IP stack. That's what was done at CWRU
MS> before this Win95 shit.
   
It's also the way WINSOCK works on OS/2, except at one more remove.
There's a DOS device driver VDOSTCP.SYS that communicates between DOS
network apps and the OS/2 native TCP/IP stack.  The WINSOCK.DLL on
Win-OS/2 is an interface to VDOSTCP.SYS.  Obviously, this also
predates Win95 by a good bit.


-- 
+----------------------------------------------------------------+
| Jason F. McBrayer              address@hidden |
| The scalloped tatters of the King in Yellow must hide Yhtill   |   
| forever.                    R.W. Chambers _The King in Yellow_ |