[Tomcat76]

HFSLIP64 is hereby abandoned. No further revisions will be made to this program.



Download HFSLIP64 v1.1.5

Changelog v1.1.5 Release 14-Feb-2010
- Fixed a little file swap when slipstreaming IE8 and some other hotfixes.

Changelog v1.1.4 Release 19-Nov-2009
- tommyp picked up the slack until the triumphant return of tomcat76. The script needed some maintance due to some newer wmp and wmp codec hotfixes. As anyone in the know knows, msft repacks wmp hotfixes different each time, this results in complications that need to be hardcoded. Nothing like being consistant. Way to go msft!



Changelog v1.1.3
- fixed a problem causing HFSVCPACK_SW1\*.exe, HFSVCPACK_SW2\*.exe and HFSVCPACK\*.cmd files not to copy over

Home page
Complete changelog
Dynamic update list for Windows XP SP2 x64
Advanced features

****************************************************************************

Fix for bug with SP2 x64 version of mplayer2.inf (thanks to redxii for pointing this out)

The [Strings] section header in the SP2 x64 version of mplayer2.inf is attached to the end of the last line of the previous section (DestinationDirs for the WOW binaries). This causes npds.zip to be copied into %ProgramFiles%\Windows Media Player[Strings] instead of %ProgramFiles%\Windows Media Player. Additionally, the [Strings] section is ignored because of this but that doesn't have an impact because the mplayer2.inf sections that are used by Windows setup don't use any strings.

1) Download SP2MPlayer2Fix_ENU.zip or SP2MPlayer2Fix_JPN.zip (depending on the SP2 language)
2) Create a folder named REPLACE inside the HFSLIP64 working folder
3) Inside REPLACE, create another folder named AMD64
4) Extract MPLAYER2.IN_ from the package you downloaded into REPLACE\AMD64 (not the zip file!)
5) Run HFSLIP64

****************************************************************************

Example of folder setup for XP Pro x64
The HF\NOREG subfolder is for hotfixes for which the registry doesn't need to be updated. You are not required to put hotfixes in HF\NOREG; they will work in HF just the same. The list only shows which updates are OK to be placed in HF\NOREG.

HF\NOREG\IE7-WindowsServer2003.WindowsXP-KB938127-x64-ENU.exe [IE7 ONLY]
HF\NOREG\Windows-KB890830-x64-V1.40.exe
HF\NOREG\WindowsMedia11-KB929399-v2-x64-INTL.exe [WMP11 ONLY]
HF\NOREG\WindowsMedia11-KB936782-x64-ENU.exe [WMP11 ONLY]
HF\NOREG\WindowsMedia11-KB939683-x64-ENU.exe [WMP11 ONLY]
HF\NOREG\WindowsMedia11-KB941569-x64-ENU.exe [WMP11 ONLY]
HF\NOREG\WindowsMedia6-KB925398-v2-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB924667-v2-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB925902-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB927891-v5-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB929123-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB930178-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB931261-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB932168-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB932596-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB935839-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB935840-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB936021-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB936357-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB936782-x64-ENU.exe [WMP DEFAULT ONLY]
HF\NOREG\WindowsServer2003.WindowsXP-KB938127-x64-ENU.exe [IE6 ONLY]
HF\NOREG\WindowsServer2003.WindowsXP-KB941202-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB941568-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB941569-x64-ENU.exe [WMP DEFAULT ONLY]
HF\NOREG\WindowsServer2003.WindowsXP-KB941644-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB941693-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB943055-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB943485-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB944338-x64-ENU.exe [IE6 ONLY]
HF\NOREG\WindowsServer2003.WindowsXP-KB944653-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB945553-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB946026-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB948590-x64-ENU.exe
HF\IE7-WindowsServer2003.WindowsXP-KB947864-x64-ENU.exe [IE7 ONLY]
HF\IE7-WindowsServer2003-x64-enu.exe [IE7 ONLY]
HF\msxml4-KB936181-enu.exe
HF\msxml6-KB933579-enu-amd64.exe
HF\MUAuth.cab
HF\muweb_site.cab
HF\Windows-en-US-KB943729-x64_b9de932f286c62685fed238462a38d734b36ff18.exe
HF\WindowsRightsManagementServicesSP2-KB917275-Client-ENU-X64.exe
HF\WindowsServer2003.WindowsXP-KB914961-SP2-x64-ENU.exe
HF\WindowsServer2003.WindowsXP-KB925876-v2-x64-ENU.exe
HF\WindowsServer2003.WindowsXP-KB933729-x64-ENU.exe
HF\WindowsServer2003.WindowsXP-KB943460-x64-ENU.exe
HF\WindowsServer2003.WindowsXP-KB947864-x64-ENU.exe [IE6 ONLY]
HF\WindowsServer2003.WindowsXP-KB948881-x64-ENU.exe
HF\WindowsUpdateAgent30-x64.exe
HF\wmp11-windowsxp-x64-enu.exe [WMP11 ONLY]

HFTOOLS\cWnd.exe
HFTOOLS\HFANSWER.INI
HFTOOLS\HFSLIP64_POST_DelObsBin.cmd
HFTOOLS\HFSLIP64_PRE_SWFlash9.cab
HFTOOLS\HFSLIP64_PRE_SWFlash9.cmd
HFTOOLS\HFSLIP64_PRE_TZ4.cab
HFTOOLS\HFSLIP64_PRE_TZ4.cmd


Example of folder setup for Server 2003 x64 Editions
The HF\NOREG subfolder is for hotfixes for which the registry doesn't need to be updated. You are not required to put hotfixes in HF\NOREG; they will work in HF just the same. The list only shows which updates are OK to be placed in HF\NOREG.

HF\NOREG\IE7-WindowsServer2003.WindowsXP-KB938127-x64-ENU.exe [IE7 ONLY]
HF\NOREG\Windows-KB890830-x64-V1.40.exe
HF\NOREG\WindowsMedia6-KB925398-v2-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB924667-v2-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB925902-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB926122-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB927891-v5-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB929123-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB930178-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB932168-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB932596-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB935839-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB935840-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB936021-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB936357-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB936782-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB938127-x64-ENU.exe [IE6 ONLY]
HF\NOREG\WindowsServer2003.WindowsXP-KB941202-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB941568-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB941569-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB941644-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB941693-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB943055-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB943485-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB944338-x64-ENU.exe [IE6 ONLY]
HF\NOREG\WindowsServer2003.WindowsXP-KB945553-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB944653-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB946026-x64-ENU.exe
HF\NOREG\WindowsServer2003.WindowsXP-KB948590-x64-ENU.exe
HF\IE7-WindowsServer2003.WindowsXP-KB947864-x64-ENU.exe [IE7 ONLY]
HF\IE7-WindowsServer2003-x64-enu.exe [IE7 ONLY]
HF\msxml4-KB936181-enu.exe
HF\msxml6-KB933579-enu-amd64.exe
HF\MUAuth.cab
HF\muweb_site.cab
HF\WindowsRightsManagementServicesSP2-KB917275-Client-ENU-X64.exe
HF\WindowsServer2003.WindowsXP-KB914961-SP2-x64-ENU.exe
HF\WindowsServer2003.WindowsXP-KB925876-v2-x64-ENU.exe
HF\WindowsServer2003.WindowsXP-KB933729-x64-ENU.exe
HF\WindowsServer2003.WindowsXP-KB943460-x64-ENU.exe
HF\WindowsServer2003.WindowsXP-KB947864-x64-ENU.exe [IE6 ONLY]
HF\WindowsServer2003.WindowsXP-KB948496-x64-ENU.exe
HF\WindowsServer2003.WindowsXP-KB948881-x64-ENU.exe
HF\WindowsUpdateAgent30-x64.exe

HFTOOLS\cWnd.exe
HFTOOLS\HFANSWER.INI
HFTOOLS\HFSLIP64_POST_DelObsBin.cmd
HFTOOLS\HFSLIP64_PRE_SWFlash9.cab
HFTOOLS\HFSLIP64_PRE_SWFlash9.cmd
HFTOOLS\HFSLIP64_PRE_TZ4.cab
HFTOOLS\HFSLIP64_PRE_TZ4.cmd

This post has been edited by tommyp: 18 February 2010 - 06:33 PM
Reason for edit: update for new release

[sabregreen]

I will start testing tomorrow i have a few machines I can test on both 2003 x64 and xp x64

[Tomcat76]

OK, thanks.

Just an FYI... Please slipstream SP2 because there are still problems with how completely new 32-bit binaries are handled (Windows setup is only instructed to copy them into the correct location, and not yet to rename them from "wfilename.ext" to "filename.ext").

I hope I'll find a solution for this that is both clean and works quick.

[sabregreen]

You want me to use hfslip to slipstream sp2 or do it manually ?

[Tomcat76]

It's your call... The script is capable of slipstreaming SP2.

But it's no longer important; 80316c should fix the problem with new 32-bit binaries.

[tain]

This is great to see! Thanks, Tomcat76! I'm not in a position to test lately but I do intend to jump on this bandwagon the first chance I get.

[sabregreen]

For the REPLACE folder, the winnt.sif file has to be placed into the AMD64 folder...I see folders arent created when you run hfslip for the first time. Just a FYI if ya didnt know.

[Tomcat76]

I just tested it again in a blank folder, and the HF, HFTOOLS and SOURCE folders are created automatically on first run.

BTW... The first beta is out.

[sabregreen]

Sorry...i get the same folders as well. I meant REPLACE, etc. I just seen in the code you don't call them. My first run through worked, no updates. Adding all updates tomorrow to see what doesnt work.

[Tomcat76]

Oops... The script wasn't copying subdirectories of REPLACE. Should be fixed now.

[sabregreen]

How about creating a list of updates ? I will post the list I have tomorrow for xp x64.

[Tomcat76]

It's already in the first post.

[sabregreen]

I just seen that right after i posted. Lol what an dummy. I assumed nothing was there. Will test tomorrow those and 2003. Is there any part specific you need help with or feedback ? IE7 ? HFCABs ?

This post has been edited by sabregreen: 18 March 2008 - 08:03 PM

[Tomcat76]

You actually can't test those because they're blocked.

Try with the list shown in the first post.
You can maybe do a run with files in the HFSVCPACK folders too.

Are there any hotfixes in your list that aren't mentioned in the first post?

[sabregreen]

Why do most of the hotfixes have to be put into NOREG subfolder ? Just curious.

[sabregreen]

I get an error using windows update complaining about invalid authenticode. Then when I hit install and try to scan for updates, It says windows update error. Same updates listed in your list.

[Martin H]

sabregreen, on Mar 19 2008, 06:26 PM, said:

Why do most of the hotfixes have to be put into NOREG subfolder ?

They don't have to be, as Tomcat76's list is just an example...

The 'HF\NOREG' and 'HF\BASIC' subfolders are an optional advanced feature for Type 1 updates.

They are meant for updates which dosen't need any post-setup commands or reg-entries from their INF files(HF\NOREG), or who dosen't need any post-setup commands and only an identifier reg-key from their INF files(HF\BASIC).

HFSLIP has hardcoded support for some of the updates which needs more reg-entries, than just the identifier reg-key...

More info here :
http://www.msfn.org/board/Experimenting-fe...er-t100448.html

[Tomcat76]

sabregreen, on Mar 19 2008, 08:26 PM, said:

I get an error using windows update complaining about invalid authenticode. Then when I hit install and try to scan for updates, It says windows update error. Same updates listed in your list.

Try the latest test release. Please show me the HFSLIP.LOG if you still have the problem.

[sabregreen]

Still same error. Also, my Program Files folder doesnt show up in the start menu.

Attached File(s)

•  HFSLIP.zip (1011bytes)
  Number of downloads: 44

[Tomcat76]

I'm getting the problem with Microsoft Update too, but haven't been able to find out why yet. It could be because I'm not nuking AU.INF as with HFSLIP for 32-bit Windowses.

In the mean time, though, you can get around it by logging off and logging back in. That does the trick for me.

I suppose you mean "Programs" folder. I have it, using both the standard and the classic Start Menu.