Tomcat76

Yes, but it's superseded by WindowsXP-KB917021-v3-x86-ENU.exe. Use this one instead.

I know more now, but I'm afraid this is out of my scope. You say that the error appears during GUI mode setup, which means that the KB888111 files were successfully copied over to the hard disk during txt mode setup. You can test this yourself by starting Windows installation again and pointing the dialog boxes you get to C:\WINDOWS\system32\drivers for hdaudbus.sy_ and to C:\WINDOWS\inf for hdaudbus.in_. I'm sure Windows setup will find them there. I think this is more of a driver problem. I've experienced it many times before when I installed drivers manually and rebooted, that Windows would ask me for the location of certain files; I point it to C:\WINDOWS\system32 or C:\WINDOWS\system32\drivers and then it finds them. Stupid, and I don't know how to avoid that. This also happened with non-HFSLIPped systems. Make sure that you use the KB888111 hotfix for Windows XP SP2. That's all I can say...

You don't seem to understand a couple of things. First of all, you should not edit TXTSETUP.SIF. Just stay within HFEXPERT\DRIVERCAB. Second, Oleg II is talking about editing the driver INF files directly (before running HFSLIP), not to copy anything into another file. Third, whatever you do will never work unless you set DRIVERCOMP in HFANSWER.INI to A, B or C. If you really want to use D, E or F then you need to use the HFEXPERT\SPXCAB folder and virtually substitute references to "driver.cab" in Oleg II's instructions with "spx.cab". Last, forget about HFDRV.CMD and HFDRV.CAB. Those are files that HFSLIP was creating a very long time ago.

Well... HFSLIP adds at least one extra [sourceDisksFiles] section, at least one extra [WinntDirectories] section, one extra [FileFlags] section for Windows XP, one new [setupData] section, one extra [HiveInfs.Fresh] section and one extra [HiveInfs.Upgrade] section, all at the bottom. Your TXTSETUP.SIF doesn't have any of those. It has one combined [sourceDisksFiles] section at the top, one combined [WinntDirectories] section, etc., EXACTLY how nLite does it. HFSLIP is simply incapable of combining sections; it can only write new lines at the bottom (It is possible to make HFSLIP capable of rearranging TXTSETUP.SIF at the end but it would severely impact the HFSLIP running time). Please just run HFSLIP again and then see at the bottom of TXTSETUP.SIF in SOURCESS\I386. It should look completely differently. I just did a test run with KB888111 and HFSLIP added these lines under the extra [sourceDisksFiles] section related to that hotfix: hdaprop.dll = 1,,,,,,,2,0,0 hdashcut.exe = 1,,,,,,,2,0,0 hdaudres.dll = 1,,,,,,,2,0,0 hdaudbus.sys = 1,,,,,,,4,0,0 hdaudio.sys = 1,,,,,,,4,0,0 hdaudbus.inf = 1,,,,,,,20,0,0 hdaudio.inf = 1,,,,,,,20,0,0

Come on... The TXTSETUP.SIF you attached has the [sourceDisksFiles] sections completely rearranged and it says "Customized by nLite - www.nliteos.com" at the bottom...

This utility can be useful for people who want to run nLite or a similar program on their source after HFSLIP. It collects the names of new files slipstreamed by HFSLIP. In the case of nLite, the list of files can be used for its "keep list". It can be run either separately, or as an HFSLIP "plug-in". As a separate utility: 1) Run HFSLIP (meaning: an existing SOURCE and SOURCESS folder are required) 2) Download HFSLIP_POST_getnewfiles_v3.zip and extract HFSLIP_POST_getnewfiles_v3.cmd into the main HFSLIP folder or in one of its direct subfolders 3) Run HFSLIP_POST_getnewfiles_v3.cmd As an HFSLIP plug-in: 1) Download HFSLIP_POST_getnewfiles_v3.zip and extract HFSLIP_POST_getnewfiles_v3.cmd into the HFTOOLS folder 2) Run HFSLIP as usual A file named NEWBIN.TXT containing the names of the new files will be created.

I have taken a look at your TXTSETUP.SIF and I'm sure your problem is the fact that nLite strips out the references to the KB888111 binaries that HFSLIP has added. Please run HFSLIP. Then open TXTSETUP.SIF and take a look at the files under the [sourceDisksFiles] section at the bottom (starting from HFSLIPWU.INF). nLite should not remove these references.

Who asked? Windows setup or the audio driver installation program?

The binaries in KB923810 are not part of the XP source. I removed the update from my list. Thanks.

Thanks for the reg file. Korean is supported now. Which version of scripten do you have in HFSVCPACK_SW1? 5.6 or 5.7? I think it's version 5.6 and it (accidentally) replaces jscript.dll from KB917344 when installed. If scripten.exe is version 5.6, please remove it from HFSVCPACK_SW1, remove WindowsXP-KB917344-x86-KOR.exe from HF and use WindowsXP-Windows2000-Script56-KB917344-x86-kor.exe in HF instead.

Not to my knowledge. I've never had this problem with an English source except when slipstreaming an older version of MSXML6 into DNF30.exe. Windows Update did complain about MSXML6 for non-English languages but I recently noticed that's no longer the case for Dutch (hopefully other languages too). If you download and install MSXML6 manually in this case, you always get a message like "all files already in place". Really stupid. And then Windows Update no longer asks for it. I was never able to figure out what needs to be done extra for non-English languages.

Microsoft have recently updated the site to support the 3rd cumulative time zone update. I removed that note now. It wouldn't have mattered. Same problem. Microsoft/Windows Update really wanted you to have the older time zone update. I'm sorry, but it's a lot of code and takes a while to explain. I don't have time to help with something that doesn't work properly. This has been covered a few time before. It's supported as long as it has "888111" in its name.

Added support for Korean thanks to bynkook. Also, Windows Update doesn't complain anymore. They have finally updated it to support the 3rd time zone update.

You are probably referring to localized namings of w03a3409.dll. I didn't know the file existed. It should be supported now.

Not really. There are still three files that need to be force-copied: ieframe.dll.mui (latest cumulative update) jscript.dll (KB933873 -- not public) vgx.dll (KB938127) A new release candidate will be out shortly.

If you are using the latest version of the main IE7 package then you must use the latest HFSLIP test release.

It's not needed when slipstreaming IE7 but my update list shows it regardless because HFSLIP doesn't slipstream IE7 by default. It creates an updated installer if you don't specify IE7SLIPSTREAM=1 in HFANSWER.INI. Just remember that you still need it for HFCABS\OPUC4.CAB, HFEXPERT\CODECS, HFEXPERT\APPREPLACEMENT and HFEXPERT\WIN if you use any of those. You don't "need" all the versions of MSXML, but newer versions are not cumulative either. If you want them all you should add them all and not just MSXML6. You probably didn't notice it, but from the Dutch time zone update the "ë" in Namibië, Brazilië and Armenië is not preserved. Every foreign language has special characters like these so HFSLIP's built-in support (with a lot of code) was only useful for the English time zone update.Use this instead as mentioned in the changelog for HFSLIP 1.6.3.

Because it was a lot of code just to support the English update. The special characters of foreign languages in localized versions of the time zone updates are lost because the INF file inside them is saved in ANSI instead of Unicode by Microsoft.Use the 3rd cumulative time zone update reworked for use with HFSLIP instead.

None of the HFSLIP versions do anything to fix the RunOnceEx problem. You should just include the latest cumulative update -- which seems to work for most people.

There are three real problems: 1) Your source has been stripped down by nLite but HFSLIP can only work with an original source. Lots of files (such as the WMP11 files) are now copied into the wrong location. 2) You added "Inicializa‡ao do Windows XP.wav" manually after HFSLIP has run. I'd double-check that the special character is not the reason of the installation failure. 3) windowsxp-kb892130.exe is not supported. As an aside... windowsxp-kb924496-x86-enu.exe (superseded by KB937143) windowsxp-kb928843-x86-enu.exe (superseded by KB935448) windowsxp-kb933360-x86-enu.exe (blocked by HFSLIP)

Thanks

I was talking about a test release. Please check the first post in this thread

How 'bout now?

A new test release to support the new IE7 installer is in the making. I'm now testing in a VM. The roots update goes in the HF folder, yes.

I know about those, but it would take things too far. I don't want HFSLIP to check the version of every binary as it will run a whole lot slower...