home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.ms-windows.programmer.win32
- Path: sparky!uunet!microsoft!hexnut!jallard
- From: jallard@microsoft.com (James 'J' Allard)
- Subject: Re: Using WinSock with Windows NT
- Message-ID: <1992Dec18.030810.20582@microsoft.com>
- Date: 18 Dec 92 03:08:10 GMT
- Organization: Microsoft Corporation
- References: <wright.81.0@lims01.lerc.nasa.gov> <724589124.2313@minster.york.ac.uk>
- Lines: 23
-
- In article <724589124.2313@minster.york.ac.uk> ken@minster.york.ac.uk writes:
- >Ted Wright (wright@lims01.lerc.nasa.gov) wrote:
- >: Is it possible for 16 bit Windows applications to make socket library
- >: calls to the 32 bit wsock32.dll library in NT?
- >
- >I've been told no (on this group - see earlier threads). But I've also been
- >told yes by other people (see earlier threads). But I can't make my X
- >windows talk to the sockets library. If you get anything to work, please
- >followup here.
-
- I've mentioned this on comp.protocols.tcp-ip.ibmpc a number of times, but it
- probably didn't find it's way over here.
-
- We'll be offering both 16- and 32-bit Windows Sockets support under Windows
- NT product 1. The October beta and SDK did *not* have the 16-bit support, but
- did have the 32-bit support. It is correct that 16-bit applications cannot
- use wsock32.dll. The 16-bit support will be shipped as winsock.dll and will
- support applications developed to Windows 3.1 and Windows Sockets.
-
- Hope this clears things up.
-
- --
- _______________________________________________________________
- J. Allard jallard@microsoft.com
- Program Manager of TCP/IP Technologies work: (206)882-8080
- Microsoft Corporation home: (206)860-8862
-