Posted: Sat Nov 24, 2012 9:52 am
Seems I've had some sort of difficulty getting the Free Allegiance installed.
After some time, found that there was a utility called ASGS that is used 'instead' of the normal 'launcher.exe'? Have tried it, used it to "update/repair" FA and it sends the files to the drives root directory instead of the install directory. Have Uninstalled and Reinstalled without problem. Can start the Allegiance.exe manually, have unblocked its activity via Firewalls, etc. Can play the Training missions via the direct allegiance.exe files... both Production and the Beta.
An oddity though, beyond what I've mentioned... is that ASGS will create OLDER VERSION allegiance.exe files when it does its 'update/repair' function, even though it does place them in the root directory on the drive.
ASGS states that it cannot confirm the security of the Allegiance install and that it is not installed correctly. Dunno why, each time I uninstalled/reboot/install there is no error in the process. When I start with the launcher.exe it does its updates 3 times in a row before finally starting up without errors, merely cannot connect to any server. Firewalls are set to OFF to determine if that is the difficulty. Something is wrong with ASGS finding OLDER versions of Allegiance.exe files. IMO. It is stepping them down from something like .10644 to .10400. Why? Anyyways, I'm too tired to continue. Hope someone has an idea.
Windows XP SP3
ThreatFire, Win-Firewall, Norton
i7, 6GB RAM
.NET 2.0, 3.0, 3.5 +SP1, 4.0
C-Runtimes installed fine also.
PS. I have created shortcuts noting to ASGS that its home directory is where it resides. Have tried ASGS from both the main Allegiance install directory and also from the Beta and Production directories as well. Trying many different combinations of it's location to resolve this. Outcomes are all the same. Have tried to push the 'updated (although downgraded versions) of the allegiance.exe file into the proper Beta or Production folders and retried this many times. Have also moved the other updated files to the Artwork directory. AND, I do not have the allegiance.pdb (SP???) file at all. Cannot find that zipfile that is mentioned in pkk's other posts to help other people with install problems. It no longer exists.
[allegiance.pdb-is missing!]
After some time, found that there was a utility called ASGS that is used 'instead' of the normal 'launcher.exe'? Have tried it, used it to "update/repair" FA and it sends the files to the drives root directory instead of the install directory. Have Uninstalled and Reinstalled without problem. Can start the Allegiance.exe manually, have unblocked its activity via Firewalls, etc. Can play the Training missions via the direct allegiance.exe files... both Production and the Beta.
An oddity though, beyond what I've mentioned... is that ASGS will create OLDER VERSION allegiance.exe files when it does its 'update/repair' function, even though it does place them in the root directory on the drive.
ASGS states that it cannot confirm the security of the Allegiance install and that it is not installed correctly. Dunno why, each time I uninstalled/reboot/install there is no error in the process. When I start with the launcher.exe it does its updates 3 times in a row before finally starting up without errors, merely cannot connect to any server. Firewalls are set to OFF to determine if that is the difficulty. Something is wrong with ASGS finding OLDER versions of Allegiance.exe files. IMO. It is stepping them down from something like .10644 to .10400. Why? Anyyways, I'm too tired to continue. Hope someone has an idea.
Windows XP SP3
ThreatFire, Win-Firewall, Norton
i7, 6GB RAM
.NET 2.0, 3.0, 3.5 +SP1, 4.0
C-Runtimes installed fine also.
PS. I have created shortcuts noting to ASGS that its home directory is where it resides. Have tried ASGS from both the main Allegiance install directory and also from the Beta and Production directories as well. Trying many different combinations of it's location to resolve this. Outcomes are all the same. Have tried to push the 'updated (although downgraded versions) of the allegiance.exe file into the proper Beta or Production folders and retried this many times. Have also moved the other updated files to the Artwork directory. AND, I do not have the allegiance.pdb (SP???) file at all. Cannot find that zipfile that is mentioned in pkk's other posts to help other people with install problems. It no longer exists.
[allegiance.pdb-is missing!]