clock for blog

Office Hours
Mon-Fri 09:00-21:00

Knowledgebase
Are Smartlaunch PUFs compatible with Gizmo's?
Posted by Panagiotis Mantzouranis on 07 February 2012 06:31 PM

PUF that store files and folders

Smartlaunch PUF that configured to save files are fully compatible with Gizmo PUF system. Move the PUF zip files of each user to store Gizmo PUF directory

 

PUF that store registry keys

Smartlaunch saves registry PUFs as regular .reg files.

Gizmo, on the other hand, saves them as zip files.

 

This makes Smartlaunch's registry PUF files incompatible with Gizmo's. For that reason we created a tool (Download Link)

that compresses .reg files into .zip, making them Gizmo compatible. Please run it once before starting using Gizmo client and point it to the folder containing user's PUF files

(usually c:\Program Files\Smartlaunch\Server\Data\Users\)

Check "Delete found registry files" ONLY if you are migrating permanently to Gizmo and want to delete .reg files after the conversion.

 

Another point you should take notice is when you have been using 64 bit OS for your client PCs (Vista 64bit & 7 64bit). All 32bit apps are redirected to Wow6432Node for storing registry info.

For example, although Call of duty 4 stores its cd key in HKEY_LOCAL_MACHINE\SOFTWARE\Activision\Call of Duty 4 , in 64bit OS this is redirected to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Νode\Activision\Call of Duty 4

In the same way, since smartlaunch client is 32bit, if you configure a registry PUF in Smartlaunch with the path HKEY_LOCAL_MACHINE\SOFTWARE\Activision\Call of Duty 4, smartlaunch will actually save the Wow6432Node path instead. If you then open the registry puf, you will see that the info point to the HKEY_LOCAL_MACHINE\SOFTWARE\Activision\Call of Duty 4.

Gizmo, being a true 64bit application, is not redirected to the Wow6432Node. When configuring a puf in Gizmo, you should always point it to the actual registry location (inside the Wow6432Νode) And since the old pufs will not contain that information, they will not be installed inside Wow6432Νode. Use the following workaround to succesfully complete the migration of your registry pufs to Gizmo (after using the tool above)

  • Create a new task for each game that saves puf registry. (Type: batch script, pre-license)
  • Add the following lines of code, replacing the paths with the ones from the game's puf:

------------------------------------------------------------CODE START------------------------------------------------------------

REG COPY "HKLM\SOFTWARE\Company name\Title" "HKLM\SOFTWARE\Wow6432Node\Company name\Title" /s /f

REG DELETE "HKLM\SOFTWARE\Company name\Title" /f

--------------------------------------------------------------CODE END--------------------------------------------------------------

For example, for Call of Duty 4:

REG COPY "HKLM\SOFTWARE\Activision\Call of Duty 4" "HKLM\SOFTWARE\Wow6432Node\Activision\Call of Duty 4" /s /f

REG DELETE "HKLM\SOFTWARE\Activision\Call of Duty 4" /f

Replace  HKLM with the appropriate path [ HKLM | HKCU | HKCR | HKU | HKCC ]

This script will copy the information from the wrong path to the right one, and then delete the wrong one. From then on, the puf will contain the correct path.

 

Q: Why don't you just configure Gizmo client as 32bit and access registry like Smartlaunch does?

A: Because then Gizmo would not have access to the 64bit part of the registry. And since 64bit applications are becoming more and more common, this would create problems.

(0 vote(s))
Helpful
Not helpful