Tomcat76

I think you don't understand the purpose of HFSLIP. HFSLIP slipstreams hotfixes into your installation source. This means that files on the CD are replaced with the newer versions that came from inside the hotfix executables. If your intention is to install hotfixes at a later point during Windows setup, use the HFSVCPACK_SW1 and HFSVCPACK_SW2 folders (for Type 1 and Type 2 hotfixes respecitively) instead, but that's not what HFSLIP was really made for.

Are you using HFSLIP?

HFSLIP supports slipstreaming of the DirectX 9.0c core for Windows 2000 SP4, Windows XP SP1, Windows Server 2003 SP1 and Windows Server 2003 SP2. HFSLIP supports slipstreaming of DirectX 9.0c extras for Windows 2000 SP4, Windows XP SP1, Windows XP SP2, Windows Server 2003 SP1 and Windows Server 2003 SP2. directx_9c_redist.exe = DirectX 9.0c core only directx_mmmyyyy_redist.exe = DirectX 9.0c core + extras If your source OS is Windows XP SP2, HFSLIP will extract directx_9c_redist.exe but it won't do anything with the files because slipstreaming the DirectX 9.0c core is not supported for Windows XP SP2. It is not supported for XP SP2 because XP SP2 already contains the DirectX 9.0c core.

If anyone has slipstreamed WMP9 into Win2K with HFSLIP and streaming of online media files fails, please try one of these fixes (save as a .REG file on the target system and double-click to execute it): All users: REGEDIT4 [HKEY_USERS\.DEFAULT\Software\Microsoft\MediaPlayer\Preferences] "ForceOnline"=dword:00000001 Current user only: REGEDIT4 [HKEY_CURRENT_USER\Software\Microsoft\MediaPlayer\Preferences] "ForceOnline"=dword:00000001 This may be implemented into the next version of HFSLIP.

Yeah, four new strings.I wish there was a tool which can convert the strings in localized versions which got lost in the ANSI export back to Unicode LE. I already tried a few programs but none could do it.

My thought too. If no newer version is slipstreamed, it's either a corrupt source, a corrupt file structure on your hard drive or even a bad drive. Run chkdsk X: /r on the drive that holds your HFSLIP folder (X: should be replaced with the correct drive letter). Then remove the SOURCE folder and copy it from CD again.

Are you sure you aren't confusing the extraction dialog box with the installation dialog box? If the DX9 executable would actually start installation, you should've observed the same problem with Type 2 hotfixes as HFSLIP uses the switches for Type 2 hotfixes to extract the redist too.What is the name of the executable and how big is it? Which are the SDK updates? I compared the versions of each file to see which DX9 binaries for 2K3 are newer/needed for 2K3SP1/SP2 in the revised code in these test releases. HFSLIP doesn't do it, but I'd like to know that for myself. Just never had the time.

Jeez... Are you still on SP1? That doesn't look too right. Should be fixed in 1.7.1rc1. BTW... That's been there since support for the BITS update was added; it isn't new to 1.7.0.

Can you first test that this solves the IE desktop icon problem? To get BRANDING.CAB, you need to download, install and run IEAK7. Configure things the way you want them, and when it's finished copy the BRANDING.CAB created by IEAK7 into the HFSLIP\HFCABS folder.

HFSLIP does not support slipstreaming of the DirectX 9.0c core (which is what directx_9c_redist.exe includes) into XPSP2 because XPSP2 already has DirectX 9.0c. If you want to have the extras for gaming and content development, use the latest redist instead (currently from November 2007).

If you're using WINNT.SIF, remove the IE branding options. They are incompatible with IE7. Use IEAK7 to create a custom BRANDING.CAB and place that file in the HFCABS folder.

These are new binaries. If you don't want them, why are you slipstreaming them in the first place? HFSLIPWU.INF, the file which adds the RunOnceEx entries to install the HFSLPxxx.INF files, is called from SYSOC.INF somewhere in the middle of Windows setup. At the next event RunOnceEx is supposed to kick in (somewhere around T-13), those RunOnceEx entries should be executed. The new HFSLIP.CMD, which removes the HFSLIP folder, can only run if the system is out of setup (after the final reboot).Theoretically, it is impossible that the HFSLIP folder gets removed before the HFSLPxxx.INF files are executed... unless nLite makes Windows identify itself as being "no longer in setup". HFSLIP.CMD checks the value of SystemSetupInProgress under the HKEY_LOCAL_MACHINE\SYSTEM\Setup registry key for that. Only if the value is "0" (dword:00000000) will it perform the installs intended to be run at first GUI logon. That code is not based on what the latest test release writes. The stuff in HFSLIPDX.INF and HFSLIPDY.INF need to be run at different stages; HFSLIP makes use of the fact that RunOnceEx and RunOnce occur at different times.

The thing is that HFSLIP 1.7.0 removes the HFSLIP folder at first GUI logon provided that no serious error occurs during Windows setup which causes the system to reboot internally and consequently run the RunOnce(Ex) at too early a stage. The latest test release, on the other hand, additionally checks (through HFSLIP.CMD) if the system is still in setup or not before executing the first GUI logon installs (and the command to remove the HFSLIP folder). If the system is still in setup, HFSLIP.CMD won't execute the intended commands and will instead add a new RunOnce entry into the registry to call itself again at the next RunOnce event. Even if the system reboots 5 times internally, HFSLIP.CMD created by the latest test release should be able to pick that up nicely. Only if the system is out of setup will the first GUI logon installs be performed (and the HFSLIP folder be removed). Concerning your other question... I suggest you read the new information on the Important things to know page on the HFSLIP web site. It links to a utility which creates a list of new binaries slipstreamed by HFSLIP.

.NET 2.0 SP1 is a standalone package (it replaces dotnetfx2.exe and the previous cumulative update). I haven't found out how to install these yet. The ADDEPLOY=1 command no longer does the trick.

I don't know what other info I might need. Try the latest test release; it delays the installation of first logon installs until the system is out of setup, and the temporary %SYSTEMROOT%\HFSLIP folder is only deleted after that.

Can you zip the new HFSLIP.LOG and attach it to your next post? My hotfix list shows the updates that are needed to keep Windows Update happy. The extra ones you have are either replaced by newer ones, not intended for the SP level in your source, or just not supported by HFSLIP at all. I don't mind checking a few, but 82 is a lot...

Down again...

I don't know of a hotfix that updates imagehlp.dll. For starters, I would remove the ampersand in the name of your HFSLIP folder because it is causing trouble. It has a specific function in DOS. From the Basic How-to page on the HFSLIP site: "It is advised, for best results, that your HFSLIP folder path does not contain spaces or any exotic characters; for example: D:\HFSLIP." You can use underscores if you like; I use them too. Second, remove all the updates that don't appear on my XPSP2 hotfix list for HFSLIP. You should first try to get a working system with what HFSLIP was designed for. You can experiment later. Concerning what Super-Magician wrote... It isn't important anymore since HFSLIP 1.7.0, but if you dumped all DX9-related CAB files in the HFCABS folder using previous versions of HFSLIP (such as 1.6.2) you will definitely get a broken build.

Thanks. It should be fixed now in version 5...

It's been down twice as were the other sites on the same server. TAiN is looking into it.

What if you change that setting from a .REG file in the HFGUIRUNONCE subfolder? Thanks for the heads up on the .NET updates.

This is actually the first time I hear about it and I couldn't find anything on it on the HFSLIP forum (unless you confused your problem with the broken Show Desktop icon). Have you tried editing SOURCESS\I386\ieuinit.in_ after HFSLIP has finished? It contains a string for "Launch Internet Explorer Browser" but I'm not sure Windows uses that file to create the icon. That's because of WindowsXP-KB925876-x86-ENU.exe. It adds a post-setup command to the global user RunOnce registry key so it's executed the first time a new user signs in.

Should be supported with version 71119a

They are all supported in HF, HF\BASIC and HF\NOREG except KB944110. This hotfix contains a new internal subfolder (WM11) which isn't covered by HFSLIP yet. The version for WMP10 isn't supported either because they changed the naming standard of the internal subfolder from WMP10L (which HFSLIP supports) to WM10L. They dropped the P. I'll add support for it in the next test release.

OK. If you have Office 2007 installed again, try the attached file on the newly installed system (not the system you ran HFSLIP on). Extract the INF file to your desktop, close all instances of MSIE, right-click the INF file and select Install. It's probably not necessary but reboot just in case. Then try Office Update again. HFSLIPWU.INF (created by HFSLIP) adds a key to the registry to allow the authorization cab of Office 2003 if IE7 is slipstreamed/installed. The attached INF file does the same but for Office 2007. opuc_o2k7.zip