Name: desktopicon Description: "Create a &desktop icon" GroupDescription: "Additional icons:" Components: main These tasks appear as check boxes and radio buttons on the Select Additional Tasks wizard page.īy itself a task does nothing: it needs to be 'linked' to other installation entries. It defines all of the user-customizable tasks Setup will perform during installation. Version Offset(hex) IDPos Unpacker Comment The details (see below) of the password protection are stored in the file install_script.iss, which is located in the root folder:Ĭode: Select all _ Note, that running the VSDC Free Video Editor installer directly the internal initialization process passes the required password to the installation process. What's it actually good for, when eventually the contents get unpacked and installed anyway? Usually, the user does not know the password, and it cannot be easily extracted from the installer. My script does not support the input of passwords, because InnoSetup installers should not request a password in the first place IMHO. When trying to unpack with InnoUnp, this installer requests the user to input a password to continue the installation routine. Thanks for providing new problem examples, it's much appreciated.ĭoes not contain any InnoSetup installer, it's just a plain executable ready to run. I think in this forum English is the preferred language, so users worldwide can follow it more easily. Inno Setup Setup Data (6.1.0) (u) no probs LEADERTASK Task Planner for Remote Working Inno Setup Setup Data (5.5.7) (u) newer version That's convenient for unpacking several InnoSetup installers to the same destination directory, without overwriting/intermixing each other. The elegance of this solution is that it allows choosing the destination of the unpacked files, and the unpacked files reside in a subfolder named after the InnoSetup installer. The InnoSetup installer gets extracted entirely into the subfolder of the passive TC file panel without any further prompts.A folder is created in the passive TC file panel, using the filename of the currently highlighted InnoSetup installer of the active TC file panel.I had in mind it's probably related to how the files are compressed, but couldn't put my finger on it.ĮDIT: I just checked and found that both PDF24 Creator installers are compressed with LZMA2, so that is certainly not the root cause of the issue.įor such cases, I created the following solution to unpack the InnoSetup installer directly with InnoUnp: The PDF24 Creator v9.2.2 installer can be unpacked via MultiArc (BatchUnpack=1), the other one not, although the listings work correctly. This is where I got stuck a couple of weeks ago: Both the downloadable installer for PDF24 Creator v9.2.2 and v10.0.11 are created with Inno v.6.0.0. Confirmed, the list command via MultiArc works flawlessly and InnoUnp can unpack LZMA2 compressed InnoSetup installers just fine.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |