Hi Shane;

  If you run the PB Packager and create an MSI, you should be able to over-ride the install location at start-up. Then just make sure that you edit the new XML file (generated by the PB IDE) so that points the App to where the RT is now installed.

Regards ... Chris

Hello,

Here is the option to change the default location.

You can change as per your choice.

Happiness Always
BKR Sivaprakash

Ok, I think my question is being misunderstood.

In order to evaluate 2019R3LTS, I need to download and install.  In order to download the install package (IDE, Compiler and Runtime) I first need to download (and run) the powerbuilder_bootstapper.exe.

Firstly, I don't get the option where to install the bootstapper as it just decides to install under 'C:\Program Files (x86)...'.  This can be tolerated as I can do this off a temp VM which overrides our policy on NOT installing onto the C drive.  Once this bootstapper is installed and and running I can choose to create an offline install package of 2019R3 and place this in a defined location.  Once this has been completed I can copy this package to our software UNC path and rollback this VM to remove all traces of the bootstrap code installed on the C drive.

Once the VM is back up and joined to domain, I can copy the 2019R3 install package back to the VM (now on domain) and begin the install.  When installing the IDE and Compiler, I get an option to change the install path HOWEVER when installing the supplied runtime package, there IS NO option to pick a location.

This is not an issue using Powerbuilder's runtime packager to produce a runtime package (which we choose to not install as part of our installation anyhow), this is an issue with the Appeon supplied Runtime package portion of the initial installation produced by the powerbuilder_bootstap.exe.

- - Shane - -

Hi,

Maybe I misunderstood the comment of Chris Pollach but I have not found an option for setting the default installation folder when packaging the runtime files using the Powerbuilder runtime packager. Only when installing the MSI file afterwards the target folder can be manually changed.

I find this is very annoying as the default location of the runtime files on a developer machine is a subfolder of C:\Program Files (x86)\Appeon\Common\PowerBuilder\ and the MSI installs them by default into C:\Program Files (x86)\Appeon\PowerBuilder Runtime Packager\ and the .xml file needs to be adjusted.

Best regards,

Bruno

Hi,

My suggestion is the following:

In the Runtime Packager it should be possible to enter the default target installation folder for the PB runtime files:

When the runtime files are installed on a client PC this should be the default location (that can be changed)

Best regards,

Bruno

Hi,

I am sorry that it appears that I hijacked this thread. My first message was a response to the message of Chris from 17 September 2021 where he wrote "If you run the PB Packager and create an MSI, you should be able to over-ride the install location at start-up!". I was not sure what he meant with "at startup" but I found the idea of indicating the default target installation location when putting together the runtime files very attractive.

When the runtime packager creates the MSI file it must anyway set the default installation location for the runtime files, so why not make it editable.

Moreover, I find the location "C:\Program Files (x86)\Appeon\Common\PowerBuilder\" much more intuitive than "C:\Program Files (x86)\Appeon\PowerBuilder Runtime Packager\" as the latter folder does not actually contain the runtime packager but the PowerBuilder runtime files. I do not know why Appeon has chosen this location, which is different to the location on a developer machine, maybe someone can explain this.

Best regards,

Bruno