ASGS Build 165 Published

takingarms1 · Post by **takingarms1** » Thu Apr 10, 2008 1:11 am

God save queen Pook!

I got the loop error but downloading the zip and manually overwriting worked great.

Post by **FreeBeer** » Thu Apr 10, 2008 1:29 am

BTW, Pook. Thanks for your efforts!

*off to calm down the whiners that can't read and follow instructions*

Fun factoid: Despite two very explicit warnings about nicks in Cadet Applications, almost 10% of all applications fail to follow them.

Burnin_1 · Post by **Burnin_1** » Thu Apr 10, 2008 2:03 am

I found a work around if you do not have your game installed on the system drive (in most cases this is drive "C"). I have my game on drive "D" and ASGS would dissapear and give me the error in the Dump log. So here is what I did so I would not have to reinstall onto my system drive.

1. Create a directory (folder) on the system drive and give it a name I called mine "Drive D".

2. Right clic on "My Computer" and select manage. Clic on Disk Management and right clic on the drive your game is on and select "Change drive letter and paths..." Clic the "Add" button. Select "Mount in the following empty NTFS folder" and enter the path or use the "Browse" button to find it. Clic OK

3. Edit your registry using regedit or another registry editing program and Navigate to HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Microsoft Games/Allegiance. You will see some folders just open them and look for anything that refers to *Path and change the paths to match the new path. Just right clic on the key you want to change and select "Modify". Type in the correct path keeping the syntax intact I just copied and pasted the new part of the path.

4. You will also have to change the shortcuts to use the new path as well.

This worked for me...Good Luck.

javaswiller · Post by **javaswiller** » Thu Apr 10, 2008 2:47 am

This hosed my game.

I get an illegal operation when I click on ASGS. I had decided to download the zip when the updater keep hanging.

Orion · Post by **Orion** » Thu Apr 10, 2008 4:51 am

Pook wrote:QUOTE (Pook @ Apr 9 2008, 07:03 PM) 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.

Do you have any strings hard coded relating to the path that may have gotten encrypted by Xenocode come obfuscation time? It just doesn't make sense to me because this should all take place at run time.. string path <- reg value (which is loaded fine, obviously), then for some reason it can't access the path? I dont get it.

Post by **Pook** » Thu Apr 10, 2008 5:20 am

Technical Wonder wrote:QUOTE (Technical Wonder @ Apr 9 2008, 11:51 PM) Do you have any strings hard coded relating to the path that may have gotten encrypted by Xenocode come obfuscation time? It just doesn't make sense to me because this should all take place at run time.. string path <- reg value (which is loaded fine, obviously), then for some reason it can't access the path? I dont get it.

Nope, it's not the obfuscation itself - the client after obfuscation also works fine. The problem exists in the Xenocode native wrapper that it uses to break ILDASM disassembling. It's a problem they confirmed and which should be corrected in their 2008 Postbuild product, when it's released. (Any time now, supposedly)

Curiosity · Post by **Curiosity** » Thu Apr 10, 2008 6:51 am

Pook wrote:QUOTE (Pook @ Apr 10 2008, 04:21 AM) It's a (previously unknown) side effect of the processing by Xenocode and I'm looking into it. The only known workaround at this time is to reinstall (or move, if you are ok editing the registry) your installation to the system drive. It doesn't have to be the default installation location, just on the system drive. (e.g. C:\Allegiance).

What? Install it on my system drive?! `yn

I cannot, will not, shall not, install any game on my system drive. No. I still remember what happened last time...

SYSTEM DRIVE ERROR KILLS ALL DATA!! /mad.gif" style="vertical-align:middle" emoid=":mad:" border="0" alt="mad.gif" /> /sad.gif" style="vertical-align:middle" emoid=":sad:" border="0" alt="sad.gif" /> /mad.gif" style="vertical-align:middle" emoid=":mad:" border="0" alt="mad.gif" /> /sad.gif" style="vertical-align:middle" emoid=":sad:" border="0" alt="sad.gif" /> <---Mixed emotions

Curiosity · Post by **Curiosity** » Thu Apr 10, 2008 7:08 am

*A few minutes later, after noticing Burnin_1's post...*

...Burnin_1, are you using Microsoft Windows XP? I can't find the registry key you stated!

PS: Apologies for double-posting.

Spinoza · Post by **Spinoza** » Thu Apr 10, 2008 8:07 am

Please, PLEASE put a WARNING for people (like me) who have alleg installed in on non system drives !
I could have lived without this update !
Now I can't live with it ...

madpeople · Post by **madpeople** » Thu Apr 10, 2008 8:42 am

i'm guessing that the ASGS servers only allow one version of ASGS to be used at any one time, so we couldn't allow people to use 160 if 165 doesn't work for them? (until this is resolved)