|
From: Tom K. <tku...@ho...> - 2004-12-30 23:54:10
|
lists.sourceforge.net rejected this the first time. Reporting-MTA: dns;hotmail.com Received-From-MTA: dns;mail.hotmail.com Arrival-Date: Thu, 30 Dec 2004 15:44:00 -0800 Final-Recipient: rfc822;wix...@li... Action: failed Status: 5.5.0 Diagnostic-Code: smtp;550-Postmaster verification failed while checking = <tku...@ho...<mailto:tku...@ho...>> 550-(result of earlier verification reused). 550-Several RFCs state that you are required to have a postmaster 550-mailbox for each mail domain. This host does not accept mail 550-from domains whose servers reject the postmaster address. 550 Sender verify failed ----- Original Message -----=20 From: Tom Kufeldt<mailto:tku...@ho...>=20 To: ro...@us...<mailto:ro...@us...> = ; 'Vitaly Dolya'<mailto:vd...@tm...> ; = wix...@li...<mailto:wix...@li...>=20 Sent: Thursday, December 30, 2004 3:43 PM Subject: Re: [WiX-users] Dark Error - error DARK0047 : Failed to close = cab Rob, This error is present on WinXP SP1 and SP2. The product packaged in = the merge module=20 is intended for versions of Windows from Win2k and later but the merge = module=20 development has been done on WinXP. This error occurred while doing new development using Wix to create a = merge module to replace an installer package originally created using Wise for = Windows Installer v2.0. That version of Wise was abandoned when it was discovered that it was = not possible to=20 automate the msi build process using the Wise tools. The Windows = Installer v2.0 SDK and msi2xml tools were used to convert the wsi file to an msi file and = automate the=20 build process. Since the product is a shared component within the organization a = requirement was=20 generated to create a merge module in place of the installer package. = At this point Wix became available and was chosen as the tool set to build Windows based = installers and merge modules. dark.exe was used to decompile the original installer = file and portions=20 of this were used to create the Wix source for the merge module. =20 Both cab files in the installer file and the merge module contain the = same files. However merge module also includes the debug symbol files for the executables = in the cab file. Therefore the merge module cab file is larger of the two cab files. To date I am unaware of any problems merging the msm file or = installing the subsequent msi file. So the only Wix related issue I have seen thus far occurs = while using dark.exe to extract the cab file from a merge module created using candle.exe, = lit.exe and light.exe. Tomk. Additional detail: msi cab =20 --a-- - - - - - 22,820,354 12-28-2004 = example.cab msm cab --a-- - - - - - 31,293,104 12-28-2004 = MergeModule.CABinet The installer file was created using the following tools msi2xml<https://sourceforge.net/projects/msi2xml/> --a-- W32i APP ENU 2.1.8.948 shp 327,680 03-01-2004 = xml2msi.exe Windows Installer v2.0 = SDK<http://msdn.microsoft.com/library/default.asp?url=3D/library/en-us/ms= i/setup/windows_installer_scripting_examples.asp> script examples --a-- - - - - - 12,571 06-26-2002 = WiMakCab.vbs --a-- - - - - - 10,965 06-26-2002 = WiFilVer.vbs =20 --a-- W32i APP ENU 5.1.2600.0 shp 79,360 10-23-2002 = makecab.exe The merge module was built using v2.0.415.0 of the Wix tools --a-- W32i APP - 2.0.2415.0 shp 15,872 12-27-2004 candle.exe --a-- W32i APP - 2.0.2415.0 shp 24,576 12-27-2004 lit.exe --a-- W32i APP - 2.0.2415.0 shp 32,768 12-27-2004 light.exe --a-- W32i DLL - 2.0.2415.0 shp 1,253,376 12-27-2004 wix.dll --a-- W32i - - - - 188,416 12-27-2004 wixcab.dll The output from dark Installer file D:\>dark -x msi_bin example.msi example.wxs Microsoft (R) Windows Installer Xml Decompiler Version 2.0.2415.0 Copyright (C) Microsoft Corporation 2003. All rights reserved. example.msi Merge module D:\>dark -x msm_bin -m example.msm example-msm.wxs Microsoft (R) Windows Installer Xml Decompiler Version 2.0.2415.0 Copyright (C) Microsoft Corporation 2003. All rights reserved. example.msm dark.exe : error DARK0047 : Failed to close cab = 'D:\msm_bin\MergeModule.CAB'. dark.exe : warning DARK0004 : Unable to find existing file=20 = D:\msm_bin\extract\FileTableName.AE66FADE_B694_436B_BC4B_3953E76FB78F to = place in src location \PROVIDER\FILENAME.DLL. Will likely = cause a linker=20 break. Note: There is a DARK0004 warning for each file in the cab. And = the directory msm_bin=20 from the command line is empty. ----- Original Message -----=20 From: Rob Mensching<mailto:ro...@us...>=20 To: 'Vitaly Dolya'<mailto:vd...@tm...> ; = wix...@li...<mailto:wix...@li...>=20 Cc: 'Tom Kufeldt'<mailto:tku...@ho...>=20 Sent: Thursday, December 30, 2004 10:09 AM Subject: RE: [WiX-users] Dark Error - error DARK0047 : Failed to = close cab 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=20 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 -----=20 From: Tom Kufeldt<mailto:tku...@ho...>=20 To: = ro...@us...<mailto:ro...@us...> ; = wix...@li...<mailto:wix...@li...>=20 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 -----=20 From: Rob Mensching<mailto:ro...@us...>=20 To: 'Tom Kufeldt'<mailto:tku...@ho...> ; = wix...@li...<mailto:wix...@li...>=20 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=20 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? |