Free Allegiance Forums

The asgs debug log is the one you want, but if debug logging is on it should have much more information in it than what you've posted.

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 Installation
7/2/2006 3:48:53 PM: Ready
7/2/2006 3:48:54 PM: Checking for system updates
7/2/2006 3:48:54 PM: Checking for existing processes
7/2/2006 3:48:54 PM: Closing running processes...
7/2/2006 3:48:54 PM: Saving Settings
7/2/2006 3:48:54 PM: Saving MRU Callsigns
7/2/2006 3:48:55 PM: Checking connectivity
7/2/2006 3:48:55 PM: Using Port: DirectPlay
7/2/2006 3:48:56 PM: Checking ASGS Client Version
7/2/2006 3:48:56 PM: Client Version: 120
7/2/2006 3:48:56 PM: Server Version: 120
7/2/2006 3:48:56 PM: Securing Installation
7/2/2006 3:48:56 PM: Validating Installation
7/2/2006 3:48:57 PM: Preparing Key
7/2/2006 3:48:57 PM: Key Generated
7/2/2006 3:48:57 PM: Connecting to ASGS Server
7/2/2006 3:48:57 PM: Authenticating
7/2/2006 3:48:58 PM: Ticket Received
7/2/2006 3:48:58 PM: Return Value: 0
7/2/2006 3:48:58 PM: Callsign: Tyrin@CDT-B(0)
7/2/2006 3:48:58 PM: Authenticated successfully
7/2/2006 3:48:58 PM: Checking messages
7/2/2006 3:48:58 PM: Return Value: 0
7/2/2006 3:48:58 PM: No messages
7/2/2006 3:48:58 PM: Checking polls
7/2/2006 3:48:58 PM: Return Value: 0
7/2/2006 3:48:58 PM: No polls
7/2/2006 3:48:58 PM: Logged In
7/2/2006 3:48:58 PM: Launching Allegiance
7/2/2006 3:49:00 PM: Active
7/2/2006 3:49:28 PM: Checking In
7/2/2006 3:49:29 PM: Return Code: 0
7/2/2006 3:49:29 PM: Check-in succeeded
7/2/2006 3:49:29 PM: Last Check-in: 7/2/2006 3:49:29 PM
7/2/2006 3:49:46 PM: Saving Form Position
7/2/2006 3:49:46 PM: Beginning Logout
7/2/2006 3:49:46 PM: Closing processes
7/2/2006 3:49:46 PM: Sending Logout Request
7/2/2006 3:49:47 PM: Logged Out
7/2/2006 3:49:47 PM: Exiting

Don't know what to suggest. It could of course be some sort of .NET permissions problem I suppose but it's doing everything else.

I'm going to assume that you're using the current installer (allsetup167.exe). At this point it sounds like you're out of luck. This particular issue has never surfaced.

I had recommended before the forumswitch to uninstall all .NET-related entries in your Control Panel's Add/Remove Programs applet then reboot.

Re-download all of the .NET 1.1 updates from windowsupdate, including all of its hotfixes and then try ASGS again.

I came to the same conclusion that the only other possibility left is a corrupt .NET installation.

--TE

Sometimes Allegiance took too long to launch on a fragmented drive, but that is not the problem here.

Could the registry be wrong somehow, Pook?
Are you using a non english XP, Trinexx?

The installer overwrites the registry at each login... I did that so a reinstall could repair it.

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...

Someone will correct me since I may have slipped on the times ...

I think you will need both .Net 1.1 and .Net 2.0.

I think Pook and TE are closer to thge problem though ...

Try opening up permissions on the Allegiance part of the Registry. I had permissions issues on Windows 2003 that required loosening permissions.

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



Also, where are the registry values for ASGS located?

All Allegiance-related registry keys are located at:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Allegiance

ASGS is located at
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Allegiance\1.0\ASGS

I'm pretty sure that ASGS determines Allegiance.exe's location based on the Allegiance\1.0 key's "EXE Path" value.

--TE