Jump to content

Hotfixes For Windows XP Professional SP1


Aaron

Recommended Posts

Aaron,

my svcpack.inf contain this:

[setupHotfixesToRun]update.exe -q -n

Q330994.exe /Q:A /R:N

js56nen.exe /Q:A /R:N

Q816093.exe /Q:A /R:N

Q823182.exe /Q /O /N /Z

Q824105.exe /Q /O /N /Z

Q824141.exe /Q /O /N /Z

Q825119.exe /Q /O /N /Z

Q828035.exe /Q /O /N /Z

Q828028.exe /Q /O /N /Z

WMP9MM2.exe

Q828026.exe /Q /O /N /Z

Q828741.exe /Q /O /N /Z

Q832353.exe /Q /O /N /Z

Q832894.exe /Q:A /R:N

Q831167.exe /Q:A /R:N

Q835732.exe /Q /O /N /Z

Q837001.exe /Q /O /N /Z

Q837009.exe /Q:A /R:N

Q837251.exe /Q:A /R:N

Q840374.exe /Q /O /N /Z

qchain.exe

DX9NTopk.exe

do i need this line? -> update.exe -q -n

your svcpack.inf doesn't contain this though. just wondering if it's needed :)

thanks!

Link to comment
Share on other sites


Only if you're slipstreaming the rollup update 1. I don't use, or endorse this method anymore due to issues that can rise from it according to some members.

Link to comment
Share on other sites

@AaronXP

your svcpack.inf contains this:

[SetupHotfixesToRun]
JS56NEN.exe /Q:A /R:N
mdac.cmd
KB823182.exe /Q /N /Z /O
KB824105.exe /Q /N /Z /O
KB824141.exe /Q /N /Z /O
KB825119.exe /Q /N /Z /O
KB826939.exe /Q /N /Z /O
KB828035.exe /Q /N /Z /O
KB828741.exe /Q /N /Z /O
KB832894.exe /Q:A /R:N
KB831167.exe /Q:A /R:N
KB835732.exe /Q /N /Z /O
KB837001.exe /Q /N /Z /O
KB837009.exe /Q:A /R:N
KB840374.exe /Q /N /Z /O
WMP9MM2.exe
KB828026.exe /Q /N /Z /O
DX9NTopk.exe

i saw these 2 lines:

KB832894.exe /Q:A /R:N

KB831167.exe /Q:A /R:N

i would like to know is if these two lines were intentionally put this way? i thought installation has to be arranged in ascending order. :rolleyes:

i also have the same question for the mdac (Q832483) :)

i would also like to know if would this be applicable on non-sp1 slipstreamed xpcd? or sp1 has to be slipstreamed 1st on the xpcd? thanks.

Link to comment
Share on other sites

Those hotfixes are for Internet Explorer and one is the cumulative update (KB832894) and therefore has to be installed before the single update (KB831167).

As for MDAC, it doesn't matter because MDAC is a standalone update (not requiring any other updates). Ofcourse, you can install that one in the right place.

Link to comment
Share on other sites

thanks. :D its clear now. :rolleyes:

btw, mine's like this:

[SetupHotfixesToRun]
JS56NEN.exe /Q:A /R:N
"Q832483.exe /C:""dahotfix.exe /q /n"" /q:a"
KB823182.exe /Q /N /Z /O
KB824105.exe /Q /N /Z /O
KB824141.exe /Q /N /Z /O
KB825119.exe /Q /N /Z /O
KB826939.exe /Q /N /Z /O
KB828035.exe /Q /N /Z /O
KB828741.exe /Q /N /Z /O
Q832894.exe /Q:A /R:N
Q831167.exe /Q:A /R:N
KB835732.exe /Q /N /Z /O
KB837001.exe /Q /N /Z /O
KB837009.exe /Q:A /R:N
KB840374.exe /Q /N /Z /O
WMP9MM2.exe
Q828026.exe /Q /N /Z /O
qchain.exe
DX9NTopk.

i got another question though, i was wondering, should i still keep qchain.exe in the list? :)

Link to comment
Share on other sites

I got a problem... While on t-13 it pops this:

capture.jpg

[ProductCatalogsToInstall] 
KB826939.cat

[SetupHotfixesToRun]
js56nen.exe /Q:A /R:N
msjavwu.exe /Q:A /R:N
KB817778.exe /q /n /z /o (This one got off to a atch file)
KB822603.exe /q /n /z /o
KB823182.exe /q /n /z /o
KB823980.exe /q /n /z /o
KB824105.exe /q /n /z /o
KB824141.exe /q /n /z /o
KB824146.exe /q /n /z /o
KB825119.exe /q /n /z /o
KB826939.exe /q /n /z
KB828028.exe /quiet /passive /norestart /o /n
KB826942.exe /quiet /passive /norestart /o /n
KB828035.exe /q /n /z /o
KB828741.EXE /q /n /z /o
KB833330.exe /quiet /passive /norestart /o /n
KB835732.exe /q /n /z /o
KB837001.exe /q /n /z /o
Q282784.exe /q /n /z /o
Q312370.exe /q /n /z /o
Q319580.exe /q /n /z /o
Q327405.exe /Q:A /R:N
Q327979.exe /q /n /z /o
Q814995.exe /q /n /z /o
Q815062.exe /q /n /z /o
;-Wrong switch above this....
Q816093.exe /q /n /z /o
Q819696.exe /q /n /z /o
Q820223.exe /Q:A /R:N
Q824145.exe /Q:A /R:N
Q828026.exe /q /n /z /o
Q828750.exe /Q:A /R:N
Q831167.exe /Q:A /R:N
Q832894.exe /Q:A /R:N
KB840374.exe /q /n /z /o
DX9NTopk.exe
qchain.exe

Got any idea? I have these switches from this topic and from running hotfixes with /? switch

Which one might it be the problem?

I am sure it is from the ones above q816093.exe cuz it popped me later error on q816093 also.

Edited by SwAToNeR
Link to comment
Share on other sites

Only if you're slipstreaming the rollup update 1. I don't use, or endorse this method anymore due to issues that can rise from it according to some members.

What kind of issues? I personally haven't had problems as yet but would like to know what to expect...

Link to comment
Share on other sites

If you were having issues, you would know already, during slipstreaming or installation. If you made it to Windows Update, and that looked OK, you should be fine.

The method used in the MSFN guide, however, is specific to the Security Rollup, and does not allow for slipstreaming a second hotfix. As SP2 approaches, the Rollup will become redundant, thus the MS method of SVCPACK.INF can be used.

Link to comment
Share on other sites

If you were having issues, you would know already, during slipstreaming or installation. If you made it to Windows Update, and that looked OK, you should be fine.

The method used in the MSFN guide, however, is specific to the Security Rollup, and does not allow for slipstreaming a second hotfix. As SP2 approaches, the Rollup will become redundant, thus the MS method of SVCPACK.INF can be used.

No.. I don't have any issues. What I meant to ask were the reasons why Aaron had stopped using the update rollup integration method. He mentions problems faced by some people and I would like to know what those problems were.

I already know what the guide is about. Thanks for your concern. :)

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...