1  |   Order by index

Nov 7, 2001, 4:04am

[View Quote] > I have been having this same problem for quite some time.
>
> It used to happen almost constantly.. then I reformatted my hard drive,
> re-installed Windows 98, installed the lastest (last)
> driver set for my video card, and then only upgraded to DirectX 7.0 as I
> think that 8.0a did not work with my video card
> which is now defunct.
>
> Since doing the above, I now crash only a few times.. and I too can avoid
> completely crashing sometimes.. by using Task Manager
> and ending aworld.exe... BUT NOT ALWAYS (Most of the time it's a complete
> FREEZE)
>
> AW Browser 3.2 Build 397
> Gateway Celeron 333
> 192mb RAM
> VooDoo3 3000 PCI (16MB) (Using Last Driver Version Released)
> Windows 98 (Not sure if it's 2nd Edition)
> 3.45gb left on AW's hard drive
> DirectX 7.0

> MSN 56k Internet Access
> *wonder if this might be the problem... as they haven't been really
> reliable in other areas*

It's a could be,
I found 3.2 to be very stable for about 3 weeks, no crashes
what so ever, then it suddenly started crashing left right and center.

Additionally I noticed the connection in the evening had started to become
rather erratic and I kept losing the connection to AW (the browser would
always report "waiting for server" every few minutes). What I did notice
was that the crashing seem to occur once the AW browser had just re
establish the connection to AW. Also i noticed that the crashes would always
occur around peak time but not off peak or early morning
I did a trace route to aw2.mpl.net in a DOS window and found there was
massive packet loss and congestion during the evening however not to such a
severe extent in the morning.

This pain continued for about one to two weeks until I decided to change
ISP's.
When I finally did get around to changing to another ISP the constant
crashing seem to have disappeared along with the severe packet loss.

To perform a trace route, open a MSdos window and type:
tracert aw2.mpl.net

1  |   Order by index