O I see...
Isn't there a way for HFSLIP to mark whether wmfdist95.exe is already present and if it is, then replace it with the one from KB900325
If it isn't then del it after HFSLIP is finished?

Thanks for changing the CAPITAL stuff!

This post has been edited by antonio_king: Jan 4 2007, 05:30 AM

Doesn't CDIMAGE and MKISOFS do this automatically (or if not, with the right switches)?

@antonio_king, I believe HFSLIP already does that.

This post has been edited by Super-Magician: Jan 4 2007, 06:35 AM

@Super-Magician
If thats the case it's not working correctly for me.

Don't know about MKISOFS but you need an extra switch for this with CDIMAGE.

Are you referring to the current test release?

Just tried the newest release... works fine after all... ooops

Just want to report that AUTOIT support is working like a champ in 70102b. I have scripts for Wink and SimpleOCR if anyone is interested.

T H A N K Y O U!

@Tomcat: Is there any way that you can code HFSLIP to process KB900325 for non-MCE computers? The only difference would be to exclude the KB900325.exe file unless the source was MCE. This is especially useful as there are normal XP hotfixes included in the Rollup.

the_guy

@ the_guy
Surely if Microsoft saw these as vulnerabilities in a standard XP system they would have released the hotfixes for all XP flavours?

@antonio_king: The majority of them were released. A few don't even have a kb article. it just makes sense to me as they aren't MCE only updates anyway.

the_guy

KB900325 still shows up on Windows Update.

In fact, even after manually installing the KB900325 update all the other updates show up even though I slipstreamed them with HFSLIP?


Also have another REQUEST...

Could we have a folder within the FIX one for MEDIACTR,

So we can copy modified files and have it recabbed in the MEDIACTR.CAB when HFSLIP does this?
This would be a fantastic addtition imo as I have to copy over the Royale.Theme file after Install to use my custom icons.

thanks!

This post has been edited by antonio_king: Jan 5 2007, 10:28 AM

Look at the last few lines of the script.

Whoops!

Hehe.

This has been there for a while. I must've been playing with that section once.
It's harmless... Two lines of code that are never called.

I'll have it fixed in the next release.


Alright. I checked out MedCtrOC.log and noticed that the updated files rely on .NET 1.1 too much. I slipstreamed CasPol.exe, fusion.dll and ngen.exe, but that only got me error messages during Windows setup about missing dependent files. So I added mscorwks.dll and msvcr71.dll, which got me a failed copy at the beginning of Windows setup for mscorwks.dll. Ran MODIFYPE on it and tried again. Now it also needed machine.config, and one other error message popped up saying that "a resource could not be found in a resource file" or something like that... but no file name was mentioned. Added machine.config, which got rid of all errors except that one that doesn't reference a name. At this point, MedCtrOC.log complains about failing to install an assembly (SonicMMBurnEngine) and to turn off CasPol logging.

I'm now going to add those four files that I have HFSLIP remove from the .NET 1.0 update (HFSLIP removes them because the installation INF doesn't do anything with them). If this doesn't help either, it'll make things very difficult. I'll have to find out which .NET 1.1 files are a minimum requirement for the installation of the Media Center rollup.

BTW... It's time that MS release an update of the rollup. When installing it "normally", I noticed that it fails miserably if WMP11 is installed -- it displays an error, and when you click OK the installer quits and initiates a system restore. Why can't it just check if the WMP10 update is needed or not, and simply skip it if WMP11 is detected? Oh well....

What do you mean by "all the other updates"? Those within the rollup package or also the regular XP hotfixes?

I'll see if something can be done here, but it won't be with the FIX folder because that's intended for last minute changes. Most likely I'll just let you put it in the HFCABS folder. This isn't top priority now, though...

This post has been edited by Tomcat76: Jan 6 2007, 08:32 AM

@Tomcat: Microsoft states on there site that the rollup is required before wmp11 can be installed.

the_guy

These are all of the MCE updates windows update asks for on my installation...
WindowsXPMediaCenter2005-KB900325-usa
WindowsXPMediaCenter2005-KB925766-ENU
WindowsXP-KB912024-v2-x86-ENU

So those are the ones I slipstream.

When I run windows update it says KB900325 is missing.
As you said yourself the standard installer doesn't work if Windows Media Player 11 is installed so I extracted KB900325.exe and ran that file.

Windows update now says that it needs KB925766, KB912024 and Windows Media Player 11 for Media Center Edition.

Ah, OK. That's understandable. KB925766 and KB912024 update files which also exist in the main update rollup.

This rollup is really bad -- it replaces existing files that are newer when you install it...

Windows Media Player 11 for Media Center Edition? Whoops... I've been testing with the wrong version...


BTW... Adding in those four .NET 1.0 files from the NDP update didn't fix anything. This could take a loooong time to debug.....

Tomcat, are you using proper windows MCE discs or do u install MC from CMDLINES.TXT?

"Regular" MCE 2005, not cmdlines. The Media Center stuff is installed from SYSOC.INF in these.

Hi man, only a question. After I have installed the slipstreamed CD there are 3 errors in setuperr.log:
-Impossible to registrer OLE control C:\Windows\system32\macromed\flash\flash.ocx
-C:\windows\system32\msxml2.dll isn't correctly signed by microsoft
-C:\windows\system32\msxml2r.dll isn't correctly signed by microsoft

Anyone have these problems? I'm an italian user and I'm so sorry for my bad english.
I have used the latest hfslip for test (70105b version). I have attached the log of hfslip maybe someone can help. Thanks

This post has been edited by S3pHiroTh: Jan 6 2007, 01:37 PM

Your English is fine

The error for Flash 9 is normal. The registration part of the newest OCX from Adobe is just broken so we'll have to wait for them to release a new version. For Win2K and Win2K3 I even had to work around this otherwise an error dialog appeared during Windows setup. Weird that they haven't updated it yet... Who'd think anyone would slipstream Flash, right?

I know about the errors for MSXML2 but am not sure why they occur. HFSLIP is including the catalog file so I guess Windows setup uses these DLLs before it checks the catalog files.