....diese fehlermeldung bei jedem Windows-start (win98) erscheint ???
Windows socket error (11001), on API'ASync Lookup'
Ich steh vor einem Rätsel....
was hab ich mir zerschossen, wenn....
Moderator: Karaokefreak
-
Karaokefreak
- SuperMod
- Beiträge: 4460
- Registriert: Mo Mai 21, 2001 12:01 am
-
Aix jongliert mit Nudelhö
- Beiträge: 4765
- Registriert: Mo Dez 06, 1999 1:01 am
was hab ich mir zerschossen, wenn....
<BLOCKQUOTE><font size="1" face="Verdana, Arial">Zitat:</font><HR>Windows Sockets Error Codes, Values, and Meanings (Q150537)
--------------------------------------------------------------------------------
The information in this article applies to:
Microsoft Windows NT Workstation versions 3.5 , 3.51
Microsoft Windows NT Server versions 3.5 , 3.51
Microsoft LAN Manager, version 2.2c
Microsoft TCP/IP-32 for Windows for Workgroups, versions 3.11 , 3.11a , 3.11b
Microsoft Windows 95
Microsoft Network Client for MS-DOS version 3.0
--------------------------------------------------------------------------------
SUMMARY
This article describes the Windows Sockets error codes.
MORE INFORMATION
The following table is a list of possible error codes returned by the WSAGetLastError() call, along with their explanations.
Windows Sockets code Error Description
------------------------------------------------------------------------
WSAEINTR 10004 Interrupted system call.
WSAEBADF 10009 Bad file number.
WSEACCES 10013 Permission denied.
WSAEFAULT 10014 Bad address.
WSAEINVAL 10022 Invalid argument.
WSAEMFILE 10024 Too many open files.
WSAEWOULDBLOCK 10035 Operation would block.
WSAEINPROGRESS 10036 Operation now in progress. This error is
returned if any Windows Sockets API
function is called while a blocking
function is in progress.
WSAEALREADY 10037 Operation already in progress.
WSAENOTSOCK 10038 Socket operation on nonsocket.
WSAEDESTADDRREQ 10039 Destination address required.
WSAEMSGSIZE 10040 Message too long.
WSAEPROTOTYPE 10041 Protocol wrong type for socket.
WSAENOPROTOOPT 10042 Protocol not available.
WSAEPROTONOSUPPORT 10043 Protocol not supported.
WSAESOCKTNOSUPPORT 10044 Socket type not supported.
WSAEOPNOTSUPP 10045 Operation not supported on socket.
WSAEPFNOSUPPORT 10046 Protocol family not supported.
WSAEAFNOSUPPORT 10047 Address family not supported by protocol
family.
WSAEADDRINUSE 10048 Address already in use.
WSAEADDRNOTAVAIL 10049 Cannot assign requested address.
WSAENETDOWN 10050 Network is down. This error may be
reported at any time if the Windows
Sockets implementation detects an
underlying failure.
WSAENETUNREACH 10051 Network is unreachable.
WSAENETRESET 10052 Network dropped connection on reset.
WSAECONNABORTED 10053 Software caused connection abort.
WSAECONNRESET 10054 Connection reset by peer.
WSAENOBUFS 10055 No buffer space available.
WSAEISCONN 10056 Socket is already connected.
WSAENOTCONN 10057 Socket is not connected.
WSAESHUTDOWN 10058 Cannot send after socket shutdown.
WSAETOOMANYREFS 10059 Too many references: cannot splice.
WSAETIMEDOUT 10060 Connection timed out.
WSAECONNREFUSED 10061 Connection refused.
WSAELOOP 10062 Too many levels of symbolic links.
WSAENAMETOOLONG 10063 File name too long.
WSAEHOSTDOWN 10064 Host is down.
WSAEHOSTUNREACH 10065 No route to host.
WSASYSNOTREADY 10091 Returned by WSAStartup(), indicating that
the network subsystem is unusable.
WSAVERNOTSUPPORTED 10092 Returned by WSAStartup(), indicating that
the Windows Sockets DLL cannot support
this application.
WSANOTINITIALISED 10093 Winsock not initialized. This message is
returned by any function except
WSAStartup(), indicating that a
successful WSAStartup() has not yet been
performed.
WSAEDISCON 10101 Disconnect.
WSAHOST_NOT_FOUND 11001 Host not found. This message indicates
that the key (name, address, and so on)
was not found.
WSATRY_AGAIN 11002 Nonauthoritative host not found. This
error may suggest that the name service
itself is not functioning.
WSANO_RECOVERY 11003 Nonrecoverable error. This error may
suggest that the name service itself is
not functioning.
WSANO_DATA 11004 Valid name, no data record of requested
type. This error indicates that the key
(name, address, and so on) was not found.
NOTE: This table does not include all of the error codes defined in Winsock.h. <HR></BLOCKQUOTE>
Brauchbar? Ich habs nicht gelesen, bevor ich es hier geposted habe
--------------------------------------------------------------------------------
The information in this article applies to:
Microsoft Windows NT Workstation versions 3.5 , 3.51
Microsoft Windows NT Server versions 3.5 , 3.51
Microsoft LAN Manager, version 2.2c
Microsoft TCP/IP-32 for Windows for Workgroups, versions 3.11 , 3.11a , 3.11b
Microsoft Windows 95
Microsoft Network Client for MS-DOS version 3.0
--------------------------------------------------------------------------------
SUMMARY
This article describes the Windows Sockets error codes.
MORE INFORMATION
The following table is a list of possible error codes returned by the WSAGetLastError() call, along with their explanations.
Windows Sockets code Error Description
------------------------------------------------------------------------
WSAEINTR 10004 Interrupted system call.
WSAEBADF 10009 Bad file number.
WSEACCES 10013 Permission denied.
WSAEFAULT 10014 Bad address.
WSAEINVAL 10022 Invalid argument.
WSAEMFILE 10024 Too many open files.
WSAEWOULDBLOCK 10035 Operation would block.
WSAEINPROGRESS 10036 Operation now in progress. This error is
returned if any Windows Sockets API
function is called while a blocking
function is in progress.
WSAEALREADY 10037 Operation already in progress.
WSAENOTSOCK 10038 Socket operation on nonsocket.
WSAEDESTADDRREQ 10039 Destination address required.
WSAEMSGSIZE 10040 Message too long.
WSAEPROTOTYPE 10041 Protocol wrong type for socket.
WSAENOPROTOOPT 10042 Protocol not available.
WSAEPROTONOSUPPORT 10043 Protocol not supported.
WSAESOCKTNOSUPPORT 10044 Socket type not supported.
WSAEOPNOTSUPP 10045 Operation not supported on socket.
WSAEPFNOSUPPORT 10046 Protocol family not supported.
WSAEAFNOSUPPORT 10047 Address family not supported by protocol
family.
WSAEADDRINUSE 10048 Address already in use.
WSAEADDRNOTAVAIL 10049 Cannot assign requested address.
WSAENETDOWN 10050 Network is down. This error may be
reported at any time if the Windows
Sockets implementation detects an
underlying failure.
WSAENETUNREACH 10051 Network is unreachable.
WSAENETRESET 10052 Network dropped connection on reset.
WSAECONNABORTED 10053 Software caused connection abort.
WSAECONNRESET 10054 Connection reset by peer.
WSAENOBUFS 10055 No buffer space available.
WSAEISCONN 10056 Socket is already connected.
WSAENOTCONN 10057 Socket is not connected.
WSAESHUTDOWN 10058 Cannot send after socket shutdown.
WSAETOOMANYREFS 10059 Too many references: cannot splice.
WSAETIMEDOUT 10060 Connection timed out.
WSAECONNREFUSED 10061 Connection refused.
WSAELOOP 10062 Too many levels of symbolic links.
WSAENAMETOOLONG 10063 File name too long.
WSAEHOSTDOWN 10064 Host is down.
WSAEHOSTUNREACH 10065 No route to host.
WSASYSNOTREADY 10091 Returned by WSAStartup(), indicating that
the network subsystem is unusable.
WSAVERNOTSUPPORTED 10092 Returned by WSAStartup(), indicating that
the Windows Sockets DLL cannot support
this application.
WSANOTINITIALISED 10093 Winsock not initialized. This message is
returned by any function except
WSAStartup(), indicating that a
successful WSAStartup() has not yet been
performed.
WSAEDISCON 10101 Disconnect.
WSAHOST_NOT_FOUND 11001 Host not found. This message indicates
that the key (name, address, and so on)
was not found.
WSATRY_AGAIN 11002 Nonauthoritative host not found. This
error may suggest that the name service
itself is not functioning.
WSANO_RECOVERY 11003 Nonrecoverable error. This error may
suggest that the name service itself is
not functioning.
WSANO_DATA 11004 Valid name, no data record of requested
type. This error indicates that the key
(name, address, and so on) was not found.
NOTE: This table does not include all of the error codes defined in Winsock.h. <HR></BLOCKQUOTE>
Brauchbar? Ich habs nicht gelesen, bevor ich es hier geposted habe
was hab ich mir zerschossen, wenn....
Ei, sowas kann man ja immer mal brauchen, wo haste des her Aix? Is da mehr von sowas, wo das her kommt?
was hab ich mir zerschossen, wenn....
@mrrxRZ
in der retrozone isses andersrum
url=URL <name>
in der retrozone isses andersrum
url=URL <name>
was hab ich mir zerschossen, wenn....
Ja ja sowas ist mir letztens passiert.
Er fährt hoch Fehlermeldung:
____________________________________
Keine intialisierung des Gerätes VKD
Weiter mit beliebieger Taste...
Starten Sie Windows neu.
____________________________________
Dann musste ich die Festplatte ausbauen.
Er fährt hoch Fehlermeldung:
____________________________________
Keine intialisierung des Gerätes VKD
Weiter mit beliebieger Taste...
Starten Sie Windows neu.
____________________________________
Dann musste ich die Festplatte ausbauen.
was hab ich mir zerschossen, wenn....
Ich schätze mal irgendwas Netzwerk/Dfu mäßiges... alle Treiber neu drüberbügeln...hilft meistens!
was hab ich mir zerschossen, wenn....
Kann das ma wer verschieben? 
was hab ich mir zerschossen, wenn....
Klar kann das einer verschieben!