Tomcat76

@Super Magician... In "autorun" mode you need to specify MULTICAB=ON additionally. And don't forget to specify AHTEST too. But let's not discuss this too much because it's an unsupported feature. If people use this and something goes wrong, we can't have a clear picture of the situation to diagnose it properly.

Because the UPDATE folder contains three needed binaries as well as an installation INF file for the registry modifications HFSLIP doesn't show this because you'd see something like: file1.ref 1 File(s) copied. file2.ref 1 File(s) copied. file3.ref 1 File(s) copied. Pretty ugly

You understood correctly

See my signature for an XPSP1 list intended for the current test release. If everything appears to be correct, can you please compress your HFSLIP.LOG and TXTSETUP.SIF files and post it here? I'm completely in the dark as everything's fine here with XPSP1. Yes. This feature is for hotfixes and/or updates that aren't on our lists.

Thanks

It depends on the situation. Here's it's OK because the SP*QFE folder doesn't contain any binaries of use.

People who've read the HFSLIP code probably know this by now, but here it is in plain English... HFSLIP does not slipstream the following updates; they are placed in the SOURCESS\I386\SVCPACK folder with a shorter name, and installed silently at T-13 during Windows setup. This is also the reason why they may appear in the Add/Remove Programs dialog. Windows-KB890830-Vx.xx.exe (Malicious Software Removal Tool) [All] UPHClean-Setup.msi (User Profile Hive Cleanup Service) [All] (installed at first logon with Win2K) Windows2000-KB917008-x86-ENU.EXE (Vulnerability in MS Management Console) [2K] MDAC_TYP.EXE (MDAC 2.8 SP1) [2K-XP] (installed at first logon) MDAC281-KB911562-x86-ENU.exe (hotfix for MDAC 2.8 SP1) [2K-XP] (installed at first logon) Windows-KB913433-x86-ENU.exe (Vulnerability in Flash Player 5/6) [XP] HMTCDWizard_enu.exe (HighMAT support for the CD Writing Wizard) [XP] wmcsetup.exe (Windows Media Connect 2.0) [XP] ENU_Q832483_MDAC_x86.EXE (Buffer overrun in an MDAC function) [XPSP1] WindowsXP-KB840374-x86-ENU.EXE (Vulnerability in Help and Support Center) [XPSP1] KB914798-v2 (Vulnerability in Windows Services DACLs) [XPSP1-2K3Gold]

Thanks

OK... Here's what you got with test version 61011b: - folder: HFEXPERT\STORAGE - config file: STORAGE.INI (not case sensitive) HFSLIP compresses the storage driver files into SOURCESS\I386 and adds the necessary info into TXTSETUP.SIF per your instructions above. The file names are also added to DOSNET.INF. Is this good?

@Oleg II: yes.

Personally, I like it a lot. Is it really this simple? I tried to implement it and it's just six lines of code. I only need to know two things: 1) do the storage driver files need to be compressed? 2) what about DOSNET.INF?

You can put the INF files in HFEXPERT\DRIVERCAB now.

Done

Hi rickybez. Welcome 1) MSICabExtract is not used by HFSLIP (and hasn't been for months). 2) Extra MSI files are not supported by the latest "final" version. However, as Kiki pointed out, the test release for the upcoming final has support for MSI files if you put them in the HFSVCPACK_SW folder; they will be installed silently at T-13 with the /qn /norestart switches. 3) For exe's in the HFSVCPACK_SW folder the /Q:A /R:N switch is used.

@Camarade Did you read the changelog? I have simplified it a little just now.

There was a problem with IE. Check again

No... every necessary file is there...

You are right about the resource file. It's the same version as the one in the 2K rollup. I guess the newer date confused me. I'm now doing a thorough check of all files and will update my lists accordingly...

I'm keeping msxml3.msi on my list for the resource file. BTW, I suppose it's a mistake from MS to say that KB924191 updates both MSXML2 and MSXML3 because it only contains an updated version of msxml3.dll -- not msxml2.dll.

Hi Oleg... Nice to see you back! Hope everything's OK. The web page is up to date as far as the current final is concerned but it needs modification for the upcoming version. Please refer to the changelog in this thread if you want to use a test release.

There are several MSXML hotfixes released today. HFSLIP needed to be updated for this (see test release 61010b), but it's for the better. MS seem to release "full" updates more frequently. The following are supported with the current test release of HFSLIP: MSXML2.5: KB832414_MSXML2.5_x86.exe (2K and XPSP1 only) MSXML2 SP6: msxml2.msi + msxml2sp6-kb887606-x86-enu.exe (all) MSXML3 SP7: KB924191 (all) MSXML4 SP2: msxml4-KB925672-enu.exe (all) MSXML6: msxml6-KB925673-enu-x86.exe (all) No longer needed: msxml3.msi msxml.msi or msxmlcab.exe (MSXML4) msxml4sp2-kb887606-x86-enu.exe (MSXML4 update) msxml6.msi

Win2K with IE5 is done. The inetcomm.dll binary from the OE 5.5 cumulative update has a broken registration section (deja vu anyone?).... HFSLIP (61010a) is letting Windows setup register inetcomm.dll from the Update Rollup (which is OK) and then overwrites the file with the version from the OE 5.5 hotfix. This is the same procedure as for the webvw.dll binary on non-English Win2K sources. All fine with Windows Update.

Yup... It's the hotfix. Will see what can be done about it. In the mean time, don't include it... or use IE6, heheh.

Hmm... This inetcomm.dll problem is also there with the current final. Would the OE5.5 hotfix be causing this? This needs some thorough testing....

Working on the inetcomm.dll problem. The IE5 section from the Update Rollup's INF isn't taken account of properly. I fixed it in an internal build and am testing it out in a VM right now. Otherwise, Win2K with IE5 is AOK (WMP9 too). Malmsteen's Odyssey album is helping me keep up the pace...