Download HFSLIP64 v1.1.3

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

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

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.

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

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.

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.

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.

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.

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.

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

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

It's already in the first post.

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 ?

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?

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

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.

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

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

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

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.

Disregard the no programs folder showing up. Resolution messed it up. Log off and log back on didnt fix the windows update error. The first message that comes up says invalid parameter authenticode. Want a screen shot ?

Yeah, I'd like a screenshot.

I don't know why exactly, but my problem with Microsoft Update seems to be fixed.

XP x64 + updates shown in first post == MU doesn't work after first GUI logon

XP x64 + updates shown in first post + time zone plugin == MU doesn't work after first GUI logon

XP x64 + updates shown in first post + time zone plugin + SWFLASH plugin + no GDIDetectionTool edit == MU works

I have tried twice (full format and reinstall) with the latest setup and everything works for me now. Don't know what triggered it.

Oh yeah... Is that an original source or was it patched before? I'm only asking because of the "INFO" message in HFSLIP.LOG. Also, have you tried without WINNT.SIF and CMDOW.EXE?

I think I've found the problem with Windows Update. For some reason, the registration of SysWOW64\wuweb.dll from AU.INF is failing. I'm going to hardcode it in HFSLIPOC.INF.

OK. This release (80322b) should be OK to work with. Server 2003 is quite a PITB...

I have tested both Windows Update and Microsoft Update with XP SP2 and Server 2003 SP2 and everything comes out clean (considering what's supported).

The real bug hunting can begin...

Whats the problem with 2003 ? I'm rerunning xp x64 now.

None that I can see. It was just "more stubborn" compared to XP

After rerunning xp x64 with the release just before the one you just posted, a lot of things are missing like internet explorer. The folder is in program files but its empty. Same for media player. Im going to re do it just to make sure nothing was corrupt. This is also on a different machine using VMware 6.0.

I never had the problem you're just mentioning and I'm also using VMware 6.0.

Make sure you got the latest plugins (if you're using any).

Did you see any error messages during Windows setup?

Does C:\WINDOWS\setuperr.log show anything post installation?

I just changed. I was using vmware 6.0 now using 6.3 to see if it makes a difference. Then I'm goign to try the new the hfslip version.

I forgot to slipstream service pack 2 is one problem. I moved machines, I was working at home this weekend. Even after slipstreaming service pack 2, its still giving me lots of errors in setuperr.log with .exe files.

a small suggestion. don't slipstream sp2 every time, just slipstream it once and use that as your source, will save a lot of time and you obviously won't be forgetting to slipstream it again

Oh i know. I forgot to copy the source I was using at work so that I could use it at home. For whatever reason, the source im using at home is acting weird. I just checksums and everything. The exact same.

Attached is my setuperr.log. There has to be something else wrong.

Removed winnt.sif, plugins, and changed in hfanswer.ini installrc=1 to installrc=. I'm rerunning now.

Must be something in my winnt.sif file that it doesnt like. I removed that and it installs properly.

I don't know much about WINNT.SIF myself, but you can always attach it here if you like (after blanking out sensitive data). Maybe there is something that catches my eye.

BTW... The INSTALLRC variable has no effect as HFSLIP64 doesn't have code that handles installation of the Recovery Console. See the default HFANSWER.INI that's linked from the first post in this thread for a list of variables that you can predefine.

Here it is. Let me know. Definitely my winnt.sif file though.

The only thing that looks suspicious to me is the AutomaticUpdates variable. What happens if you comment it out?

Same thing. I'm commenting out oempreinstall and oemskipwelcome and rerunning.

Running out of ideas here. I don't know what it is.

There's always the possibility that one or more hotfixes are incompatible with WINNT.SIF, just like you can no longer use the branding options if you slipstream IE7 into XP 32-bit.

Well... That's about all I can say on WINNT.SIF. I'm sorry.

I'm still testing one by one.

Removed automaticupdates and the driverpolicy parameters. No errors in setuperr.log

Well... It isn't the AutomaticUpdates setting (at least, that's what you said earlier).

But the DriverSigningPolicy variable could be a problem now that I think about it.
HFSLIP has always set Driver Signing to "Ignore" at T-13 via a registry edit (so actually you don't need to do that) but I once tried to have it injected into the registry through an INF file that is installed from TXTSETUP.SIF (at the end of txtmode copy). When I did that, I got all sorts of error messages during Windows setup. So I think Windows setup can't handle "tampering" (as Microsoft calls it) with the Driver Signing Policy setting at such an early stage if hotfixes are slipstreamed. It seems to be OK at T-13.

Not only that, but the NonDriverSigning value isn't used in anything but Win2K - it's ignored in XP and 2003 sysprep processing, so that might well cause problems too.

Here is a new error im getting. This is the most recent version hfslip using plugins since I fixed my error.

OK... I can see why that's happening. HFSLIP64 sets the value to "21" in the beginning, and then HFANSWER.INI is polled but the default HFANSWER.INI I had online (v1 and v2) blanks it out again. Please set the value to 21 (or any value between 10 and 21) in HFANSWER.INI or grab v3 of the default HFANSWER.INI.

I'm in the process of improving the code that handles DRIVER.CAB and SPX.CAB a bit. I'll also try to find a way to work around the problem you're having should the user have manually entered an invalid value.

Just ran. No problems at all. So, can't use DriverSigningPolicy = "Ignore". Trying 2003 now.

Everything is working thus far with 1.0.0 rc. Is WMP11 not far down the road ? I know this isnt specific to hfslip, but what about the .net maker for x64 ? I was thinking about looking at it.