I started with MCE 2005 and wound up with MCE 2004. So I checked Disc 2 \cmpnents\mediactr\i386\mediactr.cab pulled out ehshell.ex_, inflated it and checked the version number. They said MCE 2005… but a quick google told me that was MCE 2005 and that no references to MCE 2004 had even heard of. So I checked the disc’s (that I had never used before). Oh, wait a minute, that says “Windows XP Media Center Edition 2004” … (XP) 5512 (SP3’s build number) it worked!
Secondly, not being familiar with MCE for XP having never actually bothered to install the thing, it took me a few minutes to realise that this was so radically different from the Vista version that it looked more like the third party M圜inema Media Centre than screenshots that I have seen of the XP one.
Firstly, the plus pack and sonic plugins were missing from the system, this included the Royal XP skin that is supposed to be included with MCE. So it looked like it had worked… until after a couple of minutes of fiddling I realised that something looked very, very wrong (and no, not just the hashed up low-depth graphics).
Windows Malicious Software Removal Tool May 2008.
I immediately hit Windows Update and was offered nothing more than: On the start menu there was Media Center link and in clicking it the MCE initiator grumbled about the graphics card not being compatible with MCE (this was Virtual PC after all) but sure enough, MCE loaded. The install came up with OOBE and still no problems. The install got to 26 minutes, no problems, the install got to 10 minutes, no problems. So I abandoned the install and started again to ensure that I was not mixing file versions. Sure enough, the Virtual Machine installation took one look at the disc and was suddenly happy again. To test this theory, I halted the Virtual Machine that I had asking me for ehiEPG.dll, copied the contents of service pack \i386\root\cmpnents\mediactr\i386 into \cmpnents\mediactr\i386 of my slipstreamed build folder and recreated the disc 2 ISO image. My mistake here was not examining the files closer, because I assumed that perhaps there had been an issue with the slipstream script and the files had not been copied across to the delivery folder for disc 2 during the slipstream. Where are the files though?Įxtracting the SP3 installer reveals the files to be located within the Service Pack hierarchy in the location: The presence of new file is however understandable because of new files included in hot fixes to Media Centre Edition since XP SP2 was released in 2004.
The differences between the two installation file sets is quite clear, there are many files missing from the SP3 installer list and a hand full of files are new on the SP3 list. If you expand this file before you perform the slipstream with SP3 (using expand \MEDCTROC.IN_ c:\MEDCTROC.INI) and then do the same after the slipstream you will come up with a completely different set of results (shown in the table below). The Media Centre installer is conducted through a sub-file in the i386 folder called: MEDCTROC.IN_ When you perform the same action on a MCE 2005 media set, no changes are made to the cmpnents\mediactr\i386 folder on disc 2. When you slipstream XP SP3 onto Tablet PC Edition Media (which is the same as the MCE media minus the Sonic and Plus CAB’s), the Tablet PC components on CD 2 are updates as part of the slipstream. This one took me a frustratingly large amount of time to work out, but here is a rundown of how I have come to this conclusion. Windows XP Media Center 2005 – You cannot slipstream.Windows XP Media Center 2004 – You can slipstream.If you are looking for a short answer to your problem, here it is: If you check the Windows XP Slipstreamed Media, you will not be able to find the file ehiEPG.dll or ehiEPG.dl_ on the disc set. If you check the installation media, the file does not exist and you will be unable to install the Media Centre module with the Windows XP installation. Type the path where the file is located, and then click OK. The file ‘ehiEPG.dll’ on Windows XP Professional CD 2 is needed.