Patrick Flood

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...

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...