About austin2359

austin2359 · ‎Oct 28, 2010

It was a long solution, but my eventual solution was to design a vbscript that set the focus (and this required paying attention to timing with "wait statements" and using shortcut keys before setting the window). The vbscript would not execute as a custom action, but I included it as a hidden prerequisite, then kill it with a custom action. To launch it, I need a "launcher" script command line as it loops and "looks" for the window, so the "exit code" will not return while it is looping and it will hold up the install. Then it activates the window as soon as it appears.

austin2359 · ‎Oct 21, 2010

rrinblue22 wrote: In that case you can opt to install only the prerequisite silently Well the problem with this is anti-viruses sometimes mistake the silent install for a virus. I'd like to be able to change the focus when the prerequisite is launched. I'm still not sure how.

austin2359 · ‎Oct 20, 2010

rrinblue22 wrote: I think this should be on Win7 or Vista. I'm not sure if this can be controlled at the prerequisite phase, but can be handled during installation using LaunchApp with specific parameters. A way to get around this is to use silent install (if possible), but that has its drawbacks.

austin2359 · ‎Oct 18, 2010

Can this be influenced in installshield? While installing a prerequisite, sometimes the original installer sits on top, which confuses the end user. Ie I install program "a" and it calls program "b" as a prerequisite. But the dialogue window for "a" still sits on top, and confuses the user

austin2359 · ‎Oct 12, 2010

We changed our strategy. On an install, there will be no messagebox if the user already has it. The prereq will just be skipped. If the user does not have it, however, they have the option of saying no. This is done in case the user has a newer version of the product. IE they have version 5.x, you don't want to force them to install version 4.x. So they get an option. But they no longer get an option if they already have the same version. The message box was getting truncated, but we simply shortened the message.

austin2359 · ‎Oct 11, 2010

DebbieL wrote: The strings on the setup prerequisite dialog are not editable from within InstallShield, but you can edit them in the InstallShield Program Files Folder\Support\0x****.ini files before building the release. The English strings are in the 0x0409.ini file. The particular string you are asking about is 1669. I hope that helps. By any chance, can the cut off limit be increased to hold more text in these built in dialogues?

austin2359 · ‎Oct 07, 2010

I get these 14 errors when requiring dot net framework 4.0 (and reversing a 3.5 requirement), for download in the redistributales in installshield : ISDEV : error -1007: Cannot copy source 'C:\Program Files\InstallShield\2010\SetupPrerequisites\Windows Installer\3.1\x86\WindowsInstaller-KB893803-v2-x86.exe' to target 'C:\InstallShield 2010 Projects\productname PM\productname_A16_Build_1.6.0.1\PROJECT_ASSISTANT\SINGLE_MSI_IMAGE\DiskImages\DISK1\ISSetupPrerequisites\{57bcd1d4-2de9-49d9-bc0c-3f4263e9970e}\WindowsInstaller-KB893803-v2-x86.exe' ISDEV : error -5054: Could not determine the size of the file "C:\InstallShield 2010 Projects\productname PM\productname_A16_Build_1.6.0.1\PROJECT_ASSISTANT\SINGLE_MSI_IMAGE\DiskImages\DISK1\ISSetupPrerequisites\{57bcd1d4-2de9-49d9-bc0c-3f4263e9970e}\WindowsInstaller-KB893803-v2-x86.exe" ISDEV : error -1007: Cannot copy source 'C:\Program Files\InstallShield\2010\SetupPrerequisites\WindowsImagingComponent\x86\wic_x86_enu.exe' to target 'C:\InstallShield 2010 Projects\productname PM\productname_A16_Build_1.6.0.1\PROJECT_ASSISTANT\SINGLE_MSI_IMAGE\DiskImages\DISK1\ISSetupPrerequisites\{2A0CC195-B3AF-4B63-8F5C-1F88A7E28ADF}\wic_x86_enu.exe' ISDEV : error -5054: Could not determine the size of the file "C:\InstallShield 2010 Projects\productname PM\productname_A16_Build_1.6.0.1\PROJECT_ASSISTANT\SINGLE_MSI_IMAGE\DiskImages\DISK1\ISSetupPrerequisites\{2A0CC195-B3AF-4B63-8F5C-1F88A7E28ADF}\wic_x86_enu.exe" ISDEV : error -1007: Cannot copy source 'C:\Program Files\InstallShield\2010\SetupPrerequisites\Windows Installer\3.1\x86\WindowsServer2003-KB898715-x86-enu.exe' to target 'C:\InstallShield 2010 Projects\productname PM\productname_A16_Build_1.6.0.1\PROJECT_ASSISTANT\SINGLE_MSI_IMAGE\DiskImages\DISK1\ISSetupPrerequisites\{57bcd1d4-2de9-49d9-bc0c-3f4263e9970e}\WindowsServer2003-KB898715-x86-enu.exe' ISDEV : error -5054: Could not determine the size of the file "C:\InstallShield 2010 Projects\productname PM\productname_A16_Build_1.6.0.1\PROJECT_ASSISTANT\SINGLE_MSI_IMAGE\DiskImages\DISK1\ISSetupPrerequisites\{57bcd1d4-2de9-49d9-bc0c-3f4263e9970e}\WindowsServer2003-KB898715-x86-enu.exe" ISDEV : error -1007: Cannot copy source 'C:\Program Files\InstallShield\2010\SetupPrerequisites\WindowsImagingComponent\x64\wic_x64_enu.exe' to target 'C:\InstallShield 2010 Projects\productname PM\productname_A16_Build_1.6.0.1\PROJECT_ASSISTANT\SINGLE_MSI_IMAGE\DiskImages\DISK1\ISSetupPrerequisites\{7CF06819-7AA4-4e3e-AC77-07931178671B}\wic_x64_enu.exe' ISDEV : error -5054: Could not determine the size of the file "C:\InstallShield 2010 Projects\productname PM\productname_A16_Build_1.6.0.1\PROJECT_ASSISTANT\SINGLE_MSI_IMAGE\DiskImages\DISK1\ISSetupPrerequisites\{7CF06819-7AA4-4e3e-AC77-07931178671B}\wic_x64_enu.exe" ISDEV : error -1007: Cannot copy source 'C:\Program Files\InstallShield\2010\SetupPrerequisites\Windows Installer\3.1\ia64\WindowsServer2003-KB898715-ia64-enu.exe' to target 'C:\InstallShield 2010 Projects\productname PM\productname_A16_Build_1.6.0.1\PROJECT_ASSISTANT\SINGLE_MSI_IMAGE\DiskImages\DISK1\ISSetupPrerequisites\{ce5f9d26-8a64-470b-a408-6d19381f5018}\WindowsServer2003-KB898715-ia64-enu.exe' ISDEV : error -5054: Could not determine the size of the file "C:\InstallShield 2010 Projects\productname PM\productname_A16_Build_1.6.0.1\PROJECT_ASSISTANT\SINGLE_MSI_IMAGE\DiskImages\DISK1\ISSetupPrerequisites\{ce5f9d26-8a64-470b-a408-6d19381f5018}\WindowsServer2003-KB898715-ia64-enu.exe" ISDEV : error -1007: Cannot copy source 'C:\Program Files\InstallShield\2010\SetupPrerequisites\Windows Installer\3.1\x64\WindowsServer2003-KB898715-x64-enu.exe' to target 'C:\InstallShield 2010 Projects\productname PM\productname_A16_Build_1.6.0.1\PROJECT_ASSISTANT\SINGLE_MSI_IMAGE\DiskImages\DISK1\ISSetupPrerequisites\{7f53ac5d-d59d-4f72-b8d3-2cc3bb6383ce}\WindowsServer2003-KB898715-x64-enu.exe' ISDEV : error -5054: Could not determine the size of the file "C:\InstallShield 2010 Projects\productname PM\productname_A16_Build_1.6.0.1\PROJECT_ASSISTANT\SINGLE_MSI_IMAGE\DiskImages\DISK1\ISSetupPrerequisites\{7f53ac5d-d59d-4f72-b8d3-2cc3bb6383ce}\WindowsServer2003-KB898715-x64-enu.exe" ISDEV : error -1007: Cannot copy source 'C:\Program Files\InstallShield\2010\SetupPrerequisites\Windows Installer\3.1\x64\WindowsXP-KB898715-x64-enu.exe' to target 'C:\InstallShield 2010 Projects\productname PM\productname_A16_Build_1.6.0.1\PROJECT_ASSISTANT\SINGLE_MSI_IMAGE\DiskImages\DISK1\ISSetupPrerequisites\{531950bf-fab7-4434-8ca7-b5893ab197f8}\WindowsXP-KB898715-x64-enu.exe' ISDEV : error -5054: Could not determine the size of the file "C:\InstallShield 2010 Projects\productname PM\productname_A16_Build_1.6.0.1\PROJECT_ASSISTANT\SINGLE_MSI_IMAGE\DiskImages\DISK1\ISSetupPrerequisites\{531950bf-fab7-4434-8ca7-b5893ab197f8}\WindowsXP-KB898715-x64-enu.exe" Yet amazingly, the install at least initially seems to work fine. Are there serious red flag?

austin2359 · ‎Oct 01, 2010

my final resolution was just to have one installer create registry entries while it runs, and have the other read them and not execute certain parts based on if statements.

austin2359 · ‎Sep 30, 2010

I'd be satisified to even know how to detect that two installations are running at once. Ideally I'd know the function used to launch the second install, but I'd be happy just to know the total number of installs taking place in windows. Where can I get that, so that a custom action can operate a conditional? Is there a way to do this without looking at the task manager?

austin2359 · ‎Sep 29, 2010

Is there a way to detect that an installer was called by another installer, using the "uninstallapplication()" command, and skip a custom action inside that second installer? The only thing I can think of is reading and writing registry/ini files as to alert the second installer that the first installer called it using the ua() command. Is there a better way to pass this information, and thus effect the custom action logic of the second installer. Whether I do this by an if statement or an "Install UI Condition" does not matter to me.

austin2359 · ‎Sep 28, 2010

Custom actions can use installscript. That is what I meant. In MSI.

austin2359 · ‎Sep 27, 2010

Does anyone know of a conditional to put into an if statement which executes if the OS is 64 bit, but does not execute otherwise, in installscript? I haven't found anything yet.

austin2359 · ‎Sep 24, 2010

I finally solved it. LAAW_OPTION_NOWAIT instead of LAAW_OPTION_WAIT, and move it to the very end of the custom action sequence.

austin2359 · ‎Sep 24, 2010

Perhaps a vbscript could be launched at the very end, as opposed to an installscript, so that when the second uninstallation starts, the first is already concluded.

austin2359 · ‎Sep 23, 2010

"Error Message" wrote: Another program is being installed. Please wait until that installation is complete, and then try installing this software again. I've tried a few different settings. Deferred, immediate, commit, etc. I've tried different locations in the exec sequence. I've tried different locations in the ui sequence. I've tried asynchronous, synchronous, etc. This strategy has worked uninstalling other programs, but not this one. Any advice?

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

Re: Positioning Prerequisite install window on top of base installer

Re: Positioning Prerequisite install window on top of base installer

Re: Positioning Prerequisite install window on top of base installer

Positioning Prerequisite install window on top of base installer

Re: Prerequisite won't install : "won't download" but I don't want to download

Re: Prerequisite won't install : "won't download" but I don't want to download

Dot Net 4 included as download prerequisite; 14 errors follow but still works

Re: Want a custom action to skip if installer is called by "uninstallapplication()"

Re: Want a custom action to skip if installer is called by "uninstallapplication()"

Want a custom action to skip if installer is called by "uninstallapplication()"

Re: custom action condition to reveal if operating system (not cpu necessarily) is 64 bit

custom action condition to reveal if operating system (not cpu necessarily) is 64 bit

Re: Uninstall via custom action blocked by original uninstall

Re: Uninstall via custom action blocked by original uninstall

Uninstall via custom action blocked by original uninstall

Re: Positioning Prerequisite install window on top of base installer

Re: Positioning Prerequisite install window on top of base installer

Re: Positioning Prerequisite install window on top of base installer

Positioning Prerequisite install window on top of base installer

Re: Prerequisite won't install : "won't download" but I don't want to download

Re: Prerequisite won't install : "won't download" but I don't want to download

Dot Net 4 included as download prerequisite; 14 errors follow but still works

Re: Want a custom action to skip if installer is called by "uninstallapplication()"

Re: Want a custom action to skip if installer is called by "uninstallapplication()"

Want a custom action to skip if installer is called by "uninstallapplication()"