These versions are test builds and are pretty much stable. As usual, use them at your own risk.

A new final was released on November 9, 2009. If you were referred to this thread prior to November 9, please get the final from the main thread.

HFSLIP home page

*********************************************************
I hope tomcat76 doesn't mind me [tommyp] editting this post to add in a beta test build. See attachment for beta testing in preparation for the next final. Bugfixes:


There are no betas at the current time.



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

You can help by checking if the binary removal files (2000SP4.EXT, XPSP1.EXT and XPSP2.EXT) cover everything. Download dumpdupes.cmd and place it in the main HFSLIP folder (alongside the normal HFSLIP executable). Run this tool AFTER you ran HFSLIP (it namely requires a SOURCE and a SOURCESS folder to compare). If there are any duplicate binaries that can be removed, a file called EXCLUDE.TXT will be created. Let me know if it contains additional files to those that already exist in the current removal files. This program can be used to check Windows 2000, XP and 2003 sources.
Dumpdupes.cmd has one limitation: it only checks for duplicates in the current sources. This tool would have to be run again whenever new hotfixes arrive in order to ensure the list is up to date. I'll probably make another tool that outputs a full list of any driver binary that isn't supposed to be loose in I386 once I evaluated the pros and cons of both.[attachment=25420:hfslip_beta_Mar30.zip]

This post has been edited by tommyp: Nov 9 2009, 06:57 PM

Ok I have tested this again with option D selected. This log is the result.

IE7 does not seem to slipstream properly...

I can't run IE after setup, even after another restart. HFSLIP.log, setuperr.log and screenshot of error dialog box included in attachment.

Can you try without KB928089 update? I haven'it and IE7 is installed properly and without error. Except for a small issue in setuperr.log

This post has been edited by S3pHiroTh: Feb 20 2007, 06:58 AM

Okay, I didn't notice it is not in Tomcat's dynamic list.. Thanks!

@glentium
IE7-KB928089 is replaced by IE7-KB928090.

I want to bet money on it that this is the culprit:

IE7-KB928090-WindowsXP-x86-enu.exe
WindowsXP-KB928090-x86-ENU.exe

IE7-KB929969-WindowsXP-x86-enu.exe
WindowsXP-KB929969-x86-ENU.exe

Don't include hotfixes for both IE6 and IE7. Use those for IE7 when slipstreaming IE7.

@S3pHiroTh

The pngfilt.dll problem should be fixed with 70220a.

Concerning your other question... Wasn't this fixed? Try using merging option A, B or C again. New driver binaries are force-copied now...

Yes now the files before DRIVER.CAB are been added. Thanks Tomcat

Another question, yesterday Microsoft has released this update:

http://www.microsoft.com/downloads/details...;displaylang=en

Is it supported by hfslip or must recode something in the script?
I have slipstreamed the previous patch msxml6-KB927977-ita-x86.exe in DNF3.exe, should the script (the one for net packages) be updated?

This post has been edited by S3pHiroTh: Feb 20 2007, 09:32 AM

msxml6_x86.msi is supported by HFSLIP. It replaces msxml6-KB927977-xxx-x86.exe.

Unfortunately you'll have to rebuild DNF3.exe (assuming you made it with my tool). The problem is that the MSXML6 resource file contained in the MSXML6 SP1 package is OLDER than the one for MSXML6 "SP0". The MSXML6 binaries inside DNF3.exe are copied over if the ones in SYSTEM32 are older or non-existent, so the XML6 resource file will get downgraded to SP0 by mistake. You'll have to rename msxml6_x86.msi to msxml6.msi for the .NET Maker (not necessary for HFSLIP).

By the way... You can make it easier on you by setting PROCESS_DNF3_MSXML6 in the answer file for SNM to NO and only include MSXML6 with HFSLIP (or vice versa). You don't need to have those files twice.

Ok, thanks Tomcat. I'll test all tomorrow

@Tomcat, that could be it. I forgot to delete those IE6 updates... Thanks!

EDIT/UPDATE:
Thanks, everything is okay now. IE7 is now slipstreamed.

Am I correct in saying that HFSLIP is the first utility to "properly" slipstream IE7. I tried nLite, exclusively for IE7, but it's giving me Windows File Protection errors, so I went back to installing IE7 as the last routine in my RunOnceEx and the hotfixes at the next restart (using AutoIt).

But now, life is much easier with HFSLIP. Job well done!

This post has been edited by glentium: Feb 21 2007, 12:07 AM

In all the new Hfslip versions where IE7 is being slipstreamed, the "Show Desktop" Icon in the Quicklanch Bar is not showing anymore.
Everything else is btw working great. Thank you for your great work with Hfslip

Greetings from Ivan in Copenhagen.

OK... I was under the impression that this was fixed with the latest shell32.dll update. Apparantly not.

I'll put the QL fix back in.

Meanwhile, you can get the icon back by running this command from Run:

regsvr32 /s /i:U /n shell32.dll

I don't know if it's necessary, but I usually do it like this:
1) disable Quick Launch
2) execute the above command
3) log off
4) log back in and enable Quick Launch

This post has been edited by Tomcat76: Feb 21 2007, 06:18 AM

There is a way to remove this voice below?

 HFSLIP.jpg ( 45.04K ) Number of downloads: 10

"Show Desktop" icon shows on my Quick Launch toolbar. Am running from a 70220a run. XPSP2 English.

In mine it doesn't show... mmmhhh... maybe some update remove it?

This post has been edited by S3pHiroTh: Feb 21 2007, 08:22 AM

hi S3pHiroTh! i'm not sure if this is what you meant ... but this could be a little relevant: HFSLIP in Add/Remove Programs?

I have read the topic, but there isn't a safe way to delete that entry (the entry in list of installed programs is easy to delete, but not the one that I mean). I have seen that if I edit SYSOC.INF, there should be some problems.

May we know why you would want to remove that?

I'm using a Danish XP sp2, so perhaps that is why the "Show Desktop" icon is not showing on my Quick Launch toolbar. Running 70220a and v.31 with same result.

Simply I want a "clean" Windows installation... That's all