Bug reports and feature requests for 2006

  • These occured using V9.25 (2004)

    I managed to create number of CRC errors by processing UNIX file paths > 255 characters. Software should check the final file path lengths when doing batch unpack of files. This is particularly important when using the option to preserve directory structure in a folder named after the original archive.

    Need to warn user if path will be longer than 250 characters.
    Clearer error message would be helpful.

    Encountered a corrupt TAR.GZ file, gave a “CRC” error, but program still gave final dialog that said “all files processed correctly”. Clearly not.

    We need a logging mechanism, including error logs. This is a batch program; I ran something like 1000 archives through it yesterday and 50,000 files.

Log in to reply