Re: [WiX-users] Bundle fails on WIN2K machine .exe is not a valid Win32 application
- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: Monday, April 30, 2012 15:57 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Bundle fails on WIN2K machine .exe is not a valid Win32 application I agree with dropping support for Win2k but what is a shame is that running the exe doesn't display a more useful error message. I don't suppose there is anything that can be done to change this? Neil -- 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 -- Swish - Easy SFTP for Windows Explorer (http://www.swish-sftp.org) -- 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 -- Swish - Easy SFTP for Windows Explorer (http://www.swish-sftp.org) -- 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] Bundle fails on WIN2K machine .exe is not a valid Win32 application
-Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Wednesday, May 09, 2012 05:44 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Bundle fails on WIN2K machine .exe is not a valid Win32 application To pass a security review at Microsoft, the VS2010 CRT must be used. The VS2010 CRT has the latest security defenses built in. Unfortunately, the VS2010 CRT does not run on Win2K. The bad error message actually happens in the VS2010 CRT. Our code in Burn doesn't even have the opportunity to load. A simple VC2008 C program could do something like this, as a sort of bootloader-for-the-bootloader: 1. Check version of Windows. 2. If Win2000 or Win XP before SP3, throw friendly error message and exit. (maybe ShellExecute to user's default browser for Windows Update if on XP) 3. Extract the contained Burn installer (note: does not go and get from Internet!). 4. Launch the VS2010 compiled Burn. The idea is to just do a version check, and then start the real installer. Of course, newer VS versions introduce new security features so I understand and support the idea behind this policy for large applications. But this is a simple application whose scope will be very limited. I would think a very thorough code review should uncover any issues. (Besides, how are you going to attack a dumb *bootloader* like this that doesn't even communicate?) This is especially a critical point because it's the very first thing the user sees, as a first run out-of-box experience. A broken installer with an obscure error message means the user will just move on. Also, because Burn is going to be widely used within Microsoft and ISVs, this is going to be a very common problem - all the more reason to fix it. If exceptions to this rule can't be made for cases like this then I think someone up top needs their head checked. As it stands now, I guess every WiX customer who wants to address this issue is going to have to reinvent the wheel that I have just proposed, just because of this policy. Next version will be even more interesting since last I checked VS11 CRT only supports Win7+ (which I believe cuts support for WinXP SP3 and Vista before they are out of service). Vista too?! That pretty much rules out every PC older than a couple years old... let's say 3 years by the time VS11 releases... unless the user upgraded from Vista to 7. That's just out of touch with reality - I know a lot of people who (1) own computers more than a couple years old, (2) don't have the money to buy a new one, (3) don't have the expertise or money to upgrade to Windows 7. People like us who are comfortable upgrading to the latest Windows operating system are the exception - not the rule. (Perhaps Apple has found the secret, with frequent easy-to-install $29 upgrades?) Most people I know don't buy new computers every couple years. That includes myself - at home, I was running Vista on both my personal laptop and desktop until earlier this year. That's because Vista was good enough and I wasn't anxious enough to spend $$$ and time reformatting to get the fancy new Windows 7 taskbar. Unfortunately, both computers experienced hard drive crashes and now I have a new Win7 laptop; the desktop hasn't been addressed yet. Had I not experienced these hardware failures, I'd likely still be running Vista when VS11 comes out. (I never really understood/understand all the hate directed against Vista, and the love directed towards Windows 7. They are very similar operating systems. I suspect Vista got an unfair bad rap because the independent hardware vendors / independent software wasn't ready yet for the big changes; by the time Win7 came around, they had their act together. I used Vista even before SP1 came out and didn't really have any big complaints.) -- 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] Bundle fails on WIN2K machine .exe is not a valid Win32 application
On 09/05/2012 20:49, James Johnston wrote: Vista too?! No, they're just dropping support for XP/Server 2003. -- Bruce Cran -- 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] Bundle fails on WIN2K machine .exe is not a valid Win32 application
A simple VC2008 C program could do something like this, as a sort of bootloader-for-the-bootloader: This sounds like good idea. If the source for this was part of WiX and simple to build (i.e. not dependant on lot of external components) we could implement our own versions if Microsoft standards prohibit that. Could the same be achieved by recompiling the code in src\burn\stub and then extracting and replacing the burn engine using insignia? Or is the engine integral to the whole process? Neil -Original Message- From: James Johnston [mailto:johnst...@inn-soft.com] Sent: 09 May 2012 20:49 To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Bundle fails on WIN2K machine .exe is not a valid Win32 application -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Wednesday, May 09, 2012 05:44 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Bundle fails on WIN2K machine .exe is not a valid Win32 application To pass a security review at Microsoft, the VS2010 CRT must be used. The VS2010 CRT has the latest security defenses built in. Unfortunately, the VS2010 CRT does not run on Win2K. The bad error message actually happens in the VS2010 CRT. Our code in Burn doesn't even have the opportunity to load. A simple VC2008 C program could do something like this, as a sort of bootloader-for-the-bootloader: 1. Check version of Windows. 2. If Win2000 or Win XP before SP3, throw friendly error message and exit. (maybe ShellExecute to user's default browser for Windows Update if on XP) 3. Extract the contained Burn installer (note: does not go and get from Internet!). 4. Launch the VS2010 compiled Burn. The idea is to just do a version check, and then start the real installer. Of course, newer VS versions introduce new security features so I understand and support the idea behind this policy for large applications. But this is a simple application whose scope will be very limited. I would think a very thorough code review should uncover any issues. (Besides, how are you going to attack a dumb *bootloader* like this that doesn't even communicate?) This is especially a critical point because it's the very first thing the user sees, as a first run out-of-box experience. A broken installer with an obscure error message means the user will just move on. Also, because Burn is going to be widely used within Microsoft and ISVs, this is going to be a very common problem - all the more reason to fix it. If exceptions to this rule can't be made for cases like this then I think someone up top needs their head checked. As it stands now, I guess every WiX customer who wants to address this issue is going to have to reinvent the wheel that I have just proposed, just because of this policy. Next version will be even more interesting since last I checked VS11 CRT only supports Win7+ (which I believe cuts support for WinXP SP3 and Vista before they are out of service). Vista too?! That pretty much rules out every PC older than a couple years old... let's say 3 years by the time VS11 releases... unless the user upgraded from Vista to 7. That's just out of touch with reality - I know a lot of people who (1) own computers more than a couple years old, (2) don't have the money to buy a new one, (3) don't have the expertise or money to upgrade to Windows 7. People like us who are comfortable upgrading to the latest Windows operating system are the exception - not the rule. (Perhaps Apple has found the secret, with frequent easy-to-install $29 upgrades?) Most people I know don't buy new computers every couple years. That includes myself - at home, I was running Vista on both my personal laptop and desktop until earlier this year. That's because Vista was good enough and I wasn't anxious enough to spend $$$ and time reformatting to get the fancy new Windows 7 taskbar. Unfortunately, both computers experienced hard drive crashes and now I have a new Win7 laptop; the desktop hasn't been addressed yet. Had I not experienced these hardware failures, I'd likely still be running Vista when VS11 comes out. (I never really understood/understand all the hate directed against Vista, and the love directed towards Windows 7. They are very similar operating systems. I suspect Vista got an unfair bad rap because the independent hardware vendors / independent software wasn't ready yet for the big changes; by the time Win7 came around, they had their act together. I used Vista even before SP1 came out and didn't really have any big complaints.) -- 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
Re: [WiX-users] Bundle fails on WIN2K machine .exe is not a valid Win32 application
That isn't what Rob said Next version will be even more interesting since last I checked VS11 CRT only supports Win7+ (which I believe cuts support for WinXP SP3 and Vista before they are out of service). A bit off topic but does anyone know where there is any definite statement on this? Neil -Original Message- From: Bruce Cran [mailto:br...@cran.org.uk] Sent: 09 May 2012 21:23 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Bundle fails on WIN2K machine .exe is not a valid Win32 application On 09/05/2012 20:49, James Johnston wrote: Vista too?! No, they're just dropping support for XP/Server 2003. -- Bruce Cran -- 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 -- 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] Bundle fails on WIN2K machine .exe is not a valid Win32 application
On 09/05/2012 22:09, Neil Sleightholm wrote: That isn't what Rob said Next version will be even more interesting since last I checked VS11 CRT only supports Win7+ (which I believe cuts support for WinXP SP3 and Vista before they are out of service). A bit off topic but does anyone know where there is any definite statement on this? Sorry - from the VS11 beta download page it looks like the requirements _have_ moved on, to drop support for Vista (http://www.microsoft.com/visualstudio/11/en-us/downloads/go-live - Visual Studio 11 Beta – Windows 7 and Windows Server 2008 R2). When the developer preview was released there was a discussion at http://connect.microsoft.com/VisualStudio/feedback/details/690617 and then the official response was: Thanks for the report. This behavior is by design in MFC and CRT for Visual Studio vNext. The minimum supported operating systems are Windows Server 2008 SP2 and Windows Vista. Windows XP is not a supported operating system for the release (design-time or run-time). -- Bruce Cran -- 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] Bundle fails on WIN2K machine .exe is not a valid Win32 application
To pass a security review at Microsoft, the VS2010 CRT must be used. The VS2010 CRT has the latest security defenses built in. Unfortunately, the VS2010 CRT does not run on Win2K. The bad error message actually happens in the VS2010 CRT. Our code in Burn doesn't even have the opportunity to load. I expect the custom actions in the WiX toolset have similar issues to Burn. The root issue is that the VC++ team made the decision to cut backwards compatibility to only supported Windows OS's. Next version will be even more interesting since last I checked VS11 CRT only supports Win7+ (which I believe cuts support for WinXP SP3 and Vista before they are out of service). On Wed, May 2, 2012 at 11:49 AM, Alexander Lamaison sw...@lammy.co.ukwrote: I remain confused how this problem has arisen in the first place. WiX was (obviously) being compiled with versions of VS that support Win2K, Win XP. So what's changed? Windows XP hasn't changed under our feet. So that leaves WiX. What features of the newer versions of Windows and/or VS are so indispensable that they force WiX to be platform-dependent? Alex P.S. I'm happy to help restore backward comaptibility to the C++ parts of WiX but I would need someone else to do the same for the .net code; that's not my speciality. On 2 May 2012 18:50, James Johnston johnst...@inn-soft.com wrote: http://www.netmarketshare.com/operating-system-market-share.aspx?qprid=11qp customb=0qptimeframe=Mqpsp=149qpnp=11 ^-- Source of my data in this message... That is something that has been bugging me too while reading this discussion. So my random thoughts on this topic of OS compatibility... The cryptic error originally reported by OP isn't good. We only support Windows XP SP3+ as well, but if the user double-clicks the bootstrapper / self-extracting EXE, they need to get a messaging saying they need XP - not some cryptic error that might turn a user away from our application. Unfortunately, with the way Visual C++ has been dumping support for older versions of Windows, it looks like we would need to retain an older Visual C++ compiler (or find a competing compiler) for the sole purpose of making our own custom bootstrapper that shows a reasonable error. What a pain! Would be nice if WiX prevented this piece of overhead... From that link, I would guess that Windows 2000 usage must be close to zero (lumped into the 2.51% Other category). I'm less worried about that. But there's still significant XP usage, and dumping support for pre-SP2 versions of XP is disturbing. How can the bootstrapper request the user to install SP3 if the bootstrapper itself requires SP2/SP3? From what I have read, the situation gets much worse with VS11 since it drops XP support completely. This is a problem, because apparently XP still has 46% of the market. I know many of our customers still use it. We can't drop support for it. VS11 is out of touch with reality in this respect. If bootstrappers and/or custom actions start requiring Vista+, we'd have to avoid the newer versions of WiX. We'll also have to avoid VS11 ourselves for the time being. The improvements in VS11 might not justify dropping support for a lot of our customers, if it turns out not to be realistic to ask them to upgrade. And the concerns I already outlined about bootstrappers not failing gracefully apply doubly-so here - even if XP drops to, say, 10% of the market and we decide to drop support, there's still enough out there that we need the bootstrapper to kindly request Vista+. It would be nice if XP suffered a precipitous drop in market share this year, but I doubt it. Hopefully it will go away soon. I suspect it will still be common for another 2 years until companies are forced to move away from it when MS finally kills support (or suffer the security liability from an unpatched/unsupported OS). Some people/companies tend to avoid change until their lack of planning forces them into it - and maybe MS dropping support will push them over the edge to get Win7/8. By then, VS12 would be coming down the pipeline, and companies like us would still be stuck on VS2010 or older due to XP compatibility concerns if we decide not to drop support for XP just yet. (XP is the energizer bunny or something... it keeps going and going. I can't remember another consumer OS version that has had such a long life cycle!) James -Original Message- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: Monday, April 30, 2012 15:57 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Bundle fails on WIN2K machine .exe is not a valid Win32 application I agree with dropping support for Win2k but what is a shame is that running the exe doesn't display a more useful error message. I don't suppose there is anything that can be done to change
Re: [WiX-users] Bundle fails on WIN2K machine .exe is not a valid Win32 application
Sadly no. CRT dies before ever loading Burn code. On Mon, Apr 30, 2012 at 8:57 AM, Neil Sleightholm n...@x2systems.comwrote: I agree with dropping support for Win2k but what is a shame is that running the exe doesn't display a more useful error message. I don't suppose there is anything that can be done to change this? Neil -- 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] Bundle fails on WIN2K machine .exe is not a valid Win32 application
You might find the bootstrapper in Visual Studio 2008 to be useful. We're using it to deal with the .NET Framework 2.0 prerequisite, and it works fine even on Win XP RTM (untested on Win2K). (.NET 2.0 is the minimum we require because Vista RTM includes .NET 2.0, so prerequisite install is only needed for XP customers.) The bootstrapper can automatically download the framework from Microsoft and install it. After seeing how few Vista customers there are though, I don't really see a good reason to prefer it over .NET Framework 3.5, which I guess comes with Windows 7. As I recall, the big gripe I had with .NET 3.5 was that it was extremely bloated, making the ~20 MB .NET 2.0 install look like nothing. For the Visual C++ 2008 runtimes, we just use the merge modules. If you have other prereqs, you can add them. If your requirements are much more complex though, I would imagine you'd be better off with something like Burn. As a customer who gets my credit card information swiped at the store, I would hope that the Win2K machines aren't Internet-facing at all. No security patches I would imagine these days... -Original Message- From: rdinglebham [mailto:rdin...@accelitec.com] Sent: Wednesday, May 02, 2012 19:28 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Bundle fails on WIN2K machine .exe is not a valid Win32 application The problem surfaced when I started bundling my MSI packages in order to take advantage of bootstrapping the perquisites like .NET Framework 2.0 SP2, C++ run time libraries. We've been careful to build all of our client adapters in .NET 2.0/VS2008 since WIN2K is still widely used in the retail world - we have a number of customers that have a mix of XPE and WIN2K in a single store... So my WiX 3.6 MSI packages work just fine; it's the WiX 3.6 burn binaries that are embedded into the .EXE that are incapable with WIN2K. At this point I'm just copying both the bundle EXE and the MSI to my customer dropboxes. I'm just glad that I wrote all my custom actions in C# and not C++! -- 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] Bundle fails on WIN2K machine .exe is not a valid Win32 application
http://www.netmarketshare.com/operating-system-market-share.aspx?qprid=11qp customb=0qptimeframe=Mqpsp=149qpnp=11 ^-- Source of my data in this message... That is something that has been bugging me too while reading this discussion. So my random thoughts on this topic of OS compatibility... The cryptic error originally reported by OP isn't good. We only support Windows XP SP3+ as well, but if the user double-clicks the bootstrapper / self-extracting EXE, they need to get a messaging saying they need XP - not some cryptic error that might turn a user away from our application. Unfortunately, with the way Visual C++ has been dumping support for older versions of Windows, it looks like we would need to retain an older Visual C++ compiler (or find a competing compiler) for the sole purpose of making our own custom bootstrapper that shows a reasonable error. What a pain! Would be nice if WiX prevented this piece of overhead... From that link, I would guess that Windows 2000 usage must be close to zero (lumped into the 2.51% Other category). I'm less worried about that. But there's still significant XP usage, and dumping support for pre-SP2 versions of XP is disturbing. How can the bootstrapper request the user to install SP3 if the bootstrapper itself requires SP2/SP3? From what I have read, the situation gets much worse with VS11 since it drops XP support completely. This is a problem, because apparently XP still has 46% of the market. I know many of our customers still use it. We can't drop support for it. VS11 is out of touch with reality in this respect. If bootstrappers and/or custom actions start requiring Vista+, we'd have to avoid the newer versions of WiX. We'll also have to avoid VS11 ourselves for the time being. The improvements in VS11 might not justify dropping support for a lot of our customers, if it turns out not to be realistic to ask them to upgrade. And the concerns I already outlined about bootstrappers not failing gracefully apply doubly-so here - even if XP drops to, say, 10% of the market and we decide to drop support, there's still enough out there that we need the bootstrapper to kindly request Vista+. It would be nice if XP suffered a precipitous drop in market share this year, but I doubt it. Hopefully it will go away soon. I suspect it will still be common for another 2 years until companies are forced to move away from it when MS finally kills support (or suffer the security liability from an unpatched/unsupported OS). Some people/companies tend to avoid change until their lack of planning forces them into it - and maybe MS dropping support will push them over the edge to get Win7/8. By then, VS12 would be coming down the pipeline, and companies like us would still be stuck on VS2010 or older due to XP compatibility concerns if we decide not to drop support for XP just yet. (XP is the energizer bunny or something... it keeps going and going. I can't remember another consumer OS version that has had such a long life cycle!) James -Original Message- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: Monday, April 30, 2012 15:57 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Bundle fails on WIN2K machine .exe is not a valid Win32 application I agree with dropping support for Win2k but what is a shame is that running the exe doesn't display a more useful error message. I don't suppose there is anything that can be done to change this? Neil -- 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] Bundle fails on WIN2K machine .exe is not a valid Win32 application
I remain confused how this problem has arisen in the first place. WiX was (obviously) being compiled with versions of VS that support Win2K, Win XP. So what's changed? Windows XP hasn't changed under our feet. So that leaves WiX. What features of the newer versions of Windows and/or VS are so indispensable that they force WiX to be platform-dependent? Alex P.S. I'm happy to help restore backward comaptibility to the C++ parts of WiX but I would need someone else to do the same for the .net code; that's not my speciality. On 2 May 2012 18:50, James Johnston johnst...@inn-soft.com wrote: http://www.netmarketshare.com/operating-system-market-share.aspx?qprid=11qp customb=0qptimeframe=Mqpsp=149qpnp=11 ^-- Source of my data in this message... That is something that has been bugging me too while reading this discussion. So my random thoughts on this topic of OS compatibility... The cryptic error originally reported by OP isn't good. We only support Windows XP SP3+ as well, but if the user double-clicks the bootstrapper / self-extracting EXE, they need to get a messaging saying they need XP - not some cryptic error that might turn a user away from our application. Unfortunately, with the way Visual C++ has been dumping support for older versions of Windows, it looks like we would need to retain an older Visual C++ compiler (or find a competing compiler) for the sole purpose of making our own custom bootstrapper that shows a reasonable error. What a pain! Would be nice if WiX prevented this piece of overhead... From that link, I would guess that Windows 2000 usage must be close to zero (lumped into the 2.51% Other category). I'm less worried about that. But there's still significant XP usage, and dumping support for pre-SP2 versions of XP is disturbing. How can the bootstrapper request the user to install SP3 if the bootstrapper itself requires SP2/SP3? From what I have read, the situation gets much worse with VS11 since it drops XP support completely. This is a problem, because apparently XP still has 46% of the market. I know many of our customers still use it. We can't drop support for it. VS11 is out of touch with reality in this respect. If bootstrappers and/or custom actions start requiring Vista+, we'd have to avoid the newer versions of WiX. We'll also have to avoid VS11 ourselves for the time being. The improvements in VS11 might not justify dropping support for a lot of our customers, if it turns out not to be realistic to ask them to upgrade. And the concerns I already outlined about bootstrappers not failing gracefully apply doubly-so here - even if XP drops to, say, 10% of the market and we decide to drop support, there's still enough out there that we need the bootstrapper to kindly request Vista+. It would be nice if XP suffered a precipitous drop in market share this year, but I doubt it. Hopefully it will go away soon. I suspect it will still be common for another 2 years until companies are forced to move away from it when MS finally kills support (or suffer the security liability from an unpatched/unsupported OS). Some people/companies tend to avoid change until their lack of planning forces them into it - and maybe MS dropping support will push them over the edge to get Win7/8. By then, VS12 would be coming down the pipeline, and companies like us would still be stuck on VS2010 or older due to XP compatibility concerns if we decide not to drop support for XP just yet. (XP is the energizer bunny or something... it keeps going and going. I can't remember another consumer OS version that has had such a long life cycle!) James -Original Message- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: Monday, April 30, 2012 15:57 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Bundle fails on WIN2K machine .exe is not a valid Win32 application I agree with dropping support for Win2k but what is a shame is that running the exe doesn't display a more useful error message. I don't suppose there is anything that can be done to change this? Neil -- 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 -- Swish - Easy SFTP for Windows Explorer (http://www.swish-sftp.org) -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape
Re: [WiX-users] Bundle fails on WIN2K machine .exe is not a valid Win32 application
The problem surfaced when I started bundling my MSI packages in order to take advantage of bootstrapping the perquisites like .NET Framework 2.0 SP2, C++ run time libraries. We've been careful to build all of our client adapters in .NET 2.0/VS2008 since WIN2K is still widely used in the retail world - we have a number of customers that have a mix of XPE and WIN2K in a single store... So my WiX 3.6 MSI packages work just fine; it's the WiX 3.6 burn binaries that are embedded into the .EXE that are incapable with WIN2K. At this point I'm just copying both the bundle EXE and the MSI to my customer dropboxes. I'm just glad that I wrote all my custom actions in C# and not C++! Rich - Rich Dingle Accelitec, Inc. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bundle-fails-on-WIN2K-machine-exe-is-not-a-valid-Win32-application-tp7507520p7521373.html Sent from the wix-users mailing list archive at Nabble.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] Bundle fails on WIN2K machine .exe is not a valid Win32 application
I agree with dropping support for Win2k but what is a shame is that running the exe doesn't display a more useful error message. I don't suppose there is anything that can be done to change this? Neil -- 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] Bundle fails on WIN2K machine .exe is not a valid Win32 application
All, Thanks for clearing that up. In the end not having a WIN2K bundle isn't that big a deal; the .MSI's run flawlessly and that's what counts. So a quick note of appreciation: We've been using WiX for almost three years to deploy/update client API adapters that connect 3rd party POS systems (mainly in grocery) to our Cloud based services. The power and flexibility of the WiX tool set has proved to be a critical component to scaling our solution - deploying thousands of client adapters. In our B2B world it's our ability to integrate with a customer's /existing/ platform that has proved a game changer. As an example, one of MSI packages, using C# Custom Actions, reads the 3rd party values in the registry and .ini files then selects the correct API.DLL to install (currently eight different versions), suppresses UI dialogue if it's self-checkout unit, updates our .NET app config files, and manages the GAC entries, etc. If the customer installs a POS patch then a simple Repair updates the API DLL. One click of script to run the WiX MSI in quiet mode replaces an 10 page/10 minute manual install procedure - InstallSheild package plus system configuration changes. Cheers! Rich - Rich Dingle Accelitec, Inc. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bundle-fails-on-WIN2K-machine-exe-is-not-a-valid-Win32-application-tp7507520p7514752.html Sent from the wix-users mailing list archive at Nabble.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] Bundle fails on WIN2K machine .exe is not a valid Win32 application
If you vowed never to build WiX again, then it probably is not feasible. Burn is in wix\src\burn (burn.build) and as Bob noted if you want wixstdba then you'll need to build wix\src\ext\BalExtension\wixsdtba. Both are in WiX so that will require breaking your vow. smile/ On Sat, Apr 28, 2012 at 2:01 PM, Alexander Lamaison sw...@lammy.co.ukwrote: On 28 April 2012 21:18, Bob Arnson b...@joyofsetup.com wrote: On 28-Apr-12 08:08, Alexander Lamaison wrote: Is there a way round this? Can I easily compile the bootstrapper application myself with VS 2005? You'd have to do the same thing to all of Burn too. Is this feasible? I once tried to build WiX and vowed never ever ever again. Can Burn be built independently of the rest of WiX? -- Swish - Easy SFTP for Windows Explorer (http://www.swish-sftp.org) -- 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] Bundle fails on WIN2K machine .exe is not a valid Win32 application
NOTE: Win2k was out of support before WiX v3.6 even started development. We obviously don't test the code there so I really have no idea how much work it will be to make any of the native code built by WiX (Burn, and CustomActions mainly) working on Win2k. On Sun, Apr 29, 2012 at 12:04 AM, Rob Mensching r...@robmensching.comwrote: If you vowed never to build WiX again, then it probably is not feasible. Burn is in wix\src\burn (burn.build) and as Bob noted if you want wixstdba then you'll need to build wix\src\ext\BalExtension\wixsdtba. Both are in WiX so that will require breaking your vow. smile/ On Sat, Apr 28, 2012 at 2:01 PM, Alexander Lamaison sw...@lammy.co.ukwrote: On 28 April 2012 21:18, Bob Arnson b...@joyofsetup.com wrote: On 28-Apr-12 08:08, Alexander Lamaison wrote: Is there a way round this? Can I easily compile the bootstrapper application myself with VS 2005? You'd have to do the same thing to all of Burn too. Is this feasible? I once tried to build WiX and vowed never ever ever again. Can Burn be built independently of the rest of WiX? -- Swish - Easy SFTP for Windows Explorer (http://www.swish-sftp.org) -- 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 -- 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] Bundle fails on WIN2K machine .exe is not a valid Win32 application
'Out of support' is just a marketing term. It doesn't mean it magically stops working. People forget that often. Alex On 29 April 2012 08:06, Rob Mensching r...@robmensching.com wrote: NOTE: Win2k was out of support before WiX v3.6 even started development. We obviously don't test the code there so I really have no idea how much work it will be to make any of the native code built by WiX (Burn, and CustomActions mainly) working on Win2k. On Sun, Apr 29, 2012 at 12:04 AM, Rob Mensching r...@robmensching.comwrote: If you vowed never to build WiX again, then it probably is not feasible. Burn is in wix\src\burn (burn.build) and as Bob noted if you want wixstdba then you'll need to build wix\src\ext\BalExtension\wixsdtba. Both are in WiX so that will require breaking your vow. smile/ On Sat, Apr 28, 2012 at 2:01 PM, Alexander Lamaison sw...@lammy.co.ukwrote: On 28 April 2012 21:18, Bob Arnson b...@joyofsetup.com wrote: On 28-Apr-12 08:08, Alexander Lamaison wrote: Is there a way round this? Can I easily compile the bootstrapper application myself with VS 2005? You'd have to do the same thing to all of Burn too. Is this feasible? I once tried to build WiX and vowed never ever ever again. Can Burn be built independently of the rest of WiX? -- Swish - Easy SFTP for Windows Explorer (http://www.swish-sftp.org) -- 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 -- 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 -- Swish - Easy SFTP for Windows Explorer (http://www.swish-sftp.org) -- 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] Bundle fails on WIN2K machine .exe is not a valid Win32 application
No, we don't forget that. However, at some point you have to trim your tail or you end up with an enormous support burden that prevents you from moving forward. One of the big questions for us in WiX v3.7 is how many versions of VS should we support? It is expensive to keep VS2005 and VS2008 working because they use the inferior MSBuild 2.0 and MSBuild 3.5. Cutting VS2005 and VS2008 cuts a big chunk of our tail and would allow us to do more stuff. In WiX v4.0 I'm pretty sure we support only VS2010 and VS11 (whatever they end up calling that). In WiX v4.0 the big question is do we support Windows XP? VC just dropped support for in in VS11. I hesitate to cut Windows XP support because it is still very popular... but it too is going out of support very soon. These are never easy decisions. On Sun, Apr 29, 2012 at 3:42 AM, Alexander Lamaison sw...@lammy.co.ukwrote: 'Out of support' is just a marketing term. It doesn't mean it magically stops working. People forget that often. Alex On 29 April 2012 08:06, Rob Mensching r...@robmensching.com wrote: NOTE: Win2k was out of support before WiX v3.6 even started development. We obviously don't test the code there so I really have no idea how much work it will be to make any of the native code built by WiX (Burn, and CustomActions mainly) working on Win2k. On Sun, Apr 29, 2012 at 12:04 AM, Rob Mensching r...@robmensching.com wrote: If you vowed never to build WiX again, then it probably is not feasible. Burn is in wix\src\burn (burn.build) and as Bob noted if you want wixstdba then you'll need to build wix\src\ext\BalExtension\wixsdtba. Both are in WiX so that will require breaking your vow. smile/ On Sat, Apr 28, 2012 at 2:01 PM, Alexander Lamaison sw...@lammy.co.uk wrote: On 28 April 2012 21:18, Bob Arnson b...@joyofsetup.com wrote: On 28-Apr-12 08:08, Alexander Lamaison wrote: Is there a way round this? Can I easily compile the bootstrapper application myself with VS 2005? You'd have to do the same thing to all of Burn too. Is this feasible? I once tried to build WiX and vowed never ever ever again. Can Burn be built independently of the rest of WiX? -- Swish - Easy SFTP for Windows Explorer (http://www.swish-sftp.org) -- 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 -- 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 -- Swish - Easy SFTP for Windows Explorer (http://www.swish-sftp.org) -- 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] Bundle fails on WIN2K machine .exe is not a valid Win32 application
Is that not the wrong question? Rather than getting caught up in the ins and outs of which version to support, why not adopt methods that remove the decision entirely? Have you considered using CMake, for example, which generates build files for a vast range of build platforms (including VS 6 - 11)? Basically, you outsource the burden of supporting the long tail to CMake. If a *project* limits itself to a certain platform, then so be it. But its build tools certainly shouldn't. WiX has the double problem of being, itself, a build tool so should neither be limited to a certain platform by its own build tools nor limit projects that use it. Alex On 29 April 2012 18:24, Rob Mensching r...@robmensching.com wrote: No, we don't forget that. However, at some point you have to trim your tail or you end up with an enormous support burden that prevents you from moving forward. One of the big questions for us in WiX v3.7 is how many versions of VS should we support? It is expensive to keep VS2005 and VS2008 working because they use the inferior MSBuild 2.0 and MSBuild 3.5. Cutting VS2005 and VS2008 cuts a big chunk of our tail and would allow us to do more stuff. In WiX v4.0 I'm pretty sure we support only VS2010 and VS11 (whatever they end up calling that). In WiX v4.0 the big question is do we support Windows XP? VC just dropped support for in in VS11. I hesitate to cut Windows XP support because it is still very popular... but it too is going out of support very soon. These are never easy decisions. On Sun, Apr 29, 2012 at 3:42 AM, Alexander Lamaison sw...@lammy.co.ukwrote: 'Out of support' is just a marketing term. It doesn't mean it magically stops working. People forget that often. Alex On 29 April 2012 08:06, Rob Mensching r...@robmensching.com wrote: NOTE: Win2k was out of support before WiX v3.6 even started development. We obviously don't test the code there so I really have no idea how much work it will be to make any of the native code built by WiX (Burn, and CustomActions mainly) working on Win2k. On Sun, Apr 29, 2012 at 12:04 AM, Rob Mensching r...@robmensching.com wrote: If you vowed never to build WiX again, then it probably is not feasible. Burn is in wix\src\burn (burn.build) and as Bob noted if you want wixstdba then you'll need to build wix\src\ext\BalExtension\wixsdtba. Both are in WiX so that will require breaking your vow. smile/ On Sat, Apr 28, 2012 at 2:01 PM, Alexander Lamaison sw...@lammy.co.uk wrote: On 28 April 2012 21:18, Bob Arnson b...@joyofsetup.com wrote: On 28-Apr-12 08:08, Alexander Lamaison wrote: Is there a way round this? Can I easily compile the bootstrapper application myself with VS 2005? You'd have to do the same thing to all of Burn too. Is this feasible? I once tried to build WiX and vowed never ever ever again. Can Burn be built independently of the rest of WiX? -- Swish - Easy SFTP for Windows Explorer (http://www.swish-sftp.org) -- 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 -- 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 -- Swish - Easy SFTP for Windows Explorer (http://www.swish-sftp.org) -- 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 -
Re: [WiX-users] Bundle fails on WIN2K machine .exe is not a valid Win32 application
I fundamentally agree with you. However, building the code for a particular platform is the easiest part of the problem. Keeping the code working (since the platforms differ in subtle ways) is the real challenge. Personally, supporting unsupported platforms is very low on my priority list. I have enough trouble keeping WinXP support working (aka: tested). That platform is still supported and *very* popular. If you want to sign up to contribute the fixes and maintain WiX toolset working on Win2k then I'd love to see the changesets. However, to be completely transparent I'm not really excited about delaying the release of WiX v3.6 for an unsupported platform. There are too many people already looking forward to WiX v3.6 being done now. Thus if Win2k requries radical redesign that's something we'd need to look at for next release. On Sun, Apr 29, 2012 at 10:54 AM, Alexander Lamaison sw...@lammy.co.ukwrote: Is that not the wrong question? Rather than getting caught up in the ins and outs of which version to support, why not adopt methods that remove the decision entirely? Have you considered using CMake, for example, which generates build files for a vast range of build platforms (including VS 6 - 11)? Basically, you outsource the burden of supporting the long tail to CMake. If a *project* limits itself to a certain platform, then so be it. But its build tools certainly shouldn't. WiX has the double problem of being, itself, a build tool so should neither be limited to a certain platform by its own build tools nor limit projects that use it. Alex On 29 April 2012 18:24, Rob Mensching r...@robmensching.com wrote: No, we don't forget that. However, at some point you have to trim your tail or you end up with an enormous support burden that prevents you from moving forward. One of the big questions for us in WiX v3.7 is how many versions of VS should we support? It is expensive to keep VS2005 and VS2008 working because they use the inferior MSBuild 2.0 and MSBuild 3.5. Cutting VS2005 and VS2008 cuts a big chunk of our tail and would allow us to do more stuff. In WiX v4.0 I'm pretty sure we support only VS2010 and VS11 (whatever they end up calling that). In WiX v4.0 the big question is do we support Windows XP? VC just dropped support for in in VS11. I hesitate to cut Windows XP support because it is still very popular... but it too is going out of support very soon. These are never easy decisions. On Sun, Apr 29, 2012 at 3:42 AM, Alexander Lamaison sw...@lammy.co.uk wrote: 'Out of support' is just a marketing term. It doesn't mean it magically stops working. People forget that often. Alex On 29 April 2012 08:06, Rob Mensching r...@robmensching.com wrote: NOTE: Win2k was out of support before WiX v3.6 even started development. We obviously don't test the code there so I really have no idea how much work it will be to make any of the native code built by WiX (Burn, and CustomActions mainly) working on Win2k. On Sun, Apr 29, 2012 at 12:04 AM, Rob Mensching r...@robmensching.com wrote: If you vowed never to build WiX again, then it probably is not feasible. Burn is in wix\src\burn (burn.build) and as Bob noted if you want wixstdba then you'll need to build wix\src\ext\BalExtension\wixsdtba. Both are in WiX so that will require breaking your vow. smile/ On Sat, Apr 28, 2012 at 2:01 PM, Alexander Lamaison sw...@lammy.co.uk wrote: On 28 April 2012 21:18, Bob Arnson b...@joyofsetup.com wrote: On 28-Apr-12 08:08, Alexander Lamaison wrote: Is there a way round this? Can I easily compile the bootstrapper application myself with VS 2005? You'd have to do the same thing to all of Burn too. Is this feasible? I once tried to build WiX and vowed never ever ever again. Can Burn be built independently of the rest of WiX? -- Swish - Easy SFTP for Windows Explorer (http://www.swish-sftp.org) -- 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 -- 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
Re: [WiX-users] Bundle fails on WIN2K machine .exe is not a valid Win32 application
That's just stopped me in my tracks. I've been converting our dotnetinstaller bootstrapper to use Burn but had no idea that would kill our Win2k support. Seriously not good. Is there a way round this? Can I easily compile the bootstrapper application myself with VS 2005? Thanks, Alex On 28 April 2012 05:05, Rob Mensching r...@robmensching.com wrote: No. Windows 2000 is not supported by the VS 2010 CRT. Windows XP (I think SP1+). On Fri, Apr 27, 2012 at 2:34 PM, Rich Dingle rdin...@accelitec.com wrote: Is the WiX Standard Bootstrapper Application compatible with Windows 2000? My individual MSI packages all work fine but all my bundles fail immediately even if I save them to a local folder: [bundleName].exe is not a valid Win32 application. Target Machine: Win2K Pro SP4 w/KB891861 'roll up' MSIEXEC.EXE v3.1.4000.1823 Build Machine: WiX 3.6.2823 VS 2010 Rich Dingle Accelitec, Inc. 2211 Rimland Drive, Suite 230 Bellingham, WA 98226 -- 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 -- Swish - Easy SFTP for Windows Explorer (http://www.swish-sftp.org) -- 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] Bundle fails on WIN2K machine .exe is not a valid Win32 application
For reference: Visual Studio 2010 - The C run-time libraries support Windows XP with SP2, Windows XP with SP3, Windows Server 2003 with SP1, Windows Server 2003 with SP2, Windows Vista, Windows Server 2008, and Windows 7. http://msdn.microsoft.com/en-us/library/ws0swas0.aspx Neil -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: 28 April 2012 05:06 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Bundle fails on WIN2K machine .exe is not a valid Win32 application No. Windows 2000 is not supported by the VS 2010 CRT. Windows XP (I think SP1+). On Fri, Apr 27, 2012 at 2:34 PM, Rich Dingle rdin...@accelitec.com wrote: Is the WiX Standard Bootstrapper Application compatible with Windows 2000? My individual MSI packages all work fine but all my bundles fail immediately even if I save them to a local folder: [bundleName].exe is not a valid Win32 application. Target Machine: Win2K Pro SP4 w/KB891861 'roll up' MSIEXEC.EXE v3.1.4000.1823 Build Machine: WiX 3.6.2823 VS 2010 Rich Dingle Accelitec, Inc. 2211 Rimland Drive, Suite 230 Bellingham, WA 98226 -- 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 -- 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] Bundle fails on WIN2K machine .exe is not a valid Win32 application
On 28-Apr-12 08:08, Alexander Lamaison wrote: Is there a way round this? Can I easily compile the bootstrapper application myself with VS 2005? You'd have to do the same thing to all of Burn too. -- 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] Bundle fails on WIN2K machine .exe is not a valid Win32 application
On 28 April 2012 21:18, Bob Arnson b...@joyofsetup.com wrote: On 28-Apr-12 08:08, Alexander Lamaison wrote: Is there a way round this? Can I easily compile the bootstrapper application myself with VS 2005? You'd have to do the same thing to all of Burn too. Is this feasible? I once tried to build WiX and vowed never ever ever again. Can Burn be built independently of the rest of WiX? -- Swish - Easy SFTP for Windows Explorer (http://www.swish-sftp.org) -- 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] Bundle fails on WIN2K machine .exe is not a valid Win32 application
It sounds like my best option is to simply compile my installers using VS 2008. Is there any reason not to take that approach? Rich - Rich Dingle Accelitec, Inc. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bundle-fails-on-WIN2K-machine-exe-is-not-a-valid-Win32-application-tp7507520p7509753.html Sent from the wix-users mailing list archive at Nabble.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] Bundle fails on WIN2K machine .exe is not a valid Win32 application
No. Windows 2000 is not supported by the VS 2010 CRT. Windows XP (I think SP1+). On Fri, Apr 27, 2012 at 2:34 PM, Rich Dingle rdin...@accelitec.com wrote: Is the WiX Standard Bootstrapper Application compatible with Windows 2000? My individual MSI packages all work fine but all my bundles fail immediately even if I save them to a local folder: [bundleName].exe is not a valid Win32 application. Target Machine: Win2K Pro SP4 w/KB891861 'roll up' MSIEXEC.EXE v3.1.4000.1823 Build Machine: WiX 3.6.2823 VS 2010 Rich Dingle Accelitec, Inc. 2211 Rimland Drive, Suite 230 Bellingham, WA 98226 -- 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
