Mr_Smartepants

Does this "wait" issue potentially affect other files, or just that one? Nice find!

You need the Mass Storage drivers from Sony for your system to slipstream using nlite (If you're only installing to a single system). www.driverpacks.net has universal drivers that can be slipstreamed into your XP source using the DriverPacks BASE that would allow your disc to be installed to 98% of systems out there.

I'm using Win7 X64 has the host OS. Personally, I can't imagine anyone actually running XP SP1. I'd make it a prerequisite to have XP SP2 or higher. It would certainly make it easier for you to have a reduced codebase.

Both files are zipped up here: http://www.mediafire.com/file/kwq2toz2c1m/files.7z

Sorry to report that the WUAUCPL.MUI bug still exists in the MCE build I just did using 3.0.0.5.

Is that file the same through all the different XP versions? Removing the resources and doing a simple file replacement would be the simplest option, but not very elegant. Also the safest option, but not ideal either would be to not patch that file in the first place (until a fix is found). Having a partially patched system is better than a broken system.

Just got done testing the new 3.0.0.4 GUI and I can confirm that the Automatic Updates tab problem Burned reported affects all versions (Home, Pro, MCE) AND not just the 3.* versions of GUI but 2.2.0.4 also, which never previously had a problem now has the same problem. The bug must be in the resources (green.xptsp tested) or somewhere else. I tried with resources translation option checked & unchecked.

Now that I know what to look for, I can work around this issue. It's possible that 3.0.0.4 will solve the problem inadvertently.

I integrate XP SP3 MSDN sources with U_H post-sp3 updatepack along with WMP11 and a (fairly conservative) list of addons. I'll do another test just to make sure. *Edit OK, confirmed. The problem still exists. Just did XP Pro SP3 with my normal updatepack/addon load. I make the following de-selections: All other settings are defaults. Here's the relevant portion of the xptsp log: And the relevant portion of dosnet.inf Before integrating, I used ccleaner to nuke my temp files, used a clean XP source, reintegrated fresh updatepack/addons. Redownloaded xptsp 3.0.0.3 (MD5 matches site) and let the GUI download fresh themes, extras etc. I'll test again on a bare XP Pro sp3 source just to be certain. *Edit#2 Problem still exists even with an unaltered MSDN XP Pro SP3 disc. Dosnet.inf entries are made and files added even if de-selected. What else would you like me to try? *Edit#3 OK, de-selecting the entire group, then manually re-selecting the components I wanted solves the problem.

Lo que quiero hacer es posible mediante el uso PowerPacker. Usted construir

Wow, that is great news! Thank you.

Just confirmed with Pro. The problem still exists. Additional programs are installed even if they are deselected.

The above problems still exist in 3.0.0.3 on my MCE build. I have not yet tested Pro.

You used the wrong switch. No need for double-quotes. Just make a cleanup.cmd file and call it. The target directory should be empty before deleting it. DEL /F /S /Q "%AllUsersProfile%\Start Menu\Programs\Microsoft Silverlight\*.*" RD /S /Q "AllUsersProfile%\Start Menu\Programs\Microsoft Silverlight\"

I just got done testing my Pro disc which had 3.0.0.1 integrated in it, so I don't know if you've already fixed it in 3.0.0.2 but it had issues. When I go through the installer I usually uncheck the "Additional Programs" UberIcon, Visual Task Tips, Transparent Bar, True Transparency, & WinFlip but they ALL got installed anyway. I have not yet tested 3.0.0.2.

It sounds like you don't understand what you're doing. You need to first understand what cmdlines.txt and svcpack.inf are used for. First read: http://unattended.ms...xp/view/web/14/ Next read: http://unattended.ms...xp/view/web/24/

Just testing now. 3.0.0.1 is detecting my XP MCE source as XP Pro now. I'll continue with the integration and let you know of any other problems.

No problem. I'm standing by waiting to test. From my perspective, there's nothing wrong with 2.2.0.4, but I'm all for progress and supporting more users. :thumbsup_anim:

I told you it would fail. The finisher will run fine, but the individual installers were not made to be installed at T-13 and the majority of them will fail.

You'll have to check the %windir%\DPsFnshr.log

Trying v3.0.0.0 and I'm getting a fail during integration. Integrating into xp pro sp3 with u_h 1.3.0 update pack. Integration halts here with no progression if I close the cmd window. The cmd window will continue to respawn in an endless loop until I reboot.

To answer your question...no. That's not possible. Not all the installers in every DriverPack are compatible with being installed at T-13, but all are ROE compatible. If you want to test, add the following line to \i386\svcpack.inf [SetupHotfixesToRun] %SystemDrive% & cd\ & Start /wait /separate /high "" DPsFnshr.exe I haven't tested this, but I'm 90% certain that it will fail. Don't blame me if this smokes your install, melts your ice-cream or turns your cat purple.

That's because there are only two options. GUIrunonce or RunOnceEx. Both occur at roughly the same time. ROE is better (in my opinion). GUIrunonce requires entries in the winnt.sif, which is not used by everyone. If you have entries in BOTH GUIrunonce and RunOnceEx, they will both execute at the same time and cause problems. EXACTLY when do you wish to execute the finisher? Ricktendo64 already explained how to execute it during first user login.

Why aren't you asking this question over at DriverPacks.net forums? Are you afraid of us? Did you select to run the finisher at GUIrunonce or RunOnceEx? If RunOnceEx, then change the number found in %source%\$OEM$\cmdlines.txt [Commands] "ROE.exe 937" Change the 937 to any number between 10 and 999. Any number will do, but make sure it doesn't conflict with your other apps executing during RunOnceEx. For more info on ROE, read here: http://unattended.msfn.org/unattended.xp/view/web/14/

No problem. I was just doing my public service announcement for the day.