[BlackholeForever]

Tested via a fresh install of Windows 2000 SP4, with Windows Installer v2.0.2600.1183.


MSXML2.6_enu.apm specifies:

[Installation]
"Module:\msxml2.msi" /qn /norestart


/norestart is not a valid command line argument for this version of Windows Installer (see this MSDN article. An attempt to install this patch yields nothing, and rebooting, re-running AutoPatcher will show this as uninstalled (which is correct).

Note: If you also happen to select "Windows Installer 3.1 (v2)" for install in AutoPatcher, eventually this situation would correct itself through repeated runs of AutoPatcher. /norestart is a valid command line argument for Windows Installer v3.x.

To fix:

• Remove the /norestart argument (and change "RequiresReboot" to "False"). This package doesn't appear to require a reboot (verified on a manual install).
  
• Or, specify WindowsInstaller=3.0 in the .APM file.

Just an fyi...

This post has been edited by BlackholeForever: 10 June 2008 - 05:45 PM

[Erik Ramey]

reboot flag removed. Good to go

[pointertovoid]

I believe that Xml3 replaces Xml2.6 and Xml3 is brought by many other updates: Rollup1, Mdac2.8sp1, ie6.0sp1...
And that, even though the files for Xml2.6 are still present, that can't be called by other programs, even malicious ones.

So then, why should we update anything in Xml2.6?

This situation is very different from Xml3 - Xml4 - Xml6 which can and must coexist, as none replaces an other.
It is also different from Wmp6.4 - Wmp9, where Wmp6.4 remains after installing Wmp9 and can be launched by the user and I guess by a Web site as well.

Or did I miss something?

[James]

You are correct, but this Topic refers to obsolete information.

pointertovoid, on Feb 24 2009, 08:51 PM, said:

Or did I miss something?

Yes, you missed the fact that this is no longer included in AutoPatcher.

For a list of the updates currently supported, please see AutoPatcher 2000 Hotfix Depot


Since XML2.6 is no longer supported,

TOPIC CLOSED

--