About TurboFisch

TurboFisch · ‎Sep 13, 2017

think you need to just modify the options: if (SYSINFO.bIsWow64 != 0) then REGDB_OPTIONS = REGDB_OPTIONS | REGDB_OPTION_WOW64_64KEY; endif; and lose the WOW6432 in the specified key names

TurboFisch · ‎Aug 23, 2017

if you are running on a system with UAC, you might need this: if (SYSINFO.WINNT.bWinXP != TRUE) then LAAW_SHELLEXECUTEVERB = "runas"; endif;

TurboFisch · ‎Jun 27, 2017

even with installshield 2016, I had to change my args from: somebatch.cmd to cmd /c somebatch.cmd because of this I lose my errorlevel, which makes it difficult to know if I need to reboot or not. my batch file is used to install a device driver that call dpinst. I have tried using the device driver settings in the component before, but it wasn't working because we have a single driver that does both x32 & x64. the installshield seemed to be using the last setting entered. I haven't tried sp2, maybe that fixes the problem.

TurboFisch · ‎Jun 26, 2017

Apparently, it was added or updated in Service pack 1.

TurboFisch · ‎Jun 20, 2017

It appears that LaunchAppAndWait is failing for me when I try to execute a batch file on windows 10. Basically, doing this: if (SYSINFO.WINNT.bWinXP != TRUE) then LAAW_SHELLEXECUTEVERB = "runas"; endif; nOptions = nOptions|LAAW_OPTION_HIDDEN|LAAW_OPTION_SHOW_HOURGLASS|LAAW_OPTION_WAIT|LAAW_OPTION_USE_SHELLEXECUTE; SetStatusWindow (-1, szProgram+"("+szCmdLine+")"); nResult = LaunchAppAndWait (szProgram, szCmdLine, nOptions);

TurboFisch · ‎Jun 20, 2017

According to the SP 1 release notes: New InstallShield Prerequisites for Microsoft Visual C++ 2015 and .NET Framework 4.6 InstallShield includes new InstallShield prerequisites that you can add to Advanced UI, Basic MSI, InstallScript, InstallScript MSI, and Suite/Advanced UI projects: •Microsoft Visual C++ 2015 Redistributable Package (x86) •Microsoft Visual C++ 2015 Redistributable Package (x64) •Microsoft .NET Framework 4.6 Full •Microsoft .NET Framework 4.6 Web These prerequisites install the appropriate technologies on supported target systems. But they don't show up in my redistributable. The only this that the redistributable downloader shows are the language packs that I don't care about. So HOW to I get these updated?

TurboFisch · ‎May 24, 2017

So what is the problem that you are trying to solve?

TurboFisch · ‎May 18, 2017

associated it to the feature, that should be after the license step

TurboFisch · ‎May 18, 2017

why doesn't Visual studio 2015 prerequisites show up? I thought that this would be in by default on IS 2015.

TurboFisch · ‎Mar 03, 2017

Installshield 2015 fixes this issue. maybe Installshield 2014, but I haven't tried that.

TurboFisch · ‎Feb 27, 2017

It appears that the issue is directly related to the "Cache MSI Locally" property. If it is on it fails use the correct directory. If it is off then the installation path changes to windows\temp and everything works. Since my customer's use of is only using SCCM, then I don't need to cache and enable the repair option. Now I'm on the hunt for a property that will disable the "cache msi locally" from the command-line or set it via custom action when the user is system

TurboFisch · ‎Feb 27, 2017

Found a post in 2011. Apparently, this has never been fixed.

TurboFisch · ‎Feb 27, 2017

Apparently, this has not been fixed in 2013 either.

TurboFisch · ‎Feb 15, 2017

you'll want to use the command line interface. I use the .ini file approach.

TurboFisch · ‎Jan 26, 2017

Many desktop management tools are starting to install via the system account. In my case my installer fails. The log yields this: MSI (s) (80:44) [20:59:20:956]: Note: 1: 2203 2: C:\Windows\system32\config\systemprofile\AppData\Local\Downloaded Installations\{2A799340-820C-4C05-8DDE-26CA1B685CB8}\Awesome_App.msi 3: -2147287037 This error means that the file was not found. It looks like the installer is not looking in the right place: C:\Windows\SysWOW64\config\systemprofile\AppData\Local\Downloaded Installations\{2A799340-820C-4C05-8DDE-26CA1B685CB8}\Awesome_App.msi Is there a setting that controls where it should look for the extracted msi file? Usually, this location is for cached installers so that the repair function will work. Thanks,

Online Status	Offline
Date Last Visited	‎Mar 18, 2019 12:11 PM

Re: Strange behavior when reading a value from windows registry

Re: Laaw_parameters

Re: launchappandwait faiing on windows 10

Re: why doesn't Visual studio 2015 prerequisites show up?

launchappandwait faiing on windows 10

Re: why doesn't Visual studio 2015 prerequisites show up?

Re: Real Support for the Desperate

Re: How to install Prerequists at the end of Instalaltion.

why doesn't Visual studio 2015 prerequisites show up?

Re: installing as system account uses the wrong directory

Re: installing as system account uses the wrong directory

Re: installing as system account uses the wrong directory

Re: Install failure in Windows64 bit in System Account

Re: Set Product_version at runtime

installing as system account uses the wrong directory

Re: Strange behavior when reading a value from windows registry

Re: Laaw_parameters

Re: launchappandwait faiing on windows 10

Re: why doesn't Visual studio 2015 prerequisites show up?

launchappandwait faiing on windows 10

Re: why doesn't Visual studio 2015 prerequisites show up?

Re: Real Support for the Desperate

Re: How to install Prerequists at the end of Instalaltion.

why doesn't Visual studio 2015 prerequisites show up?

Re: installing as system account uses the wrong directory