Trouble on my mind
Moderator: Forum Moderators
-
- Private
- Posts: 50
- Joined: Sat Nov 04, 2006 3:30 am
Re: Trouble on my mind
I guess i shall do this when (hopefully) the invasion server runs.corvey wrote:|bah|Ariel wrote: This day i played a map (iron something) twice. The first 6 waves worked rather well, but wave 7 to 20 i respawned without any weapon.
This is most likely due to PACKET LOSS from your ISP. You can do a test by doing a ping to Joey's server to find out how much packet loss your losing. You can do a continuous ping or just counted number of 100 to calculate your packet loss.
goto the command prompt and type:
ping 204.11.33.157 -n 100
Let this run for 100 times. Then read the packet loss percentage.
To trouble shoot continuously simply type this at the command prompt:
ping 204.11.33.157 -t
If you see any "Request time outs" there is failure somewhere in your ISP. Make sure you can do this ping procedure with your LAN cable modem which is usually 192.168.100.1 to eliminate internal errors.
You can always determine if your RAM amount is enough if your hard light doesn't hit after it's been cached when playing the game. If you have continuous hard hits (look for the hard drive light) while playing the game, then you know you need more ram.
Or shall i do it now ?
Nobody is stopping you from doing it now. The time to really test it is when your having issues with the server that nobody else is. Like the missing weapons, no visible monsters, no visible power ups, etc..
Your ISP may be temporarily congested at certain times, permanently screwed up hardware, WHO KNOWS. If you have packet loss all night long then there is a problem that needs to be fix, you must call and complain.
You can test a packet loss log for all night if you want to, like this:
ping xxx.xxx.xxx.xxx -t > packetloss.txt
let that command window run all night, CTRL-C when you wake up.. use a text editor to open the file packetloss.txt, and search for "request time out". If you see ANY, then there is a possible issue.
You can also do a tracert command to see where the possible cause of failure is in a certain hop.
Good Luck
-corvey
Your ISP may be temporarily congested at certain times, permanently screwed up hardware, WHO KNOWS. If you have packet loss all night long then there is a problem that needs to be fix, you must call and complain.
You can test a packet loss log for all night if you want to, like this:
ping xxx.xxx.xxx.xxx -t > packetloss.txt
let that command window run all night, CTRL-C when you wake up.. use a text editor to open the file packetloss.txt, and search for "request time out". If you see ANY, then there is a possible issue.
You can also do a tracert command to see where the possible cause of failure is in a certain hop.
Good Luck
-corvey
- TurkeyFromHell
- Staff Sergeant
- Posts: 640
- Joined: Tue Jan 23, 2007 12:22 pm
- Contact:
ort i want ur job..Ortega wrote:The server is back up today. I do believe.
I'm so pissed My work tried to block this with their Internet Fag WAD who thinks he knows crap....Bypass his attracted to the same sex filters...thats two on my computer and Im still posting...LOL. They seem to forget I set all the computers up...MORONS
....... ort...


- TurkeyFromHell
- Staff Sergeant
- Posts: 640
- Joined: Tue Jan 23, 2007 12:22 pm
- Contact:
if whoever ur pingin is as paranoid as every1 else on this planet theyl prolly and call ur isp to cut ur service off and file criminal charges to have u sent to prison to get ass raped for a few years for "casing theyr server"... on one port... over and over and over... roflmfaocorvey wrote:Nobody is stopping you from doing it now. The time to really test it is when your having issues with the server that nobody else is. Like the missing weapons, no visible monsters, no visible power ups, etc..
Your ISP may be temporarily congested at certain times, permanently screwed up hardware, WHO KNOWS. If you have packet loss all night long then there is a problem that needs to be fix, you must call and complain.
You can test a packet loss log for all night if you want to, like this:
ping xxx.xxx.xxx.xxx -t > packetloss.txt
let that command window run all night, CTRL-C when you wake up.. use a text editor to open the file packetloss.txt, and search for "request time out". If you see ANY, then there is a possible issue.
You can also do a tracert command to see where the possible cause of failure is in a certain hop.
Good Luck
-corvey

Re: Trouble on my mind
or.. you could simply push F6 during play, and watch your packetloss readout. it'll be in the top-left corner of the screen.|bah|Ariel wrote:I guess i shall do this when (hopefully) the invasion server runs. Or shall i do it now ?
this way you don't have to worry about running a command. :hwsb:
eh? ortega, i think you have a sexy voice and all, but sometimes you make no sense. :D the only reason 32-bit operating systems don't see the entire 4 gigs is because of the physical limitation of the address space. however, two gigs is fully utilized. :hwsb2: :drinkers:Ortega wrote:Thats right...you buy 4 but the usable is 3.2 then at 2 you get 1.6
"Operating systems based on Microsoft Windows NT technologies have always provided applications with a flat 32-bit virtual address space that describes 4 gigabytes (GB) of virtual memory. The address space is usually split so that 2 GB of address space is directly accessible to the application and the other 2 GB is only accessible to the Windows executive software.
Windows NT 4.0 Memory Support. With Microsoft Windows NT 4.0 Workstation and Server operating systems, the maximum amount of physical memory supported is 4 GB. The maximum amount of virtual memory is 2 GB."
I'll just let you read it from the horse's mouth..
http://www.microsoft.com/whdc/system/pl ... AEmem.mspx
2+2=4 GIG
The OS will USE ALL 4 GIG for OS and application use.
Somebody has 'tarded math skillz.. I'm not even going to bother saying who.
Trying to help somebody else out in this thread and somebody has to come in here and censored WITH ME ON A DIFFERENT SUBJECT.
-corvey
Windows NT 4.0 Memory Support. With Microsoft Windows NT 4.0 Workstation and Server operating systems, the maximum amount of physical memory supported is 4 GB. The maximum amount of virtual memory is 2 GB."
I'll just let you read it from the horse's mouth..
http://www.microsoft.com/whdc/system/pl ... AEmem.mspx
2+2=4 GIG
The OS will USE ALL 4 GIG for OS and application use.
Somebody has 'tarded math skillz.. I'm not even going to bother saying who.
Trying to help somebody else out in this thread and somebody has to come in here and censored WITH ME ON A DIFFERENT SUBJECT.
-corvey