Super-Magician

Why is it that you have problems and many of us don't? I just tested 1.2.1 and integration works flawlessly with IE7SVCPACK=1. It probably has to do with either your source, your RunOnceEx programs, or any other program/hotfix you have integrated/slipstreamed.

The cabs only add NEW things to your source. They don't update anything.

If you want the advanced gaming support, include those files in HFCABS. If you don't need them, then don't include them! I don't think it is possible. Also, .NET is not installed unless you include it as a self-extracting switchless installer in HFSVCPACK. Like I keep telling you, please read this page. Yes, KB904706 is needed as a critical hotfix whether or not you include the DX9 cabs. The DX9 cabs are extra files not already in XP SP2 and are only needed in some gaming situations. KB904706 updates something already in your source.

@Martin L: That stronghold cookie always creates problems. @Camarade_Tux: That's expected behavior as long as the "Match user's browser during session validation" setting isn't enabled.

ha! ha! i always rename this myself too after before finalizing the ISO! Doesn't CDIMAGE and MKISOFS do this automatically (or if not, with the right switches)? @antonio_king, I believe HFSLIP already does that.

I already explained this to you earlier. You only want the *d3dx9*x86.cab and *d3dx10*x86.cab files, but the *XACT*x86.cab and *xinput*x86.cab files are also supported.

HFSLIP removes update.exe when it slipstreams hotfixes. There is no need for it. Only integrating wmp11.exe and wmfdist11.exe is not supported by HFSLIP. You should include the whole package. HFSLIP only takes what it needs to. Use an advanced decompression program like 7-Zip or WinRAR to extract the necessary CABs out of directx_dec2006_redist.exe. What you want are the *d3dx9*x86.cab and *d3dx10*x86.cab files.

Yes, like Tomcat said above, once you put the service pack installer in HF, HFSLIP will slipstream it directly into your SOURCE folder. After that, you can remove the installer from HF because it will not be processed. I assure you that if you read through http://www.hfslip.org, you'll get clarification on a lot of things. Be sure to check out the links for the update lists in Tomcat's signature. They dynamically update as you select features, showing which updates go where.

Yup, seems the login issue is resolved. Thanks, xper.

Actually, you are supposed to do it all the same time. HFSLIP does not support slipstreaming over previously HFSLIPed sources.

Any update on this script? I think it works very well in its current state, and with any minor updates you might want to make, we should be able to include it in the next final. I'm also wondering whether we can include all the necessary files in one package (as in putting wget in the HFNETCHK.zip file).

@Tomcat76 Maybe we could have a slight update to this section? ECHO This program slipstreams and integrates updates into an installable source. echo Windows 2000 SP4: Integrates/Slipstreams IE6SP1, DX9, Critical Update Hotfixes echo Windows XP SP2: Integrates/Slipstreams Critical Update Hotfixes echo Windows 2003 SP1: Integrates/Slipstreams Critical Update Hotfixes echo Copyright (C) 2005-2006 TommyP

(1) It's good to restart anyway, but it's required if you decide to include Internet Explorer 7. (2) HFSLIP is automated and deals with the many problems that often arise in Microsoft's hotfixes. It's much cleaner and doesn't leave extra junk. Plus, you only have to run one file! HFSLIP has other advantages too, including advanced features like HFEXPERT and HFAAO (application addons), and the ability to slipstream components other than pure hotfixes. (3) XPSP2 already includes DirectX 9.0c. However, if you wish to slipstream the advanced Direct3D gaming binaries that Microsoft releases bimonthly, HFSLIP supports it through the HFCABS folder. Check out Tomcat's XP SP2 update list for more information (look for DirectX on the page). (4) a. Like I said above, HFSLIP has many advantages, more about which you can read at HFSLIP's website. While some people still prefer nLite because it has a GUI and can remove components, HFSLIP can also remove stuff from your source through HFCLEANUP. b. Yes, HFSLIP does direct integration (otherwise known as pure slipstreaming) for most hotfixes. For those that can't be slipstreamed, HFSLIP integrates the hotfix through SVCPACK. c. HFSLIP uses the original name (containing the string "Windows") to determine whether a hotfix is Type 1 or Type 2. Hotfixes that contain the word "Windows" are usually Type 1; there are some that break this rule and such hotfixes are given special treatment. The same applies to those that don't contain the word "Windows"; these are usually Type 2. The main difference between the two types is the command used to extract them. d. As above. e. As mentioned above, HFSLIP supports most hotfixes. In the rare case that it doesn't, the script is modified to include support, whether it's through the SVCPACK folder or through "special treatment." I hope this helps . If you would like to learn more, be sure to check out the website. And since the script is open-source, you can take a look at it, and I'm sure you'll discover all the advantages of using HFSLIP and everything it does.

You got it!

For gdiplus.dll, there is a hotfix named gdiplus_dlnd.exe for 2K that you can place in HF.

Well, try the test release and see if you still get that error message. By the way, I see you are running HFSLIP on a computer installed with an nLited source. Now, is the source you are using with HFSLIP (i.e. in your SOURCE folder) also previously nLited? If not, you can disregard the last sentence in the post I made above.

The only change in the test release I believe would be related to your problem is some code cleanup to try to get rid of such extraneous error messages. I would recommend that you do not try running HFSLIP on an nLited source because nLite often removes components required for an HFSLIPed install to work if you're not careful enough. I believe there is some page on Fred Vorck's site regarding nLite and HFSLIP, but I can't remember exactly.

Could it be some issue with Internet Explorer 7? I have to say that even when I don't switch browsers, I often have to re-login every visit like piXelatedEmpire if I leave for more than about a half an hour between visits.

Shall I link directly to it? I'll just give you the directory. http://hotfix.xable.net/upload/ It's at the bottom.

Did you read this one yet? He is referring to that mod on the forum index that showed the statistics and let you login from that page. *** I seem to have trouble staying logged in even when the option is checked. I've cleared my cache, and my cookies are enabled and doing fine. I searched most of this topic, but I don't think there's anyone having the same exact issue as I. I've waited a few days to post this, but it's still not working.

Check for it on Xable's Hotfix Share.

KB929548 will probably fix the issue, but since it's an unofficial hotfix, it might cause problems.

@Tomcat76 Happy New Year! I noticed a few extra "The system could not find the file specified" errors over the last few releases. I remember when you spent a day or two cleaning up those messages in a release a few months ago. Think you can do a little more code cleanup? Edit: Oops. I just noticed you did this in 70102b. Thanks!

Happy New Year to everyone!

It is impossible for all intents and purposes to remove IE6 in XP. If you slipstream IE7, you are in essence removing IE6. Unfortunately, HFSLIP only integrates it because slipstreaming created problems. On the other hand, I don't see any reason why you would want to remove it.