First: the stupid errors (Winsock's fault)

It is true that the winsock functions do not set errno, its actually pretty simple to grab the error code

errno = WSAGetLastError();

this should suffice. Unfortunately, even if the error is set properly, strerror() will NOT give out the result. It'll just go back to the "Unknown error" wiich I must say is MUCH MUCH better than the stupid errors it has been giving me, like :"Bad file descriptor" or "No such file or directory".

But there are more problems with wget, and they're not recent. I've been tryin' with older versions of wget (1.8.2) and am having these very same problems on w2k machines. Whenever a transfer fails it will start giving 10093 Errors and is never able to connect again.

according to MSDN, this is what it means:

Successful WSAStartup not yet performed.

Either the application has not called WSAStartup or WSAStartup failed. The application may be accessing a socket that the current active task does not own (that is, trying to share a socket between tasks), or WSACleanup has been called too many times.

I haven't checked the error code that is given when the connection dies( stupid me, forget to make wget spit the error code >.< with a bit of luck by tomorrow I'll know it).

I'm gonna go over the code later on, and see if I can track down the problem. I'll post something more if there's anything usefull to report.

Thanks for everything :)

Tired of spam? Get advanced junk mail protection with MSN 8.

Reply via email to