SUPPORTED OPERATING SYSTEMS

The following operating systems are supported by HFSLIP64:

• Windows XP Professional x64 Edition
• Windows Server 2003 Standard x64 Edition
• Windows Server 2003 Enterprise x64 Edition
• Windows Server 2003 Datacenter x64 Edition

The Service Pack level is expected to be Service Pack 2, so you should either slipstream it manually or let HFSLIP64 take care of it.

These are theoretically supported as well but it hasn't been verified yet:

• Windows Server 2003 Enterprise Edition for Itanium-based Systems
• Windows Server 2003 Datacenter Edition for Itanium-based Systems

FOLDER STRUCTURE

Folders created automatically by HFSLIP64 if they don't exist:

• HF = for Service Pack installer, Type 1 hotfixes, MUAuth.cab and muweb_site.cab
• HFSVCPACK = for switchless executables, *.reg, *.inf and *.cmd files to be run at T-13
• HFSVCPACK_SW1 = for Type 1 hotfixes and *.msi installers to be run at T-13
• HFTOOLS = for plugins and answer file
• SOURCE = for the CD source (copy entire source to be on the safe side)

If the SOURCE folder had to be created, HFSLIP64 will exit right after that, allowing you to populate all folders as necessary.

Folders which are supported but need to be created manually:

• HF\NOREG = for Type 1 hotfixes that don't need registration (may also be placed in HF)
• HFSVCPACK_SW2 = for Type 2 hotfixes to be run at T-13 (not tested)
• HFFIRSTLOGON = for switchless executables, *.reg, *.inf and *.cmd files to be run at first logon
• HFFIRSTLOGON_SW1 = for Type 1 hotfixes and *.msi installers to be run at first logon
• REPLACE = for files and folders that need to be copied into the new source after everything is slipstreamed

INSTALLATION ORDER (T-13 & FIRST LOGON)

Order in which included T-13 applications are installed:

1. HFSVCPACK\*.exe [silent executables]
2. HFSVCPACK_SW1\*.msi [/qn /norestart ALLUSERS=1]
3. HFSVCPACK\*.reg
4. HFSVCPACK\*.inf
5. HFSVCPACK_SW1\*.exe [/quiet /norestart]
6. HFSVCPACK_SW2\*.exe [/Q:A /R:N]
7. HFSVCPACK\*.cmd

Order in which included first logon applications are installed:

1. HFFIRSTLOGON\*.exe [silent executables]
2. HFFIRSTLOGON_SW1\*.msi [/qb /norestart ALLUSERS=1]
3. HFFIRSTLOGON_SW1\*.exe [/passive /norestart]
4. HFFIRSTLOGON\*.reg
5. HFFIRSTLOGON\*.inf
6. HFFIRSTLOGON\*.cmd

DIRECTX9 EXTRAS

Extra DirectX9 binaries for gaming and content development which are supported on x64 editions of Windows XP and Server 2003 are slipstreamed.  To have these, simply place the latest DirectX9 redistributable in the HF folder.

The first time a particular DirectX9 redistributable is handled, HFSLIP64 will automatically create custom cab packages in the HF folder.  The next time HFSLIP64 is run, the custom cab packages will be used instead.  If custom DX9 packages already exist in the HF folder, the DirectX9 redistributable is only extracted if there is a version mismatch (eg, when you place a newer DirectX9 redistributable in the HF folder).  Also, in the event that custom cab packages are detected and a newer redistributable exists as well, only the newer packages inside the redistributable are processed in order to reduce the HFSLIP64 run time.

OPTIONAL ANSWER FILE

HFSLIP64 supports the use of an optional answer file named HFANSWER.INI in the HFTOOLS folder to change the way HFSLIP64 works.  The HFANSWER.INI package you can download from the HFSLIP64 Downloads page contains an HFANSWER.INI with the default settings used by HFSLIP64, so you only need it if you want to make changes.

HFSLIP64 PLUGINS

There are a few plugins available for HFSLIP64 which can be downloaded from the HFSLIP64 Downloads page.  Download the ones you wish to use and extract them into the HFTOOLS folder.

MISCELLANEOUS INFO

A Service Pack is always slipstreamed directly into the input source in the SOURCE folder.  This source is then copied into a folder named SOURCESS where all updates are slipstreamed into.

A Service Pack is not slipstreamed if the input source is already at that SP level or at a newer SP level.

By default, HFSLIP64 merges DRIVER.CAB with any existing SP*.CAB file in the SOURCESS folder.  This will reduce the size of your source, but will also take a few minutes to complete.  At the beginning of the HFSLIP64 run, you are asked whether you're OK with that or whether you prefer HFSLIP64 to just create an additional CAB file for updated driver binaries coming from hotfixes.

DRIVER32.CAB (containing 32-bit drivers) is always repacked unless no updates exist for it.

If you want to slipstream Service Pack 2 but your host OS is Windows 2000, extract update.exe and updspapi.dll from the 32-bit version of SP2 for Server 2003 and place these files in HFTOOLS.