The code below demonstrates the minimal number of changes required to make the examples from the text execute under Winsock. Further changes can be made to make this code more Winsock complaint (e.g., test socket() failure return value as SOCKET_ERROR rather than < 0). WinSock Example code:

• Tarred and gzipped archive
• Winzip archive
• Individual Files
  • TCPEchoClientWS.c
  • DieWithErrorWS.c
  • TCPEchoServerWS.c
  • HandleTCPClientWS.c
  • UDPEchoClientWS.c
  • UDPEchoServerWS.c
  • SigAction.c - Not Available (Signals are not available under Windows)
  • UDPEchoServer-SIGIO.c - Not Available (Signals are not available under Windows)
  • UDPEchoClient-Timeout.c - Not Available (Signals are not available under Windows)
  • TCPEchoServer-Fork.c - Not Available (Win32 CreateProcess requires a separate executable)
  • TCPEchoServerWS.h
  • CreateTCPServerSocketWS.c
  • AcceptTCPConnectionWS.c
  • TCPEchoServer-ThreadWS.c
  • TCPEchoServer-ForkN.c - Not Available (Win32 CreateProcess requires a separate executable)
  • TCPEchoServer-SelectWS.c
  • BroadcastSenderWS.c
  • BroadcastReceiverWS.c
  • BroadcastReceiverNonblockingWS.c (Added to show nonblocking WinSock socket since SIGIO example does not work)
  • MulticastSenderWS.c
  • MulticastReceiverWS.c
  • ResolveNameWS.c
  • ResolveServiceWS.c
• To compile:
  • Make sure you add wsock32.lib to library module list