|
From: Rob M. <ro...@us...> - 2004-12-30 18:09:28
|
Tom, did your scripts decompress the cabinet from the MSI file as well? I
think the error you're seeing from dark is occurring at the end of the
decompliation after dark is done dealing with the cabinet. Vitaly is
correct if you are on an older OS (Win9x and some Win2k. I thought it was
fixed in one of the SPs, but Vitaly is more likely to be right than me),
there were some issues with the cabinet processing code when cabinets were a
particular size and shape.
This thread plus the other threads about wixcab.dll not being as fast as it
could be makes me wonder if there are some issues in the wixcab.dll
somewhere. Tom, if you can provide more detailed information about the
issues you are seeing that would be much appreciated.
_____
From: wix...@li...
[mailto:wix...@li...] On Behalf Of Vitaly Dolya
Sent: Tuesday, December 28, 2004 8:08 AM
To: wix...@li...
Subject: Re: [WiX-users] Dark Error - error DARK0047 : Failed to close cab
I don't think this is the case but any chance the problem comes from a
several bugs in
windows cabinet processing engine? AFAIK there are some bugs in system
cabinet processing engine
on Win9x/Win2k(including SP4) which are revealed on cabinet of certain size
and compression level.
But if SDK scripts did their job...
----- Original Message -----
From: Tom Kufeldt <mailto:tku...@ho...>
To: ro...@us... ; wix...@li...
Sent: Tuesday, December 28, 2004 9:44 AM
Subject: Re: [WiX-users] Dark Error - error DARK0047 : Failed to close cab
I will look into the virus checker. I did forget to mention that I am able
to decompile the msi I build using the Installer SDK scripts.
Thank-you,
tomk.
----- Original Message -----
From: Rob Mensching <mailto:ro...@us...>
To: 'Tom Kufeldt' <mailto:tku...@ho...> ;
wix...@li...
Sent: Monday, December 27, 2004 9:50 PM
Subject: RE: [WiX-users] (no subject)
That error seems to occur most often when you have a virus checker that gets
excited when it sees cabinet files. Usually people that hit this make sure
their virus checker isn't evaluating the Temp directory. or rather they
redirect the WiX toolset to operate somewhere beside the Temp directory and
tell the virus checker to not look there.
If you don't have a virus checker, then this is probably some other bug.
Does this happen with all MSIs you build?
_____
From: wix...@li...
[mailto:wix...@li...] On Behalf Of Tom Kufeldt
Sent: Friday, December 17, 2004 4:26 PM
To: wix...@li...
Subject: [WiX-users] (no subject)
Hi,
I am receiving this error when I execute the following dark command:
dark.exe : error DARK0047 : Failed to close cab
'C:\Temp\bin\MergeModule.CAB'.
dark /m /f /x bin example.msm example.wxs
example.msm is built with no errors or warnings using wix tools 2.0.2415.0
and it passes the
merge module validation tests in Orca.exe.
Is this a known issue?
Thanks,
Tom Kufeldt
C:\Temp>cscript /nologo WiStream.vbs example.msm
MergeModule.CABinet
SummaryInformation
C:\Temp>dark
Microsoft (R) Windows Installer Xml Decompiler Version 2.0.2415.0
Copyright (C) Microsoft Corporation 2003. All rights reserved.
C:\Temp>candle
Microsoft (R) Windows Installer Xml Compiler version 2.0.2415.0
Copyright (C) Microsoft Corporation 2003. All rights reserved.
PS - Shouldn't the copyright date for the wix tools be 2003 - 2004?
|