ASGS Build 165 Published

parcival · Post by **parcival** » Wed Apr 09, 2008 9:55 pm

Adam4 wrote:QUOTE (Adam4 @ Apr 9 2008, 11:56 PM) 09/04/2008 21:33:55: A GUI management function did not execute.
09/04/2008 21:33:55: A device attached to the system is not functioning.

is what me and Orion get.

I got rid of the update loop with the zip file solution but I get this too. Also, every change I do to the ASGS settings is not saved. Maybe the problem is there (Saving/loading ASGS settings).

PS: My Allegiance is not installed on the default installation folder. Since I installed Alleg looong time ago maybe I am missing a registry entry too (probably new installer fix this).

Orion · Post by **Orion** » Wed Apr 09, 2008 10:08 pm

Aye, so far it seems that everyone who is getting this error has allegiance installed to a directory other than the standard C:

Adam4 · Post by **Adam4** » Wed Apr 09, 2008 10:08 pm

We think its Alleg not on the main drive. Mine is on G:\, Onions E:\ and so on.

Post by **Pook** » Wed Apr 09, 2008 10:21 pm

I can confirm that the issue is caused by a combination of Xenocode processing and having your install on something other than the system drive.

(ASGS before processing runs fine no matter where Allegiance is installed)

If you install anywhere on the system drive (for example, C:\Allegiance) it'll run fine.

I'll look into it, and if it's something that I can fix or work around I will. The .NET 2.0 version is currently being tested, I'll have to process it to see if it suffers from this as well.

Pook

Orion · Post by **Orion** » Wed Apr 09, 2008 10:40 pm

Doesn't ASGS use relative path to find Allegiance?

Arkof · Post by **Arkof** » Wed Apr 09, 2008 10:52 pm

Grrrr,

Oh well, thanks Pook. 2 hours from fault to workaround isn't bad.
I can live with moving my alleg install onto my C:\ for a while, and this means I can finally install Vista SP1. Might make that my task for tonight.

quackdamnyou · Post by **quackdamnyou** » Wed Apr 09, 2008 10:53 pm

I have my allegiance in the default location, and I still got a loop and had to use the zip file.

Aviation21 · Post by **Aviation21** » Wed Apr 09, 2008 11:05 pm

I tried many times and the fix was to install Allegiance on my C drive and then copy and paste the ASGS and Update ASGS pook provided at the begining of this post. I had to install Alleg on my C drive to make it all work...which might cause some problems for me because I have a very small partition for C drive.

I never install anything on my C drive because I only install XP (the operating system) on C drive which makes formatting and reinstalling windows much easier. Now I got about 2 GB left....help!

Aviation21

Furiat · Post by **Furiat** » Wed Apr 09, 2008 11:15 pm

Rewriting everything that has been said so far:

PROBLEM #1:
My ASGS client does an infinite update loop and doesn't allow login.

Solution: Use the zipfile linked in the first post. Apply instructions in said post.

PROBLEM #2:
My ASGS client shuts down when i try to login. There's an error in the ASGS logs similar to this:
09/04/2008 21:33:55: A GUI management function did not execute.
09/04/2008 21:33:55: A device attached to the system is not functioning.

Temporary Fix: Install Allegiance in the default folder (C:\Program Files\Microsoft Games\Allegiance)
Solution: None so far.

Post by **Pook** » Thu Apr 10, 2008 12:03 am

Technical Wonder wrote:QUOTE (Technical Wonder @ Apr 9 2008, 05:40 PM) Doesn't ASGS use relative path to find Allegiance?

ASGS uses the registry to find where Allegiance is. ASGS isn't the issue, like I said the non-Xenocoded version works fine no matter where you install Allegiance. This is another (albeit smaller) side-effect of the Xenocode processing.

I'm hoping that their 2008 product (which is supposed to contain the "final" fix) is out soon which should correct this issue for good.

If, on the other hand, the .NET 2.0 version of ASGS is unaffected by this bug I may just get that out as an early public beta so folks can get Allegiance put back on the drive they want it on.