HFEXPERT. The alternative $OEM$ folder... on steroids.

TommyP and I have misgivings about including this in official documentation because this requires very careful reading. Don't make us regret publishing this... we thought about just leaving it for people to discover. Please, be smart.

If this is over your head, don't do it.

The folder isn't made by HFSLIP -- make it manually and put it inside the HFSLIP directory. HFSLIP will copy all files in the folders below, and SLIPSTREAM them into the source.
You must use non-compressed binaries. The files you put here will OVERWRITE any other same-named files.
If you put a windows protected file here, setup may fail telling you it's not signed. You have been warned!

The folder structure:

Codecs: This will install codecs right with the source. Why bother with bloated downloads when you can do it yourself.
You need to create a folder called CODECS inside the HFEXPERT folder and fill it up. Put all your video/audio codecs (the dll/ocx/ax/exe files) and along with an installation INF(s). All files will end up in the system32 folder, except for the installation INF. The files put there will overwrite any existing files in the i386 folder (slipstreamed). The installation inf should be only to make registry changes, not register dlls/ax/ocx. HFSLIP takes care of registering the files. It will only register dll/ax/ocx files, registering all it can. HFSLIP will loop through all the installation INFs you put there, doing whatever is called out in the defaultinstall part of the INF. Refer to http://www.msfn.org/board/index.php?showtopic=57649 for details on slipstreaming codecs.

WIN: The folders and files placed in the WIN folder will be slipstreamed inside the SOURCESS\I386 folder and will overwrite any slipstreamed files in the SOURCESS. This will not create any additional folders in the SOURCESS\I386 folder. During installation, the files are only copied over to the WINDOWS or WINNT folder in the same folder structure you have in created in HFEXPERT\WIN. Note: You can create additional folders inside WIN.
KNOWN ISSUES: You will get copy errors if (1) files have 4 characters extensions and (2) files have spaces in the names. Also note that if your file names have the same files that are part of the original installation i386 folder, you will run into problems (in other words, you are adding files, not trying to replace them here).

HIVEINSTALL: INF files get placed here. They are installed via the TXTSETUP.SIF [HiveInfs.Fresh] portion of installation. Please note that the portion of the INF that gets installed is the SETUP section.

APPREPLACEMENT: Create a folder in HFEXPERT called APPREPLACEMENT. Place a renamed EXE file that is part of Windows.
Example 1 - SysInternal's Process Explorer, Renamed to TSKMGR.EXE
Example 2 - Media Player Classic, renamed to MPLAYER2.EXE

Special TOOLS needed:

Place the following files into the HFTOOLS folder:
1) modifype.exe

HFCLEANUP. The alternative SOURCESS reducer.

This section is UNSUPPORTED and YOUR MILEAGE MAY VARY using this. It is geared for people who want to reduce their own SOURCESS. It’s also geared for people who like crafting their own reduction files. Perhaps someone will craft additional reduction files and post them for us all to use.

1. Create a folder called HFCLEANUP next to your HFSLIP_xxxx.CMD file.
2. Download a cleanup ZIP file.

Cleanup Set for Windows 2000, XP, and 2003 (Internet Explorer removal files are included)
If using Windows 2000, please download and use this add-on too
Dialup Reducer, MS Office Reducer, Network Driver Reducer, Quicklaunch Fix

If using 2003, please put my SETUPAPI.DL_ and SAKIT.IN_ into your FIX folder

3. Extract the contents to the HFCLEANUP folder.
4. Read the !README.TXT file (located in the HFCLEANUP directory) for details on the fileset.
5. Delete any RDV/REM/RIN files that you do not want to run. T
he more Z prefixes in a name, the harder it reduces.
6. Read the detailed instructions on how to create additional reduction files in the readme.txt file that you just extracted.
For more info, go to http://www.msfn.org/board/index.php?showtopic=65537

Run HFSLIP. HFSLIP will parse each file one at a time. If you are running with FDV's fileset, you do not need to replace DLLs for setup. If you are NOT using FDV's fileset, you NEED to replace DLLs for setup, otherwise setup will complain. (If you have to ask which ones, you shouldn't be doing this...)
Please note that the cleanup portion happens at the end of the HFSLIP process. So if you replaced a file using HFEXPERT/APPREPLACEMENT and your
HFCLEANUP fileset calls to delete the file, your APPREPLACEMENT file will be deleted. You have been warned.