Tomcat76

@antonio_king That's nice, but that won't fix the problem for "regular" MCE distributions. In these, the .NET 1.0/MC/Plus/Sonic components are installed from SYSOC.INF at which point .NET 1.1 is not installed yet. This will take some time to debug so MCE slipstreaming won't make it into the next final. HFSLIP 1.2.2-rc2 adds the CAT file of the msxml2sp6-kb887606 security update. Apparantly HFSLIP wasn't doing that before. This will fix the error for msxml2.dll, but not for msxml2r.dll. This is because msxml2r.dll is not part of the security update; msxml2r.dll is taken from msxml2.msi which doesn't contain a CAT file at all. I couldn't find a hotfix containing msxml2r.dll *and* a CAT file so the msxml2r.dll error can't be avoided unless you don't include msxml2.msi.

No problem. Hope it works for you now

You don't *have* to delete those 4 cab files. HFSLIP just ignores them so having them in the HFCABS folder doesn't do anything bad. But you should remove BDAXP.cab and dxnt.cab because HFSLIP does NOT ignore these.

As I said, Windows XP SP2 already comes with DirectX 9.0c. The *ONLY* update to the DirectX9 core of Windows XP SP2 that I know is freely available is the KB904706-v2 security update. The recent packages of DirectX9 contain the ORIGINAL DirectX 9.0c core plus some EXTRA files which are not part of the core. Since Windows XP SP2 already contains the original DirectX 9.0c, you can only add the KB904706 security update and the EXTRA files from the December package of DX9. HFSLIP supports the *d3dx9*, *d3dx10*, *xact* and *xinput* extras. From your log file, these are ignored: Apr2006_MDX1_x86.cab Apr2006_MDX1_x86_Archive.cab dxdllreg_x86.cab dxupdate.cab

A few things.... 1) The handling of the DX9 core hasn't been changed since HFSLIP version 1.0, so it's strange that 1.0.1 was problematic, 1.1.0 was OK, 1.2.0 was OK too and 1.2.1 is problematic again. 2) You say that you are slipstreaming DX9 but I can't derive that from the HFSLIP log file. 3) According to your log file, you are using XP SP2, which already comes with DX9c so there's no need to slipstream it. 4) Note aside: any reason why you're not including WindowsXP-KB904706-v2-x86-PLK.exe, a security update for DX9?

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.

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

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

HFSLIP has Windows setup install MsDrmClient.msi from SVCPACK.INF but not RmClientBackCompat.msi. Is it needed? The DRM update appears in Add/Remove programs so I'd think not. I suppose this can only be found out if the machine is logged on to a server...

BTW... The idea is not that you do this stripping manually every time. But I want to verify first if it rectifies the problem before I let HFSLIP do it automatically...

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

Well... That's weird. It's almost as if the name of the file matters... Can you verify that HFSLIP copies the right file into SVCPACK? HFSLIP takes any file in HF of which the name starts with "IE7-Windows" and the last one it encounters is recorded in the XPIE7 variable. This is done so all languages are supported. In the SVCPACK section, HF\%XPIE7% is copied into SOURCESS\I386\SVCPACK as IE7_INST.EXE. I can't believe that Windows setup would trip over an underscore, so the only thing I can think of that could've gone wrong is that HFSLIP took the wrong exe.

/integrate? There are posts all over that this doesn't work with the IE7 executable and I tested it myself too: I get an error message and that's it. How come it works for you?

If I remember well, someone once had a similar issue with wmp10.inf. It doesn't make sense to me though. This is what should be happening: 1) SYSOC.INF calls HFSLIPWU.INF 2) HFSLIPWU.INF calls the [DefaultInstall] section from HFSLP156.INF At no point there are requests for wmp*.inf so I don't understand why SysPrep (or a similar tool) causes Windows setup to look for it. Do you still get an error if you remove all instances of wmp11.inf from HFSLP156.INF?

HFSLIP supports these sources:1) Clean Windows source (without ANY updates or service packs) 2) Windows source with a service pack slipstreamed but NOTHING else (NO hotfixes, NO rollups, NOTHING) Then you don't need these cabs because the contained DLLs are NEW (they don't exist in an original Windows source).

Are you referring to the current test release?

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

OK. The folders are capitalized as well as the cab files that HFSLIP updates. This is by design. If the user has a more recent version of wmfdist95.exe in the HF folder he/she should not be forced to redownload it after running HFSLIP.

As I explained a few times above, HFSLIP can only work with a "bare" source or a source that's been updated with a service pack. Other sources won't work. The DX9-related files in your screenshot are OK, but HFSLIP ignores the *MDX1* file. So you can remove it. Just so you know... Those DX9 cab files are just extras -- they don't make up the core of DX9. Some games use the *d3dx9* files; I don't know if the other DX9 extras are already used for any purpose.

That wasn't my point. I was trying to answer your question about SP2. Those cab files go in HFCABS.

You don't have to remove the SP2 installer out of the HF folder. HFSLIP automatically detects if your source has already been patched with a specific service pack or not and will only slipstream it if necessary (ie, if your source is Gold, SP1 or SP1a).Your Windows source goes in the SOURCE folder. HFSLIP applies the service pack to the Windows source in the SOURCE folder. Hotfixes are processed and their contained files are extracted into a temporary folder. The source from SOURCE is then copied into SOURCESS. The files coming from the hotfixes are copied over into the source in SOURCESS. So after your first HFSLIP run, the source in your SOURCE folder will be XP with SP2 while the source in the SOURCESS folder will be the fully updated source. The second time you run HFSLIP, it will detect that the source in SOURCE already has SP2 so it will skip the part that slipstreams it.

IE7 is not slipstreamed because it creates problems. HFSLIP has Windows setup install it at first GUI logon. The main WMP11 installer that you download from the Microsoft server should be extracted into HF\WMP11. There should be no wmfdist11.exe in the HF folder and wmp11.exe from inside the WMP11 installer should not be extracted. directx_dec2006_redist.exe doesn't belong anywhere. It will cause problems. WindowsXP-Windows2000-Script56-KB917344-x86-sve.exe is not obsolete. It goes in HF as specified on every HFSLIP hotfix list. Please read through the web site as Super-Magician already pointed out.

This is for existing addon makers to see if HFSLIP would support their addon or not. Applies to HFSLIP 1.2.2 and newer. HFSLIP fully supports/parses the following sections: * txtsetup_files * txtsetup_files_home * txtsetup_fileflags * txtsetup_dirs * dosnet_files * dosnet_files_home * sysoc * editfile * filenames * addprogram * GuiRunOnce * FileMove * DirDelete HFSLIP partially supports the following sections: * txtsetup_files_pro (this is parsed for XP Pro but this doc says it's for any non-Home OS) * dosnet_files_pro (same) HFSLIP deliberately ignores the following sections: * AddDirective (HFSLIP automatically creates section headers in destination files if they don't exist) * svcpack_catalogs (catalog files are handled automatically by HFSLIP provided they exist in the SVCPACK folder) * i386_compress (files are automatically compressed unless they exist uncompressed in the source except for files in the ASMS folder) * obsolete (it is assumed the HFSLIP user knows which hotfixes are obsolete when they include an addon) Unsupported sections: * extrafileedits * txtsetup_remove (might conflict with other features of HFSLIP) * dosnet_remove (same) * registry_addreg (same) * registry_delreg (same) * obsolete_files (same) * ...

Yes, only cab files. They need to be extracted from the directx installer with an advanced decompression program (7-zip, WinRAR, etc.). But that still doesn't explain the presence of the Windows Script 5.6 update in your HFCABS folder...

Please make sure that your SOURCE folder is properly set up for MCE 2005. I just updated the description near the top of the main post in this thread.