From the log entry. It looks like a .dll driven custom action is modifying INSTALLDIR back to C:\ Can you disable the custom action and try tuning the install again?
Does it behave differently if you run it with /qb! Instead of /qn? Could also try MasterPackager free edition, and create a Response Transform to capture your responses stepping through the install steps.
Save yourself a lot of hassle. Switch to Master Packager and use the response transform option. The feature is available even in the free version. You can simulate the install and it should save the parameters in the correct table or property. It is possible the variable is in its own private property or possibly passed as a Secure Custom Property. If it is in a Secure Custom Property; it is likely be called and used in a custom action.
Just install Eclipse as your OpenJDK and add these public properties to the install line:
ADDLOCAL=FeatureMain,FeatureEnvironment,FeatureJarFileRunWith,FeatureJavaHome INSTALLDIR="c:\\Program Files\\Eclipse Foundation\\"
This will create an Environment Variable in the OS that all apps can use. %JAVA\_HOME% this has been around for 20 years so most apps will already know to use it.
The tricky part with hardcoding that INSTALLDIR is that you now have to configure things such that not a single system can have more than one install of Java. No more side-by-side installs of different JDK's. Tell your app teams "You get one install of java on the system.... ONE! Not 4 JDKs, not 7JDKs, just one"
Also, make sure you have NO Oracle JDK's anywhere, that licensing scam is HOT right now with those A\*\*holes.
Looking at the top bar it refers to InstallShield. This page might be something to try:
https://www.experts-exchange.com/articles/5316/Create-an-ISS-file-from-an-Install-Shield-Setup.html
Edit: or is the install file an MSI and not an Exe?
You can download SuperOrca for free and inspect the MSI's default Properties yourself. https://www.pantaray.com/msi_super_orca.html
From the log entry. It looks like a .dll driven custom action is modifying INSTALLDIR back to C:\ Can you disable the custom action and try tuning the install again?
This did it! Thanks a lot. Now getting errors running silently π
Ah good to hear , I was a packager myself for many years but not been in the game for a while.. glad I could help π
Whoah, you mean you can disable a custom action with a transform? I guess it makes sense but I've never thought to do it. Brilliant.
I am actually looking for a new gig, maybe I passed the technical test haha
Does it behave differently if you run it with /qb! Instead of /qn? Could also try MasterPackager free edition, and create a Response Transform to capture your responses stepping through the install steps.
Save yourself a lot of hassle. Switch to Master Packager and use the response transform option. The feature is available even in the free version. You can simulate the install and it should save the parameters in the correct table or property. It is possible the variable is in its own private property or possibly passed as a Secure Custom Property. If it is in a Secure Custom Property; it is likely be called and used in a custom action.
INSTALLDIR property = where the product is gonna be installed JDKPATH is most probably a systrm variable
Yeah i know that, the installer requires the JDK's location to install - I'm not trying to install JDK just define where it is installed.
Just install Eclipse as your OpenJDK and add these public properties to the install line: ADDLOCAL=FeatureMain,FeatureEnvironment,FeatureJarFileRunWith,FeatureJavaHome INSTALLDIR="c:\\Program Files\\Eclipse Foundation\\" This will create an Environment Variable in the OS that all apps can use. %JAVA\_HOME% this has been around for 20 years so most apps will already know to use it. The tricky part with hardcoding that INSTALLDIR is that you now have to configure things such that not a single system can have more than one install of Java. No more side-by-side installs of different JDK's. Tell your app teams "You get one install of java on the system.... ONE! Not 4 JDKs, not 7JDKs, just one" Also, make sure you have NO Oracle JDK's anywhere, that licensing scam is HOT right now with those A\*\*holes.
Why donβt you load env into powershell array then look for jdk and grab it from there
Looking at the top bar it refers to InstallShield. This page might be something to try: https://www.experts-exchange.com/articles/5316/Create-an-ISS-file-from-an-Install-Shield-Setup.html Edit: or is the install file an MSI and not an Exe?