GreenMachine

Use the BIG X on the top right corner! (Fixed, Version 10 JUNE 2004 is current.)

From RunOnce, or similar, no problem. However ...

That's better. You could use a batch file to call all of the updates one at a time. There must be an example on the unatended site. Probably called something like INSTALLS.CMD or HOTFIXES.CMD. Plenty of them pasted all over this forum!

Let me clarify: I use the /Q /O /U /N /Z switches (Quiet, Overwrite OEM files, Unattended, No Uninstall, and No Reboot). That works fine, the installer is run, the log files report the DLLs have been copied to the DLL cache (which they were not), but not system32, and indicates a possible SFC error. The DX9 / Patch versions ARE coherent: DX9 all around. The patch IS listed in Add/Remove programs, but the DLLs are not present on the system. The patch is called from SVCPACK.INF, AFTER the DX9 install. I have tried a few variations of this theme. So, if anyone has succeeded, please let me know how YOU did it.

Double click on the files, that will install them. (You need to work on formulating your questions ... )

Here is some CMDLINES.TXT info: http://greenmachine.msfnhosting.com/READING/cmdlines.htm My rule of thumb: If you can install it from either SVCPACK or CMDLINES, do (either one: your call), otherwise RunOnce.

SVCPACK.INF is a stand alone item: there is not CMD file that calls it. Update that file correctly, put your .exe files in the I386\SVCPACK directory, and that should be fine. Most of the help you need is in the Unattended Guide.

I've had no luck getting that one in unattended either, with both the correct and incorrect updates. If anyone manages to install this from either SVCPACK.INF or CMDLINES.TXT, and it does not show up on Windows Update, and the two files (dplayx.dll and dpwsockx.dll) are the correct version (5.3.903, I think...) after installation, I'd be insterested to know how ...

God, that looks like a horror show. As soon as I made the ugly signature below, I quickly disabled signature viewing from my options ...

Behaviour by design. I believe that is a SVCPACK.INF example. I doubt WINNT.SIF likes the quotes.

That should work. Just remember, walk before you run. All XPCREATE support is dependent on first creating a FailSafe XP CD. Please see the Web Site if you are unsure of what that means.

XPCTEST looked good enough to release as XPCREATE. At least that way I should get more testers! To be clear: all downloadable versions of XPCREATE are the latest (9 JUNE 2004), which includes the AutoUpdate feature. AutoUpdate is on by default. If this is not desired, please edit the XPCREATE.INI file, as outlined on the Web Site.

XPCTEST has replaced XPCEATE. Please post in that thread!

Welcome to MSFN, pwhodges! Yes, that is due to a version mixup. I was testing with SP!, which, of course, is not available for download. Should be OK now. I've pulled the DX9 update off the list, as at this point the best solutions seems to be RunOnce for this hotfix. You should be OK now, ente.

Because there is one list, and I pick 'em. Edit XPCREATE.INI, change DLAUTO=YES to DLAUTO=NO, and you XPCREATE will not attempt to download any. For more information about how I select hotfixes for the list, have a gander at the XPCREATE Web Site. I should have a link or two in my signature.

Should work. however, that indicates to me that you are not starting the whle process from an original Windows CD ...

I thought it did, but I can't find it anywhere. Least not Type I. I suppose that is the next step.

Me, I always respected Groucho Marx for his one-liners ... IF NOT "%A%"=="%B%" IF NOT "%C%"=="%D%" GOTO BAR

Anyone else have any input on this? XPCTEST downloads the version linked to above, and I show it as missing.

Glad that fixed it. It was a white space error. I got tired of doing the TXTSET.OEM files by hand, and there seemed to be a bug in the generator.

Welcome to MSFN, JohnA. Anything is possible! Have a good read at http://unatteded.msfn.org. XPCREATE does nothing more than automate some of the processes outlined there. As for non OS stuff, XPCREATE doesn't help you there.

I knew I could count on Alanoll to understand!

Good idea, but you'd best mask that address, or it will be full of s**m faster than you can say rumpelstilsken ... hflists {at} xpcreate {dot} wiretapped {dot} us

When in doubt, google it out ... http://www.google.com/search?num=100&hl=en...lipstreaming%22 ("windows 2003 server" "hotfix slipstreaming")

Looks like the problem is in the new, automatically generated XPCREATE.CAB file. Please replace your version with the attached, and let me know. Thanks. XPCREATE.CAB