ASGS Update Loop 2

SP4WN · Post by **SP4WN** » Thu Apr 10, 2008 1:28 am

To the guys whose Alleg autocloses when you click login. Its is the GUI error, I have 3 Different Allegs installed on 3 diff HDDs for various reasons. I did the Download of the Setup Installer for my default one, reinstalled added the .zip file and it is fine.

Unfortunatley my other 2 installs get the auto-logout still. I ran it in debug, and even though it closes right away it does create a debug log file in your Allegiance Directory, which is named something like this: asgs_debug.log and looks something like this;

Code: Select all

10/04/2008 02:23:55: Initializing
10/04/2008 02:23:55: Reading Settings
10/04/2008 02:23:55: Logging Option: SIMPLE
10/04/2008 02:23:55: Loading MRU Callsigns
10/04/2008 02:23:55: Loading Form Position
10/04/2008 02:23:55: Checking Installation
10/04/2008 02:23:55: Checking OOBE
10/04/2008 02:23:55: Ready
10/04/2008 02:23:57: A GUI management function did not execute.
10/04/2008 02:23:57: A device attached to the system is not functioning.

Make sure you are installing Alleg to your C: drive or whatever your default OS drive is installed on.

Reaper_G · Post by **Reaper_G** » Thu Apr 10, 2008 1:36 am

Ok...I first performed the update loop fix 1. which said to unzip within the allegiance installed folder. That did nothing for me. I then put the new asgsclient and asgs update into the Allegiance/ASGS folder which then asked if I wanted to replace those files, which I said yes. So, now when I try to log into Allegiance, it installs the update, and then says that it is unable to launch the client. I am trying to follow the fix, plus do what I think I should do. I would appreciate any help that would be given.

IronHide96 · Post by **IronHide96** » Thu Apr 10, 2008 1:48 am

Ok mine is working again. I'm not sure what I did differently than anyone else but here is what I did

I downloaded the fix that was given to us. I extracted all the files. It brought up the Extract Wizard. From there, I zipped to the DEFAULT directory that was provided for my computer. I didn't use the 'C:\Program Files\Microsoft Games\Allegiance' directory on the help page. Then a window popped up that contained the new Updater and Client files which I copied into the original Alleg program file folder, replacing the original Updater and Client files. The game worked from there.

This is what I did for my computer. I don't know if it'll work for anyone elses but it never hurts to try

Reaper_G · Post by **Reaper_G** » Thu Apr 10, 2008 1:50 am

I did exactly like Ironhide did, but unfortunately mine is not working.

LostChild · Post by **LostChild** » Thu Apr 10, 2008 1:58 am

I updated Allegiance, got stuck in the update loop. Uninstalled, reinstalled, same thing happened, then read post, downloaded asgs zip, extracted both files to my main allegiance directory (the default on C). Now when I double-click the asgs 2.1 and attempt to log in I get this error box:

If I uninstall, reinstall (which I tried), I can get stuck again in the update loop, but if I extract the two files to allegiance, I get the above error. Must I have net framework 2? I think I only have 1, but since this is a work machine, I don't think I can upgrade.

LostChild · Post by **LostChild** » Thu Apr 10, 2008 2:02 am

I should almost mention that after I get the 'unknown error', if I exit out of asgs, I then get this error and must choose quit.

Reaper_G · Post by **Reaper_G** » Thu Apr 10, 2008 2:17 am

yeah...i fixed mine....

Okay....the fix directions are a little confusing. So when you unzip/extract make sure the files get into the Allegiance/ASGS folder and make sure to replace all. After doing this, restart your computer and it should work fine. This worked for me.

LostChild · Post by **LostChild** » Thu Apr 10, 2008 2:34 am

Hey reaper (et al), I don't have an allegiance/asgs folder. I only have allegiance (installed under microsoft games), then artwork, dev and machine as subfolders.