Hy,

I am using hfslip on W2KPro en and always get these errors:

setuperr.txt:
Error:
Setup detected that the system file named [c:\winnt\system32\msxml3.dll] is not signed properly
by Microsoft. This file could not be restored to the correct Microsoft version.
Use the SFC utility to verify the integrity of the file.

***

Error:
Setup detected that the system file named [c:\winnt\system32\msxml3r.dll] is not signed properly
by Microsoft. This file could not be restored to the correct Microsoft version.
Use the SFC utility to verify the integrity of the file.

***

Msxml3 comes with our beloved security rollup v2. So, is there a bug or something that hfslip does?

Thx!

I suppose that's because you aren't including IE6. Maybe someone that keeps IE5 can confirm. I always include IE6.

Both the 2k rollup update AND the windows update rollup have msxml3. Filedates are different between both files, but they both have the same revision. Go figure.

Note to TC. If the rollup isn't in the HF folder and you aren't slipstreaming IE6, msxml3 needs to be added to the txtsetup and it needs to be registered.

Just for 2KIE5 or also for FDV?

TC - you have mail.

The problem occurs wether I slipstream IE6 or not, always got this error.

@Tomcat76: Btw, check your PM, your Win2K update list if keeping IE5 on W2K is incomplete!

I am using the Updaterollup revision v2, the version for "IT-Pro's".

I tried several times, always getting this error.

Off topic: Are there any reported problems with MP9 and latest updates?
setuperr.log reports a .dll couldn`t be registred?

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.

Hmm, something strange happened.

As you wrote above I moved the mp6xxxx.exe from HFSVPK to HFSVPK_SW, everything else has not changed, and did reHfslip and a reinstall.

The msxml3x.dll errors are no longer existant.

Weird

Edit: @Tomcat76: The Updates of OE I PM'ed you are requested by WU/MBSA. If I slip the 2 ones mentioned WU/mbsa is happy

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...

And could that person also mention why they would run such a configuration? It seems to me that if you are going to keep/use IE it would make sense to use the latest version. Is IE5 better in some respect?

TC - If there is an OE prob with windows update, the OEUPDATE.EXE KB######.INF command must be issued. This command was in HFSLIP a while back, but was removed. Perhaps it is a good idea to add it back in.

OEUPDATE is not removed.

Yep, you're right. Sorry. Those MSOE updates used to drive me nuts. Perhaps it's the IEUPDATE or VGXUPDATE command?

I could restore IEUPDATE and VGXUPDATE for IE5 if it makes a difference.

@ThunderM: Is this a recent problem?

Back again,

The problem with the msxml3x.dll`s is still present, have to revise my info from yesterday.

Today I have created another Win2k Pro CD, this time with IE6, got problem again and even another one, check setuperr.log.

Rechecking my cd from yesterday without IE6 and without msxml3x.dll errors I recognized that the WindowsUpdateagent wasn`t slipped.

So, there is def. a problem with hfslip and Win2K. Other users who slip the same config as I should have the same entries in their setuperr.log.

Guys, please take a look.

Thx.



There is no need to change anything on OE, slipping the 2 mentioned updates runs flawless and WU/MBSA is happy.

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?

The problems you mentioned, ThunderM, that have to do with IE6 did not happen to me when I tried HFSLIP (60317) with my Win2K installation. It is probably a problem on your part, not on HFSLIP's.

It could still be language problem...

To 1: I have tried with IE5 on Win2K for 3 times, all yseterday (always checking with MBSA/WU).
I used hfslip almost since beginning, mostly on wxp.

To 2: In SVCPACK dir the wuxxxx.cab was missing, mbsa told me that WinUpdateAgent wasn`t installed -> that´s how I even recognized it.

To 3: Yes, WUA was slipped when including IE6.

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...

I get a vgx.dll missing error with an odd HFSLIP + nLite configuration. Adding vgx.dll to the nLite keepfiles section fixed it, so that may be another new thing to add to this list.

HFSLIP doesn't do anything "special" with vgx.dll. In fact, it doesn't do anything with that file at all. I don't use nLite (don't like programs of which I don't have full control) but maybe someone else that uses HFSLIP with nLite can shed some light on this. I find it strange that noone ever came across this before. But then again... You do call it an "odd configuration", so maybe you should first explain what you're doing.

My "Odd" configuration isn't perfected yet.

Someone asked me to put together easy instructions on how to get an extremely lite Win2k("easy" as in for people that can follow simple instructions, but have no intent to learn). I modified some things to get HFSLIP to not complain about USP5.1, slipstreamed dx90c, and left IE5. I got a vgx.dll and msvidctl.dll copy error when removing IE but keeping the IE core with nLite.

Adding both to keepfiles fixed that, and then I tried integrating IE6(which seemed to work fine).

I haven't posted anything on this yet though because some USP features don't seem to want to stick, which somewhat negates the point of being "easier". I was told USP has a pre-hacked explorer.exe that enables full-colour systray icons, but my USP-slipstream does not.

TC is correct, hfslip doesn't do anything with VGX. It is installed via syssetup.inf (a protected file that HFSLIP doesn't touch). I have a few applications that need VGX (and they won't install if it's not there), so i don't remove it with NLITE. Besides, now I use alternate methods to reduce my 2k sourcess . Can you say 100 meg ISO?



He uses hacked setup files to disable SFC during setup too.

Yep. I can say 100mb ISO w/ nLite & All Drivers Integrated. I can also say 250mb windows dir, and 10mb 'Programs And Apps'.

I'm going to be looking into alternative reduction methods aswell soon - nLite leaves too much registry junk lying around.

I get a 100 meg without using nlite . I'm too lazy to slipstream my drivers, but they are only 10 meg anyway.

Ok, it seems that noone is interested in it or even verify himself.

It`s ok, I solved the problems myself.

You get msxml3x.dll signing errors only, if you slip WUA on W2K, if you do not slip it and install manually later everything is fine (or use HFSVPK_SW dir)

I also reported this error:
Error:
Setup could not register the OLE Control C:\WINNT\system32\danim.dll because of the following error:
LoadLibrary returned error 126 (7e).

This problem occurs if you slip IE6.0sp1-KB905915-Windows-2000-XP-x86-ENU hotfix, again with manual integration everything goes fine.

A small tip for the guys who leave SFC intact (that´s why I went to 2K): After installation you should browse you %Windir% for setuperr.log and see what really went wrong.

My error report is on page 2 for those interested.

Anyway hfslip at least works for WXP without problems.

Thunder

In all my tests, no problems occurred with slipstreaming those hotfixes you're talking about.

The WUA20 file should not go in HFSVPK_SW as it doesn't work with /Q:A /R:N switches.

That error you received with KB905915: did you get the error as a pop-up message or in setuperr.log? Sometimes, additional errors appear in setuperr.log that are not really major errors and are *supposed* to happen.

ThunderM...

You're the first to report this problem and we haven't experienced it yet. I did what I could. I happen to own a German copy of Windows XP but not of Windows 2000 so I can't diagnose this completely myself.

A new test release is in the works. It already ignores msxml3.dll and msxml3r.dll from WUA if the Update Rollup exists; this is OK since the version numbers are identical. I'm looking into the danim.dll issue now.

It would help if you gave me the following:

- version number and file size of danim.dll on the new installation (system32 folder)
- the latest HFSLIPWU.INF file (SOURCESS\I386)