MSFN Forum: GreenMachine's Complete SVCPACK.INF - MSFN Forum

Jump to content



Unattended CD/DVD Guide Homepage · MSFN Forum Rules
  • 2 Pages +
  • 1
  • 2
  • You cannot start a new topic
  • You cannot reply to this topic

GreenMachine's Complete SVCPACK.INF All the updates installed at T-13 Rate Topic: -----

#1 User is offline   GreenMachine 

  • ineXPlicable
  • Group: Developers
  • Posts: 3,062
  • Joined: 22-August 03

Posted 12 December 2007 - 01:26 AM

In the never ending search for the complete, up to date Windows XP Installation, here is my latest SVCPACK.INF, used to install all the updates and hotfixes for Windows XP Service Pack 2. This list of updates and hotfixes are those I have determined to be neccessary to show Zero Updates needed, High Priority or Recommended, in Wiindows Update. One major obstacle is finding the hotfixes. I use a combination of standard hotfix downloads from Microsoft, inspection of WindowsUpdate.log for update URLs, and NirSoft's Port Sniffer to detect from where the hotfixes are downloaded. Please do the same to find your own hotfixes, and do not bother asking me for direct download links ...

Two problems discussed here and on other forums is how to install the .Net Frameworks (1.1, 2.0 and 3.0), and the IE7 Updates from SVCPACK.INF. This is the only part of the installation that requires "smoke and mirrors". For .Net, the file REG.EXE is extracted from the Windows source, and included in the SVCPACK folder From there it is used to change two entries in the Windows registry to allow the installation of .Net 2.0 and .Net 3.0. The order of installation of these components is also of critical importance. The order shown here was found by trial and error, as was the need for certain "helper" installations, like MSXML6-KB933579-ENU-X86.EXE and XPSEPSC-X86-EN-US.EXE and WIC_X86_ENU.EXE. For those of you wondering, the WebClient Service does not appear to be broken with this order. As I do not use it, I have not tested it as such, but it does show as Started in the Services MMC. This was NOT the case with certain other tested installation orders, where it was always in the "Starting" state. The second problem was to allow the udates to IE7 to succeed. This was achieved by extracting the IEXPLORE.EXE file from the IE7 installation package, compressing it to IEXPLORE.EX_, and replacing the IEXPLORE.EX_ file in the Windows source with the newer version. In addition to these changes, the directory i386\svcpack was created, and all files listed in the SVCPACK.INF file were included here. SVCPACK.INF was compressed to SVCPACK.IN_, and added to the i386 directory. Also the .Net installers for .Net 1.1, 2.0 and 3.0 have been renamed to DOTNET11, DOTNET20, DOTNET30, respectivly.

On the downside ... the installation source is over 900 megabytes ... Fortunatly, SP3 is just around the corner ...

[Version] 
Signature="$Windows NT$" 
MajorVersion=5 
MinorVersion=1 
BuildNumber=2600  
 
[SetupData] 
CatalogSubDir="\i386\svcpack" 
 
[SetupHotfixesToRun] 
; ---------- SVC-WIN Files ---------- 
"WINDOWSINSTALLER-KB893803-V2-X86.EXE /Q /U /O /N /Z /ER" 
; ---------- SVC-D1F Files ---------- 
"DOTNET11.EXE /Q:A /C:""INSTALL /Q""" 
; ---------- SVC-D1U Files ---------- 
"NDP1.1SP1-KB867460-X86.EXE /QN" 
"NDP1.1SP1-KB928366-X86.EXE /QN" 
; ---------- SVC-D2F Files ---------- 
"REG DELETE HKLM\Software\Microsoft\PCHealth\ErrorReporting\DW /F" 
"REG ADD HKLM\SYSTEM\Setup /V SystemSetupInProgress /T REG_DWORD /D 0 /F " 
"DOTNET20.EXE /Q:A /C:""INSTALL /Q""" 
; ---------- SVC-D2U Files ---------- 
"NETFX20SP1_X86.EXE /Q /NORESTART" 
; ---------- SVC-XMU Files ---------- 
"MSXML6-KB933579-ENU-X86.EXE /Q" 
; ---------- SVC-DRM Files ---------- 
"WINDOWSRIGHTSMANAGEMENTSERVICESSP2-KB917275-CLIENT-ENU-X86.EXE -override 1 /I MsDrmClient.msi /q" 
"WINDOWSRIGHTSMANAGEMENTSERVICESSP2-KB917275-CLIENT-ENU-X86.EXE -override 1 /I RmClientBackCompat.msi /q" 
; ---------- SVC-WMP Files ---------- 
"WMP11-WINDOWSXP-X86-ENU.EXE /Q:A /R:N /c:""SETUP_WM.EXE /Q /R:N /NoPID /DisallowSystemRestore /P:#e""" 
; ---------- SVC-HF1 and SVC-HF2 Files ---------- 
"ROOTSUPD.EXE /Q:A /R:N" 
"WINDOWS-KB909520-V1.000-X86-ENU.EXE /Q /U /O /N /Z /ER" 
"WINDOWSMEDIA11-KB929399-V2-X86-INTL.EXE /Q /U /O /N /Z /ER" 
"WINDOWSMEDIA11-KB936782-X86-ENU.EXE /Q /U /O /N /Z /ER" 
"WINDOWSMEDIA6-KB925398-X86-ENU.EXE /Q /U /O /N /Z /ER" 
"WINDOWSMEDIA-KB911564-X86-ENU.EXE /Q /U /O /N /Z /ER" 
"WINDOWSXP-KB873339-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB885836-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB886185-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB887472-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB888302-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB890859-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB891781-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB892130-ENU-X86.EXE /Q /U /O /N /Z /ER" 
"WINDOWSXP-KB893756-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB896256-V4-X86.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB896344-V2-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB896358-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB896423-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB896428-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB898461-X86-ENU.EXE /Q /U /O /N /Z /ER" 
"WINDOWSXP-KB898543-V3-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB899587-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB899591-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB900485-V2-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB900725-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB901017-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB901214-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB902400-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB904942-V2-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB905414-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB905749-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB908519-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB908531-V2-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB910437-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB911280-V2-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB911562-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB911927-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB913580-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB914388-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB914389-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB914440-V12-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB916595-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB918005-V4-X86.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB918118-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB918439-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB919007-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB920213-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB920670-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB920683-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB920685-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB920872-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB922582-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB922819-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB923191-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB923414-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB923980-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB924270-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB924667-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB925720-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB925902-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB926255-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB926436-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB927779-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB927802-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB927891-V3-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB928255-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB928843-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB929123-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB930178-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB930916-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB931261-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB931784-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB932168-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB933729-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB935448-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB935839-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB935840-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB936021-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB936357-V2-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB937894-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB938127-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB938828-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB939373-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB941202-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB941568-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB941569-X86-ENU.EXE /Q /U /O /N /Z /ER" 
"WINDOWSXP-KB941644-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB941693-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB942763-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB942830-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB942831-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB943055-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB943460-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB943485-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB944338-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB944653-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB945553-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB946026-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB947864-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB948590-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"WINDOWSXP-KB948881-X86-ENU.EXE /Q /U /O /N /Z /ER" 
; ---------- SVC-HF3 and SVC-HF4 Files ---------- 
"WINDOWSXP-KB920342-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
; ---------- SVC-CF1 Files ---------- 
"WIC_X86_ENU.EXE /Q /U /O /N /Z /ER" 
"WINDOWSMEDIA11-KB939683-X86-ENU.EXE /Q /U /O /N /Z /ER" 
"WINDOWSXP-KB905474-ENU-X86.EXE /Q /U /O /N /Z /ER" 
"WINDOWSXP-KB915865-V11-X86-ENU.EXE /Q /U /O /N /Z /ER" 
"WINDOWSXP-KB925876-X86-ENU.EXE /Q /U /O /N /Z /ER" 
"XPSEPSC-X86-EN-US.EXE /Q /U /O /N /Z /ER" 
; ---------- SVC-CF2 Files ---------- 
"WINDOWSXP-KB923789-X86-ENU.EXE /Q:A /R:N" 
; ---------- SVC-CF3 Files ---------- 
"WINDOWS-EN-US-KB943729-X86.EXE /Q /U /O /N /Z /ER" 
; ---------- SVC-MRT Files ---------- 
"WINDOWS-KB890830-V1.40.EXE /Q" 
; ---------- SVC-WUA Files ---------- 
"WINDOWSUPDATEAGENT30-X86.EXE /WuForce /Quiet /NoRestart" 
; ---------- SVC-D3F Files ---------- 
"DOTNET30.EXE /Q /NORESTART" 
; ---------- SVC-D3U Files ---------- 
"NETFX30-KB932471-X86.EXE /Q /NORESTART" 
"NETFX30SP1_X86.EXE /Q /NORESTART" 
"NETFX35_X86.EXE /Q /NORESTART" 
; ---------- SVC-IE7 Files ---------- 
"IE7-WINDOWSXP-X86-ENU.EXE /NoRestart /NoBackup /UpDate-No /Quiet" 
; ---------- SVC-IEU Files ---------- 
"IE7-WINDOWSXP-KB938127-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
"IE7-WINDOWSXP-KB947864-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE" 
; ---------- SVC-QCH Files ---------- 
"QCHAIN.EXE" 
 
[ProductCatalogsToInstall]


For those wondering ...
- This has been tested.
- The /ER switch is for Extended Error Reporting
- The /B:SP2QFE switch helps the update decide which branch of update files to use (see http://support.micro....com/kb/824994/)
- Hotfixes and updates do NOT need to be named in the 8.3 standard

This post has been edited by GreenMachine: 11 April 2008 - 12:57 AM
Reason for edit: link fixed, small spelling error


#2 User is offline   Yzöwl 

  • Wise Owl
  • Group: Super Moderator
  • Posts: 4,195
  • Joined: 13-October 04
  • OS:Windows 7 x64

Posted 12 December 2007 - 02:56 PM

First of all I'd like to thank you for the excellent information you've provided.

Now the questions:
  • Is HMTCDWIZARD necessary with WMP11
  • Can scripten.exe replace WINDOWSXP-KB917344-X86-ENU.EXE
  • Are WINDOWSXP-KB938127-X86-ENU.EXE and IE7-WindowsXP-KB938127-x86-ENU.exe not the same
    They are both installed that's why I asked.
  • Is WINDOWSXP-KB939653-X86-ENU.EXE not supposed to be IE7-WindowsXP-KB939653-x86-ENU.exe
  • Can DOTNET35.EXE be added
  • For the reg.exe, I've never tried this but since it is essentially an inf, will standard DIRIDs not work.
    you could then just use %11%\REG.EXE instead of copying the file to the svcpack directory.

#3 User is offline   GreenMachine 

  • ineXPlicable
  • Group: Developers
  • Posts: 3,062
  • Joined: 22-August 03

Posted 13 December 2007 - 03:18 PM

Aha! I have aroused, or perhaps arisen, the interest of he whose batch skills are rivaled only by ... my own! The short answers:

  • HMTCDWIZARD appears to be unnecessary. I did not realize WMP11 rendered it so.
  • SCRIPTEN.EXE can replace WINDOWSXP-KB917344-X86-ENU.EXE, however my objective here was to find the "minimal" list of updates needed for an "up to date" install, as determined by Windows Update. Additionally, in my tests, SCRIPTEN.EXE generates a non-critical digital signature error in setuperr.log when slipstreamed.
  • No, WINDOWSXP-KB938127-X86-ENU.EXE and IE7-WindowsXP-KB938127-x86-ENU.exe are not the same. The former is for IE6, the later for IE7. I suspect you knew that …
  • WINDOWSXP-KB939653-X86-ENU.EXE was supposed to be WindowsXP-KB942615-x86-ENU.exe: I missed that update: it does not show up on Windows Update, as IE7 is installed by that point.
  • I have not yet tried .Net 3.5, but I suspect I shall be forced to (by Windows Update) soon.
  • Neither DIRIDs, nor %SYSTEMROOT%SYSTEM32, seem to work.
The reason for both the IE6 and IE7 updates is that I use XPCREATE to slipstream the updates, and I want the IE6 version of the source files patched even though they will be outdated before setup is finished. IE6 updates are slipstreamed, IE7 is installed at T-13. If not slipstreaming the IE6 updates, including them in SVCPACK.INF would, indeed, be superfluous. After I create a successful slipstreamed CD, I then use the same SVCPACK.INF and SVCPACK directory with a non-slipstreamed XP source (other than the IEXPLORE.EXE file, listed above).

The SVCPACK.INF above has been updated to reflect the points mentioned here. Additionally, I neglected to mention that the .Net installers, 1.1, 2.0 and 3.0, were renamed to DOTNET11, DOTNET20 and DOTNET30, respectively.

This post has been edited by GreenMachine: 13 December 2007 - 03:24 PM

#4 User is offline   smilodon 

  • Newbie
  • Group: Members
  • Posts: 24
  • Joined: 27-September 07

Posted 30 December 2007 - 07:54 PM

A newb question: is this for Pro or Home ??? i don't think both versions use the same list.

#5 User is offline   JuMz 

  • Advanced Member
  • PipPipPip
  • Group: Members
  • Posts: 466
  • Joined: 09-August 04

Posted 02 January 2008 - 01:13 PM

Awesome job dude.

#6 User is offline   Yzöwl 

  • Wise Owl
  • Group: Super Moderator
  • Posts: 4,195
  • Joined: 13-October 04
  • OS:Windows 7 x64

Posted 02 January 2008 - 01:39 PM

I tried this method, the day after this topic was posted with just a couple of changes. The main one being swapping net2 and net3 for net3.5.
 
[Version]
Signature="$Windows NT$"
MajorVersion=5
MinorVersion=1
BuildNumber=2600

[SetupData]
CatalogSubDir="\I386\SVCPACK"

[SetupHotfixesToRun]
; ---------- SVC-WIN Files ----------
"WindowsInstaller-KB893803-v2-x86.exe /Q /U /O /N /Z /ER"
; ---------- SVC-D1F Files ----------
"DOTNET11.EXE /Q:A /C:""INSTALL /Q"""
; ---------- SVC-D1U Files ----------
"NDP1.1sp1-KB867460-X86.exe /QN"
"NDP1.1sp1-KB928366-X86.exe /QN"
; ---------- SVC-XMU Files ----------
"msxml4-KB941833-enu.exe /Q"
"msxml6-KB933579-enu-x86.exe /Q"
; ---------- SVC-DRM Files ----------
"WindowsRightsManagementServicesSP2-KB917275-Client-ENU-x86.exe -override 1 /I MsDrmClient.msi /q"
"WindowsRightsManagementServicesSP2-KB917275-Client-ENU-x86.exe -override 1 /I RmClientBackCompat.msi /q"
; ---------- SVC-WMP Files ----------
"wmp11-windowsxp-x86-enu.exe /Q:A /R:N /c:""SETUP_WM.EXE /Q /R:N /NoPID /DisallowSystemRestore /P:#e"""
; ---------- SVC-HF1 and SVC-HF2 Files ----------
"rootsupd.exe /Q:A /R:N"
"Windows-KB909520-v1.000-x86-ENU.exe /Q /U /O /N /Z /ER"
"WindowsMedia11-KB929399-v2-x86-INTL.exe /Q /U /O /N /Z /ER"
"WindowsMedia11-KB936782-x86-ENU.exe /Q /U /O /N /Z /ER"
"WindowsMedia6-KB925398-v2-x86-ENU.exe /Q /U /O /N /Z /ER"
"WindowsMedia-KB911564-x86-ENU.exe /Q /U /O /N /Z /ER"
"WindowsXP-KB873339-x86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WindowsXP-KB885836-x86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WindowsXP-KB886185-x86-enu.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WindowsXP-KB887472-x86-enu.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WindowsXP-KB888302-x86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WindowsXP-KB890859-x86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WindowsXP-KB891781-x86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"windowsxp-kb892130-enu-x86.exe /Q /U /O /N /Z /ER"
"WindowsXP-KB893756-x86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WindowsXP-KB896256-v4-x86-ENU.exe /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB896344-V2-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB896358-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB896423-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB896428-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB898461-X86-ENU.EXE /Q /U /O /N /Z /ER"
"WINDOWSXP-KB898543-V3-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB899587-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB899591-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB900485-V2-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB900725-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB901017-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB901214-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB902400-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB904942-V2-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB905414-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB905749-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB908519-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB908531-V2-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB910437-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB911280-V2-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB911562-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB911927-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB913580-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB914388-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB914389-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB914440-V12-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB916595-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"scripten.exe /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB917537-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB917953-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB918005-V4-X86.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB918118-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB918439-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB919007-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB920213-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB920670-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB920683-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB920685-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB920872-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB921503-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB922582-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB922819-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB923191-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB923414-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB923980-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB924270-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB924667-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB925720-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB925902-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB926255-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB926436-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB927779-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB927802-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB927891-V3-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB928255-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB929123-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB930178-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB930916-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB931261-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB931784-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB932168-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB933729-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB935448-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB935839-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB935840-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB936021-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB936357-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB937894-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB938127-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB938828-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB938829-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB939373-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB941202-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB941568-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB941569-X86-ENU.EXE /Q /U /O /N /Z /ER"
"WINDOWSXP-KB942615-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB942763-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB943460-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"WINDOWSXP-KB944653-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
; ---------- SVC-HF3 and SVC-HF4 Files ----------
"WINDOWSXP-KB920342-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
; ---------- SVC-CF1 Files ----------
"WIC_X86_ENU.EXE /Q /U /O /N /Z /ER"
"WindowsMedia11-KB939683-x86-ENU.exe /Q /U /O /N /Z /ER"
"WindowsXP-KB905474-ENU-x86-Standalone.exe /Q /U /O /N /Z /ER"
"WINDOWSXP-KB925876-X86-ENU.EXE /Q /U /O /N /Z /ER"
"xpsepsc-x86-en-us.exe /Q /U /O /N /Z /ER"
; ---------- SVC-CF2 Files ----------
"WINDOWSXP-KB923789-X86-ENU.EXE /Q:A /R:N"
; ---------- SVC-MRT Files ----------
"WINDOWS-KB890830-V1.36.EXE /Q"
; ---------- SVC-WUA Files ----------
"WindowsUpdateAgent30-x86.exe /WuForce /Quiet /NoRestart"
; ---------- SVC-D35F Files ----------
"REG.EXE DELETE HKLM\Software\Microsoft\PCHealth\ErrorReporting\DW /f"
"REG.EXE ADD HKLM\SYSTEM\Setup /v SystemSetupInProgress /t REG_DWORD /d 0 /f"
"DOTNETFX35.EXE /Q /NORESTART"
; ---------- SVC-IE7 Files ----------
"IE7-WINDOWSXP-X86-ENU.EXE /NoRestart /NoBackup /UpDate-No /Quiet"
; ---------- SVC-IEU Files ----------
"IE7-WINDOWSXP-KB938127-X86-ENU.EXE /Q /U /O /N /Z /ER /B:SP2QFE"
"IE7-WindowsXP-KB939653-x86-ENU.exe /Q /U /O /N /Z /ER /B:SP2QFE"
"IE7-WindowsXP-KB942615-x86-ENU.exe /Q /U /O /N /Z /ER /B:SP2QFE"
; ---------- SVC-QCH Files ----------
"QCHAIN.EXE XPCCHAIN.LOG"

[ProductCatalogsToInstall]
The only problem I had was one or two, I cannot remember now, of the `SVC-IEU Files` still showed up as required in Windows Update.

#7 User is offline   spitf1r3 

  • Newbie
  • Group: Members
  • Posts: 45
  • Joined: 25-December 07

Posted 02 January 2008 - 03:02 PM

View Postsmilodon, on Dec 31 2007, 02:54 AM, said:

A newb question: is this for Pro or Home ??? i don't think both versions use the same list.

It's applicable for both Home and Pro.
There arent many differences between them, like between Vista editions.
The only "Pro only updates" are IIS hotfixes AFAIK...
=======Edit========
Beside, how much time does it take to install those hotfixes through SVCPACK.INF?
It must take ages to do that...

This post has been edited by spitf1r3: 02 January 2008 - 03:14 PM

#8 User is offline   Neo - Matrix 

  • Hewlett Packard Brazil Support
  • Pip
  • Group: Members
  • Posts: 64
  • Joined: 08-November 02

Posted 03 January 2008 - 05:57 AM

Well,

Another Noob question. But using this topic as base, i´m supposed to have it working on other languages too right !?

Any chance of error, or can someone post if any of thoses fixes are not language based !?!
Btw, is RunOnceEX working using this method - or it breaks like the other ways !?

The only way i have RunOnceEx working now a days is using this method above:
http://www.msfn.org/board/index.php?showto...93061&st=40

To be more specific:
http://www.msfn.org/board/index.php?showto...st&p=628949 (Post) #58 - from rajesh.kumar

Another Up ...

Well, i was able to get most of the updates listed on the page:

But i can´t find theses files:

ROOTSUPD.EXE
WIC_X86_ENU.EXE
XPSEPSC-X86-EN-US.EXE

yeah i known you will not give direct links, but any chance on how to grab it. I´ve looked up using tools mentioned, but In Portuguese (Brazilian) - no chance to find out

Are thoses files on any updates / extract something to get it !? :P

How about Languages on NetFrameWork - any problem if i run Portuguese Windows with English .Net framework files - i dont want to have it in portuguese.

Another nooob question 2: WinXP SP3 is supposed to have IE7 by default right (didn´t grab my copy yet) but running with original integration, is RunOnceEX supposed to work right without any "crappy" change. And all the work to have this things workin will stop - since it updates evertyhing (critical) by default !?

Sorry for not good english :P Brazilian still learning

This post has been edited by Neo - Matrix: 03 January 2008 - 07:08 AM

#9 User is offline   DarkShadows 

  • The brighter the light, the darker the shadows.
  • PipPip
  • Group: Members
  • Posts: 271
  • Joined: 12-January 05

Posted 13 January 2008 - 10:24 AM

View PostYzöwl, on Jan 2 2008, 03:39 PM, said:

I tried this method, the day after this topic was posted with just a couple of changes. The main one being swapping net2 and net3 for net3.5.
 
[Version]
Signature="$Windows NT$"
MajorVersion=5
MinorVersion=1
BuildNumber=2600

[SetupHotfixesToRun]
; ---------- SVC-D1F Files ----------
"DOTNET11.EXE /Q:A /C:""INSTALL /Q"""
; ---------- SVC-D1U Files ----------
"NDP1.1sp1-KB867460-X86.exe /QN"
"NDP1.1sp1-KB928366-X86.exe /QN"
; ---------- SVC-XMU Files ----------
"msxml4-KB941833-enu.exe /Q"
"msxml6-KB933579-enu-x86.exe /Q"
; ---------- SVC-D35F Files ----------
"REG.EXE DELETE HKLM\Software\Microsoft\PCHealth\ErrorReporting\DW /f"
"REG.EXE ADD HKLM\SYSTEM\Setup /v SystemSetupInProgress /t REG_DWORD /d 0 /f"
"DOTNETFX35.EXE /Q /NORESTART"

[ProductCatalogsToInstall]


@Yzöwl

Q: Did you verify that the WebClient Service was running correctly after this installation completed?

To the best of my knowledge, no one has been able to get .Net Framework 3.0 or 3.5 to install from SVCPACK without breaking the WebClient Service.

#10 User is offline   Yzöwl 

  • Wise Owl
  • Group: Super Moderator
  • Posts: 4,195
  • Joined: 13-October 04
  • OS:Windows 7 x64

Posted 13 January 2008 - 01:43 PM

View PostDarkShadows, on Jan 13 2008, 04:24 PM, said:

@Yzöwl

Q: Did you verify that the WebClient Service was running correctly after this installation completed?

To the best of my knowledge, no one has been able to get .Net Framework 3.0 or 3.5 to install from SVCPACK without breaking the WebClient Service.
I don't really know how to verify it. There's nothing relevant in my event viewer and the automatic service has started without problem so far!.

Is there something else you'd like me to try in order to verify it?

#11 User is offline   DarkShadows 

  • The brighter the light, the darker the shadows.
  • PipPip
  • Group: Members
  • Posts: 271
  • Joined: 12-January 05

Posted 13 January 2008 - 04:02 PM

From what I know of the issue (which isn't much), that is enough to say it works. I believe some people reported having problems coming into the GUI logon if the WebClient service wasn't working.

I'm assuming that you are using the 197 MB .Net Framework Full Distribution Package, which has all the updates to .Net 2.0 and .Net 3.0 in it (+ the SP1 of each). Maybe the order of the updates listed in svcpack.inf that GreenMachine provided here is really the key. I tried to get the whole .Net 3.5 installed from SVCPACK (before reading this thread) without success. I'll have to play around with it again.

#12 User is offline   DarkShadows 

  • The brighter the light, the darker the shadows.
  • PipPip
  • Group: Members
  • Posts: 271
  • Joined: 12-January 05

Posted 13 January 2008 - 04:47 PM

For those wondering, here is the link to rootsupd.exe. I believe that link will always get you the most current package at all times. Microsoft also releases seperate knowledgebase articles (though without a download link on the description page) describing each Root Certificates Update. But you can download them, by knowledgebase article number, from the Microsoft Update Catalog.

The most recent Root Certificates Update is:

KB931125 -> Microsoft Root Certificate Program Members (July 2007)

#13 User is offline   Yzöwl 

  • Wise Owl
  • Group: Super Moderator
  • Posts: 4,195
  • Joined: 13-October 04
  • OS:Windows 7 x64

Posted 14 January 2008 - 09:15 AM

View PostDarkShadows, on Jan 13 2008, 10:02 PM, said:

I'm assuming that you are using the 197 MB .Net Framework Full Distribution Package, which has all the updates to .Net 2.0 and .Net 3.0 in it (+ the SP1 of each
Yes it is!

#14 User is offline   Neo - Matrix 

  • Hewlett Packard Brazil Support
  • Pip
  • Group: Members
  • Posts: 64
  • Joined: 08-November 02

Posted 14 January 2008 - 11:02 AM

View PostDarkShadows, on Jan 13 2008, 08:47 PM, said:

For those wondering, here is the link to rootsupd.exe. I believe that link will always get you the most current package at all times. Microsoft also releases seperate knowledgebase articles (though without a download link on the description page) describing each Root Certificates Update. But you can download them, by knowledgebase article number, from the Microsoft Update Catalog.

The most recent Root Certificates Update is:

KB931125 -> Microsoft Root Certificate Program Members (July 2007)


Yeah - I've found it on HFSLIP list.
Sure this is the last version, since i verify on VMWARE - my last test version on it.

:hello:

#15 User is offline   GreenMachine 

  • ineXPlicable
  • Group: Developers
  • Posts: 3,062
  • Joined: 22-August 03

Posted 14 January 2008 - 12:18 PM

@smilodn: This list is for XP Pro. Forgot to mention that ...

@Yzöwl: I suspect that the SVC-IEU (IE Updates) files that did not install are due to not including the IE7 iexplore.ex_ in your I386 installation directory. WIthout this, the IE Updates will think that IE6 is installed, and not install. That is one of the "smoke and mirror" tricks I needed to use.

@spitf1f3: Perhaps it will work for both Home and Pro: I never use nor test the Home version. It takes quite a while to install this way, but most of the time is for .Net, which is unavoidable unless you find a method to slipstream .Net (which I would neither trust nor try, but to each their own ...). To me the extra time is worth it, as I an sure to have a reliable installation, and save the time hunting down bugs left behind by non-orthodox "shortcuts". If I am really in a hurry to get an installation done, which I never seem to be ... I just start it a half hour earlier!

@Neo - Matrix: I have not tried other languages, but I assume most, if not all, of the files will install fine. I also have not tested RunOnceEx, but as the latest IE updates are installed, I would bet it works. If not, there is always the option to adjust the RunOnceEx flags so that no status boxes are shown, and that has been documented to work by both Microsoft, and others on this board. As for the three updates you cannot find (ROOTSUPD.EXE, WIC_X86_ENU.EXE and XPSEPSC-X86-EN-US.EXE), I do not remember where I got them, and I am not in my lab (nor will I be for at least another month), but I do know that all the files listed are downloadable as such: no extraction is required, I do not know how English .Net would work on PT-BR Windows. You will just have to test it ... SP3, as I last saw it, does NOT include IE7.

@DarkShadows: I did my tests with .Net 3.0 + updates. Yzöwl, I believe, from what he posts here, did use the 3.5 package. As I mention in the first post, the WebClient service appears to work just fine, though I have not tested it, as such. But in many tests, the service was perpetually in the "Starting" state. With the SVCPACK.INF file posted that was NOT the case, which was conclusive enough for me. Also, as I stated, and you repeated, the order DOES seem to be the key. The same files in different orders tested had the WebClient service listed as "Starting". So now, "To the best of your knowledge", there is a way to install .Net 3,0 (and perhaps 3.5, I cannot vouch for that), from SVCPACK.INF WITHOUT breaking the WebClient Service (which was the main reason I posted this). I also see that you have been busy writing up a few guides. Keep up the good work! They look clear and easy to follow.

As for me, I left home for a 2 week trip about a month ago, and it looks to be another month before I return. At that point, I will try to update my SVCPACK.INF to include .Net 3.5, and the latest updates. Until then: Good Luck!

#16 User is offline   Yzöwl 

  • Wise Owl
  • Group: Super Moderator
  • Posts: 4,195
  • Joined: 13-October 04
  • OS:Windows 7 x64

Posted 14 January 2008 - 01:45 PM

View PostGreenMachine, on Jan 14 2008, 06:18 PM, said:

@Yzöwl: I suspect that the SVC-IEU (IE Updates) files that did not install are due to not including the IE7 iexplore.ex_ in your I386 installation directory. WIthout this, the IE Updates will think that IE6 is installed, and not install. That is one of the "smoke and mirror" tricks I needed to use.
Yes, you're correct, I noticed it in your opening post but I wasn't willing to do that for the sake of a couple of updates.

#17 User is offline   cart0181 

  • Newbie
  • Group: Members
  • Posts: 14
  • Joined: 06-June 06

Posted 01 February 2008 - 05:50 PM

I would like to report a dead link in your original post: The link to kb824994 describing the /B switch.
While you're at it, I happened to notice a typo also, 3 lines above the dead link, I believe it was supposed to say "This has been tested."

I have a question too. What does it do when you include both the /q and the /u switches? How is it different than only the /u switch?
another question: Why the quotes around each line?

I would also like to say: Wow! I didn't know that Hotfixes and updates do NOT need to be named in the 8.3 standard, as it states in The Guide. Good thing I used a batch renaming program to make mine conform to the 8.3 standard. I would have been plssed I wasted so much time!

This post has been edited by cart0181: 01 February 2008 - 10:22 PM

#18 User is offline   Yzöwl 

  • Wise Owl
  • Group: Super Moderator
  • Posts: 4,195
  • Joined: 13-October 04
  • OS:Windows 7 x64

Posted 01 February 2008 - 10:58 PM

View Postcart0181, on Feb 1 2008, 11:50 PM, said:

I would like to report a dead link in your original post: The link to kb824994 describing the /B switch.
While you're at it, I happened to notice a typo also, 3 lines above the dead link, I believe it was supposed to say "This has been tested."
Link and spelling error fixed in original post!

#19 User is offline   GreenMachine 

  • ineXPlicable
  • Group: Developers
  • Posts: 3,062
  • Joined: 22-August 03

Posted 12 February 2008 - 07:26 PM

First post updated with Today's Patch Day Updates

#20 User is offline   lokelo 

  • Newbie
  • Group: Members
  • Posts: 11
  • Joined: 24-February 07

Posted 12 February 2008 - 09:31 PM

Which patches did you add for this month? Did you remove any?

Share this topic:


  • 2 Pages +
  • 1
  • 2
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users



All trademarks mentioned on this page are the property of their respective owners
Copyright © 2001 - 2011 msfn.org
Privacy Policy