Hi,

behaviour using Windows Installer and the CAB File Format?

AFAIK, there isn't any Windows Installer option or CAB file format to
prevent the extraction of a CAB file on a specific Windows system, and
since your CAB file could be extracted successfully on other machines, then
the CAB itself should be OK. So do you get any error message when the
extraction failed on that Windows 2000 machine, it would be useful to
isolate your problem?

Before we proceed, please test the CAB file in some other Windows 2000
machines, will the problem happen? And how about the specific file you
build CAB file with, does the problem only occur when you create CAB file
with it?

If you have any further information related to this problem, please feel
free to post here.

Thanks!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Gary,
thank you for your reply. I will add more information:

1) Error message:
Using InstallShied Setup (v X or 10.0), it is an InstallScript MSI project:
'Error 1335. The cabinet file 'Data1.cab' required for this installation is
corrupt and cannot be used. This could indicate a network error, an error
reading from the CD-ROM;, or a problem with this package.'
Available Buttons: Abort, Retry, Ignore: Retry will get the same error
message again, Ignore results in Internal error 2350 message box.
Then 'Error -1603 Fatal error during installation. Consult Windows Installer
Help (msi.chm) or MSDN for more information' message box occurs.

MSI verbose log for this situation (... representing that I cut away some
log info):
...
Action 11:10:12: InstallFiles. Copying new files
MSI (s) (84:44): Executing op:
ProgressTotal(Total=30978634,Type=0,ByteEquivalent=1)
MSI (s) (84:44): Executing op: SetTargetFolder(Folder=C:\Program Files\My
Company Name\My Product Name\)
MSI (s) (84:44): Executing op:
SetSourceFolder(Folder=1\PROGRA~1\MYCOMP~1\MYPROD~1\|program files\My Company
Name\My Product Name\)
MSI (s) (84:44): Executing op:
ChangeMedia(MediaVolumeLabel=DISK1,MediaPrompt=Please insert the disk: Please
insert the next
disk,MediaCabinet=1\Data1.cab,BytesPerTick=32768,CopierType=1,,,SignatureRequired=0,,,IsFirstPhysicalMedia=1)
MSI (s) (84:44): Executing op:
FileCopy(SourceName=default.mdb,SourceCabKey=default.mdb,DestName=default.mdb,Attributes=16384,FileSize=30978048,PerTick=32768,,VerifyMedia=1,,,,,CheckCRC=0,,,InstallMode=126091264,HashOptions=0,HashPart1=203953220,HashPart2
=687179949,HashPart3=1913356535,HashPart4=819195572,)
MSI (s) (84:44): File: C:\Program Files\My Company Name\My Product
Name\default.mdb;  To be installed;  No patch;  No existing file
MSI (s) (84:44): Source for file 'default.mdb' is compressed
InstallFiles: File: default.mdb,  Directory: C:\Program Files\My Company
Name\My Product Name\,  Size: 30978048
MSI (s) (84:44): Note: 1: 2318 2: C:\Program Files\My Company Name\My
Product Name\default.mdb
MSI (s) (84:44): Note: 1: 2360
MSI (s) (84:44): Note: 1: 2360
MSI (s) (84:44): Note: 1: 2360
... (several times the same message)
MSI (s) (84:44): Note: 1: 2360
MSI (s) (84:44): Note: 1: 1335 2: Data1.cab
MSI (s) (84:44): Note: 1: 2318 2: C:\Program Files\My Company Name\My
Product Name\default.mdb
MSI (s) (84:44): Note: 1: 2360
... (and the above about 5 more times)

Using Winrar (v3.10) on the database file (default.mdb) directly to compress
and extract will work.
Using Winrar on the data1.cab file will abort without any error message: the
file is created but of much less size (orig 30 MB, after extraction 11 MB).

Using Cabinet Manager (v 4.1.0.217):
Extraction of file(s) failed. Failure decompressing data from the cabinet
file. Size is 11 MB here as well.

2) Test on other machines: At least 5 Win2000 machines show the behaviour.
This are all machines I tested. The InstallShield support figured out the
same problem with this file.

3) The file is a database file (access) and it can be opened and changed
with Access with no problems after successfull extraction on Win 2003.

Hope this information helps.