> MSIs created by WiX toolset will run fine (as long as you target Windows
> Installer that supports Win2k).
> However, any WiX code that gets carried with your MSI (like custom actions or
> Burn) require WinXP SP2+.
Looking at the verbose log files it looks as though some custom actions must be
at work behind the scenes.
MSI (s) (EC:C0) [00:49:34:669]: Doing action: ConfigureUsers
Action 00:49:34: ConfigureUsers.
Action start 00:49:34: ConfigureUsers.
MSI (s) (EC:60) [00:49:34:713]: Invoking remote custom action. DLL:
C:\WINNT\Installer\MSI2.tmp, Entrypoint: ConfigureUsers
MSI (s) (EC:A0) [00:49:34:713]: Generating random cookie.
MSI (s) (EC:A0) [00:49:34:713]: Created Custom Action Server with PID 1108
(0x454).
MSI (s) (EC:98) [00:49:34:768]: Running as a service.
MSI (s) (EC:5C) [00:49:34:780]: Hello, I'm your 32bit Impersonated custom
action server.
Action ended 00:49:34: ConfigureUsers. Return value 3.
My installer is using these extensions.
xmlns:netfx="http://schemas.microsoft.com/wix/NetFxExtension";
xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";
xmlns:fw="http://schemas.microsoft.com/wix/FirewallExtension";
It's presumably these extensions that cannot run on Windows 2000 because it has
an old version of the Visual C++ runtime.
Would installing a newer version of the VC++ runtime on the Windows 2000 allow
the installer to run?
Andrew
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
