Extras

  1. Remove obsolete source files
  2. HFANSWER.INI - HFSLIP answer file
  3. Application addons
  4. XPize

1. Remove obsolete source files (HFSLIP 1.3.0 and newer)

You can have HFSLIP delete source files that are not needed in the I386 folder.  You need to place the relevant removal file in the HFCLEANUP folder.  Removal files contain a list of file names and currently exist for Windows 2000 (2000SP4.EXT), Windows XP SP1 (XPSP1.EXT) and Windows XP SP2 (XPSP2.EXT).  The file for Windows Server 2003 (which wasn't made yet) should be named 2003SP0.EXT, 2003SP1.EXT or 2003SP2.EXT depending on the Service Pack level.  Removal files with the old name (DBLBIN*.EXT) are renamed automatically by HFSLIP.

If you want HFSLIP to remove the obsolete files, download the one file that is intended for your OS and extract the *.EXT file into the HFCLEANUP folder:

2. HFANSWER.INI - HFSLIP answer file (HFSLIP 1.6.2 and newer)

This is a brief explanation of the variables that HFSLIP 1.6.2 and up accept from the answer file.  The file should be called HFANSWER.INI and be placed in the HFTOOLS folder.  HFANSWER.zip contains a version with the defaults used by HFSLIP.

DRIVERCOMP

Possible values: A, B, C, D, E, F or no value (prompt)
Default: no value
This presets the compression memory to be used by HFSLIP and whether DRIVER.CAB should be updated.  Providing no value will display the standard prompt (which defaults to A if no value is entered at that prompt).

SBOOTPATH

Possible values: 1 (for single boot) or no value (prompt)
Default: no value
Setting the value to 1 tells HFSLIP that the CD boot path will be the default (no multiboot CD).

MBOOTPATH

Possible values: any value (the boot path) or no value (prompt)
Default: no value
Here you can preset the CD boot path when you're intending to make a multiboot CD.  Make sure to place a backslash at the end and don't quote the path (even if there are spaces).  SBOOTPATH doesn't need to be set in this case.

DELCATS

Possible values: 0 or 1
Default: no value
Set DELCATS to 0 if you want HFSLIP to silently keep .CAT files when modded SFC*.DLL files are detected.  Set it to 1 if you want HFSLIP to silently delete them.

DELCATS_OVERRIDE

Possible values: anything
Default: no value
When setting DELCATS=1 or answering "y" to the question if HFSLIP should remove CAT files, you can use this variable to override deleting of specific CAT files.  HFSLIP expects the value to be the name of the CAT file without its extension.  For example, the CAT file for KB933566 for IE7 is named KB933566-IE7.CAT, so you should enter DELCATS_OVERRIDE=KB933566-IE7
If you want to specify more than one CAT file, do it like so:
DELCATS_OVERRIDE=KB933566-IE7
DELCATS_OVERRIDE=KB935448

BACKUPSOURCE

Possible values: 1 (ask to make backup), 2 (force a silent backup), any other value or no value (don't make backup).
Default: no value
This is for the slipstreaming of service packs.  By default, HFSLIP will not make a backup of your SOURCE.  You can override this behavior by setting the BACKUPSOURCE variable.  Set it to 1 if you want HFSLIP to always ask to make a backup or set it to 2 if you want HFSLIP to make a backup without confirmation.  When a backup is made, HFSLIP will restore it automatically near the end of the HFSLIP run.

XPIZESW

Here go the silent install switches to be used if you want HFSLIP to let Windows setup install XPize via SVCPACK.  If you prefer to slipstream XPize into the Windows source, do not set this variable (or remove it entirely) and set the FORCEXPIZESLIP variable instead.  Refer to Chapter 4 of the XPize guide for the accepted switches.  Note that the current final version of HFSLIP detects whether you have modded SFC*.DLL files in FDVFILES, FIX or HFEXPERT\APPREPLACEMENT and will abort the operation if they aren't present; this won't be the case in the future.
Example: XPIZESW=/S
Example: XPIZESW=/S /norestore

FORCEXPIZESLIP

Possible values: 1 or no value
Default: no value
Set this variable to 1 to let HFSLIP know that you want to slipstream XPize into your Windows source.

ISONAME

Possible values: any value
Default: WINLite.ISO
This sets the name of the ISO file.

ISOTITLE

Possible values: any value
Default: HFSLIPCD
This sets the title of the ISO file (will be the name of the CD).

FORCECDIMAGE

Possible values: any value (force the use of CDIMAGE.EXE) or no value (only use CDIMAGE.EXE if MKISOFS.EXE doesn't exist)
Default: no value

CDIMGSW

Possible values: any value
Default: -h -j1 -m
The switches to be used with CDIMAGE.EXE.

MKISSW

Possible values: any value
Default: -relaxed-filenames -d -D -N -J -no-emul-boot -no-iso-translate -boot-load-size 4
The switches to be used with MKISOFS.EXE.

MAKENOISO

Possible values: 1 or any other value
Default: no value
Set this to 1 if you want to skip automatic ISO creation when the required files for that are present.  This has no effect when running HFSLIP in "MAKEISO mode".

OVERWRITEISO

By specifying OVERWRITEISO=1 you can tell HFSLIP to delete an existing ISO with the same name and to not add the date and time to the name of the new ISO.  Here are the four possible situations and the name of the resulting ISO:
- neither ISONAME nor OVERWRITEISO specified: HFSLIP+version_winver_date_time.iso (default)
- only OVERWRITEISO specified: HFSLIP+version_winver.iso
- only ISONAME specified: basename_date_time.iso
- both ISONAME and OVERWRITEISO specified: basename.iso
("basename" is what you specify as ISONAME without the extension)
Examples of output names (in the order shown above):
HFSLIP61111_2K_11112006_21h20m.iso
HFSLIP61111_2K.iso
MyISO_11112006_21h20m.iso
MyISO.iso

INSTALLRC

Possible values: 1 or any other value
Default: no value
Set this to 1 if you want HFSLIP to have Windows install the Recovery Console at T-13 without user interaction.  Be advised that this requires the complete and original WINNTUPG folder, else the installation will fail.

INCWMPCSKIN

Possible values: 1 or any other value
Default: no value
Set this to 1 if you want HFSLIP to check if Classic.wmz exists in the SOURCE, and, if it finds it, instruct Windows setup to copy it over.

INCALLSKINS

Possible values: 1 or any other value
Default: no value
Set this to 1 if you want HFSLIP to check if any abandoned WMP skins exist in the SOURCE, and, if it finds any, instruct Windows setup to copy them over.  This overrides the INCWMPCSKIN variable.

NOLOGCOPY

Possible values: 1 or any other value
Default: no value
Set this to 1 to prevent HFSLIP.LOG from being copied into the SOURCESS folder.

3. Application addons

Application addons are programs or utilities reworked into specially crafted CAB or 7z files which contain binaries to be placed in the Windows source, as well as a configuration file explaining what needs to be done with those files and how Windows setup should install them.  These addons were originally made for other slipstreaming and integration tools such as nLite, but support was added into HFSLIP as well.

HFSLIP handles three types: those which add files into I386 of which the installation is regulated from SYSOC.INF, those which place binaries into the SVCPACK folder, and those which replace existing files in the Windows source.

Create a folder called HFAAO inside the HFSLIP folder and place the addons (cab files) in there.
For addons in CAB format, you'll need to put Microsoft's EXTRACT.EXE in the HFTOOLS folder.  Windows XP users can find a copy of it on their installation CD in SUPPORT\TOOLS\SUPPORT.CAB.  Users of Windows 2000 and Windows 2003 can download it free of charge from Microsoft; after you extract the Cabsdk.exe package to a temporary folder, locate the relevant file in the BIN subfolder and copy it into HFSLIP's HFTOOLS folder.
For addons in 7z format, 7za.exe is needed.  You can acquire the latest 7za.exe from this page.  Download the file of which the description reads "7-Zip Command Line Version", extract 7za.exe from this package and place it in HFTOOLS.

For more information on this subject and downloads of pre-made application addons, refer to the following links:
http://www.msfn.org/board/index.php?showforum=132
http://www.ryanvm.net/forum/viewforum.php?f=7

4. XPize

XPize is a "GUI enhancer" for 32-bit versions of Windows XP and 2003 and even replaces icons and images that Microsoft hasn't "updated" to their new XP/2003 GUI yet.  It can also add a custom boot screen, logon screen and screensavers, and updates resources still stemming from older Windows versions.  Download either the Lite or the Full version from its home page, and place it in the HF folder.

HFSLIP allows you to either slipstream XPize into your Windows source or integrate it into the SVCPACK folder to be installed at T-13.  For SVCPACK integration, set the value of the XPIZESW variable in HFANSWER.INI to your desired installation switches.  To force slipstreaming, configure the FORCEXPIZESLIP variable instead.  Refer to the HFANSWER.INI section above for more information on these switches.