I'm preparing the Macromedia Studio 8 MSIs for deployment in an environment where (roaming) users are fairly restricted from writing to the hard drive. When Fireworks 8 is launched by a non admin user, it reports that it wants to write to the HKLM registry. I've found that the installer package inserts the Path value as:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\Fireworks.exe
Path=C:\Program Files\Macromedia\Fireworks 8\

However, Fireworks is looking for C:\Program Files\Macromedia\Fireworks 8 when it launches. Within the MSI, the key value is [INSTALLDIR]. So my question is, how can I call the INSTALLDIR property from the registry table, without the \ at the end?

0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity


Are you sure this is the problem - if you remove the trailing \ from the registry after you've installed your package does the application run OK?

Similarly if you install the vendor package then add a trailing \ does it fail?

If this is the cause of the problem and you don't want to hard code the path in the registry (which you probably don't) then I guess you could have a new property (e.g. MYINSTALLDIR) to use with a vb script custom action - pick up the INSTALLDIR value then remove the trailing \ and write the value back to the MYINSTALLDIR property then use [MYINSTALLDIR] in the registry table.

If course you'd need to sequence this CA in the correct place to that MYINSTALLDIR is correct before the MSI starts writing reg values..

There maybe better / easier solutions - interesting post!

Hope this helps,
Answered 10/25/2005 by: MSIPackager
Third Degree Black Belt

Please log in to comment
Indeed. If I remove the '\', no error message. Put it back and the error occurs again.

Yeah, I was afraid it was going to be a bit more involved than I'd like. I think I'll leave it hard-coded in the transform as the package will be deployed with no user interface, so it's very unlikely it will ever be installed anywhere other than the current default.

Thanks for your help.
Answered 10/25/2005 by: meastaugh1
Senior Purple Belt

Please log in to comment