2.2 broke Allegiance exited with code: 128

[RadarRider]

The update to 2.2 went into a continous loop. Went into help -> update / repair critical files.

This stopped the looping of the update. THEN...ASGS 2.2 can't start Alleg.


Here's the crash file (one of hundreds) clip

2/18/2009 11:25:30 PM: Logged In
2/18/2009 11:25:31 PM: Launching Allegiance
2/18/2009 11:26:01 PM: Unable to launch Allegiance.
2/18/2009 11:26:01 PM: Allegiance did not launch in the time allotted.
2/18/2009 11:26:01 PM: Beginning Logout
2/18/2009 11:26:01 PM: Closing processes
2/18/2009 11:26:01 PM: Sending Logout Request
2/18/2009 11:26:02 PM: Logged Out
2/18/2009 11:26:02 PM: Allegiance exited with code: 128
2/18/2009 11:26:02 PM: Creating Crashfile

Tried uninstalling and reinstalling everything, alleg, .net 2.0 sp1 even tried the alpha engine.

Thing is if I start Alleg on its own, it comes up fine and then says I need to use asgs/authentication error.

Here is the template stuff:
Windows 2K sp4: all Microsoft update site stuff installed
Processor Speed: AMD AthlonXP 2100+
RAM: 1GB
Video Card (Make and Model#): Matrox Marvel G450
Sound Card (Make and Model#): Audigy
Connection Type (Dialup, Cable, DSL, other): Cable
Modem (Make and Model#): n/a
Router (Make and Model#): Charter's
Internet Service Provider(company name): Charter
Location(State/Province/Locality, and Country): TN
Installed Mods: None

Make and Version of firewall: None
Make and version of anti-virus: Clamwin

Confirm that you have the following installed:

* .Net 1.1 [ ]
* Service Pack 1 for .Net 1.1 [ ]
* Hotfix for .Net 1.1 [ ]

Un/Installed then reinstalled .Net 2.0 sp1

Installed on E drive (system Drive, C drive os died and this one was a backup...)

[RadarRider]

bump, no news yet on getting around W2K problem????

[badpazzword]

If you tried launching Allegiance.exe directly, what would happen?

[ogorass]

Sadly, there is no known workaround for the new ASGS compatibility issue with Windows 2000. It's being looked into though. Have patience please!