Archive Filename Standard        Previous pageReturn to chapter overviewNext page


These days, many apps and games utilize archives as part of the software (for example, a data store) and during Install-mode it would be undesirable to extract those archives. The problem is that those integral archives can be named anything -- and therefore, unpredictable. As a consequence, SetupS cannot determine which are the install-archives and which are the integral archives.

We cannot control the filenames of those integral archives but we can control the filenames of the "install" ones. The solution has been to limit the install-archive filenames to a filenaming "standard" -- similarly to how the faders and screenshots are handled, like so:

    • {BuildType}.7z|.rar|.zip|.cab (ie, ssApp.7z, ppApp.rar, etc.)
    • {SourceFolderName}.7z|.rar|.zip|.cab (ie, CCleaner_ppApp.7z, CCleaner_ppApp.rar, etc.)
    • {InstallPath}.7z|.rar|.zip|.cab (ie, CCleaner.7z, CCleaner.rar, etc.)
    • SetupS.7z|.rar|.zip|.cab
    • Patch.7z|.rar|.zip|.cab


Ξ Some Notes: 

    1. {BuildType} can be one of the following 'ssApp', 'ppApp', or 'ppGame'. 
    2. {SourceFolderName} is the same as %SourcePath% which is the full path (drive + folder) to the {BuildType}.app|.ppg file. 
    3. {InstallPath} is the same as %AppPath% which is the full path (drive + folder) to the App's or Game's actual installed-to folder.
    4. The exception to this standard will be with "legacy" ppGames which are detected by their lack of both the <BuildType> and <Catalog> keys in the .app-file.

Created with the Personal Edition of HelpNDoc: Experience a User-Friendly Interface with HelpNDoc's Documentation Tool