I start ASGS, click Login, and here is what the console window reports.
• Initializing
• Reading Settings
• Logging Option: SIMPLE
• Loading MRU Callsigns
• Loading Form Position
• Checking Installation
• Checking OOBE
• Ready
• Checking for system updates
• Checking for existing processes
• Saving Settings
• Saving MRU Callsigns
• Checking connectivity
• Using Port: DirectPlay
• Checking ASGS Client Version
• Client Version: 155
• Server Version: 155
• Securing Installation
• Validating Installation
• Preparing Key
• Key Generated
• Connecting to ASGS Server
• Authenticating
• Ticket Received
• Return Value: 0
• Callsign: Moosetek13(0)
• Authenticated successfully
• Checking messages
• Return Value: 0
• No messages
• Checking polls
• Return Value: 0
• No polls
• Logged In
• Launching Allegiance
• Unable to launch Allegiance.
• Allegiance did not launch in the time allotted.
• Beginning Logout
• Closing processes
• Sending Logout Request
• Logged Out
Can't start game
Please follow the instructions here, then fill out the template if you can't resolve it. The template gives us some key information.
Thanks!
Thanks!
-
Moosetek13
- Posts: 29
- Joined: Tue May 22, 2007 7:37 pm
Windows Version (and Service Packs): Windows XP SP2 (Media Center 2005)FreeBeer wrote:QUOTE (FreeBeer @ May 22 2007, 04:13 PM) Please follow the instructions here, then fill out the template if you can't resolve it. The template gives us some key information.
Thanks!
Processor Speed: 2.8GHz Pentium D
RAM: 3GB
Video Card (Make and Model#): Evga nVidia 6800 GS SE CO 256MB
Sound Card (Make and Model#): Soundblaster Audigy 4
Connection Type (Dialup, Cable, DSL, other): Cable
Modem (Make and Model#): Motorola SB5101
Router (Make and Model#): Netgear WGR614 v6
Internet Service Provider(company name): Cox
Location(State/Province/Locality, and Country): CA, USA
Installed Mods: none
Problem Encountered at Step #: (read the "What Should Happen" for this step#) 5
Which Program (ASGS/Allegiance): Allegiance
What Error Message: None - Allegiance fails to start and ASGS logs out.
Comments (What you tried, description, etc):
... I have created firewall rules for both ASGS and Allegiance allowing both all incoming and outgoing ports (Bitdefender Internet Security v10).
In ASGS 'Help/Update - Repair Critical Files' the update window shows Update Complete, then another error window pops up saying 'Unable to launch ASGS Client'.
I can start Allegiance directly with Allegiance.exe, but can't get into online games. I get a message about being unable to authenticate through ASGS and to start the game through ASGS (even if ASGS is already logged in - I had tried unchecking 'Launch Allegiance' in the ASGS menu, logging in, then started the game with the exe).
Last edited by Moosetek13 on Wed May 23, 2007 11:49 pm, edited 1 time in total.
-
Moosetek13
- Posts: 29
- Joined: Tue May 22, 2007 7:37 pm
-
Moosetek13
- Posts: 29
- Joined: Tue May 22, 2007 7:37 pm
Here is something new.
I clicked Beta Mode for Allegiance in ASGS, and here is the console window contents:
• Beta Mode On.
• Checking for system updates
• Checking for existing processes
• Saving Settings
• Saving MRU Callsigns
• Checking connectivity
• Using Port: DirectPlay
• Checking ASGS Client Version
• Client Version: 155
• Server Version: 155
• Securing Installation
• Unable to secure Allegiance installation.
• EXE Path Information not found in the registry.
In the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Allegiance\1.0 the entry for 'EXE Path' is C:\Program Files\Microsoft Games\Allegiance - which is the correct install location.
There is no entry for 'EXE Path' in the ASGS key, however.
Should there be, or is the one in the Allegiance key the only one?
Edit:
I have also just tried re-installing .NET Framework 1.1, but to no avail.
I clicked Beta Mode for Allegiance in ASGS, and here is the console window contents:
• Beta Mode On.
• Checking for system updates
• Checking for existing processes
• Saving Settings
• Saving MRU Callsigns
• Checking connectivity
• Using Port: DirectPlay
• Checking ASGS Client Version
• Client Version: 155
• Server Version: 155
• Securing Installation
• Unable to secure Allegiance installation.
• EXE Path Information not found in the registry.
In the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Allegiance\1.0 the entry for 'EXE Path' is C:\Program Files\Microsoft Games\Allegiance - which is the correct install location.
There is no entry for 'EXE Path' in the ASGS key, however.
Should there be, or is the one in the Allegiance key the only one?
Edit:
I have also just tried re-installing .NET Framework 1.1, but to no avail.
Last edited by Moosetek13 on Wed May 23, 2007 6:06 am, edited 1 time in total.
The Beta is different, so that's expected. When we have a Beta to test, it's installed in another directory so as not to mess up with the current release. It also points the game to a different lobby and server set in the Registry for the purpose of testing.
I suppose you could try uninstalling, then re-download and re-install the game. I took note that others have solved their connection issues by doing so. It's worth a try.
I suppose you could try uninstalling, then re-download and re-install the game. I took note that others have solved their connection issues by doing so. It's worth a try.
-
Moosetek13
- Posts: 29
- Joined: Tue May 22, 2007 7:37 pm
I have done so.
The first install was off the cd that came with this month's MaximumPC magazine.
Then I downloaded from this site and reinstalled everything fresh.
I also downloaded and installed Windows Script 5.6, just in case it was a scripting problem. GalCiv2 had some errors with its startup program as well, which was a problem with the Script install.
No luck, however.
I have just been trying different things, from the different options in ASGS to reinstalling to starting several services that I normally have set to 'Manual'.
It is getting very frustrating, to say the least.
But so far it does not seem like a connection issue. The main exe won't start, so I never even get the chance to try connecting with a server.
It just dies as it tries to launch Allegiance.exe, and then logs out.
The first install was off the cd that came with this month's MaximumPC magazine.
Then I downloaded from this site and reinstalled everything fresh.
I also downloaded and installed Windows Script 5.6, just in case it was a scripting problem. GalCiv2 had some errors with its startup program as well, which was a problem with the Script install.
No luck, however.
I have just been trying different things, from the different options in ASGS to reinstalling to starting several services that I normally have set to 'Manual'.
It is getting very frustrating, to say the least.
But so far it does not seem like a connection issue. The main exe won't start, so I never even get the chance to try connecting with a server.
It just dies as it tries to launch Allegiance.exe, and then logs out.
Is your Hard drive fragmented?
As allegiance uses a lot of memory, and if some of this memory is being used in the paging file, and as allegiance itself is quite large, your HD may have problems accessing the whole file in the time ASGS allows for.
As allegiance uses a lot of memory, and if some of this memory is being used in the paging file, and as allegiance itself is quite large, your HD may have problems accessing the whole file in the time ASGS allows for.
[img]http://www.freeallegiance.org/forums/st ... erator.gif" alt="IPB Image">
[url=http://pk.dras.us]
-
Moosetek13
- Posts: 29
- Joined: Tue May 22, 2007 7:37 pm
I defragged last week after clearing out some large video files. The page file is a single contiguous file.
I have 3GB of ram, and Allegiance comes in with a footprint of around 21MB. I am not even close to using the page file.
It loads to the first screen in about 8 seconds when I run the exe directly, and the exe itself is only 3.4MB in size.
This game may take a lot of ram when actually in a large game, but it is quite small when first loading.
I have 3GB of ram, and Allegiance comes in with a footprint of around 21MB. I am not even close to using the page file.
It loads to the first screen in about 8 seconds when I run the exe directly, and the exe itself is only 3.4MB in size.
This game may take a lot of ram when actually in a large game, but it is quite small when first loading.