Free Allegiance Forums

He's one of those people who get offended by "jaggies". He won't ever play Allegiance...

No worries, I'll work on it in my spare time. As for testing on another computer, I convinced a friend of mine to let me test it on his beat up alienware comp, and it worked fine. This, of course, only makes me angrier at the fact that it wont work on mine.

Negative, ASGS still not launching Allegiance.



EDIT: I noticed that everytime I run the autoupdate on ASGS, it always updates the main file. Significant?

QUOTE (Grimmwolf_GB @ Jul 4 2006, 03:10 AM) There are three packets for .Net 1.1

The original installer

The Service pack

The hotfix for the Service pack

Do you have all three of them?


That may very well be the problem, because I remember not installing the service pack because it kept ...

Quick glance through the registry yields no information. Assigning ALL permissions to both ASGS and Allegiance doesn't make a difference either...


GAH, wtf is the problem?! /mad.gif" style="vertical-align:middle" emoid=":mad:" border="0" alt="mad.gif" />

For future reference, partial uninstall of .NET 1.1 = VERY BAD THING.



Also, where are the registry values for ASGS located?

I actually did have a corrupted .NET installation, reinstalling .NET fixed ALOT (and I do mean ALOT) of problems on my computer, but the ASGS problem remains...

Nope, that's it. Here's the most recent one, if it helps...

7/2/2006 3:48:52 PM: Initializing
7/2/2006 3:48:52 PM: Reading Settings
7/2/2006 3:48:52 PM: Logging Option: DEBUG
7/2/2006 3:48:52 PM: Loading MRU Callsigns
7/2/2006 3:48:52 PM: Loading Form Position
7/2/2006 3:48:52 PM: Checking ...

Negative on the Allegiance debug logs, all I have is the asgs_debug.log file, and a list of files that were updated the first time I ran Allegiance.

Nope, Allegiance doesn't show up in the task manager. Also, all the debug logs I have are the same, almost letter for letter (time and dates being the exception).