PRB: CAB SDK Headers Contain Incorrect CB_MAX_DISK ValueLast reviewed: January 19, 1998Article ID: Q174866 |
The information in this article applies to:
SYMPTOMSWhen compressing data using Fci.lib from the Cabinet (CAB) SDK, a new cabinet file is started after about 134 MB of data has been compressed.
CAUSEFci.h contains an incorrect definition for CB_MAX_DISK. The value is defined as 0x7FFFFFFL (134,217,727) instead of 0x7FFFFFFFL (2,147,483,647) as it should be. CB_MAX_DISK is also defined incorrectly in this way in Fdi.h.
RESOLUTIONRedefine CB_MAX_DISK to the correct value of 0x7FFFFFFFL:
#define CB_MAX_DISK 0x7FFFFFFFL STATUSMicrosoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
MORE INFORMATIONSpecifying a value of 0 for disk size (cb value in CCAB struct) resets the value to CB_MAX_DISK. However, CB_MAX_DISK is defined incorrectly as 0x7FFFFFFL or 134,217,727. It should be 0x7FFFFFFFL, or 2,147,483,647. Data compression proceeds to about 134 Mb, then it switches to a new cabinet. The desired result of a larger cabinet (CAB) can be obtained by explicitly supplying the correct larger value. Note that a CAB can normally contain at most 65,500 or so files. There is no code in FCI to avoid exceeding this value, so the user application may have to enforce it. Also note that unless a CAB will be randomly extracted, cbFolderThresh should be explicitly set to a very large value. If the CAB will be randomly extracted, values between 100 K and 1 Mb would be appropriate.
REFERENCESFor more information about cabinets and the CAB SDK, see the following Web site:
http://www.microsoft.com/workshop/prog/cab/ Keywords : InetSDKCAB Technology : kbInetDev Version : WINDOWS:4.0,4.01 Platform : WINDOWS Issue type : kbprb |
================================================================================
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |