Tomcat76

I can't really speak for Windows Messenger 5.1; I've only done tests with MSN/Live Messenger. Windows Messenger 5.1 should upgrade Windows Messenger 4.7 (unlike MSN/Live Messenger) so something could be going wrong there. The install switches may prompt the installer to uninstall Windows Messenger 4.7 and stop there. What happens if you let Windows setup install WM 4.7, and when setup has completed, you execute messenger.msi manually? Also, as far as I know, there's a version for Windows 2000 and a version for Windows XP. Are you using the same installer?

No problem

Hi kateto I don't think this last run is a "vanilla" slipstream. The log reports: WARNING - Previously Patched Source Detected. This happens if the source was updated by HFSLIP or by nLite before. It's OK to have a service pack slipstreamed into the source (in a clean way) but nothing else. Did you re-use the new source that was created by a previous HFSLIP run?

Oops... well... modifype.exe doesn't seem to like quotes. I added them in case there were files with spaces in their name. Replace the code in the CMD with the updated code in my previous post. Make sure no files in TEST have spaces. I have never experienced copy errors with 7-zip SFX packages before, though.

HFSLIP64 is hereby abandoned. No further revisions will be made to this program. Download HFSLIP64 v1.1.5 Changelog v1.1.5 Release 14-Feb-2010 - Fixed a little file swap when slipstreaming IE8 and some other hotfixes. Changelog v1.1.4 Release 19-Nov-2009 - tommyp picked up the slack until the triumphant return of tomcat76. The script needed some maintance due to some newer wmp and wmp codec hotfixes. As anyone in the know knows, msft repacks wmp hotfixes different each time, this results in complications that need to be hardcoded. Nothing like being consistant. Way to go msft! Changelog v1.1.3 - fixed a problem causing HFSVCPACK_SW1\*.exe, HFSVCPACK_SW2\*.exe and HFSVCPACK\*.cmd files not to copy over Home page Complete changelog Dynamic update list for Windows XP SP2 x64 Advanced features **************************************************************************** Fix for bug with SP2 x64 version of mplayer2.inf (thanks to redxii for pointing this out) The [strings] section header in the SP2 x64 version of mplayer2.inf is attached to the end of the last line of the previous section (DestinationDirs for the WOW binaries). This causes npds.zip to be copied into %ProgramFiles%\Windows Media Player[strings] instead of %ProgramFiles%\Windows Media Player. Additionally, the [strings] section is ignored because of this but that doesn't have an impact because the mplayer2.inf sections that are used by Windows setup don't use any strings. 1) Download SP2MPlayer2Fix_ENU.zip or SP2MPlayer2Fix_JPN.zip (depending on the SP2 language) 2) Create a folder named REPLACE inside the HFSLIP64 working folder 3) Inside REPLACE, create another folder named AMD64 4) Extract MPLAYER2.IN_ from the package you downloaded into REPLACE\AMD64 (not the zip file!) 5) Run HFSLIP64 **************************************************************************** Example of folder setup for XP Pro x64 The HF\NOREG subfolder is for hotfixes for which the registry doesn't need to be updated. You are not required to put hotfixes in HF\NOREG; they will work in HF just the same. The list only shows which updates are OK to be placed in HF\NOREG. HF\NOREG\IE7-WindowsServer2003.WindowsXP-KB938127-x64-ENU.exe [iE7 ONLY] HF\NOREG\Windows-KB890830-x64-V1.40.exe HF\NOREG\WindowsMedia11-KB929399-v2-x64-INTL.exe [WMP11 ONLY] HF\NOREG\WindowsMedia11-KB936782-x64-ENU.exe [WMP11 ONLY] HF\NOREG\WindowsMedia11-KB939683-x64-ENU.exe [WMP11 ONLY] HF\NOREG\WindowsMedia11-KB941569-x64-ENU.exe [WMP11 ONLY] HF\NOREG\WindowsMedia6-KB925398-v2-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB924667-v2-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB925902-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB927891-v5-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB929123-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB930178-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB931261-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB932168-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB932596-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB935839-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB935840-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB936021-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB936357-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB936782-x64-ENU.exe [WMP DEFAULT ONLY] HF\NOREG\WindowsServer2003.WindowsXP-KB938127-x64-ENU.exe [iE6 ONLY] HF\NOREG\WindowsServer2003.WindowsXP-KB941202-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB941568-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB941569-x64-ENU.exe [WMP DEFAULT ONLY] HF\NOREG\WindowsServer2003.WindowsXP-KB941644-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB941693-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB943055-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB943485-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB944338-x64-ENU.exe [iE6 ONLY] HF\NOREG\WindowsServer2003.WindowsXP-KB944653-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB945553-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB946026-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB948590-x64-ENU.exe HF\IE7-WindowsServer2003.WindowsXP-KB947864-x64-ENU.exe [iE7 ONLY] HF\IE7-WindowsServer2003-x64-enu.exe [iE7 ONLY] HF\msxml4-KB936181-enu.exe HF\msxml6-KB933579-enu-amd64.exe HF\MUAuth.cab HF\muweb_site.cab HF\Windows-en-US-KB943729-x64_b9de932f286c62685fed238462a38d734b36ff18.exe HF\WindowsRightsManagementServicesSP2-KB917275-Client-ENU-X64.exe HF\WindowsServer2003.WindowsXP-KB914961-SP2-x64-ENU.exe HF\WindowsServer2003.WindowsXP-KB925876-v2-x64-ENU.exe HF\WindowsServer2003.WindowsXP-KB933729-x64-ENU.exe HF\WindowsServer2003.WindowsXP-KB943460-x64-ENU.exe HF\WindowsServer2003.WindowsXP-KB947864-x64-ENU.exe [iE6 ONLY] HF\WindowsServer2003.WindowsXP-KB948881-x64-ENU.exe HF\WindowsUpdateAgent30-x64.exe HF\wmp11-windowsxp-x64-enu.exe [WMP11 ONLY] HFTOOLS\cWnd.exe HFTOOLS\HFANSWER.INI HFTOOLS\HFSLIP64_POST_DelObsBin.cmd HFTOOLS\HFSLIP64_PRE_SWFlash9.cab HFTOOLS\HFSLIP64_PRE_SWFlash9.cmd HFTOOLS\HFSLIP64_PRE_TZ4.cab HFTOOLS\HFSLIP64_PRE_TZ4.cmd Example of folder setup for Server 2003 x64 Editions The HF\NOREG subfolder is for hotfixes for which the registry doesn't need to be updated. You are not required to put hotfixes in HF\NOREG; they will work in HF just the same. The list only shows which updates are OK to be placed in HF\NOREG. HF\NOREG\IE7-WindowsServer2003.WindowsXP-KB938127-x64-ENU.exe [iE7 ONLY] HF\NOREG\Windows-KB890830-x64-V1.40.exe HF\NOREG\WindowsMedia6-KB925398-v2-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB924667-v2-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB925902-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB926122-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB927891-v5-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB929123-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB930178-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB932168-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB932596-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB935839-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB935840-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB936021-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB936357-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB936782-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB938127-x64-ENU.exe [iE6 ONLY] HF\NOREG\WindowsServer2003.WindowsXP-KB941202-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB941568-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB941569-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB941644-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB941693-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB943055-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB943485-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB944338-x64-ENU.exe [iE6 ONLY] HF\NOREG\WindowsServer2003.WindowsXP-KB945553-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB944653-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB946026-x64-ENU.exe HF\NOREG\WindowsServer2003.WindowsXP-KB948590-x64-ENU.exe HF\IE7-WindowsServer2003.WindowsXP-KB947864-x64-ENU.exe [iE7 ONLY] HF\IE7-WindowsServer2003-x64-enu.exe [iE7 ONLY] HF\msxml4-KB936181-enu.exe HF\msxml6-KB933579-enu-amd64.exe HF\MUAuth.cab HF\muweb_site.cab HF\WindowsRightsManagementServicesSP2-KB917275-Client-ENU-X64.exe HF\WindowsServer2003.WindowsXP-KB914961-SP2-x64-ENU.exe HF\WindowsServer2003.WindowsXP-KB925876-v2-x64-ENU.exe HF\WindowsServer2003.WindowsXP-KB933729-x64-ENU.exe HF\WindowsServer2003.WindowsXP-KB943460-x64-ENU.exe HF\WindowsServer2003.WindowsXP-KB947864-x64-ENU.exe [iE6 ONLY] HF\WindowsServer2003.WindowsXP-KB948496-x64-ENU.exe HF\WindowsServer2003.WindowsXP-KB948881-x64-ENU.exe HF\WindowsUpdateAgent30-x64.exe HFTOOLS\cWnd.exe HFTOOLS\HFANSWER.INI HFTOOLS\HFSLIP64_POST_DelObsBin.cmd HFTOOLS\HFSLIP64_PRE_SWFlash9.cab HFTOOLS\HFSLIP64_PRE_SWFlash9.cmd HFTOOLS\HFSLIP64_PRE_TZ4.cab HFTOOLS\HFSLIP64_PRE_TZ4.cmd

I'm about to start a new thread. Don't use 80315aa.

Slightly updated version. Only run on test systems! hfslip-x64-80315aa.zip

If that's the message you're getting, it means the headers of the executables are borked. You'll need to run modifyPE.exe on them once. In your main HFSLIP folder, create a new folder named TEST and copy the problematic executables in there. Then save the following in a .cmd file in the main HFSLIP folder and run it: @ECHO OFF FOR /F "DELIMS=" %%I IN ('DIR/B TEST\*.exe') DO ( HFTOOLS\modifype.exe TEST\%%I -c ) PAUSE Copy them back into the HFGUIRUNONCE folder and run HFSLIP again. FYI... Long file names are OK, but remove any spaces; files with spaces in their name will copy over fine but will fail to install. This applies to .msi and .exe files in HFGUIRUNONCE. EDIT: Updated code.

To clarify... SSIP1.TXT is not supposed to be on the CD or handled by Windows setup. It is created only when HFSLPGUI.CMD is executed (and deleted when the temporary HFSLIP folder is removed). I'm only saying this in case you were looking for it on the CD or in the SOURCESS folder created by HFSLIP.

Here's the last version I worked on if you like; it's based off an old version of HFSLIP. But I should warn you that I never actually ran it so there may be problems. The updated code should cover Windows Update Agent 3.0 x64 and most Type 1 hotfixes. @cluberti: QFE binaries.

I didn't remove the previous version yet. The versions before that are archived on the server; I should make a web page for those some day.

Hey MacGyver... No coding was done in that direction for quite a while and no date is scheduled to pick it up again either. But, if time permits, I'll give it a shot again.

Up until some time ago, HFSLIP used the same headers for Type 1 and Type 2 hotfixes. I changed that for Type 1 hotfixes for Windows XP and Windows Server 2003 because they usually follow the "Product.Add.Reg" section naming; actually, the only exception I can think of right now for those OS's is the Windows Installer update. Of course every INF file in every update was tested. I wanted to do the same thing for Windows 2000 after that but never got around to it.

I really don't know. When did this start happening? Any particular version of HFSLIP?

Thanks. Link added.

You are missing an update that is crucial when slipstreaming WMP11. Please see http://hfslip.org/wmp11.html.

Thanks Rogon3, but that update contains the files from March 2007. Windows Update wants the files from April 2007. Please open C:\WINDOWS\WindowsUpdate.log and search for the LAST occurance of "KB905474"; I think you copied the link of the FIRST occurance. I'll update the info on the HFSLIP site to make that clear.

This is getting really difficult. The only thing I can imagine going on is that the temporary WINDOWS\HFSLIP folder is removed or doesn't exist prior to execution of HFSLPGUI.CMD. This causes the "CD %SYSTEMROOT%\HFSLIP" (change directory) command to fail. The system should then be in a directory in which Windows (or Windows setup) doesn't allow you to write to, which causes the registry export to fail (and that's the error message you see). Are you installing over a network? In a Virtual Machine? Does this also happen when installing from CD?

Basic slipstreamer for WKS and SRV (SP6a, rollup, Windows Installer 2.0 and select hotfixes). Download (pick latest) Read _readme.txt as well as the _support*.txt file that applies to your edition (Terminal Server not supported yet). This project may merge with HFSLIP.

To be honest, I'm clueless. The files exist in SOURCESS\I386. TXTSETUP.SIF instructs Windows setup to copy them over during TXTMODE setup. You don't get any copy error messages during TXTMODE setup. You even removed the command that removes the temporary HFSLIP folder. Files don't just vanish... I did notice one thing though, re-reading this entire thread. Maybe it's just coincidence, but you mentioned "C:\WINDOWS\HFSLIP\IHFSLP151.INF" twice. HFSLIP doesn't create "IHFSLP151.INF"; it creates "HFSLP151.INF" (without the "I" in the front).

I'm sorry; I meant HFSLPGUI.CMD from SOURCESS\I386.

Nothing bad will happen if you slipstream it into Win2K Pro. All it does is add one value into the registry that doesn't have any effect on Pro. The only "problem" is that HFSLIP 1.7.3 and earlier versions added a registry value for all Win2K versions which basically told Windows Update that RIS is installed on the machine. To avoid being presented with other RIS hotfixes on Win2K Pro in the future, you can simply remove the RemInst value under "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SetUp\OC Manager\Subcomponents". You can also remove the value that's added by KB926121 if you like but that's not necessary: Remove the Masters value under "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TFTPD\Parameters". You can actually remove the entire TFTPD key because it isn't created by installing 2K Pro normally.

Can you ZIP the HFSLIP.LOG created by HFSLIP and post it here? Thanks.

net.exe and net1.exe are command line tools so if you don't run other CMD scripts (that call net*.exe) that explains why this only happened with HFSLIP. Personally, I would've preferred to fix the problem. Do you have an idea which program might have changed net1.exe? I also did some checking and it appears that some viruses are known to use those names or even replace the files.

WINSRV.DLL -> SOURCESS\I386 UNIPROC\WINSRV.DLL -> SOURCESS\I386\UNIPROC MS are usually kind enough to keep the directory structure of the installation CD.