The information in this article applies to:
SUMMARYThis article documents the resources necessary to do Winsock development on the different Microsoft Windows platforms. The key components necessary for Winsock programming are:
MORE INFORMATIONWhere you get the necessary components for Winsock programming depends on what platform you are using. Microsoft Windows NT Versions 3.1 and 3.5 and Windows 95Header filename: WINSOCK.HImport library name: WSOCK32.LIB If you are using Microsoft Windows NT version 3.1 or 3.5, the TCP/IP protocol is provided as a component of the operating system. Please see your operating system documentation for more information about installing TCP/IP support for Microsoft Windows NT. The Winsock header file, import library, and specification are all supplied as part of the Win32 SDK. If you do not have the Win32 SDK, it can be purchased as part of the Microsoft Developer Network Level 2 subscription. The header file and import library are also supplied with the 32-bit editions of Visual C++. Visual C++ does not include the Windows Sockets specification. Microsoft Windows for Workgroups Version 3.11Header filename: WINSOCK.HImport library name: WINSOCK.LIB Windows for Workgroups does not include support for the TCP/IP protocol. However, Microsoft does provide a TCP/IP protocol for Windows for Workgroups free of charge. To learn how to obtain the TCP/IP package for Windows for Workgroups, please see the following article in the Microsoft Knowledge Base: Q111682 WFWG 3.11: How to Obtain Microsoft DLC and Microsoft TCP/IPThe following file is available for download from the Microsoft Download Center. Click the file name below to download the file: WSA16.exeFor more information about how to download files from the Microsoft Download Center, please visit the Download Center at the following Web address http://www.microsoft.com/downloads/search.aspand then click How to use the Microsoft Download Center. The header file and library for Winsock programming are not included with Visual C++ for Windows. Microsoft Windows Versions 3.0, 3.1, and 3.11Header filename: Probably WINSOCK.H (determined by vendor)Import library name: Probably WINSOCK.LIB (determined by vendor) TCP/IP support on these versions of Microsoft Windows will have to come from the underlying network. Your network vendor can tell you what TCP/IP support is available. Depending on your network and the TCP/IP implementation, you may also need to get the Winsock header and library files from your vendor. However, while not guaranteed, the files supplied in WSA16.EXE (see above) may work on your implementation. Microsoft Win32s Version 1.2Header filename: WINSOCK.HImport library name: WSOCK32.LIB A Winsock application running on Win32s will use the networking support of the underlying system. See the appropriate section above for information about TCP/IP support on the host platform. The header file, import library, and specification will be part of the Win32 SDK from which the Win32s application was created. See the section on Windows NT above for more information. Additional query words:
Keywords : kbnetwork kbAPI kbDLC kbNTOS310 kbNTOS350 kbNTOS351 kbSDKPlatform kbWinOS310 kbWinOS95 kbWinsock kbWin32s120 kbGrpNet |
Last Reviewed: November 23, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |