Like many others, I'm looking for a way to automate (at leasty partly)
applying all the post-SP2 hotfixes. Thanks to the help in these forums I've
already got SP2 slipstreamed with my original XP Pro (upgrade) CD, which is
half the battle.

I see from other posts there are several methods (integrating,
chaining,...), but apparently not all will work on an upgrade version of XP.
E.g., this article says it ( the "/integrate" method) works only on new
installs, not upgrades (http://support.microsoft.com/kb/828930).

Are there other ways to "batch patch" these things on an XP upgrade? I've
already downloaded all 70-80 updates, I just need a faster way to apply them,
i.e., without all the reboots inbetween.

Autopatcher works very well.
http://www.autopatcher.com/

--

----
Crosspost, do not multipost http://www.blakjak.demon.co.uk/mul_crss.htm
How to ask a question http://support.microsoft.com/kb/555375
How to Post http://www.dts-l.org/goodpost.htm
http://www.db-pc.com
_________________________________________________________________________________


"WallyGrommit" <(E-Mail Removed)> wrote in message
news:17CD8A25-690D-43CB-8C9F-(E-Mail Removed)...
> Like many others, I'm looking for a way to automate (at leasty partly)
> applying all the post-SP2 hotfixes. Thanks to the help in these forums
> I've
> already got SP2 slipstreamed with my original XP Pro (upgrade) CD, which
> is
> half the battle.
>
> I see from other posts there are several methods (integrating,
> chaining,...), but apparently not all will work on an upgrade version of
> XP.
> E.g., this article says it ( the "/integrate" method) works only on new
> installs, not upgrades (http://support.microsoft.com/kb/828930).
>
> Are there other ways to "batch patch" these things on an XP upgrade? I've
> already downloaded all 70-80 updates, I just need a faster way to apply
> them,
> i.e., without all the reboots inbetween.
>
>
>

Did you get it going?

"WallyGrommit" <(E-Mail Removed)> wrote in message
news:17CD8A25-690D-43CB-8C9F-(E-Mail Removed)...
> Like many others, I'm looking for a way to automate (at leasty partly)
> applying all the post-SP2 hotfixes. Thanks to the help in these forums
> I've
> already got SP2 slipstreamed with my original XP Pro (upgrade) CD, which
> is
> half the battle.
>
> I see from other posts there are several methods (integrating,
> chaining,...), but apparently not all will work on an upgrade version of
> XP.
> E.g., this article says it ( the "/integrate" method) works only on new
> installs, not upgrades (http://support.microsoft.com/kb/828930).
>
> Are there other ways to "batch patch" these things on an XP upgrade? I've
> already downloaded all 70-80 updates, I just need a faster way to apply
> them,
> i.e., without all the reboots inbetween.
>
>
>

Thanks everyone for your suggestions. Unfortunately I'll have to postpone
trying them because I just killed my HD. Not even the windows retail CD
works! Hope to be back
up in a day or two. (fingers crossed...)

A simple patcher script, source included, modify to suit your needs.

http://mylogon.net/sus/


"WallyGrommit" wrote:

> Like many others, I'm looking for a way to automate (at leasty partly)
> applying all the post-SP2 hotfixes. Thanks to the help in these forums I've
> already got SP2 slipstreamed with my original XP Pro (upgrade) CD, which is
> half the battle.
>

Ok, finally back up and running.
(p.s. As curious as I am about David B's and Ian's suggestions, I'm much too
paranoid to download unknown exes or zips - at the risk of missing out on
some really great tools. Much appreciated, though.)

I'm interested in your suggestion but having trouble parsing the cmd lines.
It's hard to tell the real line breaks from the ones inserted by my browser.
If I substitute your path/file names and ignore ECHOs/REMs, I THINK I'm
seeing just these three executable lines:
"<pathToUpdates>\quiet" "/passive /norestart /nobackup" "<pathToOutLog>"
"<pathToUpdates>\engineWindowsUpdates.cmd"
"<pathToUpdates>\q" "/q" "<pathToOutLog>"
Is this right?

Also, you mentioned attached files but not sure how to see those files. Can
I download the missing items from microsoft?


"Billy Pumphrey" wrote:

> >
> > Are there other ways to "batch patch" these things on an XP upgrade? I've
> > already downloaded all 70-80 updates, I just need a faster way to apply
> > them,
> > i.e., without all the reboots inbetween.
> >
>
> Indeed not all of them work with integrating. I have got this process down
> that works. I used the microsoft script. Try and bear with me as this is
> with my customization too.
>
> The attached files:
>
> engineWindowsUpdates.zip - This was originally called RunUpdates.cmd as you
> will see in the file. There are a few comments. You should not edit this
> file.
>
> dir.zip - This is the file structure that I have for the script
>
> runXPSP2Updates.cmd - This file is the one that you edit. There are a few
> lines that are key. I do not remember why I have the rem in there for the
> /quite switch update line, but I think it works. The idea is that you put
> all of the updates in a folder and you run this command on them and it will
> run all of the updates in that folder. The updates in the particular folder
> have to support the switches that you tell it. That is why I have two
> different commands, so that the updates will run that have the different
> commands.
>
> Echo =======================================
> Echo Install updates
> Echo =======================================
>
> Echo Installing updates with the /quiet or /passive switch
> REM Running Runupdates.cmd for the /quiet switch
> rem "\\woodenapp2\distribution$\Applications\Windows XP SP2
> Updates\engineWindowsUpdates.cmd"
> "\\woodenapp2\distribution$\Applications\Windows XP SP2 Updates\quiet"
> "/passive /norestart /nobackup" "c:\Windows\UpdateSettup.log"
> Echo Ran Runupdates.cmd for XP SP2 quiet command, rc=%ERRORLEVEL%
> >>%systemroot%\setuplog1.log
>
> Echo Installing updates with the /q switch
> REM Running Runupdates.cmd for the /q switch
> "\\woodenapp2\distribution$\Applications\Windows XP SP2
> Updates\engineWindowsUpdates.cmd"
> "\\woodenapp2\distribution$\Applications\Windows XP SP2 Updates\q" "/q"
> "c:\Windows\UpdateSettup.log"
> Echo Ran Runupdates.cmd for XP SP2 quiet command, rc=%ERRORLEVEL%
> >>%systemroot%\setuplog1.log
>
>
>
> This should get you going
>
>
>
>
>
>
>

Ok I posted the files at http://www.billypumphrey.com/downloads/

You can get them there. The script is on microsofts site some where, maybe
search for RunUpdates.cmd

I will tak you from scratch and show you how to use these files. You can of
course put them how you want but with me explaining how to use these files
that should help you understand the basics of how it works.

engineWindowsUpdate.cmd
- originallany call RunUpdates.cmd
- You do not have to change this file
- I have changed something. There is a check for files in
C:\Local\Sysinfo\..... This check is from the older BDD, I don't remember
how this check got in there or how I made up this file. I just made it so
that this check is bypassed and doesn't have to worry about these files.
- Use of this file is commented in the file itself. Here is the syntax:
engineWindowsUpdates.cmd "folderpath" "switches" "logfile" ["ostype"]
["splevel"]
- this file is called via the runXPSP2Updates.cmd file. Running this file
by itsself does nothing

runXPSP2Updates.cmd
- this is the file that you run
- example command line:
engineWindowsUpdates.cmd \\Server\Updatefilelocation "/q" "C:\Log.log"
Call the file, put the location of the update folder (remember the specified
command (/q in this case) will be ran on all updates in the update folder.
Specify a log file.

So if the folder \\Server\Updatefilelocation contains the following files:

11/22/2005 10:26 AM 1,012,064 Windows-KB890830-V1.10-ENU.exe
01/12/2006 10:13 AM 1,140,064 Windows-KB890830-V1.12-ENU.exe
05/02/2006 04:40 PM 1,813,920 Windows-KB890830-V1.15.exe
02/08/2007 02:30 PM 4,964,776 Windows-KB890830-V1.24.exe
09/14/2005 01:55 PM 851,808 Windows-KB890830-V1.8-ENU.exe
02/08/2007 02:30 PM 555,072 WindowsXP-KB923789-x86-ENU.exe

Then all of those files will be ran like this:
Windows-KB890830-V1.10-ENU.exe /q

This means that only updates that use the /q switch should be in here.

For the files that use the /quiet switch, create a new line in the batch
file of runXPSP2updates.cmd to run the /quiet switch. Like so:
engineWindowsUpdates.cmd \\Server\Updatefilelocation "/quiet" "C:\Log.log"

In my folder for the quiet switch, I have these updates in there currently:
02/14/2006 08:00 AM 611,592 WINDOWSMEDIA-KB911564-X86-ENU.EXE
05/02/2006 04:37 PM 2,556,680
WindowsMedia10-KB911565-v2-x86-ENU.exe
02/14/2006 08:00 AM 2,556,168 WINDOWSMEDIA10-KB911565-X86-ENU.EXE
02/14/2006 08:00 AM 2,299,656 WINDOWSMEDIA9-KB911565-X86-ENU.EXE
05/02/2006 04:37 PM 3,104,488 WindowsXP-KB885835-x86-ENU.exe
09/07/2005 04:44 PM 522,480 WindowsXP-KB890046-x86-ENU.exe
09/07/2005 04:44 PM 6,098,160 WindowsXP-KB890859-x86-ENU.exe
09/07/2005 04:45 PM 791,280 WindowsXP-KB893066-v2-x86-ENU.exe
09/07/2005 04:43 PM 691,440 WindowsXP-KB893756-x86-ENU.exe
09/07/2005 04:43 PM 2,077,424 WindowsXP-KB894391-x86-ENU.exe
11/02/2005 06:00 PM 2,583,280 WindowsXP-KB896256-v3-x86-ENU.exe
09/07/2005 04:43 PM 1,038,576 WindowsXP-KB896358-x86-ENU.exe
09/07/2005 04:44 PM 720,624 WindowsXP-KB896422-x86-ENU.exe
09/07/2005 04:42 PM 563,440 WindowsXP-KB896423-x86-ENU.exe
11/16/2005 11:43 AM 2,594,032 WindowsXP-KB896424-x86-ENU.exe
09/07/2005 04:44 PM 525,040 WindowsXP-KB896428-x86-ENU.exe
11/16/2005 11:39 AM 4,966,128 WindowsXP-KB896688-x86-ENU.exe
09/07/2005 04:43 PM 737,520 WindowsXP-KB899587-x86-ENU.exe
11/16/2005 11:38 AM 538,864 WindowsXP-KB899589-x86-ENU.exe
09/07/2005 04:43 PM 583,920 WindowsXP-KB899591-x86-ENU.exe
05/02/2006 04:39 PM 584,944 WindowsXP-KB900485-v2-x86-ENU.exe
11/16/2005 11:37 AM 5,167,344 WindowsXP-KB900725-x86-ENU.exe
11/16/2005 11:39 AM 1,046,256 WindowsXP-KB901017-x86-ENU.exe
02/14/2006 08:00 AM 543,472 WINDOWSXP-KB901190-X86-ENU.EXE
09/07/2005 04:44 PM 625,904 WindowsXP-KB901214-x86-ENU.exe
11/16/2005 11:40 AM 4,934,896 WindowsXP-KB902400-x86-ENU.exe
11/16/2005 11:36 AM 1,393,392 WindowsXP-KB904706-x86-ENU.exe
05/02/2006 04:39 PM 513,264 WindowsXP-KB904942-v2-x86-ENU.exe
11/16/2005 11:37 AM 621,296 WindowsXP-KB905414-x86-ENU.exe
11/16/2005 11:35 AM 582,384 WindowsXP-KB905749-x86-ENU.exe
01/11/2006 05:28 PM 4,980,976 WindowsXP-KB905915-x86-ENU.exe
01/09/2006 08:00 AM 597,232 WINDOWSXP-KB908519-X86-ENU.EXE
01/12/2006 10:10 AM 803,056 WindowsXP-KB908521-x86-ENU.exe
05/02/2006 04:38 PM 4,659,000 WindowsXP-KB908531-v2-x86-ENU.exe
01/12/2006 10:12 AM 1,193,200 WindowsXP-KB910437-x86-ENU.exe
02/07/2007 05:33 PM 1,093,432 WindowsXP-KB911280-v2-x86-ENU.exe
05/02/2006 04:38 PM 574,192 WindowsXP-KB911562-x86-ENU.exe
05/02/2006 04:35 PM 1,582,832 WindowsXP-KB911567-x86-ENU.exe
02/14/2006 08:00 AM 618,224 WINDOWSXP-KB911927-X86-ENU.EXE
05/02/2006 04:35 PM 5,027,568 WindowsXP-KB912812-x86-ENU.exe
01/11/2006 05:38 PM 727,280 WindowsXP-KB912919-x86-ENU.exe
02/14/2006 08:00 AM 804,592 WINDOWSXP-KB913446-X86-ENU.EXE
02/07/2007 05:30 PM 1,307,376 WindowsXP-KB913580-x86-ENU.exe
02/07/2007 05:27 PM 1,018,168 WindowsXP-KB914388-x86-ENU.exe
02/07/2007 05:50 PM 996,152 WindowsXP-KB914389-x86-ENU.exe
02/07/2007 05:49 PM 681,784 WindowsXP-KB914440-v12-x86-ENU.exe
03/10/2006 08:00 AM 487,664 WINDOWSXP-KB914798-X86-ENU.EXE
02/07/2007 05:29 PM 536,888 WindowsXP-KB915865-v11-x86-ENU.exe
02/07/2007 05:48 PM 611,056 WindowsXP-KB916595-x86-ENU.exe
02/07/2007 05:44 PM 764,216 WindowsXP-KB917344-x86-ENU.exe
02/07/2007 05:46 PM 942,904 WindowsXP-KB917422-x86-ENU.exe
02/07/2007 05:45 PM 788,792 WindowsXP-KB917953-x86-ENU.exe
02/07/2007 05:35 PM 567,096 WindowsXP-KB918439-x86-ENU.exe
02/07/2007 05:44 PM 567,096 WindowsXP-KB919007-x86-ENU.exe
02/07/2007 05:28 PM 685,368 WindowsXP-KB920213-x86-ENU.exe
02/07/2007 05:32 PM 789,816 WindowsXP-KB920214-x86-ENU.exe
02/07/2007 05:31 PM 972,088 WindowsXP-KB920342-x86-ENU.exe
02/07/2007 05:35 PM 523,576 WindowsXP-KB920670-x86-ENU.exe
02/07/2007 05:30 PM 607,544 WindowsXP-KB920683-x86-ENU.exe
02/07/2007 05:33 PM 1,302,840 WindowsXP-KB920685-x86-ENU.exe
02/07/2007 05:43 PM 617,272 WindowsXP-KB920872-x86-ENU.exe
02/07/2007 05:35 PM 4,479,288 WindowsXP-KB921398-x86-ENU.exe
02/07/2007 05:47 PM 563,000 WindowsXP-KB922582-x86-ENU.exe
02/07/2007 05:32 PM 824,120 WindowsXP-KB922616-x86-ENU.exe
02/07/2007 05:50 PM 4,660,536 WindowsXP-KB922760-x86-ENU.exe
02/08/2007 02:30 PM 856,376 WindowsXP-KB922819-x86-ENU.exe
02/07/2007 05:31 PM 4,237,624 WindowsXP-KB923191-x86-ENU.exe
02/07/2007 05:32 PM 725,304 WindowsXP-KB923414-x86-ENU.exe
02/07/2007 05:35 PM 2,388,288 WindowsXP-KB923689-x86-ENU.EXE
02/07/2007 05:33 PM 680,760 WindowsXP-KB923980-x86-ENU.exe
02/07/2007 05:31 PM 1,109,304 WindowsXP-KB924191-x86-ENU.exe
02/07/2007 05:34 PM 1,002,296 WindowsXP-KB924270-x86-ENU.exe
02/07/2007 05:34 PM 1,677,112 WindowsXP-KB924496-x86-ENU.exe
02/07/2007 05:28 PM 802,104 WindowsXP-KB925486-x86-ENU.exe
02/07/2007 05:34 PM 1,620,280 WindowsXP-KB925876-x86-ENU.exe
02/07/2007 05:28 PM 739,640 WindowsXP-KB926255-x86-ENU.exe
02/07/2007 05:49 PM 514,872 WindowsXP-KB928388-x86-ENU.exe
02/07/2007 05:46 PM 513,336 WindowsXP-KB929120-x86-ENU.exe
02/07/2007 05:26 PM 802,104 WindowsXP-KB929969-x86-ENU.exe

This means that all of these updates get applied with the command like:
WINDOWSMEDIA-KB911564-X86-ENU.EXE /quiet

-------------------------------------------------------------

For IE 7 and Media Player 11, you can automate these to. You can automate
the default install of IE7 or use the IE7 too kit to customize it. The
toolkit is easy to use. Let me know if you need helpe with these as well.





"WallyGrommit" <(E-Mail Removed)> wrote in message
news:742A031B-7535-4AF8-B04F-(E-Mail Removed)...
> Ok, finally back up and running.
> (p.s. As curious as I am about David B's and Ian's suggestions, I'm much
> too
> paranoid to download unknown exes or zips - at the risk of missing out on
> some really great tools. Much appreciated, though.)
>
> I'm interested in your suggestion but having trouble parsing the cmd
> lines.
> It's hard to tell the real line breaks from the ones inserted by my
> browser.
> If I substitute your path/file names and ignore ECHOs/REMs, I THINK I'm
> seeing just these three executable lines:
> "<pathToUpdates>\quiet" "/passive /norestart /nobackup" "<pathToOutLog>"
> "<pathToUpdates>\engineWindowsUpdates.cmd"
> "<pathToUpdates>\q" "/q" "<pathToOutLog>"
> Is this right?
>
> Also, you mentioned attached files but not sure how to see those files.
> Can
> I download the missing items from microsoft?
>
>
> "Billy Pumphrey" wrote:
>
>> >
>> > Are there other ways to "batch patch" these things on an XP upgrade?
>> > I've
>> > already downloaded all 70-80 updates, I just need a faster way to apply
>> > them,
>> > i.e., without all the reboots inbetween.
>> >
>>
>> Indeed not all of them work with integrating. I have got this process
>> down
>> that works. I used the microsoft script. Try and bear with me as this
>> is
>> with my customization too.
>>
>> The attached files:
>>
>> engineWindowsUpdates.zip - This was originally called RunUpdates.cmd as
>> you
>> will see in the file. There are a few comments. You should not edit
>> this
>> file.
>>
>> dir.zip - This is the file structure that I have for the script
>>
>> runXPSP2Updates.cmd - This file is the one that you edit. There are a
>> few
>> lines that are key. I do not remember why I have the rem in there for
>> the
>> /quite switch update line, but I think it works. The idea is that you
>> put
>> all of the updates in a folder and you run this command on them and it
>> will
>> run all of the updates in that folder. The updates in the particular
>> folder
>> have to support the switches that you tell it. That is why I have two
>> different commands, so that the updates will run that have the different
>> commands.
>>
>> Echo =======================================
>> Echo Install updates
>> Echo =======================================
>>
>> Echo Installing updates with the /quiet or /passive switch
>> REM Running Runupdates.cmd for the /quiet switch
>> rem "\\woodenapp2\distribution$\Applications\Windows XP SP2
>> Updates\engineWindowsUpdates.cmd"
>> "\\woodenapp2\distribution$\Applications\Windows XP SP2 Updates\quiet"
>> "/passive /norestart /nobackup" "c:\Windows\UpdateSettup.log"
>> Echo Ran Runupdates.cmd for XP SP2 quiet command, rc=%ERRORLEVEL%
>> >>%systemroot%\setuplog1.log
>>
>> Echo Installing updates with the /q switch
>> REM Running Runupdates.cmd for the /q switch
>> "\\woodenapp2\distribution$\Applications\Windows XP SP2
>> Updates\engineWindowsUpdates.cmd"
>> "\\woodenapp2\distribution$\Applications\Windows XP SP2 Updates\q" "/q"
>> "c:\Windows\UpdateSettup.log"
>> Echo Ran Runupdates.cmd for XP SP2 quiet command, rc=%ERRORLEVEL%
>> >>%systemroot%\setuplog1.log
>>
>>
>>
>> This should get you going
>>
>>
>>
>>
>>
>>
>>

Okay, I see what you're doing. And I think I found the microsoft script
you're referring to
http://www.microsoft.com/technet/tec...ilitySpotlight
Looks like just what I need. Thanks I really appreciate the help.

"Billy Pumphrey" wrote:

> Ok I posted the files at http://www.billypumphrey.com/downloads/
>
> You can get them there. The script is on microsofts site some where, maybe
> search for RunUpdates.cmd
>
> I will tak you from scratch and show you how to use these files. You can of
> course put them how you want but with me explaining how to use these files
> that should help you understand the basics of how it works.
>
> engineWindowsUpdate.cmd
> - originallany call RunUpdates.cmd
> - You do not have to change this file
> - I have changed something. There is a check for files in
> C:\Local\Sysinfo\..... This check is from the older BDD, I don't remember
> how this check got in there or how I made up this file. I just made it so
> that this check is bypassed and doesn't have to worry about these files.
> - Use of this file is commented in the file itself. Here is the syntax:
> engineWindowsUpdates.cmd "folderpath" "switches" "logfile" ["ostype"]
> ["splevel"]
> - this file is called via the runXPSP2Updates.cmd file. Running this file
> by itsself does nothing
>
> runXPSP2Updates.cmd
> - this is the file that you run
> - example command line:
> engineWindowsUpdates.cmd \\Server\Updatefilelocation "/q" "C:\Log.log"
> Call the file, put the location of the update folder (remember the specified
> command (/q in this case) will be ran on all updates in the update folder.
> Specify a log file.
>
> So if the folder \\Server\Updatefilelocation contains the following files:
>
> 11/22/2005 10:26 AM 1,012,064 Windows-KB890830-V1.10-ENU.exe
> 01/12/2006 10:13 AM 1,140,064 Windows-KB890830-V1.12-ENU.exe
> 05/02/2006 04:40 PM 1,813,920 Windows-KB890830-V1.15.exe
> 02/08/2007 02:30 PM 4,964,776 Windows-KB890830-V1.24.exe
> 09/14/2005 01:55 PM 851,808 Windows-KB890830-V1.8-ENU.exe
> 02/08/2007 02:30 PM 555,072 WindowsXP-KB923789-x86-ENU.exe
>
> Then all of those files will be ran like this:
> Windows-KB890830-V1.10-ENU.exe /q
>
> This means that only updates that use the /q switch should be in here.
>
> For the files that use the /quiet switch, create a new line in the batch
> file of runXPSP2updates.cmd to run the /quiet switch. Like so:
> engineWindowsUpdates.cmd \\Server\Updatefilelocation "/quiet" "C:\Log.log"
>
> In my folder for the quiet switch, I have these updates in there currently:
> 02/14/2006 08:00 AM 611,592 WINDOWSMEDIA-KB911564-X86-ENU.EXE
> 05/02/2006 04:37 PM 2,556,680
> WindowsMedia10-KB911565-v2-x86-ENU.exe
> 02/14/2006 08:00 AM 2,556,168 WINDOWSMEDIA10-KB911565-X86-ENU.EXE
> 02/14/2006 08:00 AM 2,299,656 WINDOWSMEDIA9-KB911565-X86-ENU.EXE
> 05/02/2006 04:37 PM 3,104,488 WindowsXP-KB885835-x86-ENU.exe
> 09/07/2005 04:44 PM 522,480 WindowsXP-KB890046-x86-ENU.exe
> 09/07/2005 04:44 PM 6,098,160 WindowsXP-KB890859-x86-ENU.exe
> 09/07/2005 04:45 PM 791,280 WindowsXP-KB893066-v2-x86-ENU.exe
> 09/07/2005 04:43 PM 691,440 WindowsXP-KB893756-x86-ENU.exe
> 09/07/2005 04:43 PM 2,077,424 WindowsXP-KB894391-x86-ENU.exe
> 11/02/2005 06:00 PM 2,583,280 WindowsXP-KB896256-v3-x86-ENU.exe
> 09/07/2005 04:43 PM 1,038,576 WindowsXP-KB896358-x86-ENU.exe
> 09/07/2005 04:44 PM 720,624 WindowsXP-KB896422-x86-ENU.exe
> 09/07/2005 04:42 PM 563,440 WindowsXP-KB896423-x86-ENU.exe
> 11/16/2005 11:43 AM 2,594,032 WindowsXP-KB896424-x86-ENU.exe
> 09/07/2005 04:44 PM 525,040 WindowsXP-KB896428-x86-ENU.exe
> 11/16/2005 11:39 AM 4,966,128 WindowsXP-KB896688-x86-ENU.exe
> 09/07/2005 04:43 PM 737,520 WindowsXP-KB899587-x86-ENU.exe
> 11/16/2005 11:38 AM 538,864 WindowsXP-KB899589-x86-ENU.exe
> 09/07/2005 04:43 PM 583,920 WindowsXP-KB899591-x86-ENU.exe
> 05/02/2006 04:39 PM 584,944 WindowsXP-KB900485-v2-x86-ENU.exe
> 11/16/2005 11:37 AM 5,167,344 WindowsXP-KB900725-x86-ENU.exe
> 11/16/2005 11:39 AM 1,046,256 WindowsXP-KB901017-x86-ENU.exe
> 02/14/2006 08:00 AM 543,472 WINDOWSXP-KB901190-X86-ENU.EXE
> 09/07/2005 04:44 PM 625,904 WindowsXP-KB901214-x86-ENU.exe
> 11/16/2005 11:40 AM 4,934,896 WindowsXP-KB902400-x86-ENU.exe
> 11/16/2005 11:36 AM 1,393,392 WindowsXP-KB904706-x86-ENU.exe
> 05/02/2006 04:39 PM 513,264 WindowsXP-KB904942-v2-x86-ENU.exe
> 11/16/2005 11:37 AM 621,296 WindowsXP-KB905414-x86-ENU.exe
> 11/16/2005 11:35 AM 582,384 WindowsXP-KB905749-x86-ENU.exe
> 01/11/2006 05:28 PM 4,980,976 WindowsXP-KB905915-x86-ENU.exe
> 01/09/2006 08:00 AM 597,232 WINDOWSXP-KB908519-X86-ENU.EXE
> 01/12/2006 10:10 AM 803,056 WindowsXP-KB908521-x86-ENU.exe
> 05/02/2006 04:38 PM 4,659,000 WindowsXP-KB908531-v2-x86-ENU.exe
> 01/12/2006 10:12 AM 1,193,200 WindowsXP-KB910437-x86-ENU.exe
> 02/07/2007 05:33 PM 1,093,432 WindowsXP-KB911280-v2-x86-ENU.exe
> 05/02/2006 04:38 PM 574,192 WindowsXP-KB911562-x86-ENU.exe
> 05/02/2006 04:35 PM 1,582,832 WindowsXP-KB911567-x86-ENU.exe
> 02/14/2006 08:00 AM 618,224 WINDOWSXP-KB911927-X86-ENU.EXE
> 05/02/2006 04:35 PM 5,027,568 WindowsXP-KB912812-x86-ENU.exe
> 01/11/2006 05:38 PM 727,280 WindowsXP-KB912919-x86-ENU.exe
> 02/14/2006 08:00 AM 804,592 WINDOWSXP-KB913446-X86-ENU.EXE
> 02/07/2007 05:30 PM 1,307,376 WindowsXP-KB913580-x86-ENU.exe
> 02/07/2007 05:27 PM 1,018,168 WindowsXP-KB914388-x86-ENU.exe
> 02/07/2007 05:50 PM 996,152 WindowsXP-KB914389-x86-ENU.exe
> 02/07/2007 05:49 PM 681,784 WindowsXP-KB914440-v12-x86-ENU.exe
> 03/10/2006 08:00 AM 487,664 WINDOWSXP-KB914798-X86-ENU.EXE
> 02/07/2007 05:29 PM 536,888 WindowsXP-KB915865-v11-x86-ENU.exe
> 02/07/2007 05:48 PM 611,056 WindowsXP-KB916595-x86-ENU.exe
> 02/07/2007 05:44 PM 764,216 WindowsXP-KB917344-x86-ENU.exe
> 02/07/2007 05:46 PM 942,904 WindowsXP-KB917422-x86-ENU.exe
> 02/07/2007 05:45 PM 788,792 WindowsXP-KB917953-x86-ENU.exe
> 02/07/2007 05:35 PM 567,096 WindowsXP-KB918439-x86-ENU.exe
> 02/07/2007 05:44 PM 567,096 WindowsXP-KB919007-x86-ENU.exe
> 02/07/2007 05:28 PM 685,368 WindowsXP-KB920213-x86-ENU.exe
> 02/07/2007 05:32 PM 789,816 WindowsXP-KB920214-x86-ENU.exe
> 02/07/2007 05:31 PM 972,088 WindowsXP-KB920342-x86-ENU.exe
> 02/07/2007 05:35 PM 523,576 WindowsXP-KB920670-x86-ENU.exe
> 02/07/2007 05:30 PM 607,544 WindowsXP-KB920683-x86-ENU.exe
> 02/07/2007 05:33 PM 1,302,840 WindowsXP-KB920685-x86-ENU.exe
> 02/07/2007 05:43 PM 617,272 WindowsXP-KB920872-x86-ENU.exe
> 02/07/2007 05:35 PM 4,479,288 WindowsXP-KB921398-x86-ENU.exe
> 02/07/2007 05:47 PM 563,000 WindowsXP-KB922582-x86-ENU.exe
> 02/07/2007 05:32 PM 824,120 WindowsXP-KB922616-x86-ENU.exe
> 02/07/2007 05:50 PM 4,660,536 WindowsXP-KB922760-x86-ENU.exe
> 02/08/2007 02:30 PM 856,376 WindowsXP-KB922819-x86-ENU.exe
> 02/07/2007 05:31 PM 4,237,624 WindowsXP-KB923191-x86-ENU.exe
> 02/07/2007 05:32 PM 725,304 WindowsXP-KB923414-x86-ENU.exe
> 02/07/2007 05:35 PM 2,388,288 WindowsXP-KB923689-x86-ENU.EXE
> 02/07/2007 05:33 PM 680,760 WindowsXP-KB923980-x86-ENU.exe
> 02/07/2007 05:31 PM 1,109,304 WindowsXP-KB924191-x86-ENU.exe
> 02/07/2007 05:34 PM 1,002,296 WindowsXP-KB924270-x86-ENU.exe
> 02/07/2007 05:34 PM 1,677,112 WindowsXP-KB924496-x86-ENU.exe
> 02/07/2007 05:28 PM 802,104 WindowsXP-KB925486-x86-ENU.exe
> 02/07/2007 05:34 PM 1,620,280 WindowsXP-KB925876-x86-ENU.exe
> 02/07/2007 05:28 PM 739,640 WindowsXP-KB926255-x86-ENU.exe
> 02/07/2007 05:49 PM 514,872 WindowsXP-KB928388-x86-ENU.exe
> 02/07/2007 05:46 PM 513,336 WindowsXP-KB929120-x86-ENU.exe
> 02/07/2007 05:26 PM 802,104 WindowsXP-KB929969-x86-ENU.exe
>
> This means that all of these updates get applied with the command like:
> WINDOWSMEDIA-KB911564-X86-ENU.EXE /quiet
>
> -------------------------------------------------------------
>
> For IE 7 and Media Player 11, you can automate these to. You can automate
> the default install of IE7 or use the IE7 too kit to customize it. The
> toolkit is easy to use. Let me know if you need helpe with these as well.
>
>
>
>
>
> "WallyGrommit" <(E-Mail Removed)> wrote in message
> news:742A031B-7535-4AF8-B04F-(E-Mail Removed)...
> > Ok, finally back up and running.
> > (p.s. As curious as I am about David B's and Ian's suggestions, I'm much
> > too
> > paranoid to download unknown exes or zips - at the risk of missing out on
> > some really great tools. Much appreciated, though.)
> >
> > I'm interested in your suggestion but having trouble parsing the cmd
> > lines.
> > It's hard to tell the real line breaks from the ones inserted by my
> > browser.
> > If I substitute your path/file names and ignore ECHOs/REMs, I THINK I'm
> > seeing just these three executable lines:
> > "<pathToUpdates>\quiet" "/passive /norestart /nobackup" "<pathToOutLog>"
> > "<pathToUpdates>\engineWindowsUpdates.cmd"
> > "<pathToUpdates>\q" "/q" "<pathToOutLog>"
> > Is this right?
> >
> > Also, you mentioned attached files but not sure how to see those files.
> > Can
> > I download the missing items from microsoft?
> >
> >
> > "Billy Pumphrey" wrote:
> >
> >> >
> >> > Are there other ways to "batch patch" these things on an XP upgrade?
> >> > I've
> >> > already downloaded all 70-80 updates, I just need a faster way to apply
> >> > them,
> >> > i.e., without all the reboots inbetween.
> >> >
> >>
> >> Indeed not all of them work with integrating. I have got this process
> >> down
> >> that works. I used the microsoft script. Try and bear with me as this
> >> is
> >> with my customization too.
> >>
> >> The attached files:
> >>
> >> engineWindowsUpdates.zip - This was originally called RunUpdates.cmd as
> >> you
> >> will see in the file. There are a few comments. You should not edit
> >> this
> >> file.
> >>
> >> dir.zip - This is the file structure that I have for the script
> >>
> >> runXPSP2Updates.cmd - This file is the one that you edit. There are a
> >> few
> >> lines that are key. I do not remember why I have the rem in there for
> >> the
> >> /quite switch update line, but I think it works. The idea is that you
> >> put
> >> all of the updates in a folder and you run this command on them and it
> >> will
> >> run all of the updates in that folder. The updates in the particular
> >> folder
> >> have to support the switches that you tell it. That is why I have two
> >> different commands, so that the updates will run that have the different
> >> commands.
> >>
> >> Echo =======================================
> >> Echo Install updates
> >> Echo =======================================
> >>
> >> Echo Installing updates with the /quiet or /passive switch
> >> REM Running Runupdates.cmd for the /quiet switch
> >> rem "\\woodenapp2\distribution$\Applications\Windows XP SP2
> >> Updates\engineWindowsUpdates.cmd"
> >> "\\woodenapp2\distribution$\Applications\Windows XP SP2 Updates\quiet"
> >> "/passive /norestart /nobackup" "c:\Windows\UpdateSettup.log"
> >> Echo Ran Runupdates.cmd for XP SP2 quiet command, rc=%ERRORLEVEL%
> >> >>%systemroot%\setuplog1.log
> >>
> >> Echo Installing updates with the /q switch
> >> REM Running Runupdates.cmd for the /q switch
> >> "\\woodenapp2\distribution$\Applications\Windows XP SP2
> >> Updates\engineWindowsUpdates.cmd"
> >> "\\woodenapp2\distribution$\Applications\Windows XP SP2 Updates\q" "/q"
> >> "c:\Windows\UpdateSettup.log"
> >> Echo Ran Runupdates.cmd for XP SP2 quiet command, rc=%ERRORLEVEL%
> >> >>%systemroot%\setuplog1.log
> >>
> >>
> >>
> >> This should get you going
> >>
> >>
> >>
> >>
> >>
> >>
> >>
>

That is it. Sorry I didn't do the searching for you. I have been trying to
get my BDD 2007 down the road.


"WallyGrommit" <(E-Mail Removed)> wrote in message
news:85EEC185-C196-4DA4-8AC8-(E-Mail Removed)...
> Okay, I see what you're doing. And I think I found the microsoft script
> you're referring to
> http://www.microsoft.com/technet/tec...ilitySpotlight
> Looks like just what I need. Thanks I really appreciate the help.
>
> "Billy Pumphrey" wrote:
>
>> Ok I posted the files at http://www.billypumphrey.com/downloads/
>>
>> You can get them there. The script is on microsofts site some where,
>> maybe
>> search for RunUpdates.cmd
>>
>> I will tak you from scratch and show you how to use these files. You can
>> of
>> course put them how you want but with me explaining how to use these
>> files
>> that should help you understand the basics of how it works.
>>
>> engineWindowsUpdate.cmd
>> - originallany call RunUpdates.cmd
>> - You do not have to change this file
>> - I have changed something. There is a check for files in
>> C:\Local\Sysinfo\..... This check is from the older BDD, I don't
>> remember
>> how this check got in there or how I made up this file. I just made it
>> so
>> that this check is bypassed and doesn't have to worry about these files.
>> - Use of this file is commented in the file itself. Here is the syntax:
>> engineWindowsUpdates.cmd "folderpath" "switches" "logfile" ["ostype"]
>> ["splevel"]
>> - this file is called via the runXPSP2Updates.cmd file. Running this
>> file
>> by itsself does nothing
>>
>> runXPSP2Updates.cmd
>> - this is the file that you run
>> - example command line:
>> engineWindowsUpdates.cmd \\Server\Updatefilelocation "/q" "C:\Log.log"
>> Call the file, put the location of the update folder (remember the
>> specified
>> command (/q in this case) will be ran on all updates in the update
>> folder.
>> Specify a log file.
>>
>> So if the folder \\Server\Updatefilelocation contains the following
>> files:
>>
>> 11/22/2005 10:26 AM 1,012,064 Windows-KB890830-V1.10-ENU.exe
>> 01/12/2006 10:13 AM 1,140,064 Windows-KB890830-V1.12-ENU.exe
>> 05/02/2006 04:40 PM 1,813,920 Windows-KB890830-V1.15.exe
>> 02/08/2007 02:30 PM 4,964,776 Windows-KB890830-V1.24.exe
>> 09/14/2005 01:55 PM 851,808 Windows-KB890830-V1.8-ENU.exe
>> 02/08/2007 02:30 PM 555,072 WindowsXP-KB923789-x86-ENU.exe
>>
>> Then all of those files will be ran like this:
>> Windows-KB890830-V1.10-ENU.exe /q
>>
>> This means that only updates that use the /q switch should be in here.
>>
>> For the files that use the /quiet switch, create a new line in the batch
>> file of runXPSP2updates.cmd to run the /quiet switch. Like so:
>> engineWindowsUpdates.cmd \\Server\Updatefilelocation "/quiet"
>> "C:\Log.log"
>>
>> In my folder for the quiet switch, I have these updates in there
>> currently:
>> 02/14/2006 08:00 AM 611,592 WINDOWSMEDIA-KB911564-X86-ENU.EXE
>> 05/02/2006 04:37 PM 2,556,680
>> WindowsMedia10-KB911565-v2-x86-ENU.exe
>> 02/14/2006 08:00 AM 2,556,168
>> WINDOWSMEDIA10-KB911565-X86-ENU.EXE
>> 02/14/2006 08:00 AM 2,299,656 WINDOWSMEDIA9-KB911565-X86-ENU.EXE
>> 05/02/2006 04:37 PM 3,104,488 WindowsXP-KB885835-x86-ENU.exe
>> 09/07/2005 04:44 PM 522,480 WindowsXP-KB890046-x86-ENU.exe
>> 09/07/2005 04:44 PM 6,098,160 WindowsXP-KB890859-x86-ENU.exe
>> 09/07/2005 04:45 PM 791,280 WindowsXP-KB893066-v2-x86-ENU.exe
>> 09/07/2005 04:43 PM 691,440 WindowsXP-KB893756-x86-ENU.exe
>> 09/07/2005 04:43 PM 2,077,424 WindowsXP-KB894391-x86-ENU.exe
>> 11/02/2005 06:00 PM 2,583,280 WindowsXP-KB896256-v3-x86-ENU.exe
>> 09/07/2005 04:43 PM 1,038,576 WindowsXP-KB896358-x86-ENU.exe
>> 09/07/2005 04:44 PM 720,624 WindowsXP-KB896422-x86-ENU.exe
>> 09/07/2005 04:42 PM 563,440 WindowsXP-KB896423-x86-ENU.exe
>> 11/16/2005 11:43 AM 2,594,032 WindowsXP-KB896424-x86-ENU.exe
>> 09/07/2005 04:44 PM 525,040 WindowsXP-KB896428-x86-ENU.exe
>> 11/16/2005 11:39 AM 4,966,128 WindowsXP-KB896688-x86-ENU.exe
>> 09/07/2005 04:43 PM 737,520 WindowsXP-KB899587-x86-ENU.exe
>> 11/16/2005 11:38 AM 538,864 WindowsXP-KB899589-x86-ENU.exe
>> 09/07/2005 04:43 PM 583,920 WindowsXP-KB899591-x86-ENU.exe
>> 05/02/2006 04:39 PM 584,944 WindowsXP-KB900485-v2-x86-ENU.exe
>> 11/16/2005 11:37 AM 5,167,344 WindowsXP-KB900725-x86-ENU.exe
>> 11/16/2005 11:39 AM 1,046,256 WindowsXP-KB901017-x86-ENU.exe
>> 02/14/2006 08:00 AM 543,472 WINDOWSXP-KB901190-X86-ENU.EXE
>> 09/07/2005 04:44 PM 625,904 WindowsXP-KB901214-x86-ENU.exe
>> 11/16/2005 11:40 AM 4,934,896 WindowsXP-KB902400-x86-ENU.exe
>> 11/16/2005 11:36 AM 1,393,392 WindowsXP-KB904706-x86-ENU.exe
>> 05/02/2006 04:39 PM 513,264 WindowsXP-KB904942-v2-x86-ENU.exe
>> 11/16/2005 11:37 AM 621,296 WindowsXP-KB905414-x86-ENU.exe
>> 11/16/2005 11:35 AM 582,384 WindowsXP-KB905749-x86-ENU.exe
>> 01/11/2006 05:28 PM 4,980,976 WindowsXP-KB905915-x86-ENU.exe
>> 01/09/2006 08:00 AM 597,232 WINDOWSXP-KB908519-X86-ENU.EXE
>> 01/12/2006 10:10 AM 803,056 WindowsXP-KB908521-x86-ENU.exe
>> 05/02/2006 04:38 PM 4,659,000 WindowsXP-KB908531-v2-x86-ENU.exe
>> 01/12/2006 10:12 AM 1,193,200 WindowsXP-KB910437-x86-ENU.exe
>> 02/07/2007 05:33 PM 1,093,432 WindowsXP-KB911280-v2-x86-ENU.exe
>> 05/02/2006 04:38 PM 574,192 WindowsXP-KB911562-x86-ENU.exe
>> 05/02/2006 04:35 PM 1,582,832 WindowsXP-KB911567-x86-ENU.exe
>> 02/14/2006 08:00 AM 618,224 WINDOWSXP-KB911927-X86-ENU.EXE
>> 05/02/2006 04:35 PM 5,027,568 WindowsXP-KB912812-x86-ENU.exe
>> 01/11/2006 05:38 PM 727,280 WindowsXP-KB912919-x86-ENU.exe
>> 02/14/2006 08:00 AM 804,592 WINDOWSXP-KB913446-X86-ENU.EXE
>> 02/07/2007 05:30 PM 1,307,376 WindowsXP-KB913580-x86-ENU.exe
>> 02/07/2007 05:27 PM 1,018,168 WindowsXP-KB914388-x86-ENU.exe
>> 02/07/2007 05:50 PM 996,152 WindowsXP-KB914389-x86-ENU.exe
>> 02/07/2007 05:49 PM 681,784 WindowsXP-KB914440-v12-x86-ENU.exe
>> 03/10/2006 08:00 AM 487,664 WINDOWSXP-KB914798-X86-ENU.EXE
>> 02/07/2007 05:29 PM 536,888 WindowsXP-KB915865-v11-x86-ENU.exe
>> 02/07/2007 05:48 PM 611,056 WindowsXP-KB916595-x86-ENU.exe
>> 02/07/2007 05:44 PM 764,216 WindowsXP-KB917344-x86-ENU.exe
>> 02/07/2007 05:46 PM 942,904 WindowsXP-KB917422-x86-ENU.exe
>> 02/07/2007 05:45 PM 788,792 WindowsXP-KB917953-x86-ENU.exe
>> 02/07/2007 05:35 PM 567,096 WindowsXP-KB918439-x86-ENU.exe
>> 02/07/2007 05:44 PM 567,096 WindowsXP-KB919007-x86-ENU.exe
>> 02/07/2007 05:28 PM 685,368 WindowsXP-KB920213-x86-ENU.exe
>> 02/07/2007 05:32 PM 789,816 WindowsXP-KB920214-x86-ENU.exe
>> 02/07/2007 05:31 PM 972,088 WindowsXP-KB920342-x86-ENU.exe
>> 02/07/2007 05:35 PM 523,576 WindowsXP-KB920670-x86-ENU.exe
>> 02/07/2007 05:30 PM 607,544 WindowsXP-KB920683-x86-ENU.exe
>> 02/07/2007 05:33 PM 1,302,840 WindowsXP-KB920685-x86-ENU.exe
>> 02/07/2007 05:43 PM 617,272 WindowsXP-KB920872-x86-ENU.exe
>> 02/07/2007 05:35 PM 4,479,288 WindowsXP-KB921398-x86-ENU.exe
>> 02/07/2007 05:47 PM 563,000 WindowsXP-KB922582-x86-ENU.exe
>> 02/07/2007 05:32 PM 824,120 WindowsXP-KB922616-x86-ENU.exe
>> 02/07/2007 05:50 PM 4,660,536 WindowsXP-KB922760-x86-ENU.exe
>> 02/08/2007 02:30 PM 856,376 WindowsXP-KB922819-x86-ENU.exe
>> 02/07/2007 05:31 PM 4,237,624 WindowsXP-KB923191-x86-ENU.exe
>> 02/07/2007 05:32 PM 725,304 WindowsXP-KB923414-x86-ENU.exe
>> 02/07/2007 05:35 PM 2,388,288 WindowsXP-KB923689-x86-ENU.EXE
>> 02/07/2007 05:33 PM 680,760 WindowsXP-KB923980-x86-ENU.exe
>> 02/07/2007 05:31 PM 1,109,304 WindowsXP-KB924191-x86-ENU.exe
>> 02/07/2007 05:34 PM 1,002,296 WindowsXP-KB924270-x86-ENU.exe
>> 02/07/2007 05:34 PM 1,677,112 WindowsXP-KB924496-x86-ENU.exe
>> 02/07/2007 05:28 PM 802,104 WindowsXP-KB925486-x86-ENU.exe
>> 02/07/2007 05:34 PM 1,620,280 WindowsXP-KB925876-x86-ENU.exe
>> 02/07/2007 05:28 PM 739,640 WindowsXP-KB926255-x86-ENU.exe
>> 02/07/2007 05:49 PM 514,872 WindowsXP-KB928388-x86-ENU.exe
>> 02/07/2007 05:46 PM 513,336 WindowsXP-KB929120-x86-ENU.exe
>> 02/07/2007 05:26 PM 802,104 WindowsXP-KB929969-x86-ENU.exe
>>
>> This means that all of these updates get applied with the command like:
>> WINDOWSMEDIA-KB911564-X86-ENU.EXE /quiet
>>
>> -------------------------------------------------------------
>>
>> For IE 7 and Media Player 11, you can automate these to. You can
>> automate
>> the default install of IE7 or use the IE7 too kit to customize it. The
>> toolkit is easy to use. Let me know if you need helpe with these as
>> well.
>>
>>
>>
>>
>>
>> "WallyGrommit" <(E-Mail Removed)> wrote in message
>> news:742A031B-7535-4AF8-B04F-(E-Mail Removed)...
>> > Ok, finally back up and running.
>> > (p.s. As curious as I am about David B's and Ian's suggestions, I'm
>> > much
>> > too
>> > paranoid to download unknown exes or zips - at the risk of missing out
>> > on
>> > some really great tools. Much appreciated, though.)
>> >
>> > I'm interested in your suggestion but having trouble parsing the cmd
>> > lines.
>> > It's hard to tell the real line breaks from the ones inserted by my
>> > browser.
>> > If I substitute your path/file names and ignore ECHOs/REMs, I THINK I'm
>> > seeing just these three executable lines:
>> > "<pathToUpdates>\quiet" "/passive /norestart /nobackup"
>> > "<pathToOutLog>"
>> > "<pathToUpdates>\engineWindowsUpdates.cmd"
>> > "<pathToUpdates>\q" "/q" "<pathToOutLog>"
>> > Is this right?
>> >
>> > Also, you mentioned attached files but not sure how to see those files.
>> > Can
>> > I download the missing items from microsoft?
>> >
>> >
>> > "Billy Pumphrey" wrote:
>> >
>> >> >
>> >> > Are there other ways to "batch patch" these things on an XP
>> >> > upgrade?
>> >> > I've
>> >> > already downloaded all 70-80 updates, I just need a faster way to
>> >> > apply
>> >> > them,
>> >> > i.e., without all the reboots inbetween.
>> >> >
>> >>
>> >> Indeed not all of them work with integrating. I have got this process
>> >> down
>> >> that works. I used the microsoft script. Try and bear with me as
>> >> this
>> >> is
>> >> with my customization too.
>> >>
>> >> The attached files:
>> >>
>> >> engineWindowsUpdates.zip - This was originally called RunUpdates.cmd
>> >> as
>> >> you
>> >> will see in the file. There are a few comments. You should not edit
>> >> this
>> >> file.
>> >>
>> >> dir.zip - This is the file structure that I have for the script
>> >>
>> >> runXPSP2Updates.cmd - This file is the one that you edit. There are a
>> >> few
>> >> lines that are key. I do not remember why I have the rem in there for
>> >> the
>> >> /quite switch update line, but I think it works. The idea is that you
>> >> put
>> >> all of the updates in a folder and you run this command on them and it
>> >> will
>> >> run all of the updates in that folder. The updates in the particular
>> >> folder
>> >> have to support the switches that you tell it. That is why I have two
>> >> different commands, so that the updates will run that have the
>> >> different
>> >> commands.
>> >>
>> >> Echo =======================================
>> >> Echo Install updates
>> >> Echo =======================================
>> >>
>> >> Echo Installing updates with the /quiet or /passive switch
>> >> REM Running Runupdates.cmd for the /quiet switch
>> >> rem "\\woodenapp2\distribution$\Applications\Windows XP SP2
>> >> Updates\engineWindowsUpdates.cmd"
>> >> "\\woodenapp2\distribution$\Applications\Windows XP SP2 Updates\quiet"
>> >> "/passive /norestart /nobackup" "c:\Windows\UpdateSettup.log"
>> >> Echo Ran Runupdates.cmd for XP SP2 quiet command, rc=%ERRORLEVEL%
>> >> >>%systemroot%\setuplog1.log
>> >>
>> >> Echo Installing updates with the /q switch
>> >> REM Running Runupdates.cmd for the /q switch
>> >> "\\woodenapp2\distribution$\Applications\Windows XP SP2
>> >> Updates\engineWindowsUpdates.cmd"
>> >> "\\woodenapp2\distribution$\Applications\Windows XP SP2 Updates\q"
>> >> "/q"
>> >> "c:\Windows\UpdateSettup.log"
>> >> Echo Ran Runupdates.cmd for XP SP2 quiet command, rc=%ERRORLEVEL%
>> >> >>%systemroot%\setuplog1.log
>> >>
>> >>
>> >>
>> >> This should get you going
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>>