I am using a wise script to deploy an application. I use the following wise command

item: Execute Program
Command Line=/s "%REG%\r18_x64.reg"

%REG% has the UNC path of the registry file

The contents of the reg file are

Windows Registry Editor Version 5.00



"DEST_FOLDER"="C:\\Program Files\\Dassault Systemes\\B18"
"DEST_FOLDER_OSDS"="C:\\Program Files\\Dassault Systemes\\B18\\win_b64"

The wise script imports the registry file to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Dassault Systemes
It should go to HKEY_LOCAL_MACHINE\SOFTWARE\Dassault Systemes

I am using Wise Script 7.0 with SP3. Please let me know what I am missing.


[align=right] [/align]
0 Comments   [ + ] Show Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


The application I am packaging is a 64-bit application for 64-bit Windows XP. The registry key that needs to be imported is a custom key for our company. The application setup is NOT an msi.
Answered 02/13/2009 by: jimcox
Orange Belt

Please log in to comment
If you're using Wise Script then WHY are you posting in this forum?

WiseScript is a 32-bit application/exe and will therefore write to the "virtual" registry.
Answered 02/13/2009 by: AngelD
Red Belt

Please log in to comment
Thanks. I thought so too, but wanted to double check. I will make a 64-bit msi for the reg. changes in WPS.
Answered 02/13/2009 by: jimcox
Orange Belt

Please log in to comment
I had to deal w/ something similar.. try calling reg.exe from %WinDir%\Sysnative
Answered 02/13/2009 by: jayteeo
Purple Belt

Please log in to comment
Answer this question or Comment on this question for clarity