Can't start game

Post by **aem** » Fri Jun 01, 2007 12:04 pm

Moosetek13 wrote:QUOTE (Moosetek13 @ Jun 1 2007, 07:25 AM) BitDefender updates automatically, and I am using version 10 - which is the latest major release.

I have tried it with all BD modules disabled, as well - to no avail.

It is not a connection issue - which is what it would be if BD was blocking something.
The main game fails to load from ASGS, but ASGS succeeds in logging in before that.

I can run the game if I start it from Allegiance.exe directly, but I can not enter the network game area if it is not started from ASGS.

Personally I would still suspect Bitdefender. No it is not a connection issue but that doesn't mean its not being blocked by BD. AV programs such as BD can affect a wide range of activities on your computer.

I sent a message to Bitdefender support and hope they will be helpful.

madpeople · Post by **madpeople** » Fri Jun 01, 2007 12:08 pm

do you have .net 2.0 too

i know 1.1 and 2.0 are different things, 3.0 might be different to 2.0

also have you tried going to http://windowsupdate.microsoft.com/ choosing custom, then choosing the software optional things that look like they might be useful (along with the high priority stuff)

(sorry if this has already been mentioned)

oh, you could also try bringing up the task manager, googeling each process listed in in the processes tab in turn, and ending them if they aren't system proceses after terminating a proces, try logging into asgs and see if it launches, do this for all your processes, find out which one you have to stop to let asgs managed to launch allegiance, that will tell you what is stopping allegiance launch

ogorass · Post by **ogorass** » Fri Jun 01, 2007 1:36 pm

I dunno then... It seems that ASGS isn't allowed by something (system, antivir, random backround proggy) to launch Allegiance. Given, that it's not BD, Id blame system access rights... Check if ASGS is authorised to launch other apps (i.e. if it's run in admin mode).

Edit: Forgot you're not running Vista.

ImmortalZ · Post by **ImmortalZ** » Fri Jun 01, 2007 5:07 pm

Try unchecking the Launch Allegiance option in ASGS and then launching Allegiance manually.

Moosetek13 · Post by **Moosetek13** » Fri Jun 01, 2007 7:26 pm

If I uncheck 'Launch Allegiance' in ASGS and launch it manually after logging in with ASGS the game will start.
Then I click on the Free Games button, enter my callsign, then am told that it could not authenticate and to start the game from ASGS.

I checked the permissions for ASGS and they look fine. It has permission to execute files.

Madpeople, yes I also have .NET 2.0 with all service packs as well.
And I always use Custom when I go to Windows Update. There are only 2 things that I do not have; the newest sound card drivers because updating audio drivers that way is a very good way to break it, and Media Player 11 because I do not like the new interface.

ImmortalZ · Post by **ImmortalZ** » Sat Jun 02, 2007 3:05 am

Moose, make sure you're adding your newbie number to the end of the callsign you enter in Allegiance when you manually start it. You can find it in the ASGS log. It'll look like "Moosetek13(n)" where n is a number.

Moosetek13 · Post by **Moosetek13** » Sat Jun 02, 2007 5:27 am

I signed in as Moosetek13(0) with the same results.
authentication failed - restart game in ASGS

Do I need to log in to ASGS that way too?

ImmortalZ · Post by **ImmortalZ** » Sat Jun 02, 2007 6:13 pm

No, ASGS automatically does that for you.

Post by **aem** » Sat Jun 02, 2007 6:17 pm

I've never been able to get into Allegiance manually w/ ASGS. Always had to let ASGS start it.

ImmortalZ · Post by **ImmortalZ** » Sun Jun 03, 2007 12:39 pm

Just throwing out ideas... *shrug*