Mr_Smartepants

BTW, I fixed my script problem. It was my own fault. :CLEANUP IF EXIST %windir%\Setup\scripts RD /S /Q %windir%\Setup\scripts >nul DEL /F /Q %0% >nul exit I was deleting the scripts before they had a chance to run.

Oops. Rookie mistake! That was leftover code from a previous Vista script. -Root certs. Are you sure? I think I started post-installing them because my installs were getting nagged by MU/WU for them. I'll check. -DirectX. Thanks! I'll try that. -.net4. Nah, that's just me being lazy.

I feel like I'm missing something critical. I can't get my setupcomplete.cmd to execute. I have it in my %cdrom%\sources\$oem$\$\Setup\scripts\setupcomplete.cmd It's in the same folder as my OOBE.cmd (auto-activating OEM script). OOBE.cmd executes just fine, but setupcomplete.cmd does not. What the hell am I doing wrong? setupcomplete.cmd @echo off for %%i in (C D E F G H I J K L M N O P Q R S T U V W X Y Z) do if exist %%i:\sources\install.wim set CDROM=%%i: echo Found CD-Rom as drive %CDROM% ::Begin hotfix install :Root Certificates echo Installing Root Certificates start /wait %CDROM%\updates\rootsupd.exe /Q :Malicious software removal tool echo Installing Malicious Software Removal Tool start /wait %CDROM%\updates\windows-kb890830-v3.17.exe /Q :DirectX echo Updating DirectX start /wait %CDROM%\updates\dxsetup-jun2010-x86.exe /Q :NET Framework 4 ::start /wait Client\netfx_core_x64.msi EXTUI=1 ::start /wait Extended\netfx_extended_x64.msi EXTUI=1 start /wait %CDROM%\updates\dotNetFx40_Full_x86_x64.exe /passive /norestart start /wait %CDROM%\updates\NDP40-KB2416472-x86.exe /passive /norestart start /wait %windir%\Microsoft.NET\Framework\v4.0.30319\ngen executequeueditems start /wait %windir%\Microsoft.NET\Framework64\v4.0.30319\ngen executequeueditems :options ::Requires .NET 4 echo Installing Super Calendar start /wait %CDROM%\updates\WinCal-Win7-x86-en-us.exe /S /v/qb echo Installing Pinball start /wait %CDROM%\updates\WinPinball-en-us.exe /S /v/qb ::start /wait %CDROM%\updates\ /silent :WPIW ::Begin WPIW echo Starting Windows Post-Install Wizard pause REG ADD "HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main" /V "Disable Script Debugger" /T "REG_SZ" /D "no" /F REG ADD "HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main" /V "DisableScriptDebuggerIE" /T "REG_SZ" /D "no" /F Start %CDROM%\WPI\wpi.hta del %0 Double clicking the setupcomplete.cmd works just fine once at the desktop, so the contents of the .cmd work fine, I just can't get it to execute on it's own. Actually, if I could just get WPI to execute properly at first login with admin privileges I'd just move all the installers to WPI. Another thing that bothers me is the DXsetup isn't silent. It halts the install to ask the user questions. Very annoying.

Yes, strange. I have v3.0.0.17 (build date 17 Jan) File: XPtsp_v3.0.0.17_GUI.exe CRC-32: 98710103 MD4: ad7ba3533720c264ac7ce733b0021a3b MD5: a1723194b39a319dbb129ec2239dd421 SHA-1: 896a0b65f16d00e8b53a060bc12c8d49d63bb8f9 The first post has links for v3.0.0.16 and yet the homepage (http://www.xptsp.com...p_Downloads.php) has a 'current' link for v3.0.0.9 (build date of 20 Feb 2011). So I guess there's some version number wacky-ness going on here. *Edit Dougiefresh closed his support forums. Because his site appears to be broken and doesn't directly link to the current version, I'll link to it here. The last good version was v3.0.0.17 Download: http://www.mediafire.com/file/e9aytda3909uo64/XPtsp_v3.0.0.17_GUI.7z

OK, I was having trouble with an error at T-15 for "missing ICFGNT.DLL" then realized this was already reported: Here: http://www.wincert.n...dpost__p__45700 and here: http://www.wincert.n...1866#entry41866 I was using AutoImage to integrate everything via RVMi (no nlite) and AI starts WMP11 Integrator after RVMi which is causing the issue. I'm wondering why the error is for ICFGNT.DLL when the filename is ICFGNT5.DLL in the XP source. Is the WMP11 integration missing the correct filename? Or where is that file being called from? Nevermind. Boooggy says it's because the WMP11 slipstreamer is seeing the source as containing WMP10 instead of the actual WMP9. I still can't get these working right with RVMi. I even scrapped using the WMP11 slipstreamer and used YumeYao's WMP11 addon. On that install there must have been an .inf error somewhere because nothing was installed (empty Start menu) though no errors displayed during install. Moving back to nlite to integrate the MCE & Sidebar addons worked fine. I was really hoping to ditch nlite this time. Oh well, this will probably be my last XP build. I've moved over almost completely to Win7.

I'm sure your Win7 MCE addon is already RVMi compatible. But it wouldn't hurt to check. Your Sidebar, Holdem, and Ultimate sounds would be my choices, but I don't want to push my luck.

Lavalys sold out Everest and it's now known as AIDA64. http://www.lavalys.com/ I imagine this addon is at end-of-life now. For those wanting to upgrade from Everest 5.5, they've set up a forum link. http://forums.aida64.com/index.php?/topic/67-everest-upgrade/

Nice! Thank you Rick! Is it still dependent on nlite for install or is it now RVMi compatible?

LOL, you're updating it faster than I can test it!

Nevermind. Now it's working.

Link is down. Access to the webpage was denied You are not authorized to access the webpage athttp://download643.mediafire.com/783gudwteefg/f17u0dapk0xk70b/GDism+ELDI+v5.2.rar. You may need to sign in.HTTP Error 403 (Forbidden): The server refused to fulfill the request.

I'll bet! (lazy) I agree with Rick. Use DriverPacks. We've already done all the hard work for you.

XPlode is an advance user setup utility. Homepage: http://www.voidfx.com/FX/XPlode:Information I've never used it. But the option for it was built into DPS BASE a long time ago.

No. You cannot decompile (or "xplode" as you say it) the DPS Finisher. The source code is compiled (or built) into an .exe file. Besides, you cannot alter the source code to change the time that it executes. It doesn't work like that. We've all tried to explain it to you several times. To change the time that the Finisher runs, you have to "call" it from different files using different methods. You must call the Finisher from either GUIRunOnce or RunOnceEx using the methods built into the DPS BASE. ANY other method is NOT supported and will probably fail (unless you know exactly what you are doing, which you don't).

That's actually fairly accurate (in a full-load) environment. That's just a ridiculous amount of power draw. Any more power and our PCs will have to have CABLE instead of WIRES.

They won't work on Win7. http://support.amd.com/us/gpudownload/windows/Legacy/Pages/radeonaiw_vista32.aspx?type=2.4.1&product=2.4.1.3.13〈=English

I haven't tried any of the other themes except for green, but the wifi tray icon bug is still there. With "Excellent" signal strength, the "5 empty bars" icon is displayed. If I take the notebook away from the router, the icon changes to 4/5 bars then 3/5 bars. Once back in the same room as the router I get the 0/5 bars icon. :| I'm sure we went over all this before, but I don't think it was ever resolve. LOL, I'm running out of things to be nit-picky about!

Bad news I'm afraid. I just tested 3.0.0.16 on XP Pro. If svcpack.inf is left uncompressed, xptsp successfully patches it, and then deletes it. After the integration is complete, neither svcpack.in_ or svcpack.inf exist in %source%\i386\

Just tried v3.0.0.15 on XP Pro SP3 VLK. I had decompressed svcpack.inf and discarded the compressed file so only svcpack.inf remained. Patching WBEMOC.INF Patching SVCPACK.INF MSG: Unable to open "SVCPACK.INF" for editing! Copying theme package to i386 folder... Adding Optional Components Patching Completed in 0 seconds. Looks like it's looking for the compressed .in_ file instead of the decompressed .inf. *Edit Confirmed. CAB compressing the .inf back to .in_ allows it to be patched. You should probably add a subroutine to check for the existence of either svcpack.inf or svcpack.in_ and act accordingly.

I also recently had a 1TB WD green drive fail in my server. They replaced it with the same model # but it had an OEM label on it. This is the first WD drive that I've personally had fail on me. Their support was easy and fast though.

The original humble bundle was just added to Steam last week. Very nice. I had signed up for the first bundle last year, I'll probably go for the second as well. It's a great way to support the developers directly.

Happy Birthday!

Ouch. Bad luck. It could have been a bad sample from the factory. It may quiet down once the bearings break-in. Does it make the same whine when it's powered on in your hand?

That should be more than OK. To isolate it from the case and eliminate any resonant hum, you could use "blue tack", the soft sticky rubbery stuff you use to stick posters to walls. Works great to put between the drives and their mounts and don't tighten the screws down tight.

Their test sample might have been a fluke. But if there's little difference in cost, go with the faster one. You would see a difference in speed in menu refresh and no media stuttering. Both would be vastly superior to your existing drive in terms of quietness. I'm looking into buying their new A-210 for myself. Maybe as a birthday present to myself.