by modio » 10.11.2013, 13:00
Thank you all for your feedback. As a result of this, I did the following:
1)Set the %tmp & %temp variables to T:\tempu, rebooted and checked that temporary files are being put in this folder.
2)Extracted a brand new wsusoffline folder from wsusoffline872.zip;
3)Ran UpdateGenerator.exe, choosing to download *only* the Microsoft updates for Windows XP (wxp) English (on the “Legacy products” tab). [I have screen prints (pdf) of all three tabs.]
4)When the run completed, I was prompted to look at the download log, The first line of this reads “09/11/2013 13:29:09.34 - Info: Starting WSUS Offline Update download (v. 8.7.2) for wxp enu”.
5)I then cut a dvd, ran UpdateInstaller.exe, and got exactly the same messages as before - “Medium does not support Microsoft Windows (wxp x86 enu). ERROR: Medium neither supports your Windows nor your Office version.”
As far as I can judge, 3) & 4) above seem to be consistent with each other (and with what I intended to happen) whereas 5) seems to be saying the opposite. This led me to wonder where the message in 5) was coming from, and exactly what test was being performed which led to this message. The answer is that these messages come from DoUpdate.cmd, and having traced what this is doing I have a *partial* explanation of what's happening.
DoUpdate.cmd is called by Update.cmd, which in turn is called by UpdateInstaller.exe. On my PC, DoUpdate.cmd does the following (amongst lots of other things):
- It sets %OS_ARCH%=x86, %OS_NAME%=wxp & %OS_LANG%=enu (the values of these variables come from an examination of my PC);
If "%OS_ARCH%” is not equal to "x64", Update.cmd looks for the existence of a folder \%OS_NAME%\%OS_LANG%\ (i.e. \wxp\enu\) in the root of the dvd;
If this folder is absent (which it is) it gives the message that the dvd does not support “wxp x86 enu”.
*My feeling is that all of this is probably the correct behavior as far as DoUpdate.cmd is concerned*.
Whilst the folder \wxp\ is missing from the root of the dvd, there *is* a folder \win\, (on the root), and this contains the following:
\win\enu
\win\glb
\win\enu\mdac281-kb911562-x86-enu_60deceb3484d516b35793e69acbfe5a54647dfec.exe
\win\enu\mdac281-kb927779-x86-enu_c172a91d2de6fdbdc6df8380e4949f518dc2c216.exe
\win\enu\msxml4-kb954430-enu_c40d3e3035b8cea714f27532fea37c05b2d4dc65.exe
\win\enu\msxml4-kb2758694-enu_24abccbcceaf5bea9c3e34ff1f64c2aa3d57e308.exe
\win\enu\msxml6-kb2758696-enu-x86_1e869fb8ae3d16b7d988c9a9e192917b941771d9.exe
\win\enu\stepbystepinteractivetraining-kb898458-x86-enu_6458cedf293b00c645e454ea01582f7ed222d7d7.exe
\win\enu\stepbystepinteractivetraining-kb923723-x86-enu_0aa7706ca52aeec58a05e5782869adc697ca37c7.exe
\win\enu\windows-kb913433-x86-enu_76805425ec45a313720bb61a3f367005b7e5a08d.exe
\win\enu\windowsmedia6-kb925398-v2-x86-enu_c8b7d9a38ecbd2bd8925345d69c53697a285b917.exe
\win\enu\windowsmedia9-kb969878-x86-enu_c512a3bf6fb3be974534bbaf4dacb78808741128.exe
\win\enu\windowsmedia9-kb2447961-x86-enu_4db7f3f902aabca9987e6a0f59a210be1d6aede2.exe
\win\enu\windowsmedia11-kb954154-x86-enu_9b75815f8c5d57dc8e2e22e221fb1a106f9ce6a0.exe
\win\enu\windowsmedia64-kb954600-x86-enu_3b39912a17ea27d6b788a9609353177697911dc4.exe
\win\enu\windowsmedia64-kb974112-x86-enu_da66b8ec1ecd2260a7df5d934b7c880cd665f3b9.exe
\win\enu\windowsrightsmanagementservicessp2-kb917275-client-enu-x86_9b4eeb13ff82a93d6d8ddb3ff9bd6b6890bae1c9.exe
\win\glb\capicom-kb931906-v2102_5891b5de8ce331dc998656e20f1ce0b795e88786.exe
\win\glb\rootsupd.exe
So I think the questions - to which I do not have an answer - are:
a) Why were the folders \wxp\ & \wxp\enu\ not created by wsusoffline, when it seems that this is what should have happened given the combination of what I asked for - 3) above - and the way that DoUpdate.cmd works? This is even more of a puzzle given that the log at 4) seems to suggest that everything has gone to plan at this point.
and
b) Were the folders \win\ & \win\enu\ created instead?