rec.autos.simulators

> >Creepily enough...that's the same error code number I used to get while
> >trying to connect Trillian to AOL Instant Messenger..

> >Regardless...hmm...do they have any other programs running aside from all
of
> >the transparent services and whatnot? (Like AIM, ZoneAlarm, etc).
ZoneAlarm
> >always gave me problems when trying to race online.  Just had to exit
every
> >time I raced.

> >Milhouse

> That is odd, as this appears to be a GPL generated error message.
> Don't think that they're usng ZoneAlarm and neither is an AOL user.
> The XP user is probably running XP's built in firewall by default.
> Last Sunday's race went fine, so maybe XP's DUN just can't handle poor
> lats or lost packets as well as Win98?

> >Hi gang.  We have a couple people in our GPL league getting disco'd
> >from on-line sessions on a regular basis.  The error message
> >"10054:ERROR DETECTED ON NETWORK DEVICE" appears in the *chat* window,
> >lats climb up and then the driver gets disco'd (GPL error message, not
> >a Windows system message).  This is happening to one driver using
> >Windows XP and to another uding Win2K, so it's probably related since
> >they share some core code.  Is there some background task in XP that
> >would cause this message?  Unfortunately the XP user is a novice and
> >can't supply a lot of details, and XP by default has a lot of junk
> >running in the background.

> From the MSDN Library:

> WSAECONNRESET
> (10054)
> Connection reset by peer.
> A 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, or the remote host used 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 keepalive 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.

> Now, don't ask me what it means....

> Remco

> i belive all it means is GPL lost connection with the host.
> used to happen to me in the olden days when i was on 56k.
>i think the drivers in question need to make sure their connection settings
>are not setup to "disconect if idle for 20 mins" as if i remember correctly
>windoze doesent concider online racing as an active thing and asumes your
>connection is idle.

>neil

>>remco

>> i belive all it means is GPL lost connection with the host.
>> used to happen to me in the olden days when i was on 56k.
>>i think the drivers in question need to make sure their connection settings
>>are not setup to "disconect if idle for 20 mins" as if i remember correctly
>>windoze doesent concider online racing as an active thing and asumes your
>>connection is idle.

>>neil

>That's probably the solution, friend of mine had the same error
>message and fixed it by turning off that auto-disconnect option.

>>The reason probably being the GPL only uses UDP (just a hunch) and
>>only TCP/IP packets are seen as activity.

>>Or I may be talking out my neck here. ;-)

>Why do you allways remind me of STNG's Data :)

>>>Why do you allways remind me of STNG's Data :)

>>What's that??

>Star Trek Next Generation.. come on Ruud, every male who owns a
>computer watches Star Trek!

>>Yes, I know him.
>>Sorry 'bout the techno-talk then. :) UDP is just a different internet
>>protocol which is used by a lot of games to do their communication.
>>TCP/IP is reliable (resends lost packets) and used for reliable
>>communications, but often games leave this out as you'll need reliable
>>UDP packets anyway.
>>The 'idle detection' scheme may detect only TCP/IP packets, and thus
>>think you're not using the network. A bit like frantically moving your
>>joystick in a racing game may still make Windows think it's idle and
>>put up a screensaver just when you're 100 meters away from a new PB.
>>;-)

>Hey, I even understood that :)

>Kirk out.