There is however 1 problem I6comp.exe cannot read InstallShield version 5 files. The autodetect only distinguishes between different Installshield compression methods, but not the archive architecture. Orlp, thanks for all of your work on this.

This has been requested several times in the past, but I was never able to get any sample apps to use for testing. Your code looks good, and I'd certainly like to add it to the next version of UniExtract (I couldn't do it in time for 1.4.2), but I still need one or more sample apps for testing.

Could you please post a download link to an application that uses this format? Edit: After rereading your post I see that you mentioned a couple apps. Unfortunately, I don't have a copy of Photoshop, and obviously you can't post download links for it. Do you happen to know of any other apps, preferably freeware or shareware, that use this format? I'm not familiar with Homesite; is that something I can download?

Hi, I'm afraid I've only ever seen commercial apps using I5Comp format and as it is now obsolete they won't be offering it on the WEB. Homesite is commercial also (it is an Adobe product). I can understand that you'd like to see the code working before you incorporate it into the extractor.

So I'm attaching a small cab which is part of Installshield version 5. It's called _sys1.cab and is 175K long. It contains four files. Hope this helps, Oliver.

Windows 10 Enterprise 2015 Ltsb X86 Assembly Language. There is however 1 problem I6comp.exe cannot read InstallShield version 5 files. The autodetect only distinguishes between different Installshield compression methods, but not the archive architecture. Orlp, thanks for all of your work on this. This has been requested several times in the past, but I was never able to get any sample apps to use for testing. Your code looks good, and I'd certainly like to add it to the next version of UniExtract (I couldn't do it in time for 1.4.2), but I still need one or more sample apps for testing.

Universal Extractor relies heavily on. Decompressor for InstallShield 3.x archives and installers; used to extract InstallShield 3. And SFX installers. This is where you actually select the files that will be installed by the installer that you’re creating. You can select as many files as you want here.

Could you please post a download link to an application that uses this format? Edit: After rereading your post I see that you mentioned a couple apps. Unfortunately, I don't have a copy of Photoshop, and obviously you can't post download links for it. Do you happen to know of any other apps, preferably freeware or shareware, that use this format? I'm not familiar with Homesite; is that something I can download? I'm sorry but I forgot to post the header file with the cab - here they both are in a zip file. I've just checked that the code works with 1.4.2 and it seems to be ok.

The only thing I miss is a tickbox to keep UE opened after extraction so I can expand another file. This wouldn't be difficult to implement, but I'm trying to understand the usefulness. You can drag-and-drop a file onto the binary or a shortcut to the binary just as fast as the GUI. Alternatively, if you're using the installer and have context menu associations enabled, you can simple select all of the files that you want to extract, right-click on one of them, then Click UniExtract to Subdir. All selected files will be extracted to their own subdirectories. Any other thoughts on this?

For InstallShield MSI based projects I have found the following to work: setup.exe /s /x /b'C: FolderInWhichMSIWillBeExtracted' /v'/qn' This command will lead to an extracted MSI in a directory you can freely specify and a silently failed uninstall of the product. The command line basically tells the setup.exe to attempt to uninstall the product (/x) and do so silently (/s). While doing that it should extract the MSI to a specific location (/b). The /v command passes arguments to Windows Installer, in this case the /qn argument. The /qn argument disables any GUI output of the installer. Just a disclaimer: A setup.exe file can contain an embedded MSI, it can be a legacy style (non-MSI) installer or it can be just a regular executable with no means of extraction whatsoever. The 'discussion' below first presents the use of admin images for MSI files and how to extract MSI files from setup.exe files.

Then it provides some links to handle other types of setup.exe files. Also see the comments section. Remember that a 'last resort' is to launch the installer and then look for extracted files in the temp folder. There is built-in MSI support for file extraction (admin install) MSI or Windows Installer has built-in support for this - the extraction of files from an MSI file. This is called an. It is basically intended as a way to create a network installation point from which the install can be run on many target computers. This ensures that the source files are always available for any repair operations.

Note that running an admin install versus using a zip tool to extract the files is very different! The latter will not adjust the media layout of the media table so that the package is set to use external source files - which is the correct way. Always prefer to run the actual admin install over any hacky zip extractions. As to compression, there are actually used for the cab files inside the MSI file format: MSZip, LZX, and Storing (uncompressed). All of these are handled correctly by doing an admin install.

Important: for repair, modify and uninstall scenarios. Starting with Windows 7 (MSI version 5) the MSI files are now cached full size to avoid breaking the file signature that prevents the UAC prompt on setup launch (a known Vista problem). This may cause a tremendous increase in disk space consumption (several gigabytes for some systems). To prevent caching a huge MSI file, you should run an admin-install of the package before installing. This is how a company with proper deployment in a managed network would do things, and it will strip out the cab files and make a network install point with a small MSI file and files besides it.

Admin-installs have many uses It is recommended to read more about admin-installs since it is a useful concept, and I have written a post on stackoverflow:. There is no need to use any tool!! We can follow the simple way. I do not know which tool built your self-extracting Setup program and so, I will have to provide a general response.

Most programs of this nature extract the package file (.msi) into the TEMP directory. This behavior is the default behavior of InstallShield Developer. Without additional information, I would recommend that you simply launch the setup and once the first MSI dialog is displayed, you can examine your TEMP directory for a newly created sub-directory or MSI file. Before cancelling/stopping an installer just copy that MSI file from TEMP folder. After that you can cancel the installation.