32 bit registry path (xfire detection)

[Distiler]

Yo!

 

Can anybody help me here with an xfire thing please? I'm trying to make those Xfire folks fix automatic detection for FC2 and DCS:Ka-50 ( http://www.xfire.com/forums/182686/topic/2231485/ )

 

What is the path for DCS:Ka-50 32bit OS registry? for 64 bit is:

 

LauncherDirKey=HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Eagle Dynamics\BlackShark\Path

 

(the "Wow6432Node" part is the 64-32 bit translator in 64bit Windows)

Edited February 12, 2011 by Distiler

[Distiler]

oh lol, solved, you don't need the \wow6432 Node\ in the path for either the 32 or 64 bit OS. If anybody wants to try, here's the modifications to xfire_games.ini

 

[5774]
LongName=DCS: Black Shark
ShortName=dcsbs
LauncherDirKey=HKEY_LOCAL_MACHINE\SOFTWARE\Eagle Dynamics\BlackShark\Path
LauncherExe=\bin\x86\stable\launcher.exe
DetectExe=\bin\x86\stable\simulator.exe
Launch=%UA_LAUNCHER_EXE_PATH% %UA_LAUNCHER_EXTRA_ARGS% %UA_LAUNCHER_NETWORK_ARGS%
InGameRenderer=D3D9
InGameFlags=USE_PRESENT|ENABLE_MOUSE

[4201]
LongName=Lock On Flaming Cliffs 2
ShortName=lomac 
LauncherDirKey=HKEY_LOCAL_MACHINE\Software\Eagle Dynamics\LockOn Flaming Cliffs 2\Path\Path
LauncherExe=\bin\x86\stable\launcher.exe
DetectExe=\bin\x86\stable\simulator.exe
Launch=%UA_LAUNCHER_EXE_PATH% %UA_LAUNCHER_EXTRA_ARGS% %UA_LAUNCHER_NETWORK_ARGS%
InGameRenderer=D3D9
InGameFlags=USE_PRESENT|ENABLE_MOUSE

Edited February 12, 2011 by Distiler

[Distiler]

I'm still not sure why I can exchange HKEY_CURRENT_USER\Software\Eagle Dynamics\LockOn Flaming Cliffs 2\Path\Path by HKEY_LOCAL_MACHINE\Software\Eagle Dynamics\LockOn Flaming Cliffs 2\Path\Path and still works. The first one is the real path, I guess "local machine paths" is refered somehow to all "current users". Never quite understood the registry XD