7yler

Nice one. Thanks Guys, it works great. I'm using WPI.EXE, and it works like a charm. Cheers.

@Strel I just done a test with no RESTRICTED HOTFIXES, just the basic patches, and it wont install on Win2003. When I extracted the files, and run the MSI files from 20/30/35 I get following error.

Just tested with WPI.EXE and the same problem, CDROM not Defined. Checking the log, both WPIPATH and ROOT get the correct drive, just not CDROM. %WPIPATH%=D:\APPS\Default.WPI\7.7.0 %ROOT%=D:\APPS\Default.WPI %CDROM%= Will continue to use 7.1.1 for now. Cheers 7yler WPI_Log_2009.10.03_22.32.22.txt

Thanks Kel, its my little home project I've been playing with to keep myself amused. WPI gets called from RunOnceEx. I 'm happy to continue to using 7.1.1 for now, but it would be nice to start using the latest versions. I have been aware of this since release 7.2 but have been lazy in chasing it up. EDIT: Thank Kel, i will give the EXE a shot and let you know

Hi Kel, I have included a image of my folder structure.

@Strel I'm was running SNM post install (not T-13), and it was 2003 (showing KB951847), XP was ok. I tried SNM 20090922 this time and I'm having problems with it not installing at all (I am using the RESTRICTED HOTFIXES), so I cant get the logs to you at the moment. I'm currently really busy, so I will retry later in the week when I get the chance. EDIT: Just done a quick test on 2003 (XP is ok), and it looks like 20SP2/30SP3/35SP1 are not being installed at all, possibly RESTRICTED HOTFIXES causing the problem. Maybe a RegTweak is causing WU to think it needs KB951847. Later in the week, I will try WITHOUT any RESTRICTED HOTFIXES. By the way SNM complains if KB971595/KB972251 are used.

I been using SNM for a long time and its a great tool, thanks for you hard work. I'm currently using SNM 20090913 and it works great, no problems on XP, but Win2003 is asking for KB951847. Thanks for any help

I've been using WPI 7.1.1 for a long time with no problems on WinXP, if I upgrade to WPI 7.7, I have a problem were %CDROM% is not being defined. It may be caused by the way I have my folders structured, but I would prefer not to change it. I have included log files for both 7.1.1 and 7.7 versions. Thanks for any help WPI_Log_7.1.1.txt WPI_Log_7.7.0.txt

Copy the following script, and use it at RunOnceEx or GuiRunOnce. This will do what you want at the end of the build. Includes x64 script as well (AMD64) which you can remove if only doing a x32 build. Not sure about coping at the start of the build. Hope this helps. Cheers @ECHO OFF :: **** Copy, Compress and Set Install Files to %WinDir% FOR /F "tokens=3" %%I IN ('REG QUERY HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup /v SourcePath') DO SET SourcePath=%%I MD "%WinDir%\i386" COMPACT /C /F /I /Q "%WinDir%\i386" XCOPY /V /E /I /Q /H /Y "%SourcePath%i386" "%WinDir%\i386" IF DEFINED ProgramFiles(x86) ( MD "%WinDir%\AMD64" COMPACT /C /F /I /Q "%WinDir%\AMD64" XCOPY /V /E /I /Q /H /Y "%SourcePath%AMD64" "%WinDir%\AMD64" ) REG ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup" /F /T REG_SZ /V SourcePath /D %WinDir%\ REG ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup" /F /T REG_SZ /V ServicePackSourcePath /D %WinDir%\

Glad to be able to help in some small way. I've gained a lot from looking at the HFSLIP scripts, with alot more still to learn. So very happy that i can contribute something. I've had problems with START in the past were the following happerns: START /WAIT "%~dp0SETUP.EXE" <-- does not work correctly START "Install" /WAIT "%~dp0SETUP.EXE" <-- Works fine Is it possible that START "%~dp0SETUP.EXE" is seeing "%~dp0SETUP.EXE" as the "title" Therefore START "HFSLIP" "%~dp0SETUP.EXE" may work ... Keep up the great work.

Corrent, "SourcePath" is the full path to installation source. I've been using Mutliboot and it does point to the folder not the root. So for D:\PRO\i386 or D:\ADV\i386, "SourcePath" would be D:\PRO or D:\ADV. At work we use Network installs and "SourcePath" points to the UNC Path. Here's another Script I use if i what to copy SourceFile to the local drive. @ECHO OFF :: **** Copy, Compress and Set Install Files to %WinDir% FOR /F "tokens=3" %%I IN ('REG QUERY HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup /v SourcePath') DO SET SourcePath=%%I MD "%WinDir%\i386" COMPACT /C /F /I /Q "%WinDir%\i386" XCOPY /V /E /I /Q /H /Y "%SourcePath%i386" "%WinDir%\i386" REG ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup" /F /T REG_SZ /V SourcePath /D %WinDir%\ REG ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup" /F /T REG_SZ /V ServicePackSourcePath /D %WinDir%\

This command should do what your after. :: **** Command Prompt Here REG ADD "HKCR\Directory\shell\Command Prompt Here\Command" /f /t REG_SZ /ve /d "cmd.exe /k cd %%1"

For the Recovery Console you could try this @ECHO OFF :: **** Install Windows Recovery Console FOR /F "tokens=3" %%I IN ('REG QUERY HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup /v SourcePath') DO SET SourcePath=%%I "%SourcePath%i386\WINNT32.EXE" /cmdcons /unattend Then your not dependant on a path. You need to make sure i386\WINNTUPG exists, and contains the following 4 files: CFGMGR32.DLL NETMAP.INF NETUPGRD.DLL SETUPAPI.DLL It should work at T-13 but havn't tested.

SP3 includes SP2. So remove SP2 and only include SP3 in HF folder.

Hi Tomcat, Can you add the fix for the Terminal Services Administrator Tools shortcuts (caused by the new mstsc.exe binary), like you did for HFSLIP64. Thanks 7yler