Slow Launcher

Havocide

Ive had similar issues before and found it was a memory problem.

**Roukan**

Pinging auth.station.sony.com [199.108.0.139] with 32 bytes of data:

Reply from 199.108.0.139: bytes=32 time=19ms TTL=121

Reply from 199.108.0.139: bytes=32 time=18ms TTL=121

Reply from 199.108.0.139: bytes=32 time=19ms TTL=121

Reply from 199.108.0.139: bytes=32 time=18ms TTL=121

Reply from 199.108.0.139: bytes=32 time=22ms TTL=121

Reply from 199.108.0.139: bytes=32 time=19ms TTL=121

Reply from 199.108.0.139: bytes=32 time=17ms TTL=121

Reply from 199.108.0.139: bytes=32 time=20ms TTL=121

Reply from 199.108.0.139: bytes=32 time=22ms TTL=121

Reply from 199.108.0.139: bytes=32 time=17ms TTL=121

Reply from 199.108.0.139: bytes=32 time=17ms TTL=121

Reply from 199.108.0.139: bytes=32 time=18ms TTL=121

Reply from 199.108.0.139: bytes=32 time=24ms TTL=121

Reply from 199.108.0.139: bytes=32 time=24ms TTL=121

Reply from 199.108.0.139: bytes=32 time=22ms TTL=121

Reply from 199.108.0.139: bytes=32 time=18ms TTL=121

Reply from 199.108.0.139: bytes=32 time=18ms TTL=121

Reply from 199.108.0.139: bytes=32 time=19ms TTL=121

Reply from 199.108.0.139: bytes=32 time=18ms TTL=121

Reply from 199.108.0.139: bytes=32 time=20ms TTL=121

Ping statistics for 199.108.0.139:

    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 17ms, Maximum = 24ms, Average = 19ms

Pinging recursion.thematrixonline.com [199.108.0.72] with 32 bytes of data:

Reply from 199.108.0.72: bytes=32 time=18ms TTL=120

Reply from 199.108.0.72: bytes=32 time=18ms TTL=120

Reply from 199.108.0.72: bytes=32 time=17ms TTL=120

Reply from 199.108.0.72: bytes=32 time=18ms TTL=120

Reply from 199.108.0.72: bytes=32 time=19ms TTL=120

Reply from 199.108.0.72: bytes=32 time=17ms TTL=120

Reply from 199.108.0.72: bytes=32 time=18ms TTL=120

Reply from 199.108.0.72: bytes=32 time=18ms TTL=120

Reply from 199.108.0.72: bytes=32 time=20ms TTL=120

Reply from 199.108.0.72: bytes=32 time=20ms TTL=120

Reply from 199.108.0.72: bytes=32 time=21ms TTL=120

Reply from 199.108.0.72: bytes=32 time=20ms TTL=120

Reply from 199.108.0.72: bytes=32 time=21ms TTL=120

Reply from 199.108.0.72: bytes=32 time=18ms TTL=120

Reply from 199.108.0.72: bytes=32 time=19ms TTL=120

Reply from 199.108.0.72: bytes=32 time=18ms TTL=120

Reply from 199.108.0.72: bytes=32 time=19ms TTL=120

Reply from 199.108.0.72: bytes=32 time=23ms TTL=120

Reply from 199.108.0.72: bytes=32 time=20ms TTL=120

Reply from 199.108.0.72: bytes=32 time=20ms TTL=120

Ping statistics for 199.108.0.72:

    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 17ms, Maximum = 23ms, Average = 19ms

Pinging syntax.thematrixonline.com [199.108.0.76] with 32 bytes of data:

Reply from 199.108.0.76: bytes=32 time=20ms TTL=120

Reply from 199.108.0.76: bytes=32 time=20ms TTL=120

Reply from 199.108.0.76: bytes=32 time=24ms TTL=120

Reply from 199.108.0.76: bytes=32 time=20ms TTL=120

Reply from 199.108.0.76: bytes=32 time=17ms TTL=120

Reply from 199.108.0.76: bytes=32 time=17ms TTL=120

Reply from 199.108.0.76: bytes=32 time=19ms TTL=120

Reply from 199.108.0.76: bytes=32 time=19ms TTL=120

Reply from 199.108.0.76: bytes=32 time=18ms TTL=120

Reply from 199.108.0.76: bytes=32 time=20ms TTL=120

Reply from 199.108.0.76: bytes=32 time=18ms TTL=120

Reply from 199.108.0.76: bytes=32 time=18ms TTL=120

Reply from 199.108.0.76: bytes=32 time=19ms TTL=120

Reply from 199.108.0.76: bytes=32 time=16ms TTL=120

Reply from 199.108.0.76: bytes=32 time=17ms TTL=120

Reply from 199.108.0.76: bytes=32 time=18ms TTL=120

Reply from 199.108.0.76: bytes=32 time=19ms TTL=120

Reply from 199.108.0.76: bytes=32 time=21ms TTL=120

Reply from 199.108.0.76: bytes=32 time=35ms TTL=120

Reply from 199.108.0.76: bytes=32 time=20ms TTL=120

Ping statistics for 199.108.0.76:

    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 16ms, Maximum = 35ms, Average = 19ms

Pinging vector.thematrixonline.com [199.108.0.80] with 32 bytes of data:

Reply from 199.108.0.80: bytes=32 time=23ms TTL=120

Reply from 199.108.0.80: bytes=32 time=18ms TTL=120

Reply from 199.108.0.80: bytes=32 time=17ms TTL=120

Reply from 199.108.0.80: bytes=32 time=23ms TTL=120

Reply from 199.108.0.80: bytes=32 time=18ms TTL=120

Reply from 199.108.0.80: bytes=32 time=17ms TTL=120

Reply from 199.108.0.80: bytes=32 time=18ms TTL=120

Reply from 199.108.0.80: bytes=32 time=19ms TTL=120

Reply from 199.108.0.80: bytes=32 time=20ms TTL=120

Reply from 199.108.0.80: bytes=32 time=30ms TTL=120

Reply from 199.108.0.80: bytes=32 time=21ms TTL=120

Reply from 199.108.0.80: bytes=32 time=19ms TTL=120

Reply from 199.108.0.80: bytes=32 time=17ms TTL=120

Reply from 199.108.0.80: bytes=32 time=20ms TTL=120

Reply from 199.108.0.80: bytes=32 time=20ms TTL=120

Reply from 199.108.0.80: bytes=32 time=19ms TTL=120

Reply from 199.108.0.80: bytes=32 time=21ms TTL=120

Reply from 199.108.0.80: bytes=32 time=20ms TTL=120

Reply from 199.108.0.80: bytes=32 time=16ms TTL=120

Reply from 199.108.0.80: bytes=32 time=17ms TTL=120

Ping statistics for 199.108.0.80:

    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 16ms, Maximum = 30ms, Average = 19ms

**Roukan**

So I found the problem after conversing with Bayamos

# Turn off Crash Reporter
EnableCrashDumpUploads = 0

**phi** · 03/10/2008 05:12:49

*adds to solutions notes*
So your launcher was trying to upload a crash dump? Did you crash when the servers went down?

Also check for the following files in your MxO install directory and delete them.:

any files ending in .dmp ( eg: MatrixOnline_7.5591_crash_0.dmp )
a matching text file ( eg: MatrixOnline_7.5591_crash_0.dmp.txt )
a crash log ( eg: ClientErrors_0.txt )
the crash reporter log file ( eg: crashreporter.log )

You should be able to turn the crash reporter back on safely then.

**Roukan**

phi wrote:

*adds to solutions notes*
So your launcher was trying to upload a crash dump? Did you crash when the servers went down?

Also check for the following files in your MxO install directory and delete them.:
any files ending in .dmp ( eg: MatrixOnline_7.5591_crash_0.dmp )
a matching text file ( eg: MatrixOnline_7.5591_crash_0.dmp.txt )
a crash log ( eg: ClientErrors_0.txt )
the crash reporter log file ( eg: crashreporter.log )

You should be able to turn the crash reporter back on safely then.

I turned the option on after doing all that. I crashed and the crash report kept coming up everytime I launched the game. It was not that big, but annoying. I put on that and it worked perfectly. No crash reporter, and the launcher ran smooth. Then the SOE-wide shutdown happened and my launcher became crap.