Weird, radar.
You shouldn't even have an AGC.dll in your c:\allegBeta folder.
Try deleting it.
--TE
Unable to loggin with asgs
Yeah, AGC.dll is only needed for the server and lobby, the client does not need it at all.
It is not in the regular bundles, but as a dev you must have grabbed it /tongue.gif" style="vertical-align:middle" emoid=":P" border="0" alt="tongue.gif" />
I am not sure why ASGS hangs at 'securing installation' for you, at least that is what I gathered from chatting with you just before. You did say you tried ASGS in http and directplay port modes.
Do you need to use a proxy to get to the web? I am guessing no.
It is not in the regular bundles, but as a dev you must have grabbed it /tongue.gif" style="vertical-align:middle" emoid=":P" border="0" alt="tongue.gif" />
I am not sure why ASGS hangs at 'securing installation' for you, at least that is what I gathered from chatting with you just before. You did say you tried ASGS in http and directplay port modes.
Do you need to use a proxy to get to the web? I am guessing no.

DOG PROPERTY LAWS:
2. If it's in my mouth, it's mine.
[unless it tastes bad, then it is yours.]
I'm having exactly the same problems with the new R3 tagged versions of the alpha. It used to work fine with asgs beta mode too with the previous versions(about 2 weeks ago I think). Atleast the builds from 24. and 26.9. didn't work for me at the same dates. It always says invalid signature. Did someone figure out a solution? I just have the exe (yes it's the right one) and some microsoft dlls and some ATL.dll+atl71.dll in the directory.
I'm new, and I'm clueless!
ASGS is on and the signatures are updated. Works for me...
--TE
--TE
Last edited by Tigereye on Wed Sep 27, 2006 8:08 pm, edited 1 time in total.
The Allegiance community currently hates their sysadmin because he is doing: [Too Much] [____________|] [Too Little]
Current reason: Removing the PayPal contribute page. Send Bitcoin instead: 1EccFi98tR5S9BYLuB61sFfxKqqgSKK8Yz. This scale updates regularly.




