The Furious Angels

FA Discussion => Off Topic => Topic started by: Eroz on August 09, 2005, 05:50:54 pm

Title: Error Code:10054
Post by: Eroz on August 09, 2005, 05:50:54 pm: MY bot keeps crashing because of one little problem, almost on matter what setup I have. The Error I am getting is Error Code 10054. When I input this into the Trillian support dbase it gives me a page saying this is a windows Winsock error, the Windows dbase says this.
Quote

WSAECONNRESET
10054

Connection reset by peer.
An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, the host or remote network interface is disabled, or the remote host uses a hard close (see setsockopt for more information on the SO_LINGER option on the remote socket). This error may also result if a connection was broken due to keep-alive activity detecting a failure while one or more operations are in progress. Operations that were in progress fail with WSAENETRESET. Subsequent operations fail with WSAECONNRESET.

Can I even fix this?
Title: Error Code:10054
Post by: Anonymous on August 09, 2005, 06:03:51 pm: Refresh/reinstall winsock?
Title: Error Code:10054
Post by: Styan on August 09, 2005, 06:09:44 pm: You could try what sared says... or it could also be an auto-protect feature on AIM shutting down the connection to the bot...
Title: Error Code:10054
Post by: Eroz on August 09, 2005, 06:33:24 pm: Yea, if anyone is running Trillian if you can get the "Show Status Window" and see if you get the
"General error when attempting service redirection on service 6." with your mxo account.
Title: Error Code:10054
Post by: Eroz on August 09, 2005, 08:19:00 pm: DAMN YOU WINSOCK
Title: Error Code:10054
Post by: ArchNemesis on August 09, 2005, 08:21:46 pm: I wub j00 winsock! :P
Title: Error Code:10054
Post by: Anonymous on August 09, 2005, 08:22:23 pm: This is one of those 'for the hell of it' ideas. Try it.

http://download.microsoft.com/download/0/e/0/0e05231b-6bd1-4def-a216-c656fbd22b4e/W95ws2setup.exe
Title: Error Code:10054
Post by: Eroz on August 09, 2005, 08:23:15 pm: It's not like it really matter, cause ket bot works just as good and appeartly doesn't have the same problems I have.
Title: Error Code:10054
Post by: Styan on August 09, 2005, 09:02:24 pm: Quote from: "Sared"
This is one of those 'for the hell of it' ideas. Try it.

http://download.microsoft.com/download/0/e/0/0e05231b-6bd1-4def-a216-c656fbd22b4e/W95ws2setup.exe

LOL Sared, in the Electrical Engineering world (and yes its probably a canadian thing whitemyst...) we say

"Just for shits and giggles"... :p
Title: Error Code:10054
Post by: Avzeke (Khr0n1k) on August 09, 2005, 09:38:16 pm: hah i hear people say that, that arent in electrical enginering world.
Title: Error Code:10054
Post by: Eroz on August 09, 2005, 11:21:17 pm: This version of Winsock 2 is meant for older Windows platforms. All of its features are already part of your current Windows operating system, so there is no need to install it.
Title: Error Code:10054
Post by: Eroz on August 09, 2005, 11:23:59 pm: Could someone explain to me what the hell is crashing, and is it possible that it could be my router and not my computer?
Title: Error Code:10054
Post by: Eroz on August 09, 2005, 11:42:09 pm: w00t, I just found out it is computer/router/ISP that is causing the error so my bot works.
Title: Error Code:10054
Post by: Ketamininja on August 10, 2005, 03:36:34 am: :p
Title: Error Code:10054
Post by: Styan on August 10, 2005, 11:04:22 am: Quote from: "Khr0n1k"
hah I hear people say that, that arent in electrical enginering world.

Yea its quite widely used...

We say it a lot when were in our lab classes... like ... "Just for shits and giggles lets wire this thing like this... and see what happens... " *wire it up* "ok turn it on..."

**$$## KABOOM!! ##$$**

Me with burnt hand from sparking: "well we know it doesn't work like that.."

Glad you got it sorted out eroz :)
Title: Error Code:10054
Post by: Eroz on August 10, 2005, 12:03:33 pm: I didn't sort it out, but it could possibley be run on another computer fine. I'm playing with Windows today to see if I get around it.