Reply to Thread

Post a reply to the thread: Skipping File Compression

Your Message

Click here to log in

What's the name of our main installation product (in uppercase letters), directly followed by the current year?

 

You may choose an icon for your message from this list

Additional Options

  • Will turn www.example.com into [URL]http://www.example.com[/URL].

Topic Review (Newest First)

  • 01-22-2018, 03:37 AM
    linder

    Re: Skipping File Compression

    Hi Seth,

    new compiler component sent.

    Does this work?

    Friedrich
  • 01-20-2018, 04:38 AM
    linder

    Re: Skipping File Compression

    I'll send you a new small compiler component to test the fix. We have tested it on your .png file.

    It's caused by this:

    FIX : [SB#8-01151] Installer: Under certain circumstances, a possible silent buffer overrun resulted in an incorrect output if the compressed data size was between 65533 and 65535 bytes.

    This issue is there since the first release of SetupBuilder 5 in 2005.

    Friedrich
  • 01-19-2018, 08:53 AM
    st09

    Re: Skipping File Compression

    Yes, I will test it. What tests have you already run?
  • 01-18-2018, 02:59 AM
    linder

    Re: Skipping File Compression

    Hello,

    we have a modified library for SB10. Can I send the new compiler component (only 10KB) to test it?

    Friedrich
  • 01-17-2018, 01:37 PM
    linder

    Re: Skipping File Compression

    Update: I think I know what causes this. We'll do some more tests. More later...

    Friedrich
  • 01-17-2018, 03:57 AM
    linder

    Re: Skipping File Compression

    Hello,

    very interesting issue (I can reproduce this with SetupBuilder V5 from August 2005, V6, V7, V8 and V10). I'll get back to you.

    BTW, as a quick fix, change the "Fast" compression method back to "Standard".

    Friedrich
  • 01-16-2018, 11:21 AM
    st09

    Re: Skipping File Compression

    Hello Friedrich,

    Thank you for your prompt response. I appreciate the clarification of LSPack versus LSZip. I have put together a sample project with the behavior that I am observing. Please note that the CRC in the build report is 72E37C6C, but the CRC of the installed file is 4C8BE551.

    Regards
  • 01-16-2018, 02:46 AM
    linder

    Re: Skipping File Compression

    Hello,

    LSZip will definitely never alter the contents of a file! It checks the CRC-32 before compression and the CRC-32 after decompression. Even if only one bit changes (e.g. file transmission error), you'll receive a decompression error.

    BTW, the installer itself does not use LSZip. Only if you ZIP/UNZIP .zip files from within your installer then LSZip is used.

    Friedrich
  • 01-16-2018, 02:44 AM
    linder

    Re: Skipping File Compression

    Hello,

    what are you doing with LSZip from your setup.exe? Do you decompress a ZIP archive during the installation process?

    But to answer the question, there are no known issues with LSZip. LSZip always checks the original CRC-32 value against the CRC-32 value after the decompression process.

    Additional note: the SetupBuilder compiler and installer are using the LSPack (not LSZip). From the technical point-of-view, it is absolutely impossible that LSPack alters the contents of a file. During the compression process (when you build the setup.exe), it generates the CRC-32 value of the file and stores it in the archive header and in the script. After the decompression process, it generates again the CRC-32 value of the decompressed file and checks it against the stored CRC-32 value.

    Friedrich
  • 01-15-2018, 12:11 PM
    st09

    Re: Skipping File Compression

    Are there any known issues with LSZip? We are encountering a case where the installed file does not match the build report (HTML file).
This thread has more than 10 replies. Click here to review the whole thread.

Posting Permissions

  • You may post new threads
  • You may post replies
  • You may not post attachments
  • You may not edit your posts
  •