PRB: Encrypted EXE Larger In Size After Compression

Last reviewed: June 27, 1995
Article ID: Q125863
The information in this article applies to:
  • Microsoft FoxPro for Windows, version 2.6a

SYMPTOMS

After using SetupWizard to compress an executable built with encryption, you discover that the compressed file (.EX$ file) is actually larger in physical size than its original size as an ,EXE file.

CAUSE

Because the file is encrypted, the compression algorithm used by SetupWizard fails to find repeated characters to encode, so it cannot compress the encrypted file.

STATUS

This behavior is by design.

MORE INFORMATION

Steps to Reproduce Behavior

  1. Use an existing Project such as ORGANIZE.PJX in the \SAMPLE\ORGANIZE directory under the main FoxPro directory or create a new simple Project for testing purposes.

  2. Build the Project into an Executable with encryption. To do this, choose options from the Project menu, and in the resulting dialog screen, select the Encrypt Code check box.

  3. For testing purposes only, place this encrypted .EXE file in an empty directory along with the FOXW2600.ESL Support Library file.

  4. Run the SetupWizard application (SETUP.APP) in the DKWIZARD directory under the main FoxPro directory. Specify a different directory for the compressed files. SetupWizard will create this directory for you.

  5. After SetupWizard has finished, compare the file size of the .EX$ to the .EXE file, and note that the .EX$ file is larger.


Additional reference words: FoxWin 2.60a
KBCategory: kbtool kbprb
KBSubcategory: FxtoolDk


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: June 27, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.