home *** CD-ROM | disk | FTP | other *** search
/ NetNews Usenet Archive 1992 #18 / NN_1992_18.iso / spool / comp / os / mswindo / misc / 2189 < prev    next >
Encoding:
Text File  |  1992-08-19  |  1.2 KB  |  34 lines
  1. Newsgroups: comp.os.ms-windows.misc
  2. Path: sparky!uunet!charon.amdahl.com!pacbell.com!mips!sdd.hp.com!decwrl!csus.edu!netcom.com!netcomsv!sjsumcs!sundance!rick
  3. From: rick@sundance.SJSU.EDU (Richard Warner)
  4. Subject: Re: TCP/IP DLL for Windows 3.1?
  5. Message-ID: <rick.714267511@sundance>
  6. Sender: news@sjsumcs.sjsu.edu (News Administrator)
  7. Nntp-Posting-Host: sundance.sjsu.edu
  8. Organization: San Jose State University - Math/CS Dept.
  9. References: <714077032.11227@minster.york.ac.uk> <1992Aug18.132440.29080@progress.com>
  10. Date: 19 Aug 92 23:38:31 GMT
  11. Lines: 21
  12.  
  13. leary@progress.COM (James Leary) writes:
  14.  
  15. >ken@minster.york.ac.uk writes:
  16.  
  17. >>Does anyone out there know of a product which gives a TCP transport to
  18. >>Windows 3.1 apps (via a DLL hopefully) which (even more hopefully) conforms
  19. >>to the winsock protocol?
  20.  
  21. >Novell's LAN Workplace for DOS
  22. >Wollogong's TCP/IP Utilities
  23.  
  24. You left out Netmanage's NEWT, which is the TCP stack they are
  25. using in their new NFS server and are licensing to a lot of the
  26. X server vendors.
  27.  
  28. >These are two that have DLL's for support of TCP/IP transports. (We at
  29. >Progress have written our software to support these from within Windows).
  30.  
  31. >Regards,
  32.  
  33. >Jim Leary
  34.