Tomcat76

I believe that's not what HFSLIP is all about. TommyP should be able to tell if I'm right or wrong. Personally, I don't feel like messing with this either.

You could try that to see if it fixes some problems you're having. XPize offers the option to ignore certain files if you install it via SVCPACK, I think. Rapidshare again... I'm not gonna wait 42 minutes to get the Visual Styles file. But I could download Folder Size and I see a problem with it: it needs something to be run during GuiRunOnce, which HFSLIP doesn't support with application addons. This probably can't be fixed.

@ebernard This thread is about hfslip.org. You're talking about FDV's site which is about to be slimmed down. Concerning my hotfix lists on this forum and on my server (see my signature)... It's been requested before but I don't have the time for that. Some people also asked to put MD5 sums there. It may happen some day.

nLite? An old HFCLEANUP reducer? HFSLIPWU.INF will "error out" if any of those are missing.

OK. That hasn't been the case for several months. BBIE outputs *.BIN files, MKISOFS can work with *.BIN files, and CDIMAGE can work with *.BIN files. There's no point in forcing people to rename it to *.IMG so it was dropped. Since that change, if BOOT.IMG exists but not BOOT.BIN, BOOT.IMG is automatically renamed to BOOT.BIN. Thanks.

The XPSP2 installer can be named xpsp2*.exe from now on if MS ships it like that. The old *835935* from the MS Download Center still works, of course.

We're slowly heading for a new release. I don't intend to add any more to it in this round, so... let us know if something broke. Comments on the new HFEXPERT\PROGRAMFILES feature would be nice too...

I don't see anything really wrong in there except that "readme.txt" from TAiN's package is being registered. Either remove this file or use the latest test release where TXT files from HFEXPERT\CODECS are not registered. I think there's only three possible culprits: 1) XPize 2) One or more of the "extra" hotfixes you include 3) Any one of the following files is missing in the new source: wuapi.dll, wuaueng.dll, wuaueng1.dll, wucltui.dll, wups.dll, wups2.dll, wuweb.dll, muweb.dll, iuctl.dll, opuc.dll, LCC.dll, msxml4.dll or msxml6.dll

That's good to hear, ctpooon. And you're welcome. I hope you can fix your problem with winnt.sif...

anti-malware: - PCTools Spyware Doctor - Sunbelt CounterSpy - Ewido anti-spyware - Kaspersky anti-virus - HijackThis protection: - Spybot Search & Destroy - Lavasoft Ad-Aware Personal - Windows Defender - "full DEP" - AVG Free Edition or Avast! On my PC, I just use AVG and Opera in terms of "protection". I've been online since 1999 and only experienced two boot sector viruses that came in through Outlook Express a long time ago. The programs listed above come from personal experience when cleaning up other people's PCs.

Heh... The test release does 5 minutes faster for you... That's nice. Personally, I don't think LegitCheckControl.cab is the problem this time (or maybe the previous time too but you never knew that) because it's "international". I've been using the same CAB file on different language installations of Windows and haven't experienced any problems with it. Can you try once without WINNT.SIF?

This isn't an update for Windows Server 2003, but an update for .NET Framework 2.0. It should be applied after .NET 2.0 is installed, or used to patch an administrative installation of .NET 2.0.

FDVT=Y (or FDVT=N). You need test release 60726c, though.

Anyone?

ctpooon... Do you mind trying the latest test release? It handles hotfixes a bit differently and I also added a possible fix for your "Traditional" problem. Just place the CMD in your current HFSLIP working folder. You don't need to create a new HFSLIP folder and copy everything over.

You can do whatever you like, but I strongly advise against editing SYSOC.INF. Removing the entry for HFSLIPWU.INF will cause that file to not be processed, which is responsible for a whole lot more than just the "HFSLIP Total Slipstream" entry in Add/Remove Programs. It handles the registration of all the hotfixes you slipstreamed, WMP, DirectX9, codecs, things you cleaned up, etc. Either edit HFSLIPWU.INF, or use a .reg file that deletes the registry key responsible for the entry in Add/Remove Programs.

OK. "HFEXPERT\PROGFILES" is ready for consumption, hehe. Let the reports roll in...

One that fails the codec tests in Gspot. I want to know if it's HFSLIP's fault.

When I click the MSXML 4.0 SP2 Other languages (msxml.msi) + latest binary update in the same language box, it shows me msxml.msi and msxml4sp2-kb887606-x86-enu.exe XML2 is different from XML4, but OK. This isn't important now. If HFSLIP detects that a source is already slipstreamed, it will ignore the service pack installer and just proceed with other things. Since HFSLIP detects your source as "SP1" and it is not updated by HFSLIP, it can only mean two things:- something went wrong when you slipstreamed SP2 - you do not include the required CD tag file WIN51.SP2 (automatically created when slipstreaming SP2) HFSLIP itself uses the CD tag to determine the service pack level, but the script part that actually *does* the slipstreaming uses the name of the newest SP*.CAB file inside SOURCE\I386. My guess is that you don't have WIN51.SP2, but you do have SP2.CAB. If you want HFSLIP to slipstream SP2 again, you need to put the original Windows XP source or Windows XP with SP1 inside the SOURCE folder -- not Windows XP with SP2. Thanks for the other info. I'll update HFSLIP to see if I can fix the "Traditional Chinese" problem.

Kiki... I need these two files from that HFSLIP run: - TXTSETUP.SIF - HFSLIPWU.INF I want to exclude any registration issues. Thanks.

If the intention is to slipstream SP2 then you need the hotfixes for SP2. ctpooon got that right. @ctpooon... My hotfix list doesn't ask to place the following files in the HF folder: msxml2sp6-kb887606-x86-cht.exe WindowsXPMediaCenter2005-KB900325-usa.exe I don't mention the XML2 update at all, and you should extract wmfdist95.exe from the KB900325 update per the instructions on my page. What's strange is that the service pack didn't slipstream and that the localization seems to be represented wrongly in HFSLIP.LOG (it should be "Traditional Chinese" and not "Traditional"). Check this: 1) Are you running HFSLIP from a Windows account that has Administrative privileges? 2) Did you get a warning message from HFSLIP that your source is not a clean source? 3) Did you get a warning message that you cannot slipstream Windows Update Agent? 4) Go to E:\hfslip\xp\SOURCE\I386 and open PRODSPEC.INI in Notepad (by double-clicking it). Scroll down and let me know what it says next to "Localization=".

Where are you trying to download it from?

Here you can post constructive comments telling us how the HFSLIP web site can be improved. Report spelling or grammatical errors, if sections can be worded better, etc. URL: hfslip.org <rant>One thing I won't change is the core code of the site. It was designed from the ground up to be XHTML 1.1 compliant and at the same time compatible with MSIE 5.5, MSIE 6, as well as any standards-compliant web browser (tested in Opera 9, Mozilla SeaMonkey 1.0 and Mozilla Firefox 1.5). For MSIE in general you need to have scripting enabled, and for MSIE6 on XPSP2 and Win2003 in particular you need to allow it to process active content. Working around the "yellow information bar" problem means degrading the code to "street HTML", resulting in degraded display and possible compatibility problems with modern web browsers. I won't go there. People who want to progress should be rewarded.</rant>

OK. Updated. Keep the corrections coming, but please don't do it in this thread. I'll start a new one.

Uh? Your browser's cache must be way behind, then. It was last updated on the 18th and "priviledges" is written "priviledges" in both the Preface and in Step 8.