How to inspect a XPe qfi update to make a DUA pkg

[jimt]

I am interested in using the self-extract feature of XPe updates. The XPe
SP2 FP2007 help at this url:

http://msdn2.microsoft.com/en-us/library/aa940850.aspx

says that you can inspect a runtime XPe update by executing the update exe
with a /x option. However the WINDOWSXP-KB923789-X86-ENU.EXE upgrade on the
X13-38770.img file (from the restricted OEM website) reports /C as the
option when /? is used as the command line switch. Furthermore the /C
option does not extract anything, instead it seems to try and apply the
patch. The /x switch causes a popup msg of "Another copy of the 'KB923789'
package is already running on your system. You can only run one copy at a
time."

In addition there is no accompanying .RTF file to describe this package.

How can we create a DUA package without being able to examine the contents
of the update? As a workaround I am using winzip to examine the individual
files of the update. Still, it seems like the extract option should work
too.

 

[KM]

I can't comment on why Microsoft keep changing the command line switches for those update installers - I just don't know why. It
does seem to be confusing to everyone who's trying to use it :-(

Anyway, the update you mention does support extracting files [extract only, no installation] but you have to be *careful* with the
command line parameters. It tool mea while to figure out that the installer doesn't like relative paths but only accepts absolute
path [/T option].

Try the following command:
WindowsXP-KB923789-x86-ENU.exe /C /T:c:\temp /Q

Feel free to change the path but keep it in the same style - <drive>:\directory\...

 

[jimt]

Thanks KM, your suggestion for running self-extraction worked.

The only remaining issue would be the missing .RTF documentation files. I
have heard they just aren't ready based on the MS release procedure and
tools. Too bad, as they supply some important registry change information
for the update, which is required to construct a DUA update pkg. The
workaround is to pick this info out of the update's .ini file.