guysmiley

Service packs have had the ability to self-slipstream since W2K SP1 with the -s switch. Thanks for the compliment, GM. I've been writing batch files since DOS 2.1 so I've become reasonably handy with the task. -Wiseguy del Batchfile

You can fix that by redirecting error output of the command. For instance, in a dir where no tmp files exist: dir *.tmp >nul 2>&1 In English this command means, "Redirect output of the DIR command to the NUL handle, as well as redirect error output (specified by 2>) to STDOUT (&1)." Since STDOUT is alredy being routed to NUL so will STDERR.

I just found another thread that says 832483 can't be installed directly from svcpack.inf (which sounds logical). However, the top post says that the syntax can be called out with a batch file in svcpack.inf. If CreateProcess is being used to spawn these patches at the end of GUI setup don't you need to wrap the call to your batch file with "%windir%\system32\cmd.exe /c [batchfile.cmd]" or can you just put "KB832483.CMD" in svcpack.inf and have it work?

Letmein, I'm trying also to get 832483 working. What was the final command line that you used in svcpack.inf to make setup apply this patch? The double-double quotes didn't work for me.