CS / connection / XP help me thinks ????
09 January 2002, 12:57 AM
#1
Scooby Regular
Thread Starter
Join Date: Jun 2001
Location: From 208BHP to 311BHP and 12.8sec 1/4mile
Posts: 2,509
Likes: 0
Received 1 Like
on
1 Post
Hi CSers
Been having problems with my connection on CS.
I keep getting thrown out of CS/DOD etc with the following error. Only experienced on Half Life programs.
NET_sendpacket ERROR:WSAEINTR
Now this never happend until I upgraded to XP which was the same time CS 1.3 was out (pre release version of XP
). I have had all the usual Fush entity packets, connection problem, lag etc but this just throws me outof HL all together. I can then come back in to CS again usually with no problem. Connection to CS server sometimes takes a while.
Is this a :-
modem problem (incorrect driver)
CS problem that requires a special never heard of command
XP problem
ISP problem (ntl on 56K modem)
Anybody with any suggestions
Cheers
Neal
Been having problems with my connection on CS.
I keep getting thrown out of CS/DOD etc with the following error. Only experienced on Half Life programs.
NET_sendpacket ERROR:WSAEINTR
Now this never happend until I upgraded to XP which was the same time CS 1.3 was out (pre release version of XP
). I have had all the usual Fush entity packets, connection problem, lag etc but this just throws me outof HL all together. I can then come back in to CS again usually with no problem. Connection to CS server sometimes takes a while.Is this a :-
modem problem (incorrect driver)
CS problem that requires a special never heard of command
XP problem
ISP problem (ntl on 56K modem)
Anybody with any suggestions
Cheers
Neal
09 January 2002, 10:07 AM
#3
Scooby Regular
Join Date: Apr 2001
Location: Hants
Posts: 1,103
Likes: 0
Received 0 Likes
on
0 Posts
NET_sendpacket ERROR:WSAEINTR
WSAEINTR (10004)
Interrupted function call.
A blocking operation was interrupted by a call to WSACancelBlockingCall.
WSACancelBlockingCall
The WSACancelBlockingCall function has been removed in compliance with the Windows Sockets 2 specification, revision 2.2.0.
The function is not exported directly by Ws2_32.dll and Windows Sockets 2 applications should not use this function. Windows Sockets 1.1 applications that call this function are still supported through the Winsock.dll and Wsock32.dll.
Blocking hooks are generally used to keep a single-threaded GUI application responsive during calls to blocking functions. Instead of using blocking hooks, an applications should use a separate thread (separate from the main GUI thread) for network activity.
WSAEINTR (10004)
Interrupted function call.
A blocking operation was interrupted by a call to WSACancelBlockingCall.
WSACancelBlockingCall
The WSACancelBlockingCall function has been removed in compliance with the Windows Sockets 2 specification, revision 2.2.0.
The function is not exported directly by Ws2_32.dll and Windows Sockets 2 applications should not use this function. Windows Sockets 1.1 applications that call this function are still supported through the Winsock.dll and Wsock32.dll.
Blocking hooks are generally used to keep a single-threaded GUI application responsive during calls to blocking functions. Instead of using blocking hooks, an applications should use a separate thread (separate from the main GUI thread) for network activity.
09 January 2002, 10:21 AM
#4
Scooby Regular
Join Date: Nov 2001
Posts: 2,576
Likes: 0
Received 0 Likes
on
0 Posts
I thought that error could mean anything under cs.
I've seen under Win2k the error "NET_sendpacket ERROR:No Error" which doesn't help.
H
-also gets weird errors, but on Uk2 servers only. Why they hell do they portscan me
I've seen under Win2k the error "NET_sendpacket ERROR:No Error" which doesn't help.
H
-also gets weird errors, but on Uk2 servers only. Why they hell do they portscan me
Trending Topics
01 September 2002, 07:10 PM
#8
Scooby Regular
Join Date: May 2001
Posts: 730
Likes: 0
Received 0 Likes
on
0 Posts
Neal,
just got this from the counter-strike forum
tried a lot of different solution to stop lag in CS with win XP. When I touched a key my ping was huge.
TO CORECT THIS CONTROL LAG!:
disable sound hardware acceleration - controlpannel>sound>advanced>slidebar to off!
if it doesn't try update drivers from video, sound, modem and XP. or search for other soutions in forum
Tim.
HTH
rr[/b]
[Edited by roadrunner - 1/9/2002 7:11:18 PM]
just got this from the counter-strike forum
tried a lot of different solution to stop lag in CS with win XP. When I touched a key my ping was huge.
TO CORECT THIS CONTROL LAG!:
disable sound hardware acceleration - controlpannel>sound>advanced>slidebar to off!
if it doesn't try update drivers from video, sound, modem and XP. or search for other soutions in forum
Tim.
HTH
rr[/b]
[Edited by roadrunner - 1/9/2002 7:11:18 PM]
Thread
Thread Starter
Forum
Replies
Last Post
Mattybr5@MB Developments
Full Cars Breaking For Spares
12
18 November 2015 07:03 AM