Hi Yes, it'll be choosing based on the hard disk with the most free space. It's related to the way your TARGETDIR is resolving. check out ROOTDRIVE property.. By adding a ROOTDRIVE property with a value of C:\ will force the msi to always install to C: ... View more

Hi ARP is controlled by the registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{Your ProductCode} What ever is in the UninstallString entry within this key will be what gets run when you click Remove in ARP (usually this will be 'msiexec /x{Your ProductCode}' There are some options you can play around with in InstallShields 'General Information > Add or Remove Programs' section but these are limited to that of what is allowed to be changed by Windows Installer. If adjusting these don't give your the behaviour you want then a way around it is to create a new uninstall registry key with the minimum entries of 'DisplayName' & 'UninstallString' and supress the original Windows Installer entry from appearing in ARP Key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\[ProductName] String Entries: DisplayName = "[ProductName]" UinstallString = "[INSTALLDIR]setupfolder\setup.exe" To supress the Windows Installer default ARP entry, add a property ARPSYSTEMCOMPONENT=1 to the MSI. The only issue with the above method is that you would need to have setup.exe in a permanently accessible location to the user. An uninstall string of UnistallString = "msiexec /i {Your ProductCode}" might be a safer bet. ... View more

I don't think there is any deny option. A standard Lockpermissions table will only give you use of a combination of Read / Write / Execute permissions. Not exactly sure what you are trying to achieve, but you could set full permissions for a given folder to only the System account, which would pretty much deny access to this folder for everyone else..? i.e: LockObject - Table - Domain - User - Permission INSTALLDIR - CeateFolder - (Null) - SYSTEM - 268435456 ... View more

it may be worth doing a find in the Direct Editor for "7.6.1" in-case its listed in any of the ISBuildSourcePath columns (you may have already done this). If not, and the only reference to 7.6.1 is in your Media>Releases, then using the Release Wizard you could try to build a new release (different product configuration) and see what happens. ... View more

Have you checked the 'Path Variables' section in InstallShield? Sometimes there can be some rouge references in there.. ... View more

Hi Each file in your .cab file needs a reference in the File Table. For that reason I don't think you'll be able to get one file in a cab file extracted to two different folders as you can only list one directory for each file in the File Table. As for updating the existing .cab; not impossible (you'll need to find a tool that will let you edit .cab files -e.g. Microsoft have an SDK), but i wouldn't recommend this approach. Personally, for repackaging an app I steer away from compressed cab source files where possible. I'd first create an admin install point from the MSI: (msiexec /a ). This will give you an MSI source folder with the extracted files and MSI. In your InstallShield Transform 'Files and Folders', create your additional required folder structure and just drag and drop the file from your MSI source folder into your new folder in 'Files and Folders'. InstallShield should do the rest. Cleanest way i can think of without scripting.. ... View more

73. Ability to select (and delete) multiple components in the Setup Design view. i.e when there's 20 components to delete from project it gets a little tedious with the click, delete, click, delete... ... View more

32. English (United Kingdom) language ..yes Flexera, Enterprise environments DO localise their system builds and this gets picked up in repackager .ism's and triggers an "unsupported language" message when opening in InstallShield. ... View more

Hi, to help with some logic behind this; Windows Installer by default will create an ARP entry for each MSI installed. If you have ARPSYSTEMCOMPONENT set to 1, the default ARP entry will still be created but will be 'hidden' and not appear in the ARP list. The usual reasons you would set the ARPSYSTEMCOMPONENT property are either.. a) you don't want an entry to appear in the ARP list, or b) you want to customise the handling of the uninstallation of your application. If you wanted option b), you would achieve this via setting the ARPSYSTEMCOMPONENT (to hide the default ARP entry) and add your own registry entries that would create your custom ARP entry. If you were then to remove the ARPSYSTEMCOMPONENT property from the above example, you will end up with your custom ARP entry and also the default windows installer ARP entry - two ARP entries! More than likely you also have custom ARP entries being set in your registry table; check your registry table for keys being created to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall If they exist, you can either take them out and let Windows Installer handle the ARP entry, or if they are required add the property ARPSYSTEMCOMPONENT=1 to hide the default entry. As for reason why Installshield has built your project like this - I can't answer as for a basic MSI type it should normally go with the default Windows Installer ARP behaviour. ... View more

Hi er, sorry forgot that the Quickpatch Ui is quite limiting! you may have to build to msp instead to achieve this (de-select build Update.exe in your quickpatch project) then reopen the created msp in InstallShield, which should let you edit the component attribute in Direct Editor. ... View more

Check the component attribute value for your registry key For 64bit registry components, the attribute of the component should be 260. (256 is the 64bit attribute + 4 for registry) ... View more

Hi For an application packager a standalone MSI is always a nice to have 😄 , but any application packager should be able to cope with your setup.exe even if you left it as it is. However, what will definatley help is (as you mention) to include any required properties directly in your MSI property table. Also, to launch directly from an Installscript MSI, you will also need a property of ISSCRIPTDRIVEN=1 ... View more

Hmm, how about creating a new vbscript custom action to fetch the registry properties? It a little bit crude but the custom action script would be something along the lines of: Dim objShell, strKey1, strKey2 Set objShell = CreateObject("WScript.Shell") On Error Resume Next strKey1 = ObjShell.RegRead("HKLM\SOFTWARE\Wow6432Node\InstallShield\16.0\CurrentVersion") strKey2 = ObjShell.RegRead("HKLM\SOFTWARE\Wow6432Node\InstallShield\AdminStudio\ASLocation") Session.Property("REGVALUE1") = strKey1 Session.Property("REGVALUE2") = strKey2 This should push the values of your registry keys into the desired Properties (REGVALUE1 etc) which could then be referenced elsewhere in your package. I think the problem with the system search is that it is essentially returning a True or False value based on the Reglocator table and doesn't return the actual value of the key. ... View more

Hi What method are you trying to access the Wow6432Node key? Is this scripted? Is your MSI pure 32bit running on 64bit machine? This kind of thing is a right pain (thank MS!) but there are ways of achieving it ... View more