Author Topic: host connection lost and AH.exe closing down (Read 325 times)

cpxxx · « **on:** January 12, 2008, 12:46:20 PM »

I am thoroughly frustrated at this pont. I just spent the better part of an hour trying to get in any online arena. The same last night and the night before. This has being ongoing for the last few months. Sometimes I get in mostly I don't. Once in the link is invariably stable and I have no problems. IF I get in.

I went through Skuzzies advice and switched off everything possible. Windows updates, Anti virus etc, to no avail.

I always get one of two situations. When preloading tex cache, at or around YAKWNG. I get host connection lost. The tex continues to load and eventually AH closes. Alternatively it loads to the end, then the screen goes black, then white. Finally I get the dreaded message that AH failed to execute and would I like to send an message to Microsoft, as if they cared.

I can access the offline arena, so I must surmise it is a connection issue.
I'm no computer expert so am baffled. Can anyone help?

At thie rate there is little point in me continuing to subscribe to AH unless this is fixed.

The Fugitive · « **Reply #1 on:** January 12, 2008, 12:51:34 PM »

Check the top "sticky" for the technical support thread for connection tips.

Download pingplotter, after installing it, type in the address in the tips thread, and run the ping for about 15 minutes. Take a screen shot and post the picture here.

What your looking for is no "red" in the plots. Long delays will be red as well as lost packets. This will show us what kind of connection you have. Maybe we can narrow down the trouble after that.

Skuzzy · « **Reply #2 on:** January 12, 2008, 01:55:12 PM »

I am betting his preload is taking too long causing the connection to timeout.

Easy way to check is to uncheck the preload options and see if it works.

If it does, you have two choices.
1) Leave them unchecked.
2) Reduce the "Maximum Texture Size".

cpxxx · « **Reply #3 on:** January 12, 2008, 06:32:07 PM »

Thanks Skuzzy that worked. I unchecked the preload. Simple as that. Clearly it was timing out. I wouldn't mind I had read that bit in the help guide but it didn't dawn on me that I only have 1 meg of ram not the 1.5 suggested. Phew! Think I'll add some ram now. I had no problems previously though. I wonder why it changed.

On a positive note. I have cleaned out a lot surplus rubbish from my system.

Thanks again.

Skuzzy · « **Reply #4 on:** January 12, 2008, 08:41:40 PM »

I would check the background processes on the computer to see if something is eating away at the CPU.