Repackage installation path
Hi,
For a Windows 7 x64 deployment I repackeged GSview and GhostScript into one package with Wise Package Studio 8. I used the x64 installations.
Both software packages are installed in c:\program files during the snapshot. Afterwards I filtered out all crap and compiled the package. Finaly I started the MSI installation and noticed the installation path is changed to c:\program files (x86). I manually changed it to c:\program files\, but the installation files are copied to c:\program files (x86).
Any suggestion how to fix this?
For a Windows 7 x64 deployment I repackeged GSview and GhostScript into one package with Wise Package Studio 8. I used the x64 installations.
Both software packages are installed in c:\program files during the snapshot. Afterwards I filtered out all crap and compiled the package. Finaly I started the MSI installation and noticed the installation path is changed to c:\program files (x86). I manually changed it to c:\program files\, but the installation files are copied to c:\program files (x86).
Any suggestion how to fix this?
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
anonymous_9363
13 years ago
As far as I'm aware, if the binaries are 32-bit - irrespective of how the MSI is set up - Windows will always put them into the X86 folder.
Posted by:
MARIN
13 years ago
On the machine where I repackaged the files, the files are located in the c:\program files\ folder.
Posted by:
anonymous_9363
13 years ago
...and that machine, I'd bet, runs Windows XP 32-bit?
Best practice is that one packages on the lowest common denominator OS, i.e. XP 32-bit.
Best practice is that one packages on the lowest common denominator OS, i.e. XP 32-bit.
Posted by:
dreyer
13 years ago
In the directory table, are you using ProgramFiles64Folder? Even if the Platform is set to AMD64 in the Summary Information of the .msi it will still place the installation files to C:\Program Files (x86) if you're using ProgramFilesFolder in the directory table.
ProgramFilesFolder TARGETDIR .:ProgramF|Program Files
ProgramFiles64Folder TARGETDIR .:ProgramF|Program Files <- must be used to install to C:\Program Files\ on x64.
It does not matter if the source executable is 32bit or 64bit, the directory table controls where the files are placed.
I may be wrong here but technically I don't think it matters whether a 64bit application is installed to C:\Program Files (x86) or C:\Program Files\, it's just a way to seperate 32 and 64bit applications for organizational purposes in case you have two versions of the same application. 32bit applications still use the 32bit emulator (WOW64) at launch regardless of which Program Files folder it's stored in.
ProgramFilesFolder TARGETDIR .:ProgramF|Program Files
ProgramFiles64Folder TARGETDIR .:ProgramF|Program Files <- must be used to install to C:\Program Files\ on x64.
It does not matter if the source executable is 32bit or 64bit, the directory table controls where the files are placed.
I may be wrong here but technically I don't think it matters whether a 64bit application is installed to C:\Program Files (x86) or C:\Program Files\, it's just a way to seperate 32 and 64bit applications for organizational purposes in case you have two versions of the same application. 32bit applications still use the 32bit emulator (WOW64) at launch regardless of which Program Files folder it's stored in.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.