Re: [WiX-users] WiX support for (gulp!) WinNT4
On 05-May-12 10:31 AM, Bob Arnson wrote: Are you using the same OS on the build machine? I am almost certain that I used the same OS on the build machine (64-bit Windows 7). But obviously there have been a lot of updates to Windows since then. I was able to successfully build a NT4-compatible MSI using an older WinXP VM. I used the WIXUI_DONTVALIDATEPATH trick to make it get past the validation issue as well. Thank you very much! --Quinton Tormanen -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX support for (gulp!) WinNT4
On 02-May-12 11:51, Quinton Tormanen wrote: The schema is 200, and when built back in 2010 using the same source and toolset it worked up until the path validation. Are you using the same OS on the build machine? MSI (c) (88:6F): Note: 1: 2203 2: rmcwin.msi 3: -2147286779 MSI (c) (88:6F): MainEngineThread is returning 1620 -2147286779 is STG_E_OLDDLL, which means The compound file %1 was produced with a newer version of storage. It's possible a newer OS or OS component is creating the .msi file in a way that can't be read on NT4. I've never heard of that before but then NT4 isn't exactly a common target in 2012... -- sig://boB http://joyofsetup.com/ -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX support for (gulp!) WinNT4
On 01-May-12 20:03, Bob Arnson wrote: See wix.chm on WIXUI_DONTVALIDATEPATH for how to skip validation. That sounds perfect Bob. Unfortunately, now when I build from the same source/toolset, the resulting MSI won't start at all. It gives error 1620 on WinNT4+SP6 (but works on newer OSes). This happens, of course, with or without your WIXUI_DONTVALIDATEPATH property. The schema is 200, and when built back in 2010 using the same source and toolset it worked up until the path validation. Is there anything I can do to determine exactly what caused MSIEXEC 2.00.2600.2 to reject the MSI file? The only ICE I get through Orca is ICE66: Complete functionality of the Shortcut table is only available with Windows Installer version 4.0. Your schema is 200. This is likely caused by the presence of the (empty) Display* and Description* columns. But I got that in the MSI file built in 2010 as well. Here is the short log that is generated by MSIEXEC 2.00.2600.2 on WinNT4+SP6: === Verbose logging started: 5/2/12 7:45:13 Build type: SHIP UNICODE 2.00.2600.02 Calling process: C:\WINNT\system32\msiexec.exe === MSI (c) (88:6F): Resetting cached policy values MSI (c) (88:6F): Machine policy value 'Debug' is 0 MSI (c) (88:6F): *** RunEngine: *** Product: rmcwin.msi *** Action: *** CommandLine: ** MSI (c) (88:6F): Note: 1: 2203 2: rmcwin.msi 3: -2147286779 MSI (c) (88:6F): MainEngineThread is returning 1620 === Verbose logging stopped: 5/2/12 7:45:13 === -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX support for (gulp!) WinNT4
All versions of WiX can generate MSIs targeting any version of Windows Installer. However, you will have to be very careful about using WiX toolset custom actions (usually via Extensions) because we compile against the latest security approved CRTs which sets our minimum OS level to what is still in support by Microsoft (and sometimes a little less). I bet you're using the WixUI and that has a custom action in it to verify paths. You'll have to hack that out (basically, create your own UI) to get it all to run on NT4. On Mon, Apr 30, 2012 at 4:00 PM, Quinton Tormanen quint...@deltamotion.comwrote: We have an older product that supports WinNT4 (with SP6+IE4). The installer for this product was built using WiX 3.0.5419.0. The last release was November 2010. We found that running the MSI file on WinNT4+SP6+IE4 appears to work except that the user cannot get past selecting a target folder, because clicking Next always reports Installation directory must be on a local hard drive even for C:\Program Files\RMCWin. Just today, I rebuilt the MSI file using the same source and WiX toolset (3.0.5419.0). However, this time, running the MSI file on WinNT4+SP6+IE4 gives error 1620 (This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package) immediately. Both MSI files are marked with Schema 200, and the pristine WinNT4+SP6+IE4 virtual machine has Windows Installer 2.00.2600.2 installed on it. Question #1: Any ideas on the source of either failure mode, or why it changed when building with the same source and toolset but on very different dates? The toolset and source are version controlled by Perforce. Question #1: What versions of WiX can generate Window NT4+SP6/WindowsInstaller2.00 compatible MSI files? Quinton Tormanen Software Engineer Delta Computer Systems, Inc. http://www.deltamotion.comhttp://www.deltamotion.com/ -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX support for (gulp!) WinNT4
On 01-May-12 11:17, Rob Mensching wrote: I bet you're using the WixUI and that has a custom action in it to verify paths. You'll have to hack that out (basically, create your own UI) to get it all to run on NT4. See wix.chm on WIXUI_DONTVALIDATEPATH for how to skip validation. -- sig://boB http://joyofsetup.com/ -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WiX support for (gulp!) WinNT4
We have an older product that supports WinNT4 (with SP6+IE4). The installer for this product was built using WiX 3.0.5419.0. The last release was November 2010. We found that running the MSI file on WinNT4+SP6+IE4 appears to work except that the user cannot get past selecting a target folder, because clicking Next always reports Installation directory must be on a local hard drive even for C:\Program Files\RMCWin. Just today, I rebuilt the MSI file using the same source and WiX toolset (3.0.5419.0). However, this time, running the MSI file on WinNT4+SP6+IE4 gives error 1620 (This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package) immediately. Both MSI files are marked with Schema 200, and the pristine WinNT4+SP6+IE4 virtual machine has Windows Installer 2.00.2600.2 installed on it. Question #1: Any ideas on the source of either failure mode, or why it changed when building with the same source and toolset but on very different dates? The toolset and source are version controlled by Perforce. Question #1: What versions of WiX can generate Window NT4+SP6/WindowsInstaller2.00 compatible MSI files? Quinton Tormanen Software Engineer Delta Computer Systems, Inc. http://www.deltamotion.comhttp://www.deltamotion.com/ -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
