Tomcat76

Here is version 1.4.5. Here are previous test releases (mostly between 1.4.5 and 1.5.0). If the error occurs on different systems it can only be an HFSLIP problem, a corrupt source problem (which would imply your install CD is damaged) or corrupt hotfixes. Have you tried burning the hotfixes you have in your HF folder at work onto a CD and using those at home?

That explains the amount of warnings in WU1.TXT but it makes it difficult for me to locate the problem. Do you mind running HFSLIP with all hotfixes and then making a WU*.TXT file for that?

@Glowy Is Windows Update asking you to install KB933566 or is HFNETCHK? It appears to me that MS didn't implement support for IE7 in the XML file yet because KB933566 for IE7 does not contain browseui.dll at all. Windows Update usually does a better check than that. Your WU1.TXT file actually tells me your system is fine. @zedox Now that's weird. If I have to believe WU1.TXT, pretty much everything failed to slipstream. Do you have an $OEM$ folder with a bunch of files? Do you have enough hard disk space? Also try the latest test release.

The HFSLIP web site states that for the slipstreaming of IE7. Did you specify IE7SLIPSTREAM=1 in HFANSWER.INI?

Alright. Can both of you give me a WUx.TXT file? Here are the instructions.

This is an advanced feature and no active support will be provided for it. My dynamic hotfix lists won't be updated for it either. Using HFSLIP 1.6.0 or newer, you can reduce the amount of HFSLPxxx.INF files for Type 1 hotfixes in the new source as well as the amount of registry additions. There are two new folders for this: HF\BASIC and HF\NOREG. The main difference between them is that one identifier key is added into the registry for the hotfixes in HF\BASIC while no identifier key is added into the registry for hotfixes in HF\NOREG. However, for some hotfixes requiring more registry edits, hardcoded support has been added into HFSLIP if they are placed in either HF\BASIC or in HF\NOREG; this includes hotfixes with updates for shell32.dll (Win2K/XP), p2p*.dll (WinXP), usb*.sys (WinXP), msxml3.dll (Win2K/XP), kerberos.dll (Win2K), localspl.dll (Win2K), ipsec.sys (Win2K) and the Package Installer for WinXP. Also, an often recurring setting for "BufferPolicyReads" is added for Win2K. Note 1: only Type 1 hotfixes are supported in HF\BASIC and HF\NOREG. Note 2: this was only tested with Win2K+IE6+WMP9+MDAC281, WinXP SP2 and Win2K3 SP2, so the list below may need to be updated for other OS's and configurations. Note 3: the hotfix names in HF\BASIC are expected to be in this format: "<word>-KBxxxxxx-<word>*.exe" or "<word>-<word>-KBxxxxxx-*.exe". If the KB article number is not in the 2nd or 3rd position and is not preceded and followed by a hyphen, the identifying registry key will fail to be created. Here is some info that could be useful if you want to keep Windows Update happy. Most hotfixes don't require any identifier key(s), so everything goes in HF\NOREG except... To be placed in HF\BASIC (Windows Update wants the one registry key): Windows2000-KB926121-x86-ENU.EXE WindowsXP-KB885836-x86-ENU.exe To be placed in HF (requiring too much registry edits or containing post-setup commands): IE cumulative update (currently KB933566) IE7-WindowsXP-x86-enu.exe MDAC*.exe OE5.5*.exe OE6*.exe WindowsInstaller-KB893803-v2-x86.exe Windows-KB909520-v1.000-x86-ENU.exe Windows2000-KB842773-x86-ENU.EXE Windows2000-KB891861-v2-x86-ENU.EXE Windows2000-KB896358-x86-ENU.EXE Windows2000-KB900725-x86-ENU.EXE Windows2000-KB922582-x86-ENU.EXE Windows2000-KB928843-x86-ENU.EXE WindowsServer2003-KB923845-x86-ENU.exe WindowsServer2003-KB925876-v2-x86-ENU.exe WindowsServer2003-KB932716-x86-ENU.exe WindowsXP-KB896358-x86-ENU.exe WindowsXP-KB897338-v3-x86-ENU.exe WindowsXP-KB905474-ENU-x86-Standalone.exe WindowsXP-KB912817-v2-x86-ENU.exe WindowsXP-KB913580-x86-ENU.exe WindowsXP-KB914440-v12-x86-ENU.exe WindowsXP-KB922120-v5-x86-ENU.exe WindowsXP-KB922668-x86-ENU.exe (COM+ Rollup 14) WindowsXP-KB923845-x86-ENU.exe WindowsXP-KB925876-x86-ENU.exe WindowsXP-KB932716-x86-ENU.exe WindowsXP-KB933684-v2-x86-ENU.exe WindowsXP-KB935448-x86-ENU.exe Also to be placed in HF (not supported in HF\BASIC or HF\NOREG at all): Service Pack installers msxml* WindowsRightsManagement*.exe WindowsUpdateAgent30-x86.exe WMP9/10/11 installers and other Type 2 updates

SETUP.CMD is OK. You could maybe remove the entire CMDOW line and insert PAUSE above the EXIT command; then run SETUP.CMD. Maybe you'll see an error message that could be of use.

Well... I kind of figured it would return. I did one HFSLIP run and renamed the SOURCESS folder to SOURCESS_OLD. Then I renamed the root folder from "slippin" to "slippin-xp" and ran HFSLIP again. Both SOURCESS folders were identical. Then I renamed the root folder to "WIN-CD" (just like you had). New SOURCESS folder was also identical. That was about three hours ago. I now made an ISO from the latest SOURCESS folder and am installing from it. It's past "Installing drivers" and I didn't get an ASMS error. So I guess the hyphen wasn't the problem. I'm interested in what happens if you use the different hard drive.

I'll ask TommyP. It's his text

I don't think you'll see one any time soon. I want to fix the problems caused by having a hyphen in the HFSLIP folder path first.

It may be that the IE7 installer and/or the IE7 hotfix(es) are corrupt. Can you download them again? Also, I advise you do a run without WINNT.SIF.

Move the HFSLIP folder to C:\HFSLIP and run HFSLIP again. Does that help?

A bit obvious. You have file names with special characters. But I see you are also using file names which already exist in the source. Also, HFSLIP copies all files together into the I386 folder; this means that if you want cmdialog.vbx in both system32 and system32\dllcache it will not work. You should definitely delete these files (and don't use them in $OEM$ either): D:\Win2K\HFSlip\HFEXPERT\WIN\System32\dllcache\drmclien.dll D:\Win2K\HFSlip\HFEXPERT\WIN\System32\dllcache\gdiplus.dll D:\Win2K\HFSlip\HFEXPERT\WIN\System32\dllcache\wmasf.dll D:\Win2K\HFSlip\HFEXPERT\WIN\System32\dllcache\wmidx.dll D:\Win2K\HFSlip\HFEXPERT\WIN\System32\dllcache\wmvcore.dll The following can remain in HFEXPERT: D:\Win2K\HFSlip\HFEXPERT\WIN\deltree.exe D:\Win2K\HFSlip\HFEXPERT\WIN\lista.txt D:\Win2K\HFSlip\HFEXPERT\WIN\Notepad2.exe D:\Win2K\HFSlip\HFEXPERT\WIN\Notepad2.ini D:\Win2K\HFSlip\HFEXPERT\WIN\Notepad2.txt D:\Win2K\HFSlip\HFEXPERT\WIN\procexp.chm D:\Win2K\HFSlip\HFEXPERT\WIN\procexp.exe D:\Win2K\HFSlip\HFEXPERT\WIN\System\winaspi.dll D:\Win2K\HFSlip\HFEXPERT\WIN\System32\cmdialog.vbx D:\Win2K\HFSlip\HFEXPERT\WIN\System32\cmdow.exe D:\Win2K\HFSlip\HFEXPERT\WIN\System32\directx.cpl D:\Win2K\HFSlip\HFEXPERT\WIN\System32\msconfig.chm D:\Win2K\HFSlip\HFEXPERT\WIN\System32\msconfig.cpi D:\Win2K\HFSlip\HFEXPERT\WIN\System32\msconfig.cpl D:\Win2K\HFSlip\HFEXPERT\WIN\System32\msconfig.exe D:\Win2K\HFSlip\HFEXPERT\WIN\System32\msinet.ocx D:\Win2K\HFSlip\HFEXPERT\WIN\System32\msvcp71.dll D:\Win2K\HFSlip\HFEXPERT\WIN\System32\msvcr71.dll D:\Win2K\HFSlip\HFEXPERT\WIN\System32\regedit.cpi D:\Win2K\HFSlip\HFEXPERT\WIN\System32\regedit.cpl D:\Win2K\HFSlip\HFEXPERT\WIN\System32\themes.cpl D:\Win2K\HFSlip\HFEXPERT\WIN\System32\vbrun300.dll D:\Win2K\HFSlip\HFEXPERT\WIN\System32\wnaspi32.dll D:\Win2K\HFSlip\HFEXPERT\WIN\System32\drivers\aspi32.sys For everything else I advise you keep using $OEM$. There are several more files which you can embed through FIX but they will have to be renamed so they match the name of existing files in the source and be compressed. This is beyond my time and has nothing to do with HFSLIP.

It was always supported, being a basic Type 2 hotfix. Since HFSLIP 1.4.0, fontinst.exe and fontinst.inf are deleted because they aren't needed and I've been including the update myself ever since. It goes in the HF folder.

The modified IE7 installer that is placed in I386\SVCPACK is a quiet installer (using /quiet switch) as opposed to the first GUI logon installer (using /passive switch). I suppose you waited a while after double-clicking IE7_INST.EXE to make sure it's installed, and then rebooted. Can you expand IE7_INST.EXE and show what's inside SETUP.CMD?

I highly doubt this could have something to do with it, but can you try renaming "L:\WIN-CD" to "L:\WINCD"? Remove the hyphen.

Try test release 70627a. It should fix the ASMS problem that I saw in the ASMS.CAB report. For the rest I'm still in the dark...

@Oleg I'm using the latest version that's available for Windows XP. What is the difference with the one you attached?

Strange that you have compressed files in your original ASMS folder. There was a time when HFSLIP compressed new ASMS files in the new source but people were complaining that this caused Windows setup to fail so we stopped compressing ASMS files. I guess I could have HFSLIP compress updated ASMS files if they are compressed in the old source. Your DRVINDEX.INF files only show that there's something weird going on with your system. The following files are missing after merging the driver cabs: okml3320.gpd okml3321.gpd okml332x.gpd okml9res.dll I strongly suggest that you run a chkdsk /r on the partition from which you run HFSLIP as well as your system drive, and pay special attention to the names of the files which are "repaired". If any hotfixes are shown, they should be redownloaded. After that, also delete the SOURCE folder and copy your CD again.

No problems with the list. The last thing I can do is compare DRVINDEX.INF from SOURCE and SOURCESS since you mentioned that the problem went away if using DRIVERCOMP=D.

OK. I'm going to take a closer look at your list. Meanwhile, can you tell me if the following three files exist in your original source (SOURCE folder)? I386\ASMS\60\MSFT\WINDOWS\COMMON\CONTROLS\comctl32.dll I386\ASMS\60\MSFT\WINDOWS\COMMON\CONTROLS\controls.cat I386\ASMS\60\POLICY\60\COMCTL\comctl.cat

You are talking about the "IE7 installer" so I guess you didn't slipstream it this time. INSTALL.INS from BRANDING.CAB should be inside IE7_INST.EXE in that case. Can you verify that it is? BTW... Was this file created with IEAK7? I'm having a hard time believing that because of this: Wizard_Version=6.0.5730.1001 dotnet2.exe If placed in HFSVCPACK, it should've been copied into SOURCESS\I386\SVCPACK just like before. The only difference is that the current test release initiates the install from SVCPACK.INF (just like in the old days) instead of from HFSLIP.CMD. You know... I'm beginning to think that there are files that fail to copy on your computer. The first ASMS.CAB file you gave demonstrates a problem that's really puzzling me. But I can only say that for sure once you follow up on my last post in the other thread.

Uh... It was released yesterday when I mentioned it to you:

It is not in SOURCESS\I386\SVCPACK? HFSLIP doesn't copy BRANDING.CAB but its content. If it's not too big, can you attach it here?

A full source without KB923191. I think that's the most logical step...