FAZ R4 Beta Installer

Dogbones · Post by **Dogbones** » Tue Jun 05, 2007 1:33 am

Thanks for the installer aem. If I hope to be off dial up soon and back to broadband. Form posting is okay, painful, but okay, but downloading files and such is just to painful at the moment.

Post by **BlackViper** » Tue Jun 05, 2007 1:38 pm

dumb questions.

Once installed (installer smooth as silk) do you use the beta.exe to launch or use asgs in beta mode?

If I use the beta.exe I get a message ASGS failure. Use ASGS to launch.

If I use ASGS in beta mode I get a invalid file sig and do I wish to repair. Should I repair or am I doing something completely stupid here?

w0dk4 · Post by **w0dk4** » Tue Jun 05, 2007 1:43 pm

If you start the Allegiance_R4beta.exe, there will be no ASGS authentication needed. Maybe your v1.1 Registry Keys point to the main lobby?

AaronMoore · Post by **AaronMoore** » Tue Jun 05, 2007 1:46 pm

BV, I got those errors when I followed the manual instructions.

Not sure if this will help, but this is what I did:

I removed the other files i added before
Installed the nescesary C++ runtimes
I extracted the files into a seperated folder under allegiance, I used the installer, and pointed it to the folder, pressed install, and ran the Allegiance_R4beta.exe located in the folder I pointed the installer to.

Once I ran it, it prompted for a user to connect to the Lobby, and then I was in...

have you done anything different?

Post by **BlackViper** » Tue Jun 05, 2007 1:46 pm

What corrections needed? Yep, I just realized it takes me to the normal MOTD screen.

Post by **BlackViper** » Tue Jun 05, 2007 2:01 pm

NM, got it. Allguard.exe had to be deleted.

parcival · Post by **parcival** » Tue Jun 05, 2007 2:15 pm

BlackViper wrote:QUOTE (BlackViper @ Jun 5 2007, 05:01 PM) NM, got it. Allguard.exe had to be deleted.

You cannot login with ASGS yet because the R4 Beta executable has a new hash but ASGS is using an old one.
(Pook or TE need to update the hash, although there is no real need, yet)

Dogbones · Post by **Dogbones** » Tue Jun 05, 2007 3:44 pm

Yep, run it WITHOUT ASGS for now. We are (or are going to) be updating the executable frequently so it does not make sense to use update the hash's yet.

I guess we need to be more clear on when and when not to use ASGS. As a rule of thumb, always try running the beta executable directly (without ASGS) first, and if you get the error message saying you need to use ASGS, relaunch using ASGS in beta mode. This should cover you in all (or at least most) cases.

Dogbones · Post by **Dogbones** » Wed Jun 06, 2007 2:17 pm

There is a new client http://fazdev.alleg.net/FAZ/Allegiance_R4beta.zip
We will likely have ASGS turned on for tonights test.

Just replace the current beta Allegiance.exe with the one in the above zip, then use ASGS beta mode.

DO NOT repair the executable. If it asks you to either make sure you have the latest beta, or try launching the beta without ASGS.

Things are in flux so bear with us.

Post by **aem** » Wed Jun 06, 2007 5:14 pm

Dogbones wrote:QUOTE (Dogbones @ Jun 6 2007, 10:17 AM) There is a new client http://fazdev.alleg.net/FAZ/Allegiance_R4beta.zip
We will likely have ASGS turned on for tonights test.

Just replace the current beta Allegiance.exe with the one in the above zip, then use ASGS beta mode.

DO NOT repair the executable. If it asks you to either make sure you have the latest beta, or try launching the beta without ASGS.

Things are in flux so bear with us.

could you swap the new client into your zip file? Shouldn't have to download the old one then replace it with the new one if this is their first time downloading R4.