[RELEASE] Boooggy's WMP 11 direct integration solution
-
- Posts: 53
- Joined: Fri Dec 22, 2006 1:41 pm
I used WMP11 integrator V. .991 downloaded last night and hash verified. Used RVM integrator 1.5.3, hash Verified too. Updatepack and addos hashes verified before the integration. Everything went perfeclty when omiting that update. I'm goping to try it again tonight by downloading that update again, and I'll be replaying back with the results. In fact, I'm using last night integration for replaying back watching movies and listening to music right now.
SP3 integrationw as done by creating a shortcut and adding the -s switch and the path of the XPCD extraction.
SP3 integrationw as done by creating a shortcut and adding the -s switch and the path of the XPCD extraction.
Last edited by Broly10000 on Mon May 05, 2008 8:27 pm, edited 1 time in total.
Is there any difference between using /integrate vs [service pack] -s:[source]?bryanh wrote:Ok - I think this will answer all questions
1) Started from a clean XP Corp Gold
2) Slipstreamed SP3 from the command line with the /integrate command
3) Used WMP11 Integrator in integrate WMP11 - NO hotfixes as requested
Looking for a way to post requested files
An FC /b on all the files says that they are the same.Fragbert wrote:Is there any difference between using /integrate vs [service pack] -s:[source]?bryanh wrote:Ok - I think this will answer all questions
1) Started from a clean XP Corp Gold
2) Slipstreamed SP3 from the command line with the /integrate command
3) Used WMP11 Integrator in integrate WMP11 - NO hotfixes as requested
Looking for a way to post requested files
-
- Posts: 53
- Joined: Fri Dec 22, 2006 1:41 pm
boooggy wrote:broly
that fix, 946665 is broken from microsoft. please redownload and please try first running it to see if its working. then integrate.
the err u are getting is cause of that hotfix.
Thats right, tried it as you said it and it worked. So now i have SP3 slipstreamed, WMP11 with all the updates and IE7 with all the updates. And after running the latest .Net silent installer posted here, the only thing left in WU is root certificates and silverlight.
like i said before.....my site contains all fixes that microsoft issued for wmp11. and all links are directly from microsoft.
as for sp3
i did like this:
used nlite
slisptreamed updatepack, some addons, ie7 and wmp11 plus wmp fixes.
then removed some things
then made the unattended and used all patches from patched files page from nlite.
then created iso and installed.
as for sp3
i did like this:
used nlite
slisptreamed updatepack, some addons, ie7 and wmp11 plus wmp fixes.
then removed some things
then made the unattended and used all patches from patched files page from nlite.
then created iso and installed.
- nonno fabio
- Posts: 1627
- Joined: Mon Jun 06, 2005 10:36 am
- Location: Northern Italy
- Contact:
try to add these lines in the Slipstreamer equivalent of entries.ini
This should solve the problems caused by SP3 (when you must add files from .inf, XP now uses wbemoc.inf in place of sysoc.inf, but wbemoc is not executed during setup).
It is Onepiece stuff, not mine, so please don't ask me about
Code: Select all
[EditFile]
I386\WBEMOC.INF,SourceDisksNames,WBEMOC_SDN
I386\WBEMOC.INF,SourceDisksFiles,WBEMOC_SDF
[ExpandCab]
I386\napprov.mo_,\I386
I386\napschem.mo_,\I386
[WBEMOC_SDN]
1="Windows XP SP3 CD/DVD-ROM","WIN51",,"i386"
[WBEMOC_SDF]
napclientprov.mof=1
napclientschema.mof=1
It is Onepiece stuff, not mine, so please don't ask me about

Don't ask for a different configuration of Onepiece's XP AIO Update Pack: use one of the existing vanilla XP UpdatePack with your preferred addons instead
-
- Posts: 53
- Joined: Fri Dec 22, 2006 1:41 pm
ace_neo wrote:Broly10000 could u post procedure how u slipstreamed WMP11 with all the updates?
Do boogy site contains all updates of wmp 11 in sp3?
from which source of information u achieved stability of wmp11 in sp3?
I used tweked inetegration, selected all the updates in booggy's page, changed the icon to the vista icon, and thats it, nothing else selected. It worked for me with the SFC enabled. I dont use hacked files on my install, other than the theme file and i change that after the installation to add a couple of thing to make XP looks like vista, look for vistamizer. If you need more details of the rest, look at my 2 previews posts or PM me.
-
- Posts: 227
- Joined: Fri Jan 12, 2007 8:07 am
I am happy to say that my initial test worked. I used the Addon from here first and then WMP11 Integrator. And it looks good - going to do some more tests and will report back.boooggy wrote:bryan
after lookin into setupapi.log ...it seems that setup still cries out about napclientprov.mof.
so please try with the fix i posted and then please resend me those files...without txtsetup.
thank you.
UPDATE : Everything is working just fine now. Thank you for all your help.
Thank you
Bryan
WMP11 Slipstreamer v0.991 Bug Report.
---
Unhandled Exception
KB929399.exe
KB929773.exe
KB932390.exe
KB933547.exe
KB935551.exe
KB935552.exe
KB939209.exe
KB939683.exe
KB941569.exe
KB942264.exe
KB944110.exe
KB944882.exe
KB946665.exe
System.ComponentModel.Win32Exception: %1 is not a valid Win32 application
at Epsilon.Win32.Resources.ResourceEditor.throwWin32Exception()
at Epsilon.Win32.Resources.ResourceEditor.loadResourceLibrary()
at WMP11Slipstreamer.CM.GetCabData(String pathToSfxCab)
at WMP11Slipstreamer.Backend.NativeExtractHotfix(String hotfixInstaller, String destinationPath)
at WMP11Slipstreamer.Backend.standardHotfixApply(String fixesFolder, Dictionary`2 hotfixFileDictionary)
at WMP11Slipstreamer.Backend.ApplyFixes()
at WMP11Slipstreamer.MainGUI.workerMethod(Object addonSettings)
Deleting "D:\xp-nlite\i386\wmp11temp"... Done!
The source being modified has not been damaged.
All changes have been successfully reverted.
---
What I used was a clean Windows XP x86 SP0 VLK (corp) ENU source, with SP3 slipstreamed the official Microsoft way (e.g. applying SP3 with the /integrate switch). nLite and/or RVMIntegrator were not even used at this point, and no custom winnt.sif or anything else for that matter either. All I used was the original VLK CDROM and the SP3 x86 RTM build 5512 that was officially re-released yesterday.
After that I tried it again, this time having nLite integrate the earlier posted NR_WBEM_Fix_AddOn.7z fix and SFC set to disabled. This gave the same "Unhandled Exception" error as with the earlier used clean XP/SP3 source. BTW, this is the first time I have an issue with WMP11 Slipstreamer.
---
Unhandled Exception
KB929399.exe
KB929773.exe
KB932390.exe
KB933547.exe
KB935551.exe
KB935552.exe
KB939209.exe
KB939683.exe
KB941569.exe
KB942264.exe
KB944110.exe
KB944882.exe
KB946665.exe
System.ComponentModel.Win32Exception: %1 is not a valid Win32 application
at Epsilon.Win32.Resources.ResourceEditor.throwWin32Exception()
at Epsilon.Win32.Resources.ResourceEditor.loadResourceLibrary()
at WMP11Slipstreamer.CM.GetCabData(String pathToSfxCab)
at WMP11Slipstreamer.Backend.NativeExtractHotfix(String hotfixInstaller, String destinationPath)
at WMP11Slipstreamer.Backend.standardHotfixApply(String fixesFolder, Dictionary`2 hotfixFileDictionary)
at WMP11Slipstreamer.Backend.ApplyFixes()
at WMP11Slipstreamer.MainGUI.workerMethod(Object addonSettings)
Deleting "D:\xp-nlite\i386\wmp11temp"... Done!
The source being modified has not been damaged.
All changes have been successfully reverted.
---
What I used was a clean Windows XP x86 SP0 VLK (corp) ENU source, with SP3 slipstreamed the official Microsoft way (e.g. applying SP3 with the /integrate switch). nLite and/or RVMIntegrator were not even used at this point, and no custom winnt.sif or anything else for that matter either. All I used was the original VLK CDROM and the SP3 x86 RTM build 5512 that was officially re-released yesterday.
After that I tried it again, this time having nLite integrate the earlier posted NR_WBEM_Fix_AddOn.7z fix and SFC set to disabled. This gave the same "Unhandled Exception" error as with the earlier used clean XP/SP3 source. BTW, this is the first time I have an issue with WMP11 Slipstreamer.
Code: Select all
WMP11Slipstreamer v0.991
Detected source: Windows™ XP Professional SP3
Hotfixes:
windowsmedia11-kb946665-x86-intl.exe
WindowsXP-KB941569-x86-ENU.EXE
windowsmedia11-kb928788-x86-intl.exe
windowsmedia11-kb929399-v2-x86-intl.exe
windowsmedia11-kb929773-x86-intl.exe
windowsmedia11-kb932390-x86-intl.exe
windowsmedia11-kb933547-x86-intl.exe
windowsmedia11-kb935551-x86-intl.exe
windowsmedia11-kb935552-x86-intl.exe
windowsmedia11-kb939209-x86-intl.exe
WindowsMedia11-KB939683-x86-ENU.exe
windowsmedia11-kb942264-x86-intl.exe
windowsmedia11-kb944110-x86-intl.exe
windowsmedia11-kb944882-x86-intl.exe
System.ComponentModel.Win32Exception: %1 is not a valid Win32 application
at Epsilon.Win32.Resources.ResourceEditor.throwWin32Exception()
at Epsilon.Win32.Resources.ResourceEditor.loadResourceLibrary()
at WMP11Slipstreamer.CM.GetCabData(String pathToSfxCab)
at WMP11Slipstreamer.Backend.NativeExtractHotfix(String hotfixInstaller, String destinationPath)
at WMP11Slipstreamer.Backend.standardHotfixApply(String fixesFolder, Dictionary`2 hotfixFileDictionary)
at WMP11Slipstreamer.Backend.ApplyFixes()
at WMP11Slipstreamer.MainGUI.workerMethod(Object addonSettings)
Deleting "C:\Documents and Settings\Administrator\Desktop\WinXP_Custom\i386\wmp11temp"... Done!
The source being modified has not been damaged.
All changes have been successfully reverted.
If I do it with out the hotfixes it works perfectly.
Okay, thank you for mentioning. I will try again without KB946665. However, it might be a good idea to mention this on Boooggy's site since nothing is mentioned there, despite KB946665 is listed.n7Epsilon wrote:All who are having this problem, this has been solved many times before, please look again at the first post in the thread for information about KB946665.exe (being corrupt from MS server).

-
- Posts: 53
- Joined: Fri Dec 22, 2006 1:41 pm
First of all I am not 100% sure this error is caused by your addon but i only get this error when i use a install with wmp11 slipstreamed.
I get the following error in qfecheck:
KB947864: This hotfix should be reinstalled.
The following files are incorrect for this hotfix:
C:\WINDOWS\SYSTEM32\BROWSEUI.DLL
C:\WINDOWS\SYSTEM32\SHLWAPI.DLL
C:\WINDOWS\SYSTEM32\SHDOCVW.DLL
The following files are not valid in the system catalog:
C:\WINDOWS\SYSTEM32\WININET.DLL
C:\WINDOWS\SYSTEM32\URLMON.DLL
C:\WINDOWS\SYSTEM32\DXTRANS.DLL
C:\WINDOWS\SYSTEM32\DXTMSFT.DLL
C:\WINDOWS\SYSTEM32\EXTMGR.DLL
C:\WINDOWS\SYSTEM32\PNGFILT.DLL
C:\WINDOWS\SYSTEM32\MSTIME.DLL
C:\WINDOWS\SYSTEM32\MSRATING.DLL
C:\WINDOWS\SYSTEM32\MSHTMLED.DLL
C:\WINDOWS\SYSTEM32\JSPROXY.DLL
I downloaded the hotfix manually and re-installed it:
now i only get the following errors:
KB947864: This hotfix should be reinstalled.
The following files are incorrect for this hotfix:
C:\WINDOWS\SYSTEM32\BROWSEUI.DLL
C:\WINDOWS\SYSTEM32\SHLWAPI.DLL
C:\WINDOWS\SYSTEM32\SHDOCVW.DLL
So the Catalog errors are gone.
When I do an install without the wmp11 slipstream i don`t get this error so maybe anybody here knows what i should do to fix these errors?
Thanks!
I get the following error in qfecheck:
KB947864: This hotfix should be reinstalled.
The following files are incorrect for this hotfix:
C:\WINDOWS\SYSTEM32\BROWSEUI.DLL
C:\WINDOWS\SYSTEM32\SHLWAPI.DLL
C:\WINDOWS\SYSTEM32\SHDOCVW.DLL
The following files are not valid in the system catalog:
C:\WINDOWS\SYSTEM32\WININET.DLL
C:\WINDOWS\SYSTEM32\URLMON.DLL
C:\WINDOWS\SYSTEM32\DXTRANS.DLL
C:\WINDOWS\SYSTEM32\DXTMSFT.DLL
C:\WINDOWS\SYSTEM32\EXTMGR.DLL
C:\WINDOWS\SYSTEM32\PNGFILT.DLL
C:\WINDOWS\SYSTEM32\MSTIME.DLL
C:\WINDOWS\SYSTEM32\MSRATING.DLL
C:\WINDOWS\SYSTEM32\MSHTMLED.DLL
C:\WINDOWS\SYSTEM32\JSPROXY.DLL
I downloaded the hotfix manually and re-installed it:
now i only get the following errors:
KB947864: This hotfix should be reinstalled.
The following files are incorrect for this hotfix:
C:\WINDOWS\SYSTEM32\BROWSEUI.DLL
C:\WINDOWS\SYSTEM32\SHLWAPI.DLL
C:\WINDOWS\SYSTEM32\SHDOCVW.DLL
So the Catalog errors are gone.
When I do an install without the wmp11 slipstream i don`t get this error so maybe anybody here knows what i should do to fix these errors?
Thanks!
Just ran several test installs.
Windows XP SP3 slipstreamed (nLite)
DriverPacks Base 8.05 (w/all recent updated hardware drivers)
RyamVM 1.5.3
DirectX_9.0c_End-User_Runtime_AddOn_0.3.3_-_redxii
DotNetFx_All_In_1_Addon_v2
NR_IE7en_Addon_1.1.1
NR_WBEM_Fix_AddOn
WMP Slipstreamer (w/all currently listed Hot Fixes)
nLite Unattended, Tweaks and ISO build.
All tests resulted in flawless installations.
Thanks to Ryan, Signet, boooggy, redxii, MrNxDmX, Bâshrat the Sneaky, nuhi, and all who have contributed to this success.
Special thanks to the forum members for testing and responding with pertinent input.
Windows XP SP3 slipstreamed (nLite)
DriverPacks Base 8.05 (w/all recent updated hardware drivers)
RyamVM 1.5.3
DirectX_9.0c_End-User_Runtime_AddOn_0.3.3_-_redxii
DotNetFx_All_In_1_Addon_v2
NR_IE7en_Addon_1.1.1
NR_WBEM_Fix_AddOn
WMP Slipstreamer (w/all currently listed Hot Fixes)
nLite Unattended, Tweaks and ISO build.
All tests resulted in flawless installations.
Thanks to Ryan, Signet, boooggy, redxii, MrNxDmX, Bâshrat the Sneaky, nuhi, and all who have contributed to this success.
Special thanks to the forum members for testing and responding with pertinent input.
A Bug report
WMP11Slipstreamer v0.991
Detected source: Windows™ XP Professional SP2
Hotfixes:
WindowsXP-KB941569-x86-ENU.EXE
windowsmedia11-kb928788-x86-intl.exe
windowsmedia11-kb929773-x86-intl.exe
windowsmedia11-kb932390-x86-intl.exe
windowsmedia11-kb933547-x86-intl.exe
windowsmedia11-kb935551-x86-intl.exe
windowsmedia11-kb935552-x86-intl.exe
windowsmedia11-kb939209-x86-intl.exe
WindowsMedia11-KB939683-x86-ENU.exe
windowsmedia11-kb942264-x86-intl.exe
windowsmedia11-kb944110-x86-intl.exe
windowsmedia11-kb944882-x86-intl.exe
windowsmedia11-kb946665-x86-intl.exe
System.ComponentModel.Win32Exception: The system cannot find the file specified
at Epsilon.Win32.Resources.ResourceEditor.throwWin32Exception()
at Epsilon.Win32.Resources.ResourceEditor.loadResourceLibrary()
at WMP11Slipstreamer.CM.GetCabData(String pathToSfxCab)
at WMP11Slipstreamer.Backend.NativeExtractHotfix(String hotfixInstaller, String destinationPath)
at WMP11Slipstreamer.Backend.ExtractWMP11Installer()
at WMP11Slipstreamer.MainGUI.workerMethod(Object addonSettings)
Deleting "F:\Ryanvm\New\i386\wmp11temp"... Done!
The source being modified has not been damaged.
All changes have been successfully reverted.
WMP11Slipstreamer v0.991
Detected source: Windows™ XP Professional SP2
Hotfixes:
WindowsXP-KB941569-x86-ENU.EXE
windowsmedia11-kb928788-x86-intl.exe
windowsmedia11-kb929773-x86-intl.exe
windowsmedia11-kb932390-x86-intl.exe
windowsmedia11-kb933547-x86-intl.exe
windowsmedia11-kb935551-x86-intl.exe
windowsmedia11-kb935552-x86-intl.exe
windowsmedia11-kb939209-x86-intl.exe
WindowsMedia11-KB939683-x86-ENU.exe
windowsmedia11-kb942264-x86-intl.exe
windowsmedia11-kb944110-x86-intl.exe
windowsmedia11-kb944882-x86-intl.exe
windowsmedia11-kb946665-x86-intl.exe
System.ComponentModel.Win32Exception: The system cannot find the file specified
at Epsilon.Win32.Resources.ResourceEditor.throwWin32Exception()
at Epsilon.Win32.Resources.ResourceEditor.loadResourceLibrary()
at WMP11Slipstreamer.CM.GetCabData(String pathToSfxCab)
at WMP11Slipstreamer.Backend.NativeExtractHotfix(String hotfixInstaller, String destinationPath)
at WMP11Slipstreamer.Backend.ExtractWMP11Installer()
at WMP11Slipstreamer.MainGUI.workerMethod(Object addonSettings)
Deleting "F:\Ryanvm\New\i386\wmp11temp"... Done!
The source being modified has not been damaged.
All changes have been successfully reverted.
new version!
change log for 1.2:
1. Complete rewrite of ini file editor, massive file editing speed increase (SimpleIniEditor renamed to IniParser)
2. Complete rewrite of cabinet.dll interface, problems with COMODO Defense+ fixed, now x64 compatible (can be compiled and work with 64-bit cabinet.dll)
3. Complete separation of Backend from user interface, switch to events. Cross-thread dialogs now open with the main window as its owner correctly.
4. Cleaned up Backend error handling.
5. Removal of embedded uxtheme.dll and msobmain.dll hotfixes. Slipstreamer will break unattended and display a warning if it finds that uxtheme or msobmain need updating, integrate those fixes before running the slipstreamer to avoid this.
6. Updated to support Windows XP Service Pack 3 (automatically applies wbem fix if required)
7. Fixed issues on x64 WMP11
8. Fixed issue presented here
change log for 1.2:
1. Complete rewrite of ini file editor, massive file editing speed increase (SimpleIniEditor renamed to IniParser)
2. Complete rewrite of cabinet.dll interface, problems with COMODO Defense+ fixed, now x64 compatible (can be compiled and work with 64-bit cabinet.dll)
3. Complete separation of Backend from user interface, switch to events. Cross-thread dialogs now open with the main window as its owner correctly.
4. Cleaned up Backend error handling.
5. Removal of embedded uxtheme.dll and msobmain.dll hotfixes. Slipstreamer will break unattended and display a warning if it finds that uxtheme or msobmain need updating, integrate those fixes before running the slipstreamer to avoid this.
6. Updated to support Windows XP Service Pack 3 (automatically applies wbem fix if required)
7. Fixed issues on x64 WMP11
8. Fixed issue presented here
-
- Posts: 6
- Joined: Wed Nov 28, 2007 4:04 pm
Got this with new version. Have tested all dowmloaded hotfixes; all install OK (not corrupted).
WMP11Slipstreamer v1.2.0.0
Detected source: Windows™ XP Professional SP2
Hotfixes:
WindowsXP-KB941569-x86-ENU.EXE
windowsmedia11-kb928788-x86-intl.exe
windowsmedia11-kb929399-v2-x86-intl.exe
windowsmedia11-kb929773-x86-intl.exe
windowsmedia11-kb932390-x86-intl.exe
windowsmedia11-kb933547-x86-intl.exe
windowsmedia11-kb935551-x86-intl.exe
windowsmedia11-kb935552-x86-intl.exe
windowsmedia11-kb939209-x86-intl.exe
WindowsMedia11-KB939683-x86-ENU.exe
windowsmedia11-kb942264-x86-intl.exe
windowsmedia11-kb944110-x86-intl.exe
windowsmedia11-kb944882-x86-intl.exe
windowsmedia11-kb946665-x86-intl.exe
Epsilon.Parsers.IniParser+Exceptions+MalformedLineException: [SetupHotfixesToRun] contains a malformed line: (wmfdist95.exe /Q:A /R:N /C:"wmsetsdk.exe /WMFDIST /Q /R:N /DisallowSystemRestore). Line number: 219. Identifier: Svcpack.Inf
at Epsilon.Parsers.IniParser.ParseIniCore(TextReader textReader, Boolean throwForMalformedLines, String firstSectionName, Boolean allowSections)
at Epsilon.Parsers.IniParser.Init(TextReader iniStream, Boolean throwFormatExceptionForMalformedLines)
at Epsilon.Parsers.IniParser..ctor(String filePath, Boolean throwForMalformedLines)
at WMP11Slipstreamer.Backend.PrepareForParse()
at WMP11Slipstreamer.Backend.SlipstreamWMP11()
at WMP11Slipstreamer.MainForm.WorkerMethod(Object workerParam)
Deleting "G:\MCE2005SP2\i386\wmp11temp"... Done!
The source being modified has not been damaged.
All changes have been successfully reverted.
WMP11Slipstreamer v1.2.0.0
Detected source: Windows™ XP Professional SP2
Hotfixes:
WindowsXP-KB941569-x86-ENU.EXE
windowsmedia11-kb928788-x86-intl.exe
windowsmedia11-kb929399-v2-x86-intl.exe
windowsmedia11-kb929773-x86-intl.exe
windowsmedia11-kb932390-x86-intl.exe
windowsmedia11-kb933547-x86-intl.exe
windowsmedia11-kb935551-x86-intl.exe
windowsmedia11-kb935552-x86-intl.exe
windowsmedia11-kb939209-x86-intl.exe
WindowsMedia11-KB939683-x86-ENU.exe
windowsmedia11-kb942264-x86-intl.exe
windowsmedia11-kb944110-x86-intl.exe
windowsmedia11-kb944882-x86-intl.exe
windowsmedia11-kb946665-x86-intl.exe
Epsilon.Parsers.IniParser+Exceptions+MalformedLineException: [SetupHotfixesToRun] contains a malformed line: (wmfdist95.exe /Q:A /R:N /C:"wmsetsdk.exe /WMFDIST /Q /R:N /DisallowSystemRestore). Line number: 219. Identifier: Svcpack.Inf
at Epsilon.Parsers.IniParser.ParseIniCore(TextReader textReader, Boolean throwForMalformedLines, String firstSectionName, Boolean allowSections)
at Epsilon.Parsers.IniParser.Init(TextReader iniStream, Boolean throwFormatExceptionForMalformedLines)
at Epsilon.Parsers.IniParser..ctor(String filePath, Boolean throwForMalformedLines)
at WMP11Slipstreamer.Backend.PrepareForParse()
at WMP11Slipstreamer.Backend.SlipstreamWMP11()
at WMP11Slipstreamer.MainForm.WorkerMethod(Object workerParam)
Deleting "G:\MCE2005SP2\i386\wmp11temp"... Done!
The source being modified has not been damaged.
All changes have been successfully reverted.
Been using this for over a year now, but I'm still having the same trouble I've had from the beginning: This slipstreamer borks DRM somehow.
The problem is with media sharing: WMPNetworkSvc Event ID 14344: WMCreateDeviceRegistration() encountered error '0xc00d2711'. The Windows Media DRM components on your computer might be corrupted.
Have had this problem without fail on every WMP11 slipstreamed disc since mid 2007. My usual fix is WMP reinstallation + luck, but I tried to fix without reinstalling this time.
http://drmlicense.one.microsoft.com/Ind ... ndivit.asp doesn't work because it reports DRM error. So I tracked down the fix it downloads "IndivIt211.wma" and when I run that it says "Windows Media Player is not installed properly. Reinstall the Player."
The problem is with media sharing: WMPNetworkSvc Event ID 14344: WMCreateDeviceRegistration() encountered error '0xc00d2711'. The Windows Media DRM components on your computer might be corrupted.
Have had this problem without fail on every WMP11 slipstreamed disc since mid 2007. My usual fix is WMP reinstallation + luck, but I tried to fix without reinstalling this time.
http://drmlicense.one.microsoft.com/Ind ... ndivit.asp doesn't work because it reports DRM error. So I tracked down the fix it downloads "IndivIt211.wma" and when I run that it says "Windows Media Player is not installed properly. Reinstall the Player."
-
- Posts: 6
- Joined: Wed Nov 28, 2007 4:04 pm
Thanks, that's from MCE2005 Rollup2, which I didn't realize had the WMP updates (duh) and had integrated w/ nLite before the WMP11 slipstream. Will try again another way.boooggy wrote:your source have already integrated hotfixes ....i am talking about wmfdist95.exe whinch is a fix for wmp 9 and wmp10. and the command line is incorect wmfdist95.exe /Q:A /R:N /C:"wmsetsdk.exe /WMFDIST /Q /R:N /DisallowSystemRestore. its missing a quote .....thats why slisptreamer had this err.
...and thanks for all your fine work, boooggy.
What do you mean... I use the slipstreamer. WMP works fine and everything appears normal until I enable media sharing. At which time media sharing doesn't work but every other aspect of WMP is fine.boooggy wrote:rootworn
please let me know what exactly u do .....cause i dont have this problem.
You've never had trouble using WMP with a Windows Media Center Extender?
- roirraWedorehT
- Posts: 763
- Joined: Sun Oct 15, 2006 2:25 pm
Have you tried the same setup recently but without using WMP11 Slipstreamer? In other words, by installing WMP11 manually after XP is installed?rootworm wrote:What do you mean... I use the slipstreamer. WMP works fine and everything appears normal until I enable media sharing. At which time media sharing doesn't work but every other aspect of WMP is fine.boooggy wrote:rootworn
please let me know what exactly u do .....cause i dont have this problem.
You've never had trouble using WMP with a Windows Media Center Extender?
This not a bug. This is the correct (proper) formatting for the INF according to Microsoft INF rules. Everyone should use quotes properly. When IniParser saves an INI. It normalizes the INF to use proper INF formatting rules. (a little like TidyHTML)
If the silent installer doesn't work, then it could be a bug that MS doesn't follow their own rules and I will try to make an exception to treat this section differently when saving, but if it works, then I am correct and I will not remove this behavior (in that case, people will need to learn to do things the right way).
@rootworm: I do not have Windows Media Center extender or MCE2005 to test this. I am caught up in exams at the moment, when I'm done with them, maybe I'll PM you so we can test this a little better.
If the silent installer doesn't work, then it could be a bug that MS doesn't follow their own rules and I will try to make an exception to treat this section differently when saving, but if it works, then I am correct and I will not remove this behavior (in that case, people will need to learn to do things the right way).
@rootworm: I do not have Windows Media Center extender or MCE2005 to test this. I am caught up in exams at the moment, when I'm done with them, maybe I'll PM you so we can test this a little better.
I can confirm that putting the line in quotes does work. I have the following:n7Epsilon wrote:This not a bug. This is the correct (proper) formatting for the INF according to Microsoft INF rules. Everyone should use quotes properly. When IniParser saves an INI. It normalizes the INF to use proper INF formatting rules. (a little like TidyHTML)
If the silent installer doesn't work, then it could be a bug that MS doesn't follow their own rules and I will try to make an exception to treat this section differently when saving, but if it works, then I am correct and I will not remove this behavior (in that case, people will need to learn to do things the right way).
Code: Select all
[SetupHotfixesToRun]
"SUNJAVA.EXE -ai"
SPTD.EXE add /q
-- Jondar
- roirraWedorehT
- Posts: 763
- Joined: Sun Oct 15, 2006 2:25 pm
this isn't causing errors but its a bit unexpected!
this was triggered only when " -*" switch was used, which is mostly common with some of RogueSpear's new installers!
also, if i had to integrate "the same thing" for some reason after using the slipstreamer, I would get 2 versions of the same line (quoted and unquoted)
these are the only things to consider when warping the issue around ...
great work & congrats
this was triggered only when " -*" switch was used, which is mostly common with some of RogueSpear's new installers!

also, if i had to integrate "the same thing" for some reason after using the slipstreamer, I would get 2 versions of the same line (quoted and unquoted)
these are the only things to consider when warping the issue around ...
great work & congrats
this is for my bad explaining! 
i was referring to integrator or nlite, when it so happens that someone can over integrate the same file more then once..
& as in this case:
once before slipstreamer is used and once after ..
where i think integrator or nlite wont recognize "that" and then add the "same" unquoted...

i was referring to integrator or nlite, when it so happens that someone can over integrate the same file more then once..
& as in this case:
once before slipstreamer is used and once after ..
where i think integrator or nlite wont recognize "that" and then add the "same" unquoted...
[quote="roirraW "edor""]
Yes. It's fine if I install manually with no slipstream. Also of note is DRM folder is empty with WMP11 slipstream. It shouldn't be empty. (I don't think it was empty on SP2 disks, but I'm not certain)
edit - I just built an MSI of WMP11 + all updates. It installs fine and media sharing is working so I guess I'll stick with the MSI for now.
Have you tried the same setup recently but without using WMP11 Slipstreamer? In other words, by installing WMP11 manually after XP is installed?[/quote]rootworm wrote:What do you mean... I use the slipstreamer. WMP works fine and everything appears normal until I enable media sharing. At which time media sharing doesn't work but every other aspect of WMP is fine.boooggy wrote:rootworn
please let me know what exactly u do .....cause i dont have this problem.
You've never had trouble using WMP with a Windows Media Center Extender?
Yes. It's fine if I install manually with no slipstream. Also of note is DRM folder is empty with WMP11 slipstream. It shouldn't be empty. (I don't think it was empty on SP2 disks, but I'm not certain)
edit - I just built an MSI of WMP11 + all updates. It installs fine and media sharing is working so I guess I'll stick with the MSI for now.
Last edited by rootworm on Mon May 19, 2008 4:53 am, edited 2 times in total.
good app I used it on my recent sp3 test cd. Seems to have all worked but the hotfixes which I integrated after it using nlite do not show as installed hotfixes does anyone know if thats how its supposed to be?
Also as some feedback I got confused by the instructions for nlite, they say to add the installer inside nlite which I did and caused an error it meant the wmp11 exe file. Not the wmp11 slipstreamer.
Also as some feedback I got confused by the instructions for nlite, they say to add the installer inside nlite which I did and caused an error it meant the wmp11 exe file. Not the wmp11 slipstreamer.
- roirraWedorehT
- Posts: 763
- Joined: Sun Oct 15, 2006 2:25 pm
Hotfixes for WMP11 or just in general - for SP3??? I would assume you mean for WMP11, however, you should have the WMP11 Slipstreamer integrating both WMP11 and all of it's current hotfixes listed on the WMP11 Slipstreamer home page, so there wouldn't be any need to integrate them separately using nLite.Chrysalis wrote:good app I used it on my recent sp3 test cd. Seems to have all worked but the hotfixes which I integrated after it using nlite do not show as installed hotfixes does anyone know if thats how its supposed to be?
Someone else may have to answer this as I use the WMP11 Slipstreamer as a separate application.Chrysalis wrote:Also as some feedback I got confused by the instructions for nlite, they say to add the installer inside nlite which I did and caused an error it meant the wmp11 exe file. Not the wmp11 slipstreamer.
What I do know is that you have to have the WMP11 Slipstreamer installed, but I would think that you had done that. That's why I alleviate all confusion on my part and just use the WMP11 Slipstreamer separately, but I've just been too lazy to learn how to use it properly through nLite.
@enu_user: Then nLite and/or integrator need to get better then and start coding more robust ini parsers then. If you are afraid of this then use wmp11slip at the end.
I think the quotes issue is more of a problem only in RunPreSetupCommands, RunPostSetupCommands and SetupHotfixesToRun where everybody seems to be doing it wrong, but for txtsetup.sif, dosnet.inf ... etc. this will not be a problem because file list sections don't use quotes by definition (Because no dangerous characters like = / \ * , ... etc.) so it will never cause the problems you described.
Also, no one should go about integrating the same things over and over (at least with the current integrator status) since I don't think any one is equipped to handle this well.
- For WMP11 hotfixes, we do not add registry entries to show Windows that the hotfixes have been installed because (Thankfully) Windows Update is smart enough to check the actual file version, so if no wmp fixes show on windows update, the fixes were integrated correctly.
boooggy tests this very well before each release (checking file versions and hotfix integration).
I think the quotes issue is more of a problem only in RunPreSetupCommands, RunPostSetupCommands and SetupHotfixesToRun where everybody seems to be doing it wrong, but for txtsetup.sif, dosnet.inf ... etc. this will not be a problem because file list sections don't use quotes by definition (Because no dangerous characters like = / \ * , ... etc.) so it will never cause the problems you described.
Also, no one should go about integrating the same things over and over (at least with the current integrator status) since I don't think any one is equipped to handle this well.
- For WMP11 hotfixes, we do not add registry entries to show Windows that the hotfixes have been installed because (Thankfully) Windows Update is smart enough to check the actual file version, so if no wmp fixes show on windows update, the fixes were integrated correctly.
boooggy tests this very well before each release (checking file versions and hotfix integration).
- roirraWedorehT
- Posts: 763
- Joined: Sun Oct 15, 2006 2:25 pm
Yeah, amazingly MU (in contrast to WU) appears to know about the hotfixes too. I would assume that MU is still ignorant when it comes to Office 2003 hotfix integrations, as it used to be, whereas WU was smart with them.n7Epsilon wrote:- For WMP11 hotfixes, we do not add registry entries to show Windows that the hotfixes have been installed because (Thankfully) Windows Update is smart enough to check the actual file version, so if no wmp fixes show on windows update, the fixes were integrated correctly.
I wonder why MU would recognize WMP11's hotfixes but not Office 2003's?
Can anyone else test WMP11 media sharing with this slipstreamer?
If you can please start WMP11, click the Library button and select Media Sharing and check "Share my media". On the next screen that pops up just hit OK.
After that start Event Viewer and check the System tab for WMPNetworkSvc events.
You don't need to have a media device on the network to test it, if everything is working you will have event 14206.
(Note that SSDP Discovery Service cannot be disabled)
If you can please start WMP11, click the Library button and select Media Sharing and check "Share my media". On the next screen that pops up just hit OK.
After that start Event Viewer and check the System tab for WMPNetworkSvc events.
You don't need to have a media device on the network to test it, if everything is working you will have event 14206.
(Note that SSDP Discovery Service cannot be disabled)
Yes, this feature works. I performed exactly the steps you laid out. (Well, that is after I re-enabled SSDP.)rootworm wrote:Can anyone else test WMP11 media sharing with this slipstreamer?
If you can please start WMP11, click the Library button and select Media Sharing and check "Share my media". On the next screen that pops up just hit OK.
After that start Event Viewer and check the System tab for WMPNetworkSvc events.
You don't need to have a media device on the network to test it, if everything is working you will have event 14206.
(Note that SSDP Discovery Service cannot be disabled)
As a note to the above working, my install is setup like this:
- 1. Start out with an original SP2 slipstreamed source.
2. Integrate SP3 into source.
3. Integrate WMP11 into source with all updates WMP updates.
4. This point is where all future updates start (have seperate copy of source at this point.)
5. Copy source from point 4 and add winnt.sif, OEM folders, and custom svcpack.inf installers
6. Using Ryan's Integrator, redxii's post SP3 update pack is used plus a bunch of addons, removals, etc.
7. Typically test in Virtual PC to verify install.
A mind is like a parachute, it only functions when it is open.
--Anonymous
How to Ask Questions the Smart Way
--Anonymous
How to Ask Questions the Smart Way