Tomcat76

@Camarade_Tux: HFSLIP didn't process KB911565 because of an old restriction for KB817787. That's corrected now. Quite a coincidence... I was testing XPSP1 the last couple of hours and noticed the same thing... We're nearing in. I still need to do some stress-testing on Win2K, especially with USP5 as there seem to be some problems in that domain.

@SQ5FG: I quickly checked them and they should be supported. If no new test version will be released, the only difference between the current test version and the next final will be: added support for IUCTL.CAB in conjunction with RVM Update Pack when WindowsUpdateAgent20.exe is absent. Checked OK: - WinXP SP2 English + RVM Update Pack - WinXP SP2 Dutch + SWFLASH.CAB Still to be checked: WinXP SP1 + Win2K USP5

So how's 60523a doing IRL?

This isn't important, but I've always used that redirect link in my sticky threads above. I took it from a LegitCheckControl thread somewhere in a different section on the MSFN forums. The links on my standalone web pages on the other hand are direct download links which may become obsolete from time to time.

tjabocom... Please try the latest test release and make it not unattended. See how far you get...

Uh no... It's the reverse: HFSVPK_SW has been renamed to HFSVCPACK_SW. But the old is still accepted (HFSLIP automatically renames it).

Plus, we're talking Windows 2000 here

@Camarade_Tux: Which version did you use? To everyone... Any new problems with this release? No more updates are planned for the next final release except for a "cosmetic" change in the part that handles HFCLEANUP. This needs to be rounded up as the current final doesn't handle some of the hotfixes that appear on Windows Update. To check: - WinXP SP1: when not including MDAC_TYP.EXE and MP10Setup.exe, Windows Update should only propose WMP10 and the Windows XP Documentation Update - WinXP SP2: RVM Update Pack - Win2K: Gurgelmeyer's USP5 - application addons - HFEXPERT

With HFSLIP, you can slipstream any WinNT 5.x version (2K-XP-2K3) while running any WinNT 5.x version. Normally, you can't slipstream Windows XP SP2 into a Windows XP source while running Windows 2000, but HFSLIP works around that. HFSLIP doesn't burn directly to CD.

Open in Notepad and go to File > Save As. You can then see the encoding it's in. It's strange they only made it available for English systems. But it doesn't update the Portuguese KBD layouts either so I don't understand why you wanted it in the first place...

Yeah... I began to wonder who the FDV is that's sending me e-mails...

I don't believe in god...

Oh, I see now. But I also see that all the language descriptions are in English, so this hotfix isn't to be used on non-English systems apparantly. Also, INTL.INF is in Unicode format which I don't want to edit as it would become an ANSI file which might make the install fail.

I've no idea how to handle file names that start with an exclamation mark in this context. Maybe Yzöwl knows this. Would it be a problem to use an underscore or something else instead?

That's a strange problem, heisking. I placed a file in HFEXPERT\WIN\PCHEALTH\HELPCTR\BATCH and let HFSLIP do its thing. The filename was entered into TXTSETUP.SIF correctly. As Super-Magician said, could you attach your zipped HFSLIP.LOG file? Thanks...

I can't really provide help for Nero, I'm afraid. It's been over a year since I used that program. What happens if you use CDIMAGE.EXE to create the ISO, burn the ISO with Nero and install from that? If you aren't adding anything to the Windows source after HFSLIP has run, you can let HFSLIP take care of making the ISO. Place a bootable BIN file and either CDIMAGE.EXE or MKISOFS.EXE in the HFTOOLS folder and run HFSLIP. If you don't have a BIN file, put BBIE.EXE in HFTOOLS and make sure you have your Windows installation CD loaded in the CD-ROM drive while running HFSLIP.

I just tested this myself and HFSLIP takes INTL.INF from KB897338 and puts it into the new source without modification. I also examined the code that handles the hotfixes and I can't see why this is happening for you. By the way... Support for KB897338 in general was dropped in a recent test release. The current test version namely doesn't let Windows setup know that there are new files from this hotfix. I'm thinking of re-enabling support for KB897338; I'll run it by TommyP. But it's not related to your INTL.INF problem.

Do post back if you have more results. A new final is coming up and I would like to have this fix included. As far as your "vbscript.dll" problem is concerned... If HFSLIP is adding an extra line for it in TXTSETUP.SIF then that's not really "wrong", but it might mess up with some types of installations. Symantec LiveState is one example and I already hard-coded some workarounds for it. I'm gonna see if I can stop HFSLIP from adding lines into TXTSETUP.SIF (and DOSNET.INF) that are already present in those files. HFSLIP isn't doing that by definition, though; this case is rather unique.

If you're just into adding "all" hotfixes then you can do with the RVM Integrator in this particular case. But HFSLIP can do much more than adding hotfixes.

Actually... So you can install it up front. The actual download page doesn't say it's to be used on Windows XP SP2 exclusively either.I'll add it to the SP2 list too.

It is supposed to be supported completely. Your CAT problem seems to be unique. The only part that isn't covered is the removal of duplicate driver binaries but that's "corrected" with DBLBINXP.EXT. Not that I can see. But you're lucky... XP is "better" than 2000 at letting you install things at T-13 but it's still not perfect; some programs (like MDAC_TYP.EXE) just won't install at T-13.

@Super-Magician: I removed your hotfix post as I finally got around to updating the list in the main post; it might've confused people reading this thread in a few months from now. I've also removed the "taboo posts." The thing is... When the SP2 system boots up and gets right up to Windows Update, there's no point anymore in listing it on Windows Update, is there? So the question is... Does it really apply to SP2 when it's slipstreamed, and is "update.sys" updated by a later hotfix?

The number of post-SP1 hotfixes is already exceptionally large. Imagine what the list will look like in one and a half year. It's not so much adding of new hotfixes to the list that's going to take the most time, but rather verifying which hotfixes will have become obsolete.

CAB files or CAT files? I've really no idea. I never use mkisofs so I don't know this program. TommyP added support for it a long time ago... It's already at version 2.0.6? Then I better check that it's still working properly in HFSLIP, hehe. I used 2.0.5...Your file list is getting better. There are still some duplicates. Did you check RVM's list? You can remove msxmlcab.exe, msxml6.msi, the D3DX9 cabs, swflash.cab and MUWEB_SITE.CAB. At this moment, you don't need LegitCheckControl.cab either I believe. There could still be some hotfixes that you can remove but I didn't verify that. Are these two different programs? Addon_LClock_v4w_dgelwin.cab Addon_LClock_v4_dgelwin.cab Yep. Not exactly. If there are files with identical names then the latest will be used. But SYSOC.INF or SVCPACK.INF will install the program more than once (once per addon). This isn't necessarily problematic but it can be. It's best not to try that out.