Yes, there is one, I met. I use as a console unpacker in Far Manager through the Multiarc plugin. They asked for a hint, I decided to give an example - hwi64_810.exe does not open, and in the console the Innounp version of Inno Setup 6.30 and the error message. The original Innounp 0.50 has a size of less than 690 KB, and the Jürgen Rathlev console v1.72.0 is not only three more than three more (2155 KB), but for some reason Netwkstagetinfo() calls to obtain a remote host configuration. And why do...
The repository for my innounp Unicode version is now online:: Innounp on GitHub
Thank you Jürgen, now the situation is clear. When you create the GitHub repo for your branched innounp, please post the news everywhere because I think yours is a really important project. Thank you again.
I am providing a Windows GUI for the Inno Setup Unpacker on GitHub, The description there contains a link to the SourceForge website of innounp. Since there have been no updates of the SourceForge project since 2020 and the source codes not yet are adapted to the current Delphi versions (by default strings are Unicode) I have modified them so that they can be compiled with Delphi 10ff. Some bugs have also been fixed. Apart from that, it is a branch of the original sources but currently still experimental....
Thank you Andrii. Since you probably know this program better than me, can you explain what the Rathlev version really is? It seems like a branched version of this same repository but the author doesn't explain that in any place (unless I lost something from the German part). Even the documentation is still the old one. The changelog has been updated but the other paragraphs are still the same and, for this reason, they are a bit odd (i.e. "Once you have the bug report ready, post it to the forum..."....
Try this - https://www.rathlev-home.de/index-e.html?tools/prog-e.html#unpack
The new InnoSetup version 6.3.1 has been released two days ago. Unfortunately Innounp 0.50 is not able to open this kind of packages. Is there any hope for an update? Thanks
Same issue here - I guess there is no new ROPS Decompiler available?
Hi. Here is the file, that InnoSetupUnpacker couldn't handle - https://github.com/lihas/WindowDetective/releases It claims the following: Signature detected: Inno Setup Setup Data (6.0.0) (u). This is not a supported version.
Those who want to use innounp easily from context menu can use this; http://www.dvbsupport.net/download/index.php?act=download&id=273
Fixed in the innounp Unicode version 1.66: more information
When rebuilding the Script it always outputs the same number of WizardSmallImages as WizardImages in the Setup Header because it is using the same var for both: StrConst('WizardImageFile', GetImageFileList(WizardImages, false)); StrConst('WizardSmallImageFile', GetImageFileList(WizardImages, true)); It should use the appropriate image list: StrConst('WizardImageFile', GetImageFileList(WizardImages, false)); StrConst('WizardSmallImageFile', GetImageFileList(WizardSmallImages, true));
When rebuilding the Script it always outputs the same number of WizardSmallImages as WizardImages in the Setup Header because it is using the same var for both: StrConst('WizardImageFile', GetImageFileList(WizardImages, false)); StrConst('WizardSmallImageFile', GetImageFileList(WizardImages, true)); It should use the correct image list: StrConst('WizardImageFile', GetImageFileList(WizardImages, false)); StrConst('WizardSmallImageFile', GetImageFileList(WizardSmallImages, true));
$>innounp -x -m innosetup-6.2.2.exe ... #94 embedded\License.txt #95 embedded\CompiledCode.bin #96 embedded\WizardImage0.bmp #97 embedded\WizardImage1.bmp #98 embedded\WizardSmallImage0.bmp #99 embedded\WizardSmallImage1.bmp #100 embedded\WizardSmallImage2.bmp #101 embedded\WizardSmallImage3.bmp #102 embedded\WizardSmallImage4.bmp #103 embedded\WizardSmallImage5.bmp #104 embedded\WizardSmallImage6.bmp install_script.iss: LicenseFile=embedded\License.txt WizardImageFile=embedded\WizardImage0.bmp,embedded\WizardImage1.bmp...
When rebuilding the Script it always outputs the same number of WizardSmallImages as WizardImages in the Setup Header because it is using the same var for both: StrConst('WizardImageFile', GetImageFileList(WizardImages, false)); StrConst('WizardSmallImageFile', GetImageFileList(WizardImages, true)); It should use the correct image list: StrConst('WizardImageFile', GetImageFileList(WizardImages, false)); StrConst('WizardSmallImageFile', GetImageFileList(WizardSmallImages, true));
When rebuilding the Script it always outputs the same number of WizardSmallImages as WizardImages in the Setup Header because it is using the same var for both: StrConst('WizardImageFile', GetImageFileList(WizardImages, false)); StrConst('WizardSmallImageFile', GetImageFileList(WizardImages, true)); Is should use the correct image list: StrConst('WizardImageFile', GetImageFileList(WizardImages, false)); StrConst('WizardSmallImageFile', GetImageFileList(WizardSmallImages, true));
well using iExplorerCommand for Appx Package app identify
Why do you think the program needs to be rewritten in C++ or C#? The definitions for context menus are made in Windows by registry entries and are usually created during program installation. I recommend to use my Inno Setup Unpacker - Windows GUI (written in Delphi). The installation optionally creates an entry in the context menu for exe files. More infirmation: Inno Setup Unpacker - Windows GUI
hi i was wondering if you were going to make context menu for this i guessing you need to rewrite the source into C++ or C# and use a wrapper so it can not to sure what your plans are though hopefully something like this will be added
It is a known issue. Unfortunately I can not do much about it. ROPS Decompiler uses original Pascal Script source code for decompilation process. But authors did not update it to work properly with newest PS versions.
Could you provide an update for the ROPS decompiler? The ifps3 version creates a file with 2 bytes. The rops-3.0.53.935-disasm version generates: [ERROR] Script descompilation failed The CompileCode.bin came from: ; Version detected: 6100 (Unicode)
I apologize, I found the source of the error - in the OS catalog lay version 0.49 and was called a %PATH%. Updated it to version 0.50 and the error has gone. I forgot that there is also a binary is lying around ...:( False alarm.
Try unpack new Inno Setup installation, example, have console messages: innounp -x -b -d123 SQLiteExpertPersSetup64.exe Signature detected: Inno Setup Setup Data (6.1.0) (u) This is not directly supported, but i'll try to unpack it as version 6000 ; Version detected: 6100 (Unicode) Unpacking failed. This version is not supported. but Far 3.0 + MultiArc is success unpack this installer. Samples can download on https://www.sqliteexpert.com/v5/SQLiteExpertPersSetup64.exe (is Freeware) Update requir...
Try unpack new Inno Setup installation, example, have console messages: innounp -x -b -d123 SQLiteExpertSetup64.exe Signature detected: Inno Setup Setup Data (6.1.0) (u) This is not directly supported, but i'll try to unpack it as version 6000 ; Version detected: 6100 (Unicode) Unpacking failed. This version is not supported. but Far + MultiArc is success unpack this installer. Update required.
Hallo, ich habe jetzt auch noch einige Befehlszeilenoptionen eingebaut: Optionen: [<name>] [/d:<ddir>] [/f:<filter>] [/m] [/s] [/a] [/o] [/l:xx] <name> : Name der zu entpackenden Setup-Datei <ddir> : Zielverzeichnis für entpackte Dateien <filter> : Dateifilter /m : interne eingebettete Dateien verarbeiten /s : Dateien ohne Pfade entpacken /a : alle Kopien von doppelten Dateien verarbeiten /o : Dateien überschreiben /l:xx : Sprache auswählen (xx = en, de, fr, it oder hu) Viele Grüße J. Rathlev Hello,...
Hallo, ich habe jetzt auch noch einige Befehlszeilenoptionen eingebaut: Optionen: [<name>] [/d:<ddir>] [/f:<filter>] [/m] [/s] [/a] [/o] [/l:xx] <name> : Name der zu entpackenden Setup-Datei <ddir> : Zielverzeichnis für entpackte Dateien <filter> : Dateifilter /m : interne eingebettete Dateien verarbeiten /s : Dateien ohne Pfade entpacken /a : alle Kopien von doppelten Dateien verarbeiten /o : Dateien überschreiben /l:xx : Sprache auswählen (xx = en, de, fr, it oder hu) Viele Grüße J. Rathlev Hello,...
Hallo, ich habe jetzt auch noch einige Befehlszeilenoptionen eingebaut: Optionen: [<name>] [/d:<ddir>] [/f:<filter>] [/m] [/s] [/a] [/o] [/l:xx] <name> : Name der zu entpackenden Setup-Datei <ddir> : Zielverzeichnis für entpackte Dateien <filter> : Dateifilter /m : interne eingebettete Dateien verarbeiten /s : Dateien ohne Pfade entpacken /a : alle Kopien von doppelten Dateien verarbeiten /o : Dateien überschreiben /l:xx : Sprache auswählen (xx = en, de, fr, it oder hu) Viele Grüße J. Rathlev Hello,...
Hallo, ich habe jetzt auch noch einige Befehlszeilenoptionen eingebaut: Optionen: [<name>] [/d:<ddir>] [/f:<filter>] [/m] [/s] [/a] [/o] [/l:xx] <name> : Name der zu entpackenden Setup-Datei <ddir> : Zielverzeichnis für entpackte Dateien <filter> : Dateifilter /m : interne eingebettete Dateien verarbeiten /s : Dateien ohne Pfade entpacken /a : alle Kopien von doppelten Dateien verarbeiten /o : Dateien überschreiben /l:xx : Sprache auswählen (xx = en, de, fr, it oder hu) Viele Grüße J. Rathlev Hello,...
oh cool, exe-file updatet at jrathlev's Download page :) https://www.rathlev-home.de/index-e.html?home-e.html#unpack
Hi, i have short create a Icon for Innounp, :) i have a Totalcommander and make it as internal Command, therefore had i need a Icon.. so.. in short, created a Ico.. and why only for me.. oky, give it the community and the owner :) have fun :) best Blacky Blackcrack blackysgate.de usercmd.ini (? = let show the Parameters before execute, the "?" can you remove [em_innounp] cmd=%Commander_Path%\proggs\innounp\innounp.exe Button=%Commander_Path%\proggs\innounp\innounp.ico Param=? %S -x -d%T menu="InnoUnp"...
Hi, i have short create a Icon for Innounp, :) i have a Totalcommander and make it as internal Command, therefore had i need a Icon.. so.. in short, created a Ico.. and why only for me.. oky, give it the community and the owner :) have fun :) best Blacky Blackcrack blackysgate.de usercmd.ini [em_innounp] cmd=%Commander_Path%\proggs\innounp\innounp.exe Button=%Commander_Path%\proggs\innounp\innounp.ico Param=? %S -x -d%T menu="InnoUnp" [em_innounpsub] cmd=%Commander_Path%\proggs\innounp\innounp.exe...
oh nice, did not know, there is a new Version of it.. Thank you Jürgen !! Github Account : https://github.com/jrathlev/InnoUnpacker-Windows-GUI https://www.rathlev-home.de/index-e.html?home-e.html#unpack Jürgen, take the icons.. best
Hi, i have short create a Icon for Innounp, :) i have a Totalcommander and make it as internal Command, therefore had i need a Icon.. so.. in short, created a Ico.. and why only for me.. oky, give it the community and the owner :) have fun :) best Blacky Blackcrack blackysgate.de usercmd.ini [em_innounp] cmd=%Commander_Path%\proggs\innounp\innounp.exe Button=%Commander_Path%\proggs\innounp\innounp.ico Param=? %S -x -d%T menu="InnoUnp" [em_innounpsub] cmd=%Commander_Path%\proggs\innounp\innounp.exe...
Hi, i have short create a Icon for Innounp, :) i have a Totalcommander and make it as internal Command, therefore had i need a Icon.. so.. in short, created a Ico.. and why only for me.. oky, give it the community and the owner :) have fun :) best Blacky Blackcrack blackysgate.de
@jurgen rathlev Thanks for the reply. Very intersting. Can I propose in your github repository the italian translation (it.po/it.mo)? Thanks.
Hello, in innounp 0.50 some Unicode characters are processed incorrectly. You can use my fully Unicode compatible modification of innounp (version 1.61) instead. Goto my GitHub page for more information. At the bottom of the page you will find a link to the download location of the executables.
Hi. I used innounp 0.50 to unpack some exe installer created with Inno Setup 5.5.0. No error during unapcking. When iwant to open the .iss file withe Inno Setup 5.6.1 Unicode compiler I see a blank file. When iwant to open the .iss file withe Inno Setup 6.2.1 Unicode compiler I see a blank file. No Mapping for the Unicode character exists in the target multi-byte code page Exe installer to test this issue. mgTool https://drive.google.com/uc?export=download&id=1nJE8NChZzwbdW2mLS89sFt8ZRTnjUxeS TYPViewer...
Better late, than never: Unpacking works fine with innounp 0.50.
I know of the bug you are talking about. For some reason, when you want to extract a setup that has multiple .bin files setup-0.bin, setup-1.bin, setup-2.bin, setup-3.bin, setup-4.bin, etcetera, then it would ask for non-existing files setup-0-2.bin, setup-0-3.bin, setup-0-4.bin files This is a very old bug. A workaround for this is to rename the setup-0.bin into setup.0 When extracting the .0 file, this bug won't trigger and all the bin files will be extracted normally without the prompts.
File name pattern for .bin files is stored in main .exe file. If you renamed them for some reason there is no way to tell unpacker to use them.
I have searched high and low and can not find anything. Is there a away, or could it be included in the next release? To send the correctly named and sequenced setup-0 > 10.bin files through the command line? As to stop the file dialog popping up. Something like: innounp.exe -x setup-0.bin setup-1.bin etc..... I have tried serval different ways myself, and spent 6 hours on google/duck duck go looking. If I have missed something, or if this is possible to include in a future release? Can you please...
Ariman Big thanks! version 0.50 working success! Fork -> /dev>nul - there was a "smart guy" who packed Tru64 UNIX binaries in Inno Setup - the fork unpacks them from the second - third time, innounp 0.50 immediately and without errors ...
Delphi 10 uses a predefined global conditional symbol called UNICODE In original Inno source it was a Delphi symbol. Inno ansi and inicode versions were compiled in different Delphi versions and predefined UNICODE was used to split the two. Although I don't have Delphi 10 to test the build process and resulting binaries I will try to incorporate your changes. They make sense.
Innounp should have unique errorcode. I agree with that. Maybe one day it will be implemented :). Would be nice if Innounp would displays the password hash that is used to verifiy the password. You can see password hash in the reconstructed script.
Inno Setup Unpacker 0.50 released
Thanks! I try test it, but: version 0.50 (Your, updated): $ innounp -x -b ccsetup.exe Signature detected: Inno Setup Setup Data (6.1.0) (u) This is not directly supported, but i'll try to unpack it as version 6000 ; Version detected: 6100 (Unicode) Unpacking failed. This version is not supported. version1.61.2 $ innounp -x -b ccsetup.exe ; Version detected: 6100 (Unicode) 1 {app}\clipc,1.exe Reading slice F:\Tmp\7\ccsetup.exe 2 {app}\clipc,2.exe 3 {app}\clipc.chm 4 {app}\click.wav 5 {app}\click2.wav...
Thanks! I try test it, but: $ innounp -x -b ccsetup.exe Signature detected: Inno Setup Setup Data (6.1.0) (u) This is not directly supported, but i'll try to unpack it as version 6000 ; Version detected: 6100 (Unicode) Unpacking failed. This version is not supported.
The new innounp version 1.61 is compatible to Inno Setup version 6.1 and can be compiled with Delphi 10. Revisions were made to fit to the current native string type (UnicodeString) and some exit codes were added (0..3). Older InnpSetup versions are still supported. The GUI has language support for English and German. Download of updated sources and GUI
The new innounp version 1.61 is compatible to Inno Setup version 6.1 and can be compiled with Delphi 10. Revisions were made to fit to the current native string type (UnicodeString) and some exit codes were added (0..3). The GUI has language support for English and German. Download of updated sources and GUI
The new innounp version 1.61 is compatible to Inno Setup version 6.1 and can be compiled with Delphi 10. Revisions were made to fit to the current native string type (UnicodeString). The GUI has language support for English and German. Download of updated sources and GUI
John Williams / XRayz Software ClipCache v3.7.0, testing: try unpack use innounp 0.49 and have messages: innounp -x -b ccsetup.exe Signature detected: Inno Setup Setup Data (6.1.0) (u) This is not directly supported, but i'll try to unpack it as version 6000 ; Version detected: 6100 (Unicode) Unpacking failed. This version is not supported.
The exit codes is really important for interoperability with other programs. Okay the good thing: When innounp exits it passes 0 as ProcessExitCode. in cmd.exe you may query the exit code via: echo %errorlevel% The thing to improved is: When there is some error innounp exits with 1. So at least the program gets notified that something went wrong. However many different thing can go wrong. Innounp should have unique errorcode. At least for all known 'exit conditions' should also have their own exit...
https://web.archive.org/web/20170201213810/http://vdisasm.com/isd/ https://web.archive.org/web/20180723142751/https://vdisasm.com/isd/files/isdsetup.1.5.exe https://archive.is/oho93
https://web.archive.org/web/20170201213810/http://vdisasm.com/isd/ https://web.archive.org/web/20180723142751/https://vdisasm.com/isd/files/isdsetup.1.5.exe
Hi, inno 6.1.0 encounterd, and cannot extract. Will there be an update?
Not really sure. Never needed to see how it is serialized in byte sequence. Version data is 10 bytes long. 4 bytes for 0.0 (all zeroes), 4 bytes for 6.0 (zeroes and 1 byte = 6). Last 2 bytes for Win service pack are not printed in script so can be anything. Can't say offhand exact position of 6 between zeroes.
OK, I get that. So, could you please tell me what sequence that is, unless it's a secret? You don't have to believe it will be useful to me to answer that question, do you?
OK, I get that. So, could please tell me what sequence that is, unless it's a secret? You don't have to believe it will be useful for me to answer that question, do you?
As I've said that sequence is inside solid compressed data block. You can't change data without full recompression.
Well, there has to be some byte sequence that causes innounp to add "MinVersion: 0.0,6.0" to the script it reconstucts. Apparently, that same sequence causes the installation to abort on a lower version of Windows when the setup file is run. If I knew what that sequence was, I could change it to lower the minimum version requerement.
Script is not "decompiled". It is "reconstructed". It does not exists in the installer, unpacker runs through all the data and tries to reconstruct the script as close as possible to the original one based on the things found inside the binary data. Which in turn is a solid compressed archive. And you can not patch solid archived data without full recompression.
Yes, it's present. I still wonder if it's possible to edit the script of a compiled installation, not by modifying the installation file but by modifying the contents of RAM after it's executed (it's possible to suspend the process, which can then be edited in memory to one's heart content). There has to be a certain byte sequence that corresponds to "MinVersion: 0.0,6.0" and since you know how to decompile the script, you should know the exact sequence of bytes that corresponds to it. I'm thinking...
Check for file embedded\CompiledCode.bin. If it is present then there were code attached. It does not mean that it is very important code. But you will loose it if you try to recompile the installer with reconstructed script.
How can I check if there's any code attached to the script?
It is not possible to modify the existing installer to change Win version requirements. Technically you can rebuld installer from reconstructed script and extracted files but you'll loose any code that were attached to the script (if there is one). Or may be you can simply use extracted files if installer does not do any magic and just unpacks files to some location.
Hello. As described at https://msfn.org/board/topic/181866-inno-setup-6-on-windows-xp/ I am trying to install software that would most likely work on Windows XP, but packaged into an Inno Setup installer that would not run on XP. I managed to overcome some of the obstacles and get the setup executable to run, only to be frustrated by the "This program does not support the version of Windows your computer is running." message. I think it might be the install script (the archive with which I attached...
Hello. As described at https://msfn.org/board/topic/181866-inno-setup-6-on-windows-xp/ I am trying to install software that would most likely work on Windows XP, but packaged into and Inno Setup installer that would not run on XP. I managed to overcome some of the obstacles and get the setup executable to run, only to be frustrated by the "This program does not support the version of Windows your computer is running." message. I think it might be the install script (the archive with which I attached...
As described at https://msfn.org/board/topic/181866-inno-setup-6-on-windows-xp/ I am trying to install software that would most likely work on Windows XP, but packaged into and Inno Setup installer that would not run on XP. I managed to overcome some of the obstacles and get the setup executable to run, only to be frustrated by the "This program does not support the version of Windows your computer is running." message. I think it might be the install script (the archive with which I attached to...
The compiling of innounp with Delphi 10 requires some changes to the source code: Compiler conditional symbol UNICODE must be renamed to ISUNICODE because Delphi 10 uses a predefined global conditional symbol called UNICODE Some changes from "string" to "AnsiString" are required Aside from that, I created a Windows GUI for innounp. Download of modified sources and GUI
The compiling of innounp with Delphi 10 requires some changes to the source code: Compiler conditional symbol UNICODE must be renamed to ISUNICODE because Delphi 10 uses a predefined global conditional symbol called UNICODE Some changes from "string" to "AnsiString" are required Aside from that, I created a Windows GUI for innounp. Download of modified sources and GUI
For anyone else who finds this broken link in the future: 1.2: https://download.cnet.com/Inno-Setup-Decompiler/3000-2383_4-77452731.html 1.3 Portable: http://www.solidfiles.com/v/72zD4jLPmP3qx/dl
It is not an issue. It is how installer is packed. GOG packs lot of stuff this way. Usually it is patches, but sometimes full games too. Bundled script file assembles game content from tmp folder after unpacking.
Hello. I tried innounp on many GOG games before, but today I run at the issue. I tried unpack Doomdark's Revenge (available for free on GOG https://www.gog.com/game/doomdarks_revenge), which according info is 5.5.7 IS package, and even though on first look it seems that everything went smoothly, after I check actual directory to which it unpacked files, I found that result files are all wrong. Almost all files were unpacked into tmp directory, where I can find a lot directories, which shoudn't be...
I resolve this task for Far Manager, and resolving is simple, step by step: 1) Your needed Far Manager and MultiArc plug-in whith Custom.fmt submodule, innounp.exe v0.49 or newer and change the some default Far setting. 2) In Far command prompt type command far:config and pess Enter; 3) Find settings : PluginConfirmations.OpenFilePlugin to 1 System.PluginMaxReadData to 768000 Notes: this is minimal needed value 4) In to MultiArc custom_user.ini add new section: [InnoSetup6] TypeName=Inno Setup 6...
I resolve this task for Far Manager, and resolving is simple, step by step: 1) Your needed Far Manager and MultiArc plug-in whith Custom.fmt submodule, innounp.exe v0.49 or newer and change the some default Far setting. 2) In Far command prompt type command far:config and pess Enter; 3) Find settings : PluginConfirmations.OpenFilePlugin to 1 System.PluginMaxReadData to 768000 Notes: this is minimal needed value 4) In to MultiArc custom_user.ini add new section: [InnoSetup6] TypeName=Inno Setup 6...
I resolve this task for Far Manager, and resolving is simple, step by step: 1) Your needed Far Manager and MultiArc plug-in whith Custom.fmt submodule, innounp.exe v0.49 or newer and change the some default Far setting. 2) In Far command prompt type command far:config and pess Enter; 3) Find settings ~~~ PluginConfirmations.OpenFilePlugin to 1 System.PluginMaxReadData to 768000 *Notes: this is minimal needed value* 4) In to MultiArc custom_user.ini add new section: [InnoSetup6] TypeName=Inno Setup...
I resolve this task for Far Manager, and resolving is simple, step by step: 1) Your needed Far Manager and MultiArc plug-in whith Custom.fmt submodule, innounp.exe v0.49 or newer and change the some default Far setting. 2) In Far command prompt type command far:config and pess Enter; 3) Find settings ~~~ PluginConfirmations.OpenFilePlugin to 1 System.PluginMaxReadData to 768000 *Notes: this is minimal needed value* 4) In to MultiArc custom_user.ini add new section: [InnoSetup6] TypeName=Inno Setup...
I resolve this task for Far Manager, and resolving is simple, step by step: 1) Your needed Far Manager and MultiArc plug-in whith Custom.fmt submodule and change one default Far setting. 2) In Far command prompt type command far:config and pess Enter; 3) Find setting System PluginMaxReadData and setup here up to1048576 or 0x100000 hex 4) In to MultiArc custom_user.ini add new section: [InnoSetup6] TypeName=Inno Setup 6 ID=49 6E 6E 6F 20 53 65 74 75 70 20 53 65 74 75 70 20 44 61 74 61 20 28 36 IDOnly=1...
I resolve this task for Far Manager, and resolving is simple, step by step: 1) Your needed Far Manager and MultiArc plug-in whith Custom.fmt submodule and chage one default Far setting. 2) 1) In Far command prompt type command far:config and pess Enter; 3) Find setting System PluginMaxReadData and setup here up to1048576 or 0x100000 hex 4) In to MultiArc custom_user.ini add new section: [InnoSetup6] TypeName=Inno Setup 6 ID=49 6E 6E 6F 20 53 65 74 75 70 20 53 65 74 75 70 20 44 61 74 61 20 28 36 IDOnly=1...
Both ROPS disassemblers show an error, IFPS3 Tools creates an empty file. Yet, IFPSTools on Github was able to disassemble the script just fine.
Is it possible to have a casacde menu stile like innounp shell -> Extract/Info/List
Certainly - the attached zip contains an installer, the .iss files used to create it, and text files with the build command and the extraction results, showing the contents of the intended target directory and the _ folder at the root level where the files ended up. This stackoverflow page illustrates the problem that switching to the extended path syntax solved for us: https://stackoverflow.com/questions/38789616/inno-setup-compiler-cannot-find-the-path-specified-error-with-long-paths (Note that...
Could you provide a sample installer for tests? It would be simpler when there are some files with reproducable behavior to play with.
Hi - I've run into an issue using Inno Setup Unpacker to extract the contents of some installers we create in-house. Due to some comically-long paths the development team has added to our software we use the windows extended path format for our destination directories, like so: Source: "bin64\*_{#MyTargetSuffix}.pdb"; DestDir: "\\?\{app}\bin64"; Flags: ignoreversion This works properly for the actual installer, but innounp ends up putting all of the files in an _ /{app} directory at the root of the...
It is possible. But what's the point in making it a separate command? You can easily get list of languages from recompiled script. There is a special section.
No feedback by the program developer?
@ariman_ua @quickener Could be possible to add in new release a command line option (ex.- --check-language) to check/show which language are inlcuded in the .exe file of the installer? I see that in other tools for Inno Setup exe file like innoextract there is an option like this. Could be useful to check what languages are included in installer exe before to unapck it. This the report like Checking languages included in Inno Setup installer .exe file File selected = 'Internet Download Accelerator...
@ariman_ua @quickener Could be possible to add in new release a command line option (ex.- --check-language) to check/show which language are inlcuded in the .exe file of the installer? I see that in other tools for Inno Setup exe file like innoextract there is an option like this. Could be useful to check what languages are included in installer exe before to unapck it. This the report like Checking languages included in Inno Setup installer .exe file File selected = 'Internet Download Accelerator...
@ariman_usa @quickener Could be possible to add in new release a command line option (ex.- --check-language) to check/show which language are inlcuded in the .exe file of the installer? I see that in other tools for Inno Setup exe file like innoextract there is an option like this. Could be useful to check what languages are included in installer exe before to unapck it. This the report like Checking languages included in Inno Setup installer .exe file File selected = 'Internet Download Accelerator...
@ariman_usa @quickener Could be possible to add in new release a command line option (ex.- --check-language) to check/show which language are inlcuded in the .exe file of the installer? I see that in other tools for Inno Setup exe file like innoextract there is an option like this. Could be useful to check what languages are included in installer exe before to unapck it. Thanks.
Could be possible to add in new release a command line option (ex.- --check-language) to check/show which language are inlcuded in the .exe file of the installer? I see that in other tools for Inno Setup exe file like innoextract there is an option like this. Thanks.
Now v. 0.49 is compatible with exe file created by Inno Setup 6.x.x.
Could be possible to add in new release a command line option to check/show which language are inlcuded in the .exe file of the installer? I see that in other tools for Inno Setup exe file. Thanks.
Aditya11ttt This build used some, both renamed original innounp.exe v0.49. See SHA-256 hash summ: SHA-256 (innounp.e32) = a249edb5a464b74328603a44e5f2d38e69678f5a690485cd5f211d969693fb1d SHA-256 (innounp.exe) = a249edb5a464b74328603a44e5f2d38e69678f5a690485cd5f211d969693fb1d
use this rar upadted to latest v6
v0.49 posibly can't detect some Inno Setup 6.0.x installers. Example ClipCashe v3.6.3 used Inno Setup 6.0.x and if use Far3 + MultiArc + Custom.fmt + Innounp v0.49 can't detect this installer. In to changelg autor is says: " Improve installer appearance." - this installer not detetected, but use commad innounp -x -b ccsetup.exe I can unpack it and see commen in to install_script.iss: (string 1) ;InnoSetupVersion=6.0.0 (Unicode) GIMP 2.10.10 used Inno Setup 5.5.9 (UNICODE) and can unpack using Far3...
v0.49 posibly can't detect some Inno Setup 6.0.x installers. Example ClipCashe v3.6.3 used Inno Setup 6.0.x and if use Far3 + MultiArc + Custom.fmt + Innounp v0.49 can't detect this installer. In to changelg autor is says: " Improve installer appearance." - this installer not detetected, but use commad innounp -x -b ccsetup.exe I can unpack it and see commen in to install_script.iss: (string 1) ;InnoSetupVersion=6.0.0 (Unicode) GIMP 2.10.10 used Inno Setup 5.5.9 (UNICODE) and can unpack using Far3...
v0.49 posibly can't detect some Inno Setup 6.0.x installers. Example ClipCashe v3.6.3 used Inno Setup 6.0.x and if use Far + MultiArc Innounp v0.49 can't detect this installer. In to changelg aupr's is says: " Improve installer appearance." - this installer not detetected, but use commad innounp -x -b ccsetup.exe I can unpack it and see commen in to install_script.iss: (string 1) ;InnoSetupVersion=6.0.0 (Unicode)