Author | Topic: installation folder | |
---|---|---|
Nevzat Kanbur | installation folder on Sun, 06 Oct 2024 00:34:09 +0300 Hi, I've downloaded trial version v.2.0 and installed. It is installed to Program Files (x86) folder. But I want to ,nstall it to different folder. For ex. C:\ALASKA folder. But install does not have option to do it. any help please rgds Nevzat | |
Jan Escholt | Re: installation folder on Sun, 06 Oct 2024 15:53:07 +0200 Hi Nevzat, that is by design. But you can contact the Support, there is a way to change that. Jan Am 05.10.2024 um 23:34 schrieb Nevzat Kanbur: > Hi, > I've downloaded trial version v.2.0 and installed. > It is installed to Program Files (x86) folder. > But I want to ,nstall it to different folder. > For ex. C:\ALASKA folder. But install does not have option to do it. > > any help please > rgds > Nevzat > | |
Andreas Gehrs-Pahl | Re: installation folder on Mon, 14 Oct 2024 22:43:31 -0400 Nevzat, You can specify some public properties when doing the installation, but I'm not entirely certain that this has no repercussions for later updates. It shouldn't, but I have not tried it for a long time. The runtime parameters for msiexec.exe (the MS Installer) program include an option to set public installation properties, including the following three that specify the destination folders. Only the last one can be changed through the GUI: * PATH_PROGRAMFILES (default depends on OS) * PATH_USER (default depends on User) * PATH_WWWROOT (only one that can be changed in the GUI) To set any of those variables, just add them to the msiexec.exe call on the command line: msiexec.exe /i <x.msi> PATH_PROGRAMFILES="C:\Alaska\" PATH_USER="D:\Test\" Make sure that you include the double quotes (") around the directory names and the trailing backslash (\) for all of the directories! In older versions (before 2.00.742), all of these directories could be changed in the GUI, and they were also named differently: CMD_PROGRAMFILESFOLDER CMD_PERSONALFOLDER * CMD_AUXWWWROOT To get a list of available public properties, you can log the installation process to a log file, using various msiexec.exe /l options. There are several other public parameters that can be changed to automate the installation process, including the ADDLOCAL and REMOVE properties, with which you can determine which features are installed and which aren't. Some additional documentation on msiexec.exe can be found here: https://learn.microsoft.com/en-us/windows/win32/msi/windows-installer-guide Hope that helps, Andreas Andreas Gehrs-Pahl Absolute Software, LLC phone: (989) 723-9927 email: Andreas@AbsoluteSoftwareLLC.com web: http://www.AbsoluteSoftwareLLC.com [L]: https://www.LinkedIn.com/in/AndreasGehrsPahl [F]: https://www.FaceBook.com/AbsoluteSoftwareLLC | |
Andreas Gehrs-Pahl | Re: installation folder on Mon, 14 Oct 2024 22:47:08 -0400 Nevzat, >There are several other public parameters that can be changed to automate >the installation process, including the ADDLOCAL and REMOVE properties, with >which you can determine which features are installed and which aren't. That should read: There are several other public parameters that can be changed to automate the installation process, including the ADDLOCAL and REMOVE properties, with which you can specify which features are installed and which aren't. Andreas Andreas Gehrs-Pahl Absolute Software, LLC phone: (989) 723-9927 email: Andreas@AbsoluteSoftwareLLC.com web: http://www.AbsoluteSoftwareLLC.com [L]: https://www.LinkedIn.com/in/AndreasGehrsPahl [F]: https://www.FaceBook.com/AbsoluteSoftwareLLC |