Free Allegiance Forums

Windows Version (and Service Packs): XP Home Service Pack 3 build 2600
Processor Speed: 2.4Ghz
RAM: 1,024 MB
Video Card (Make and Model#): NVIDIA GeForce 6600GT
Sound Card (Make and Model#): Realtek AC97
Connection Type (Dialup, Cable, DSL, other): DSL

Router (Make and Model#): Pragmatic Lectron AR800C2
Internet Service Provider(company name): Telecom Broadband
Location(State/Province/Locality, and Country): Auckland, New Zealand
Installed Mods: none?

Make and Version of firewall: COMODO Internet Security (dunno what version, updates daily)
Make and version of anti-virus: (as above)

Confirm that you have the following installed:

* .Net 1.1 [yes]
* Service Pack 1 for .Net 1.1 [yes]
* Hotfix for .Net 1.1 [yes]



Drive Allegiance is installed on: C:\Games\Allegiance

Problem Encountered at Step #: 5
Which Program (ASGS/Allegiance): ASGSClient
What Error Message:
• Launching Allegiance
• Unable to launch Allegiance.
• Allegiance did not launch in the time allotted.
Comments (What you tried, description, etc):

Well initially, I encountered Error: 'Application failed to initialize properly. Error 0xc000007b', but i downloaded the replacement files from the wiki, then I ran the ASGSUpdate.exe (which updated and launched the client), entered my user and password, but the game doesn't launch.

The debug file looks like this:
• 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
• Closing running processes...
• Saving Settings
• Saving MRU Callsigns
• Checking connectivity
• Using Port: DirectPlay
• Checking ASGS Client Version
• Client Version: 165
• Server Version: 165
• Securing Installation
• Validating Installation
• Preparing Key
• Key Generated
• Connecting to ASGS Server
• Authenticating
• Ticket Received
• Return Value: 0
• Callsign: pyrodrake(3)
• 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

So, I went back to the wiki, and looked into the Error: 'Unable to launch Allegiance.'?, and tryed the things there, and those didn't do anything, so, as a last resort I ask here for help. So any suggestions, I had no problems when I played ages awhile ago....?

Thanks in advance.

Pyrodrake wrote:QUOTE (Pyrodrake @ Jan 3 2009, 12:22 PM) • 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

This error happends, if you moved the Allegiance directory after installation.

Solutions:

Reinstall Allegiance to C:\Games\Allegiance.

OR

Fix registry settings:
Goto HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Allegiance\1.0Adjust the keys "ArtPath" and "EXE Path", so they point to your current location

pkk wrote:This error happends, if you moved the Allegiance directory after installation.

Solutions:

Reinstall Allegiance to C:\Games\Allegiance.

This isn't the problem because I installed it there first + I tryed this 3 times.

pkk wrote:Fix registry settings:

* Goto HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Allegiance\1.0
* Adjust the keys "ArtPath" and "EXE Path", so they point to your current location

I checked this out and they already point to the correct location.
ArtPath -> C:\Games\Allegiance\Artwork
EXE Path -> C:\Games\Allegiance

So, sadly this is not the problem, thanks for trying though

There have been reported issues with commodo recently. Uninstall it (don't just disable it) and do a hard reboot (power down the machine). Start back up and try to connect. This will verify if commodo is part of the problem.

FreeBeer wrote:QUOTE (FreeBeer @ Jan 4 2009, 11:29 AM) There have been reported issues with commodo recently. Uninstall it (don't just disable it) and do a hard reboot (power down the machine). Start back up and try to connect. This will verify if commodo is part of the problem.

I tried this, and then tryed again with no firewall/AV at all, and still the same problem (So I assume the COMODO either isn't a problem or is only a part of it). Thanks for the suggestion, though.

You did reboot after removing commodo, right?

Ok.. check your router to see if there are any off rules in there that might be blocking you. I'm not familiar with your router, so I can't be of too much help here.

Yes, I did restart afterwards.

I'm fairly sure it's not the router, since its a pretty simple router, and the same router I previously used to play the game awhile ago. That being said, I wouldn't know what to look for in routers that would interfere with this type of thing...

Probably a .Net issue.
QUOTE I previously used to play the game awhile ago.[/quote]
What recently have you done (Installed, Uninstalled, modified,...etc) ?

Safe side:

amsunaakage wrote:QUOTE (amsunaakage @ Jan 4 2009, 04:26 AM) Uninstall and completely remove any files of the following:

1- Allegiance.
2- Antivirus/Firewall.
3- Use this TOOLto remove all your .Net framework versions.

Now Install :

1- .NET Framework Version 1.1
2- .NET Framework 1.1 Service Pack 1
3- Allegiance Setup

ImmortalZ wrote:QUOTE (ImmortalZ @ Feb 17 2008, 12:31 AM) Check if you have a directory called "Program" in the C drive, other than Program Files.

This one worked for me when I had the same problem. It won't need to be a folder; any file that starts with "Program" will affect it.

Ok, next round, first I checked for files or folders called programs (both a look manually, quickly, and a search) - there was not any.
So, the simpler thing not working I uninstalled Allegiance, Antivirus/firewall, then used the tool to remove all versions of dotnetfx, then restarted computer.
Then, Installed dotnet 1.1, the SP1, and the update, then restarted.
Then I installed Allegiance again, and ran ACGSUpdate, which updated the client, and then I get the exact same problem as I try to log in.
So I'll answer the next question .. ..

amsunaakage wrote:What recently have you done (Installed, Uninstalled, modified,...etc) ?

Hmn, it was a long time ago, since then there's been a full system wipe at least once, hardware-wise: more RAM added, HDDs changed, and possibly (but I cant remember, another graphics card), although other than that its the same. Software-wise it's probably a fair amount different, it's hard to say, it's been awhile.
Edit: Clarified a bit.