FAZ R5 update/repair critical files

Questions / Announcements area for beta tests of Allegiance's future updates.
Post Reply
scorpion69
Posts: 9
Joined: Thu Jun 15, 2006 7:00 am

Post by scorpion69 »

Hi,

I just tried to install the R5 Beta according to these descriptions:

HSharps announcement
FAZ R5 info

When I try: "Start ASGS in beta mode and repair/update critical files then launch"
ASGS runs into this exception and just stops (no update):

CODE
************** Ausnahmetext **************
System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
bei ASGSUpdate.RegistryAdapter.GetValue(RegistrySection Section, String Key, String Item, String DefaultValue)
bei ASGSUpdate.Form1.CreateWebService()
bei ASGSUpdate.Form1.InitUpdate()
bei System.Windows.Forms.Form.OnLoad(EventArgs e)
bei System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
bei System.Windows.Forms.Control.CreateControl()
bei System.Windows.Forms.Control.WmShowWindow(Message& m)
bei System.Windows.Forms.Control.WndProc(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Geladene Assemblys **************
mscorlib
Assembly-Version: 2.0.0.0.
Win32-Version: 2.0.50727.1434 (REDBITS.050727-1400).
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll.
----------------------------------------
ASGSUpdate
Assembly-Version: 2.2.3337.16843.
Win32-Version: 2.2.3337.16843.
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Games/Allegiance/ASGSUpdate.exe.
----------------------------------------
System.Windows.Forms
Assembly-Version: 2.0.0.0.
Win32-Version: 2.0.50727.1434 (REDBITS.050727-1400).
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll.
----------------------------------------
System
Assembly-Version: 2.0.0.0.
Win32-Version: 2.0.50727.1434 (REDBITS.050727-1400).
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll.
----------------------------------------
System.Drawing
Assembly-Version: 2.0.0.0.
Win32-Version: 2.0.50727.1434 (REDBITS.050727-1400).
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll.
----------------------------------------
Microsoft.VisualBasic
Assembly-Version: 8.0.0.0.
Win32-Version: 8.0.50727.1434 (REDBITS.050727-1400).
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll.
----------------------------------------
System.Web.Services
Assembly-Version: 2.0.0.0.
Win32-Version: 2.0.50727.1434 (REDBITS.050727-1400).
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Web.Services/2.0.0.0__b03f5f7f11d50a3a/System.Web.Services.dll.
----------------------------------------
System.Data
Assembly-Version: 2.0.0.0.
Win32-Version: 2.0.50727.1434 (REDBITS.050727-1400).
CodeBase: file:///C:/Windows/assembly/GAC_64/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll.
----------------------------------------
System.Xml
Assembly-Version: 2.0.0.0.
Win32-Version: 2.0.50727.1434 (REDBITS.050727-1400).
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll.
----------------------------------------
mscorlib.resources
Assembly-Version: 2.0.0.0.
Win32-Version: 2.0.50727.1434 (REDBITS.050727-1400).
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll.
----------------------------------------
System.Windows.Forms.resources
Assembly-Version: 2.0.0.0.
Win32-Version: 2.0.50727.1434 (REDBITS.050727-1400).
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms.resources/2.0.0.0_de_b77a5c561934e089/System.Windows.Forms.resources.dll.
----------------------------------------


Sorry, but I don't know the proper translation of the german error messages into english error messages.
But "Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt." means something like
"the object reference couldn't be linked to an object instance"

I suspect this is some kind of Vista64 issue. On my system, the Allegiance registry key path is not
HKEY_LOCAL_MACHINE, SOFTWARE\Microsoft\Microsoft Games\Allegiance\1.0
HKEY_LOCAL_MACHINE, SOFTWARE\Microsoft\Microsoft Games\Allegiance\1.1

but
HKEY_LOCAL_MACHINE, SOFTWARE\Wow6432Node\Microsoft\Microsoft Games\Allegiance\1.0
HKEY_LOCAL_MACHINE, SOFTWARE\Wow6432Node\Microsoft\Microsoft Games\Allegiance\1.1


Any advice what I need to do?

Regards,
Scorp


P.S.: my system stats

Windows Version (and Service Packs): Windows Vista 64Bit Home Premium (6.0, Build 6001) + SP1
Processor Speed: Intel® Core™2 Quad CPU Q9300 @ 2.50GHz (4CPUs), ~2.5GHz
RAM: 4094MB
Video Card (Make and Model#): NVIDIA GeForce 8800 GTS 512 (2 Cards, SLI mode), Driver Version 7.15.0011.8120
Sound Card (Make and Model#): Realek High Definition Audio (on Board)
Connection Type (Dialup, Cable, DSL, other): DSL
Modem (Make and Model#): Teledat 331 LAN
Router (Make and Model#): Belkin 4 Port Router
Internet Service Provider(company name): GMX
Location(State/Province/Locality, and Country): Germany
Installed Mods: CortUI

Make and Version of firewall: Windows Firewall
Make and version of anti-virus: Avira AntiVir Personal 9.0.0.403, 03.06.2009



fuzzylunkin1

Post by fuzzylunkin1 »

Have you run MadP's beta switcher? If not, run it (and make sure to run it as Administrator).

Then you should be able to proceed normally, if I understand your error properly. I did the same thing today with Vista x64.


EDIT:
Fixed a spelling error.
Last edited by fuzzylunkin1 on Thu Jun 25, 2009 9:57 am, edited 1 time in total.
scorpion69
Posts: 9
Joined: Thu Jun 15, 2006 7:00 am

Post by scorpion69 »

fuzzylunkin1 wrote:QUOTE (fuzzylunkin1 @ Jun 25 2009, 11:54 AM) Have you run MadP's beta switcher? If not, run it (and make sure to run it as Administrator).
I tried, but it didn't work on my system. The betaswitch.ahk searches the regisrtry keys at
HKEY_LOCAL_MACHINE, SOFTWARE\Microsoft\Microsoft Games\Allegiance\1.0

and those keys don't exist on my system.

Beta registry keys already exist at
HKEY_LOCAL_MACHINE, SOFTWARE\Wow6432Node\Microsoft\Microsoft Games\Allegiance\1.1

So I manually changed the key CfgFile to http://fazdev.alleg.net/FAZ/FAZR5.cfg and tried the ASGS update/repair


Funny thing is, I can switch ASGS to beta mode and launch Allegiance, connect to the Beta server and even create a game.
It crashes when I launch the game, most likely because I'm missing the updates.
But it seems to me the registry keys for the Beta are at the proper place.
Otherwise I assume that all these things shouln't work at all (shouldn't find the allegiance.exe beta build for example).



Zapper
Posts: 1306
Joined: Sat Jan 29, 2005 8:00 am
Location: Denmark

Post by Zapper »

scorpion69 wrote:QUOTE (scorpion69 @ Jun 25 2009, 12:29 PM) I tried, but it didn't work on my system. The betaswitch.ahk searches the regisrtry keys at
HKEY_LOCAL_MACHINE, SOFTWARE\Microsoft\Microsoft Games\Allegiance\1.0

and those keys don't exist on my system.

Beta registry keys already exist at
HKEY_LOCAL_MACHINE, SOFTWARE\Wow6432Node\Microsoft\Microsoft Games\Allegiance\1.1

So I manually changed the key CfgFile to http://fazdev.alleg.net/FAZ/FAZR5.cfg and tried the ASGS update/repair


Funny thing is, I can switch ASGS to beta mode and launch Allegiance, connect to the Beta server and even create a game.
It crashes when I launch the game, most likely because I'm missing the updates.
But it seems to me the registry keys for the Beta are at the proper place.
Otherwise I assume that all these things shouln't work at all (shouldn't find the allegiance.exe beta build for example).
In the 1.1 registry, where is the "Exe Path" and "ArtPath" pointing??
Do you have a seperate folder for the Beta allegiance.exe??
Life suck's and then u play Alleg.
-.. ..- -.- . -. ..- -.- . .----. . -- .. ... - .... . --. .-. . .- - . ... -
Image
scorpion69
Posts: 9
Joined: Thu Jun 15, 2006 7:00 am

Post by scorpion69 »

Zapper wrote:QUOTE (Zapper @ Jun 25 2009, 12:49 PM) In the 1.1 registry, where is the "Exe Path" and "ArtPath" pointing??
ArtPath = C:\Program Files (x86)\Microsoft Games\Allegiance\Artwork
EXE Path = C:\Program Files (x86)\Microsoft Games\Allegiance\beta
Zapper wrote:QUOTE (Zapper @ Jun 25 2009, 12:49 PM) Do you have a seperate folder for the Beta allegiance.exe??
Yes.
The regular allegiance.exe is in C:\Program Files (x86)\Microsoft Games\Allegiance
The Beta is in C:\Program Files (x86)\Microsoft Games\Allegiance\beta


But the exception occurs with ASGSUpdate.exe and not with allegiance.exe.
The Beta will probably work fine if I can do manually the things that "update/repair critical files" should do.



Zapper
Posts: 1306
Joined: Sat Jan 29, 2005 8:00 am
Location: Denmark

Post by Zapper »

I see the problem... Do you have a dev folder in the artwork folder?? and/or do you have the Artwork which is required with the new Beta.
Make sure you have the artwork from the zip in this post http://www.freeallegiance.org/forums/index...showtopic=44386

Make sure you have a the dev folder in the retail/regular artwork folder and that it contain the artwork from the artwork zip..

Missing artwork crashes Alleg.

Z
Life suck's and then u play Alleg.
-.. ..- -.- . -. ..- -.- . .----. . -- .. ... - .... . --. .-. . .- - . ... -
Image
scorpion69
Posts: 9
Joined: Thu Jun 15, 2006 7:00 am

Post by scorpion69 »

I put those artwork files in the dev folder. Now the Beta seems to be running fine.

Thanks Zapper! :iluv:



Adam4
Posts: 2144
Joined: Sun Sep 03, 2006 9:05 am
Location: England

Post by Adam4 »

Wow64 is Windows x64's x86 emulator.
Adam4
Posts: 2144
Joined: Sun Sep 03, 2006 9:05 am
Location: England

Post by Adam4 »

This was also an issue for me, running an x64 system.

Solution:

Copy the entire HKEY_LOCAL_MACHINE, SOFTWARE\Wow6432Node\Microsoft\Microsoft Games\Allegiance\ branch.

Manually edit the file, and remove all instances of Wow6432Node, so addresses should read: HKEY_LOCAL_MACHINE, SOFTWARE\Microsoft\Microsoft Games\Allegiance\1.1

Merge the information into the registry.

Should work.
Post Reply