Tried running the FAZ servers. When I use the regular ASGS login I get the invalid signature message before alleg actually launches.
So I tried downloading everything again. Still same problem.
So I went straight through the FAZ Beta icon on my desktop and I get the Failure to login to lobby message.
So I uninstall everything and replace the FAZ allegiance file with my old one and I cannot login to the regular servers.
EDIT: Found the error of my ways will update after reinstalling and updating allegiance and reinstalling FAZ and zip files (into FAZ folder this time).
Unable to loggin with asgs
-
overkill13
- Posts: 14
- Joined: Sat Aug 12, 2006 2:42 am
- Location: Canada
Last edited by overkill13 on Thu Sep 21, 2006 2:03 am, edited 1 time in total.
This is my nan. Without it, I am nothing. Without me, my nan is nothing.
It's better to be on the ground wishing you were flying than flying wishing you were on the ground.
Fighter pilots make movies. Attack pilots make history.
It's better to be on the ground wishing you were flying than flying wishing you were on the ground.
Fighter pilots make movies. Attack pilots make history.
When you say you downloaded everything...
did you dl both the retail installer and the new R3 exe? Did you remember to copy (overwrite) the old Allegiance.exe in the Freeallegiance folder with the new Allegiance.exe that you got from the R3 file?
And to confirm, you do need to go through ASGS (check Beta Mode) to launch the correct client and to get to the beta servers.
did you dl both the retail installer and the new R3 exe? Did you remember to copy (overwrite) the old Allegiance.exe in the Freeallegiance folder with the new Allegiance.exe that you got from the R3 file?
And to confirm, you do need to go through ASGS (check Beta Mode) to launch the correct client and to get to the beta servers.
-
overkill13
- Posts: 14
- Joined: Sat Aug 12, 2006 2:42 am
- Location: Canada
Like I said I found the error of my ways...
I copied the zipped files to my regular allegiance location. Not the location of the installed R3 FAZ installer. This screwed everything up. So I reinstalled allegiance and updated it. Reinstalled the FAZ installer and moved the four zipped files to the FAZ installed folder and all is well.
I copied the zipped files to my regular allegiance location. Not the location of the installed R3 FAZ installer. This screwed everything up. So I reinstalled allegiance and updated it. Reinstalled the FAZ installer and moved the four zipped files to the FAZ installed folder and all is well.
This is my nan. Without it, I am nothing. Without me, my nan is nothing.
It's better to be on the ground wishing you were flying than flying wishing you were on the ground.
Fighter pilots make movies. Attack pilots make history.
It's better to be on the ground wishing you were flying than flying wishing you were on the ground.
Fighter pilots make movies. Attack pilots make history.
Downloaded the beta installer - installed
downloaded the beta R3 client - installed
started with no ASGS - got the message - use ASGS
told ASGS to use beta mode and started it up
"invalid signature"
I reloaded several times using the default directory once.
The new beta files were loaded into whatever directory I was trying.
This system sucks cuz :
once ASGS checks it and don't lilke it - it is destroyed ( how can it fix beta copies ? with last weeks stuff ?weird )
and it doesn't say where it is looking for anything
or the date/version etc.
if you knew some of this you might be able to make it work
..................................................................
I can play when ASGS is turned off.
When it is on - no go.
radar
downloaded the beta R3 client - installed
started with no ASGS - got the message - use ASGS
told ASGS to use beta mode and started it up
"invalid signature"
I reloaded several times using the default directory once.
The new beta files were loaded into whatever directory I was trying.
This system sucks cuz :
once ASGS checks it and don't lilke it - it is destroyed ( how can it fix beta copies ? with last weeks stuff ?weird )
and it doesn't say where it is looking for anything
or the date/version etc.
if you knew some of this you might be able to make it work
..................................................................
I can play when ASGS is turned off.
When it is on - no go.
radar
It doesn't fix beta copies.
The only way to get past the invalid signature error is to redownload the latest Allegiance.exe and replace your copy in your beta's folder.
ASGS cannot "repair" it.
--TE
The only way to get past the invalid signature error is to redownload the latest Allegiance.exe and replace your copy in your beta's folder.
ASGS cannot "repair" it.
--TE
The Allegiance community currently hates their sysadmin because he is doing: [Too Much] [____________|] [Too Little]
Current reason: Removing the PayPal contribute page. Send Bitcoin instead: 1EccFi98tR5S9BYLuB61sFfxKqqgSKK8Yz. This scale updates regularly.
Radar, ASGS, in beta mode, checks the path set by the 1.1 registry keys, so make sure that is where you are sticking the latest Allegiance.exe (along with the vc8 dlls).Tigereye wrote:QUOTE (Tigereye @ Sep 21 2006, 01:03 AM) The only way to get past the invalid signature error is to redownload the latest Allegiance.exe and replace your copy in your beta's folder.
I should not have to say this but the system doesn't 'suck'.
Yes it is not a one click install, but it is pretty damn close and it is a beta, and you are a smart cookie, you'll figure it out with our help if need be.
Last edited by Dogbones on Thu Sep 21, 2006 2:42 pm, edited 1 time in total.
DOG PROPERTY LAWS:
2. If it's in my mouth, it's mine.
[unless it tastes bad, then it is yours.]
"sucks" refers to the lack of information provided to help you figure it out.
It doesn't mean the working system sucks - just when its broke - trying to guess what is going on with no usable info is not desirable
..................................................
The "latest Allegiance.exe" would be FZ R2 right?
If it means the R3 Beta Allegiance.exe then I have done that as indicated in my post.
................................................................................
.......................
this is what I do:
From the links on the home page to the FAZ instructions:
Download the beta installer and tell it to install the beta into c:\allegBeta.
Download the R3 beta client and unzip it into c:\allegBeta
Run c:\allegBeta\Allegiance.exe and get "use ASGS" message.
Run ASGS with beta mode on - get the "invalid signature" message.
the registry 1.1 exe path is c:\allegBeta.
i have repeated the above using the default location also. The 1.1 exe location was correct.
the system works with ASGS off. so ?
................................................................................
..........
what should I be doing different ? Seems ok to me.
radar
It doesn't mean the working system sucks - just when its broke - trying to guess what is going on with no usable info is not desirable
..................................................
The "latest Allegiance.exe" would be FZ R2 right?
If it means the R3 Beta Allegiance.exe then I have done that as indicated in my post.
................................................................................
.......................
this is what I do:
From the links on the home page to the FAZ instructions:
Download the beta installer and tell it to install the beta into c:\allegBeta.
Download the R3 beta client and unzip it into c:\allegBeta
Run c:\allegBeta\Allegiance.exe and get "use ASGS" message.
Run ASGS with beta mode on - get the "invalid signature" message.
the registry 1.1 exe path is c:\allegBeta.
i have repeated the above using the default location also. The 1.1 exe location was correct.
the system works with ASGS off. so ?
................................................................................
..........
what should I be doing different ? Seems ok to me.
radar
Message
ok the message "file agc.dll has invalid signature"
the AGC.dll in the beta directory came from the R3 beta client download just minutes before.
code version
I am using whatever version beta is coming from the sight minutes before I try each time.
My public version is FAZ R2 in c:/programs/Microsoft games...... and i can play the regular lobbies with it.
the beta is being loaded into c:\allegBeta not c:\allegBeta\FreeAllegiance.
.............................................................
also to note - i have been using dial up to play reg alleg.
ASGS will not secure the location unless the dial up is connected - otherwise it just hangs.
once i connect the dial up and login again - it says that the agc.dll is invalid.
radar
ok the message "file agc.dll has invalid signature"
the AGC.dll in the beta directory came from the R3 beta client download just minutes before.
code version
I am using whatever version beta is coming from the sight minutes before I try each time.
My public version is FAZ R2 in c:/programs/Microsoft games...... and i can play the regular lobbies with it.
the beta is being loaded into c:\allegBeta not c:\allegBeta\FreeAllegiance.
.............................................................
also to note - i have been using dial up to play reg alleg.
ASGS will not secure the location unless the dial up is connected - otherwise it just hangs.
once i connect the dial up and login again - it says that the agc.dll is invalid.
radar
Last edited by Radar on Fri Sep 22, 2006 1:32 am, edited 1 time in total.
