Tomcat76

Check the latest release, TAiN. This one allows the HFEXPERT\WIN folder (and its subfolders) to act as some kind of "backdoor" to slip in files that are removed with HFCLEANUP. Consider this basic rule: Do not place files in HFEXPERT\WIN that you are removing with HFCLEANUP. If you add them anyway, those files will not be removed. This makes more sense to me and it makes HFSLIP more flexible. It's easier to add in a few files in HFEXPERT\WIN than it is to edit removal filesets. It can also help with debugging problematic filesets.

HFSLIP supports slipstreaming DX9 into WinXP SP1. Do you have the same problem when not nLiting the SOURCESS folder? Be sure to include the cd tag file in the SOURCE folder.

Use one of the test builds; I corrected an issue with LegitCheckControl.dll on WinXP SP2.

TAiN... The solution depends on what the actual problem is. 1) The four files in question reside in the CD's I386 folder but they are not copied over into SYSTEM32 2) The four files in question do not reside in the CD's I386 folder or the version is wrong/different I can figure that out myself if you send me your txtsetup.sif file... @Camarade_Tux No. When merging driver.cab with the SP cab, the reference to the SP cab was not removed from DOSNET.INF. It may have affected people who install from a floppy but I'm not sure of that. Either way, that's corrected now.

Uh... the DX9 package contains files specifically for 9x, files specifically for 2K, files specifically for XP and files specifically for 2K3. It's not all "common". I hate to bring you this sad news, but... Linux was at that stage 15 years ago....

Oh, but HFSLIP has experience with that. Try 60314b. If it's what I think it is, that version should work around the problem.

What file? Nobody's been talking about the FIX folder here...

OK. I'll release a new test version soon. 1) No; it's only needed for the Windows Update Catalog site 2) Try this link: http://www.microsoft.com/downloads/details...50-ee01256aaa92 I suppose it needs to go in the HF folder.

It's a miracle HashTab, Open Subfolder, Office Update Engine, StartupMonitor and Attributes Context Menu even install right. A new test release that fixes the handling of these addons is ready to be posted but I'm waiting for the wga1.inf results first. You do know that HFSLIP handles the original Office Update CAB, right? It's called opuc3.cab and can be placed in the HFCABS folder.

Download the attached file. When booted into the "faulty" system, right-click the file and select "Install". Then go to Windows Update.

Can I have links for "ConAtrib", "HashTab", "OUEngine", "OpenSub" and "SrtupMon"? There's something wrong with them.

I think... At least, that's how it used to be done for the two 2K rollup files in the past.

Was the latter also the case with 60310 or is that something you don't know given the path problems you were having before? Does it still happen if you only include hotfixes in the HF folder?

OK... Use a clean, non-unattended and non-SP4 source. Create a folder called HFSPACK and place the SP4 executable in it. Place the necessary IE6 cabs in the HFCABS folder and place the update rollup (Windows2000-KB891861-v2-x86-DEU.EXE) in the HF folder. Run HFSLIP. You are the first to report this problem so I want to be sure that the problem doesn't lie elsewhere.

dziubek... Forget the regsvr32 thing, but do this: start a system that you just made (one that has the LegitCheckControl problem), open up the Windows Registry and search for the following string: 17492023-C23A-453E-A040-C7C580BBF700 I just need to know if you get results or not (yes or no).

If you're using the FIX folder, then rename the DLL to WGA1.DL_. (This is not a test as opposed to my question in another thread.) MUWEB... Yes I know. That was an issue that's been debated for several months now ever since MS started beta testing this service. Noone seems to know how to do it.

The one with all the *.CPL files in their original addon packs (including CDImageGUI).

Uh... I don't see how combining everything would save that much of space. You'd still need to have all sources and you'd still have all final sourcess. $OEM$ folders don't need to be on your hard drive while running HFSLIP and the hotfixes don't take up much space (unless you're dealing with XPSP1). Time is certainly not saved because HFSLIP would still need to be run on all sources. Currently, I got 2K PRO SP4 English, 2K PRO SP4 Dutch, 2K PRO SP4 French, XP PRO SP1a English, XP PRO SP2 English, XP PRO SP2 Dutch, 2K3 SVR Gold English, 2K3 SVR SP1 English, 2K3 ADV SP1 English, 2K3 DCS SP1 English and 2K3 WEB SP1 English plus all hotfixes residing in their own HFSLIP folder on a 20gig partition. It's enough for a basic multiboot. If you want to add in additional programs, I'd say 30 or at the most 40GB would suffice, even when you ditch the $OEM$ folder and use an alternate method (like SVCPACK), and then use CDIMAGE.EXE with the -o switch to copy duplicates to the ISO only once.

The *.cpl and *.cpi files should be placed in HFEXPERT\WIN\SYSTEM32, yes. I wrote that in my previous message but then I edited it. @murvun: I also thought they need to have the same name, but one of the packages is renaming CDImagex.cpi to CDImageGUI.cpi and leaves CDImage.cpl alone. The final names are not the same. @dziubek: Can you PM me your HFSLIPWU.INF and TXTSETUP.SIF file?

LegitCheckControl.dll... For testing, open a Run box (in a freshly installed system), type the following and press Enter: regsvr32 LegitCheckControl.dll *.CPL files... I see some of those need to be renamed. In that case, you should use the HFAAO method. CDImageGUI... I'll need to check that out. I don't see anything special about that package.

Oh no... There we go again...

It's not that complicated, actually, for HFSLIP. SVCPACK types: ,SetupHotfixesToRun, filename.exe /q These are only useful to create if a switch is needed to install the file. If no switch is needed, it's easier to just plunk the installation file in the HFSVCPACK folder. SYSOC types for which the destination directories are supported by Windows setup: PackageName=ocgen.dll,OcEntry,install.inf,HIDE,7 install.inf = 1,,,,,,,20,0,0 program.exe = 1,,,,,,,2,0,0 The supported folders are WINNT/WINDOWS and their subfolders. In the example here, "20" stands for INF and "2" for SYSTEM32. You can check TXTSETUP.SIF for the supported directories and their corresponding numbers. SYSOC types for which not all destination directories are supported by Windows setup: PackageName=ocgen.dll,OcEntry,install.inf,HIDE,7 install.inf = 1,,,,,,,20,0,0 program.exe = 1,,,,,,_x,,3,3 It is assumed that the installation INF contains the necessary information to copy over the files. If you just want to copy files (into folders supported by TXTSETUP.SIF): filename.exe = 1,,,,,,,2,0,0 program2.exe = 1,,,,,,,2,0,0 These are useless to make because you can use the HFEXPERT folder for this. If a WINNT/WINDOWS subfolder is not supported by TXTSETUP.SIF or it needs to be created, you can do it like this: [txtsetup_dirs] 250 = VIDEOS 251 = SYSTEM32\CRASH All the above information applies to the file "ENTRIES_whatever.INI" which you include in the CAB package. Remaining things to know: - how to compose an INF that's to be installed from SYSOC.INF - how to create the CAB file - (for experts) how to create a CAB file inside the CAB file which contains all or most files (eg: the WMP10 addon pack)

Hi glc650 These are obsolete: ENU_Q832483_MDAC_x86.EXE js56nen.exe Windows2000-KB329115-x86-ENU.exe (part of SP4) WindowsMedia-Q828026-x86-ENU.exe These are missing: IE6.0sp1-KB833989-x86-ENU.exe (security) IE6.0sp1-KB887797-Windows-2000-XP-x86-ENU.exe (optional) scripten.exe Windows2000-KB908506-x86-ENU.EXE (critical/optional) Windows2000-KB912475-x86-ENU.EXE (optional)

The other linked page has a sticky near the top which is a tutorial. Here's a direct link: http://www.ryanvm.net/forum/viewtopic.php?t=1290 Just one thing... Many people seem to advocate the use of "100" in txtsetup.sif. Its necessity is a hoax. 100 stands for "files on a Windows XP or Windows 2003 CD that was patched with a service pack" 2 stands for "files on a Windows 2000 CD that was patched with a service pack" or "files that are on the 2nd Windows XP CD" 1 stands for "files on any Windows CD, patched or unpatched with a service pack" So to make an addon pack intercompatible, use "1". HFSLIP automatically changes "100" to "1", but I just wanted to mention this.

NTPRINT.INF is a Unicode file so all HFSLIP can do (provided something actually needs to be done) is add lines to it. You can try the attached script. It supposes there's an existing SOURCESS folder so run HFSLIP first. It adds lines to NTPRINT.INF containing the file names which were originally in the SP cab file and tells Windows setup that the files in question reside in the driver.cab file now.