Latest Posts »
Latest Comments »
Popular Posts »

Outlook Express Error Codes - Winsock Errors

Written by The Geekette on August 23, 2005 – 1:15 am
Posted in Applications, Mail Clients, Winsock | No Comments »

0×800CCC40 WINSOCK_WSASYSNOTREADY Network subsystem is unusable. 
0×800CCC41 WINSOCK_WSAVERNOTSUPPORTED Windows Sockets cannot support this application. 
0×800CCC42 WINSOCK_WSAEPROCLIM 
0×800CCC43 WINSOCK_WSAEFAULT Bad address. 
0×800CCC44 WINSOCK_FAILED_WSASTARTUP Unable to load Windows Sockets. 
0×800CCC45 WINSOCK_WSAEINPROGRESS Operation now in progress. This error appears if a Windows Sockets API is called while a blocking function is in progress.

End of Article



Winsock Error Codes

Written by The Geekette on August 22, 2005 – 1:31 pm
Posted in Internet, Networking, Winsock | 1 Comment »

10004  WSAEINTR Interrupted system call.
10009  WSAEBADF Bad file number.
10013  WSEACCES Permission denied.
10014  WSAEFAULT Bad address.
10022  WSAEINVAL Invalid argument.
10024  WSAEMFILE Too many open files.
10035  WSAEWOULDBLOCK Operation would block.
10036  WSAEINPROGRESS Operation now in progress. This error is returned if any Windows Sockets API function is called while a blocking function is in progress.
10037  WSAEALREADY Operation already in progress.
10038  WSAENOTSOCK Socket operation on nonsocket.
10039  WSAEDESTADDRREQ Destination address required.
10040  WSAEMSGSIZE Message too long.
10041  WSAEPROTOTYPE Protocol wrong type for socket.
10042  WSAENOPROTOOPT Protocol not available.
10043  WSAEPROTONOSUPPORT Protocol not supported.
10044  WSAESOCKTNOSUPPORT Socket type not supported.
10045  WSAEOPNOTSUPP Operation not supported on socket.
10046  WSAEPFNOSUPPORT Protocol family not supported.
10047  WSAEAFNOSUPPORT Address family not supported by protocol family.
10048  WSAEADDRINUSE Address already in use.
10049  WSAEADDRNOTAVAIL Cannot assign requested address.
10050  WSAENETDOWN Network is down. This error may be reported at any time if the Windows Sockets implementation detects an underlying failure.
10051  WSAENETUNREACH Network is unreachable.
10052  WSAENETRESET Network dropped connection on reset.
10053  WSAECONNABORTED Software caused connection abort.
10054  WSAECONNRESET Connection reset by peer.
10055  WSAECONNRESET No buffer space available.
10056  WSAEISCONN Socket is already connected.
10057  WSAENOTCONN Socket is not connected.
10058  WSAESHUTDOWN Cannot send after socket shutdown.
10059  WSAETOOMANYREFS Too many references: cannot splice.
10060  WSAETIMEDOUT Connection timed out.
10061  WSAECONNREFUSED Connection refused.
10062  WSAELOOP Too many levels of symbolic links.
10063  WSAENAMETOOLONG File name too long.
10064  WSAEHOSTDOWN Host is down.
10065  WSAEHOSTUNREACH No route to host.
10091  WSASYSNOTREADY Returned by WSAStartup(), indicating that the network subsystem is unusable.
10092  WSAVERNOTSUPPORTED Returned by WSAStartup(), indicating that the Windows Sockets DLL cannot support this application.
10093  WSANOTINITIALISED Winsock not initialized. This message is returned by any function except WSAStartup(), indicating that a successful WSAStartup() has not yet been performed.
10101  WSAEDISCON Disconnect.
11001  WSAHOST_NOT_FOUND Host not found. This message indicates that the key (name, address, and so on) was not found.
11002  WSATRY_AGAIN Nonauthoritative host not found. This error may suggest that the name service itself is not functioning.
11003  WSANO_RECOVERY Nonrecoverable error. This error may suggest that the name service itself is not functioning.
11004  WSANO_DATA Valid name, no data record of requested type. This error indicates that the key (name, address, and so on) was not found.



Fixing the Winsock Windows 98 and ME

Written by The Geekette on August 21, 2005 – 1:48 pm
Posted in 9x, Applications, ME, Registry, Spyware and Adware, Tips, Windows, Winsock | No Comments »

Windows 9x and ME users:

A) Use Regedit.exe to navigate to: HKEY_LOCAL_MACHINESystemCurrentControlSetServicesWinsock. 
B) Export the Winsock key to a Winsock.reg file, to save it. 
C) Delete the Winsock key. 
D) Navigate to: HKEY_LOCAL_MACHINESystemCurrentControlSetServicesWinsock2.
E) Export the Winsock2 key to a Winsock2.reg file, to save it.
F) Delete the Winsock2 key.
G) Exit Regedit.exe.
H) Control Panel / Network and Dial-up Connections.
I) Right-click Local Area Connection and press Properties.
J) Select Internet Protocol (TCP/IP) and press Uninstall.
K) After uninstalling TCP/IP, shutdown and restart your computer.
L) If TCP/IP is NOT automatically re-installed, use Control Panel / Network and Dial-up Connections.
M) Right-click Local Area Connection and press Properties.
N) Press Install.
O) Press Protocol / Add.
P) Select Internet Protocol (TCP/IP) under Network Protocol, possibly under Microsoft, and press OK.
Q) After the TCP/IP install, power off and power on your external modem, or shutdown and restart your computer.