I have a huge installer that indeed has some corrupted data (running setup indeed fails to extract numerous files near the end). Actually that was the reason I looked for the setup unpacker.
Is it possible to FORCE the unpacker extract as much as it can?
Ignore the errors, scip corrupted files (would be nice to also list them) and extract the rest.
Right now, it just fails.
Here is the output:
; Version detected: 5402 (Unicode)
Critical error: The setup files are corrupted. Please obtain a new copy of the p
rogram.
Error (EAbort) "Operation aborted" at address 0047E153
I wonder if that address is helpful in any way (for example point me to the corrupted bin).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Address points to the unpacker's memory, so it's not really helpful.
Success of the forced unpacking depends on compression used. In solid compression any file depends on previous ones. So if file is corrupted then it is quite likely that you will not be able to unpack anything after it at all. If files are compressed independently then task is much easier, you can process each file individually and just skip over corrupted files.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have a huge installer that indeed has some corrupted data (running setup indeed fails to extract numerous files near the end). Actually that was the reason I looked for the setup unpacker.
Is it possible to FORCE the unpacker extract as much as it can?
Ignore the errors, scip corrupted files (would be nice to also list them) and extract the rest.
Right now, it just fails.
Here is the output:
; Version detected: 5402 (Unicode)
Critical error: The setup files are corrupted. Please obtain a new copy of the p
rogram.
Error (EAbort) "Operation aborted" at address 0047E153
I wonder if that address is helpful in any way (for example point me to the corrupted bin).
Address points to the unpacker's memory, so it's not really helpful.
Success of the forced unpacking depends on compression used. In solid compression any file depends on previous ones. So if file is corrupted then it is quite likely that you will not be able to unpack anything after it at all. If files are compressed independently then task is much easier, you can process each file individually and just skip over corrupted files.