TommyP's

Universal 2K/XP/2K3 IE6/DX9/WMP/Hotfix Slipstreamer

Advanced features

1. HFSVCPACK - REG, INF and CMD files
2. FIX - Replace existing files in the source
3. HFEXPERT - Codecs, WIN files, replace apps & inject hives
4. FDVFILES - Remove Internet Explorer from Windows 2000
5. HFCLEANUP - Reduce your source

This is for advanced users only.

Most of these features require a file called modifyPE.exe.  Download the modpe081.zip package and extract modifyPE.exe into the HFTOOLS folder.

1. HFSVCPACK - REG, INF and CMD files

This doesn't need much info.  Your custom .REG, .INF and .CMD files should go in the HFSVCPACK folder.  They will be executed at T-13, so take into account that not everything might work.  Windows 2000, for example, won't correctly apply a "CascadeControlPanel" setting.  Use the [DefaultInstall] section for the INF files.

2. FIX - Replace existing files in the source

The files in this folder are copied into the new source near the end of the HFSLIP run.  Since no other processing is done to them, make sure that they are tagged as "valid system files" (if needed), and that they are in the correct format.  If the file to be overwritten is a compressed file, the new file should be compressed as well; this can be done with MAKECAB.  The FIX folder is most commonly used for bootup files, WINNT.SIF and custom SFC*.DL_ files.  Only files in the I386 folder are replaced.

3. HFEXPERT - Codecs, WIN files, replace apps & inject hives

This folder needs to be created manually inside the HFSLIP folder and can contain the following subfolders: WIN, CODECS, APPREPLACEMENT, DRIVERCAB, HIVEINSTALL and PROGRAMFILES.

HFEXPERT\WIN should contain files to be placed in the WINNT/WINDOWS directory or its subdirectories.  If you would like to add files into SYSTEM32, create the HFEXPERT\WIN\SYSTEM32 folder structure and put those files in there.  New entries are created in TXTSETUP.SIF and DOSNET.INF so only use this for NEW binaries.

Your standalone video and audio codec files (dll/ocx/ax/exe) as well as INF files to configure the codecs can be placed in the HFEXPERT\CODECS folder.  As is the case with the HFEXPERT\WIN folder, these files are referenced to in TXTSETUP.SIF and DOSNET.INF, but in addition Windows setup is being instructed to register the codec files.  As a result, you don't need to register your codec files from your INF files; these should therefore be used for general registry changes only, such as registration and association of file types.  For these INFs, the [DefaultInstall] section is used.

Some codec resources:

HFEXPERT\APPREPLACEMENT is intended for files that need to replace existing files in the source.  The difference with the FIX folder is that these files should be left uncompressed and that modifyPE is run on them.  This could for example be used to replace mplayer2.exe with Media Player Classic and TASKMGR.EXE with Sysinternal's Process Explorer.  Don't forget to give these files a name that already exists in the source (mplayer2.exe and TASKMGR.EXE respectively for the examples), otherwise nothing will be replaced.

In HFEXPERT\DRIVERCAB, you can place your custom driver binaries (in extracted format).  HFSLIP will replace existing files in DRIVER.CAB with the files you provide.  Note that this only works with merging options A, B and C.  Files in SP*.CAB and newer driver binaries that come with hotfixes are also replaced as your files are added after Microsoft's driver packages have been merged.

Your hive files go in HFEXPERT\HIVEINSTALL.  These INFs are injected as custom hives via TXTSETUP.SIF's [HiveInfs.Fresh], meaning that you should use the [SETUP] section of the INF file.  During Windows setup, they are executed right at the end of textmode file copy (before the first reboot).

HFEXPERT\PROGRAMFILES, a new feature, can be considered an $OEM$\$Progs alternative.  Create the folder PROGRAMFILES inside HFEXPERT and place your subfolders and files in it.  That's it.  HFSLIP duplicates the older structure in SOURCESS\I386\PFILES.  All files except CAB files are compressed, but please note that they retain their original name for convenience.  Long file/folder names are supported as well as file/folder names with spaces.  During Windows setup, the files are installed directly into their intended location via an INF file (HFSLIPPF.INF) which is called from SYSOC.INF.

4. FDVFILES - Remove Internet Explorer from Windows 2000

FDV came up with a fileset to remove Internet Explorer from Windows 2000.  Not possible?  Well... it is.  Grab his file set (available in several languages) and extract it into the FDVFILES folder.  All information can be found on FDV's Remove IE from Windows 2000 at install page.  Note: while that page provides different integration methods, it is advised you use the FDVFILES folder when using HFSLIP.

5. HFCLEANUP - Reduce your source

This feature is UNSUPPORTED and YOUR MILEAGE MAY VARY, so don't complain if your applications don't work.  It is geared for people who want to reduce their installation source and understand the impact this may have.

Create the HFCLEANUP folder inside the HFSLIP folder.  Then download the cleanup package(s) you want:

Extract the content of the package(s) into the HFCLEANUP folder.  If using Windows 2003, also download FDV's setupapi.dl_ and sakit.in_ directly into the FIX folder.

Read the !README.TXT file in the HFCLEANUP directory for details on the fileset and on how to create additional reduction files if needed.  More information can be obtained here.

Delete any RDV/REM/RIN files that you do not want to run.  The more Z prefixes in a name, the harder it reduces.  Also, if you are NOT using FDV's fileset, you NEED to replace setup DLLs, otherwise Windows setup will complain.

You are free to create your own reduction files or filesets and to post them on the HFSLIP support forum for general use once you're sure they are working.