Tomcat76

It's nothing major. I inserted a PAUSE right before the CLEANUP section and another PAUSE right after the CLEANUP section.He already said twice that everything's fine at the second PAUSE. The only things that mod DOSNET.INF after that are HFCLEANUP, HFEXPERT\WIN and FDV. I suppose we can scratch FDV as a possibility on WinXP.

In that case, you don't know if it's a new problem or not. You mean "wusetup.cat"?This is strange. HFSLIP doesn't restrict the slipstreaming of Windows Update Agent based on IE version. The only "filtering" that's done is based on the OS language... and I can't see how that would differ depending on the version of IE. I could understand if Windows refused to *install* WUA files when IE5 is used but they should still be present in the SOURCESS\I386 folder...

Can I have a look at the ERROR_REPORT.TXT file from that installation?

It could still be language problem...

That's really odd. You wrote that DOSNET.INF is intact at the second pause. After the second pause, only these parts are modifying DOSNET.INF on WinXP: HFCLEANUP and HFEXPERT\WIN. But, judging by your ERROR_REPORT.TXT file, you aren't using any of those. Would you mind keeping only these files in HFTOOLS and running HFSLIP again? modifyPE.exe MSICabExtract.exe MSICabExtract.txt

The point is that you should not be including those updates as they are intended for a different version of Outlook Express. Have you always had this problem with the OE updates? When did you try HFSLIP for the first time? Exactly how did you determine Windows Update Agent wasn't slipped? Are files missing on the CD?Is Windows Update Agent slipstreamed when including IE6?

I could restore IEUPDATE and VGXUPDATE for IE5 if it makes a difference. @ThunderM: Is this a recent problem?

Thanks. That greatly limits things. Do you have an ERROR_REPORT.TXT from that last one?

OEUPDATE is not removed.

Alright. Would you mind running the latest test release (60326a) and provide me with your ERROR_REPORT.TXT, HFSLIPWU.INF and TXTSETUP.SIF files? I suggest you compress them together. After that, please run 60326a again but choose merging option A, B or C and install that. I need to know if the problem really lies with the "non merging"... Thanks.

I did a complete file by file comparison between versions 60207b and 60208. In the newer version, the section which creates the SPX.CAB file was revised. For the rest, the files are completely identical. Are you using merging options D/E/F? If so, have you tried A, B or C? Personally, I find it hard to imagine that that's the problem. Are you absolutely certain that the problems started from version 60208 onwards?

OK. Thanks. I'll check it out.

Here's an idea... Try HFSLIP_60107.CMD and HFSLIP_60207b.CMD. Something "big" was changed between those two. Edit... Wait a second... I found a whole lot more. The two files I mentioned in this post are too far apart so it wouldn't prove much. Here's a package containing two versions that are much closer together; one right before the "big change" and the other one right after.

@jackie OK... I've tried to locate all versions between January 1st & February 8 that I still have lying around. Most of those are test builds so if a new problem arises just ignore that version. There's 10 of them. jackie.7z Thanks... and good luck...

Jackie... Which is the last one that works for sure? Have you tried that version recently?

Would you mind trying this special debug version? It pauses twice. Each time it pauses, could you check if DOSNET.INF in SOURCESS\I386 is still intact?

That's what Jackie wrote: "just slipstream the hotfixes and it still has the same problem"

This is gonna be difficult. Did you see the changelog for Feb 8? Very discriptive... During that time, I started "doing stuff" in HFSLIP but only small things and all went through TommyP. I didn't keep a personal record of every detail until I took things more into my hands in the 2nd half of February. Which is the last one that works for sure?

Yes... wdigest.dll will be updated from 5.1.2600.2180 to 5.1.2600.2784, but you shouldn't notice any difference. I haven't seen anyone complain yet.

OK. Thanks for the heads up. Could anyone else using IE 5.01 on Win2K confirm that the following two security updates are needed? IE 5.5sp2-KB823353-x86-ENU.exe (Cumulative Security Update for Outlook Express 5.5 SP2) oe 5.5sp2-KB897715-Windows2000-x86-ENU.exe (Vulnerability in Outlook Express 5.5 SP2) Judging by the version number, it appears not but ThunderM says Windows Update and MBSA stop complaining after integrating these with HFSLIP. Very strange...

OK. A couple of comments... 1) Remove the underscores from "Proj_Unattended" and "HFSlip_MUI" (don't replace them with spaces) 2) Download the latest test release (60325b) and extract the contained CMD into your HFSLIP working folder ("HFSlipMUI" or whatever you're going to call it). You need 7Zip or WinRAR to extract it. 3) Put wmcsetup.exe in the HF folder 4) Is that DirectX executable supposed to work with the /Q:A /R:N switches? Why don't you just take out the necessary d3dx9 cab files from the original package and place them in the HFCABS folder? Edit: 5) Remove WindowsMedia10-KB911565-x86-ENU.exe. It can only be used when MP10Setup.exe is in the HF folder. If you decide to put MP10Setup.exe in the HF folder, remove WindowsMedia9-KB911565-x86-ENU.exe instead.

MP9 is not slipstreamable. You'll have to put it in the HFSVPK_SW folder. You can, however, slipstream the KB911565 update for WMP9 which contains a newer wmp.dll file (put the exe in the HF folder). When WMP9 gets installed (during SVCPACK), it will leave the newer wmp.dll file in tact. This "pre-loading" only possible on Win2K as it doesn't contain wmp.dll out of the box. BTW... wmp6cdcs.exe goes in HFSVPK_SW. I'll be back in a short while on the msxml3 stuff.

It's an update for Outlook Express 6 which is needed when installing Internet Explorer 7.

Just for 2KIE5 or also for FDV?

Are you entering a custom path when HFSLIP starts?