nightshark wrote:he's talking about lag. the giveaway is that it happens when he turns around.
do this: open command prompt from your start menu (in accessories) and type
ping uosecondage.com -t
let it run for a while, then press ctrl-c and copy and paste the result here
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Mike>ping uosecondage.com -t
Pinging uosecondage.com [64.34.183.167] with 32 bytes of data:
Reply from 64.34.183.167: bytes=32 time=91ms TTL=114
Reply from 64.34.183.167: bytes=32 time=100ms TTL=114
Reply from 64.34.183.167: bytes=32 time=96ms TTL=114
Reply from 64.34.183.167: bytes=32 time=1061ms TTL=114
Reply from 64.34.183.167: bytes=32 time=91ms TTL=114
Reply from 64.34.183.167: bytes=32 time=92ms TTL=114
Reply from 64.34.183.167: bytes=32 time=90ms TTL=114
Reply from 64.34.183.167: bytes=32 time=91ms TTL=114
Reply from 64.34.183.167: bytes=32 time=91ms TTL=114
Reply from 64.34.183.167: bytes=32 time=91ms TTL=114
Reply from 64.34.183.167: bytes=32 time=101ms TTL=114
Reply from 64.34.183.167: bytes=32 time=1023ms TTL=114
Reply from 64.34.183.167: bytes=32 time=91ms TTL=114
Reply from 64.34.183.167: bytes=32 time=90ms TTL=114
Reply from 64.34.183.167: bytes=32 time=90ms TTL=114
Reply from 64.34.183.167: bytes=32 time=94ms TTL=114
Reply from 64.34.183.167: bytes=32 time=96ms TTL=114
Reply from 64.34.183.167: bytes=32 time=91ms TTL=114
Reply from 64.34.183.167: bytes=32 time=89ms TTL=114
Reply from 64.34.183.167: bytes=32 time=1022ms TTL=114
Reply from 64.34.183.167: bytes=32 time=90ms TTL=114
Reply from 64.34.183.167: bytes=32 time=89ms TTL=114
Reply from 64.34.183.167: bytes=32 time=92ms TTL=114
Reply from 64.34.183.167: bytes=32 time=90ms TTL=114
Reply from 64.34.183.167: bytes=32 time=90ms TTL=114
Reply from 64.34.183.167: bytes=32 time=92ms TTL=114
Reply from 64.34.183.167: bytes=32 time=90ms TTL=114
Reply from 64.34.183.167: bytes=32 time=1028ms TTL=114
Reply from 64.34.183.167: bytes=32 time=101ms TTL=114
Reply from 64.34.183.167: bytes=32 time=89ms TTL=114
Reply from 64.34.183.167: bytes=32 time=91ms TTL=114
Reply from 64.34.183.167: bytes=32 time=90ms TTL=114
Reply from 64.34.183.167: bytes=32 time=89ms TTL=114
Reply from 64.34.183.167: bytes=32 time=94ms TTL=114
Reply from 64.34.183.167: bytes=32 time=93ms TTL=114
Reply from 64.34.183.167: bytes=32 time=1043ms TTL=114
Reply from 64.34.183.167: bytes=32 time=91ms TTL=114
Reply from 64.34.183.167: bytes=32 time=101ms TTL=114
Reply from 64.34.183.167: bytes=32 time=94ms TTL=114
Reply from 64.34.183.167: bytes=32 time=104ms TTL=114
Reply from 64.34.183.167: bytes=32 time=94ms TTL=114
Reply from 64.34.183.167: bytes=32 time=89ms TTL=114
Reply from 64.34.183.167: bytes=32 time=91ms TTL=114
Reply from 64.34.183.167: bytes=32 time=1005ms TTL=114
Reply from 64.34.183.167: bytes=32 time=89ms TTL=114
Packets: Sent = 45, Received = 45, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 89ms, Maximum = 1061ms, Average = 217ms
If over 100 is bad we can see where the problem is, constant 1000 ping time every 8 packets. Im fairly illiterate about the internet so is this something on my end, something between me and the server or?
While I dont know much about the internet I do know a bit about how win xp works. I defrag my drive every night, there could be a video problem slowing me down a bit as well, my card is getting old and Im sure its not working as good as it did when new.
Im also having a problem that is talked about in a different post where the client keeps on disconnecting on me. Im fairly sure this is cause by the fact that Im on wireless, behind a firewall I have no control over. This problem has been rectified and Im just waiting for my new internet to be installed.