Aaron

Is this what you needed? http://board.MSFN.org/index.php?showtopic=7673

IPv6?

/me frowns I don't know why I don't get these folders.

Glad you enjoyed it, fun isn't it? Welcome to MSFN Orsi

http://news.sina.com.cn/s/2003-10-09/16191886838.shtml

If you have a look in C:\Windows\Microsoft.NET\Framework\ you can see the version number of a folder, like "v1.1.4322". Hope that helps!

You can do it that way if you want. There's no issues from using Qxxxxxx.exe instead. Also if you list your hotfixes in numerical order, its likely all the new KB named ones will be last on the list.

It's available on http://www.MSFN.org/unattended/xp/directx.htm but I'm gonna have to remove it soon due to EULA violations. Both the DirectX 9.0b and WMP9MM2 OPKs are 32MB (there's no .Net Framework OPK), but bandwidth is an issue...

Sure, I'll wait until the SRP is out before applying dates to future hotfixes, because the SRP makes 90% of critical updates on that list redundant

Yep, using wimp9.cmd is enough, as long as that and mpsetupxp is in the svcpack folder.

That command doesn't work in svcpack because it doesn't like quotes. You can however put a batch file in its place and call out to the exe with the full command shown out by snooz.

Welcome to MSFN Swift!

Preinstallation Environment

yeah, neophyte has confirmed that the /DisableSystemRestore switch doesn't work on the main executable itself, only the wm_setup.exe file within. More information on the syntax to be used on MPSetupXP.exe can be found at this thread: http://board.MSFN.org/index.php?showtopic=9439&hl=

Not at all, only file replacements are being done by hotfixes, not file additions.

Everyone can choose to use WinISO/UltraISO if they wish. There's a small number of people that never have any luck using these kind of programs, as on some occasions it can crash or render the ISO unbootable.

If 4 of those batch files are being executed as each line under [GuiRunOnce] then create another batch file to execute your four batch files. Like this: start /wait $systemdrive$\install\batch1.cmd >>C:\batch1.log start /wait $systemdrive$\install\batch2.cmd >>C:\batch2.log start /wait $systemdrive$\install\batch3.cmd >>C:\batch3.log start /wait $systemdrive$\install\batch4.cmd >>C:\batch4.log EXIT Call this startbatch.cmd and use this in [GuiRunOnce] instead. Its done this way because [GuiRunOnce] doesn't like the >> command. Not sure on how to log svcpack.inf activities though

I created a D:\ NTFS partition, and installed Windows XP again to C:\ with all the svcpack hotfixes, and D:\ still remains empty.

What switches do you use?, I'll have to create a partition in Virtual PC and see why its doing what you explained.

Still in beta, might come out today or next wednesday. btw, I didn't call the svcpack method on the site "slipstreaming". There's several ways svcpack.inf can be used. Even running the batch in GuiRunOnce isn't "slipstreaming" either. In the end, its up to you what method you want to use. I'm going to be adding alternatives to the site, including the script you mentioned above

z00mX - Go to Windows Update and install all the critical updates available, especially this update: Q824146 A Buffer Overrun in RPCSS Could Allow an Attacker to Run Malicious Programs

Yes, you should have quotes at the start and the end: I've also removed the trialling slashes before every semi-colon. Gosh - I think the limit has been increased to 4096 characters since Windows 2000. Will need to check up on that again to be sure. Edit: here it is http://support.microsoft.com/default.aspx?...kb;en-us;312535

Agree with you there. Some people also post all their complete code/scripts even when the problem they're having occurs before some of their batch scripts are being executed.

just the $OEM$ folder. As for the Current User regtweaks - yes