• Announcements

    • xper

      MSFN Sponsorship and AdBlockers!   07/10/2016

      Dear members, MSFN is made available via subscriptions, donations and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, become a site sponsor and ads will be disabled automatically and by subscribing you get other sponsor benefits.
Guest

nLite bug when slipstreaming Windows?-WindowsMedia-KBxxxxxx

11 posts in this topic

I have now made these updates into add-ons that will slipstream properly.

They are created by running the UDC script located on my web page. xdot.tk

Just look through the high-priority listing for filenames WindowsXP-WindowsMedia-KB.......CAB

Due to the nature of Windows Media updates, they do not slipstream properly if you use the direct hotfix integration method (slipstreaming). This is because there are multiple files in these updates - WMP 9 version, WMP 10 version and WMP 11 versions. nLite will always integrate the WMP 11 version. I presume this is because the version number is the highest.

If you are slipstreaming WMP 11 then you don't need my add-ons.

As of these writing, these updates are affected:

WindowsXP-WindowsMedia-KB952069-v2-x86-ENU.exe

WindowsXP-WindowsMedia-KB954155-x86-ENU.exe

WindowsXP-WindowsMedia-KB973540-x86-ENU.exe

WindowsXP-WindowsMedia-KB975558-x86-ENU.exe

WindowsXP-WindowsMedia-KB978695-x86-ENU.exe

WindowsXP-WindowsMedia-KB2378111-x86-ENU.exe

Symptoms:

Setup will hang right before the OOBE splash screen (black background, Windows logo, "Please wait..." under logo).

post-12166-0-16554500-1291817452_thumb.j

Rebooting will bypass the OOBE and you should be good to go but you WMP will be broken. See image...

2e1rsj8.png

Resolutions:

Remake your CD with my add-ons and reinstall.

or

Download and run the installer for WMP 9 for XP here. After installing, run Windows Update so your player gets patched. (Don't really know if this will work)

or

Install Windows Media Player 11 for Windows XP

For non English versions, I'm afraid I have no add-ons. You must use the /integrate switch instead.

Integrate Usage: /integrate:path where path refers to the folder that contains the i386 folder.

Example: C:\MyUpdatesFolder\WindowsXP-WindowsMedia-KB973540-x86-ENU.exe /integrate:C:\MyXPSource

Edited by -X-
0

Share this post


Link to post
Share on other sites

I use KB952069v2 and KB968816 and they integrate just fine.

I think the reason why it's working is that I also integrate wmfdist11.exe (Windows Media Format Runtime 11) on top of WMP9 (present on the XP CD) PRIOR to these 2 updates. The result is a Windows Media Player 9 that plays .wmv and .wma files encoded with WMP11 codecs including VC-1.

Try it and see if it also works for you.

0

Share this post


Link to post
Share on other sites

I know they integrate with nLite but the file versions nLite places in i386(and the files subsequently installed during setup) are wrong. They may even work without wmfdist11.exe. The files in question are...

LOGAGENT.EX_

WMNETMGR.DL_

WMP.DL_

WMPDXM.DL_

WMSPDMOD.DL_

WMVCORE.DL_

0

Share this post


Link to post
Share on other sites

I have now made these updates into add-ons that will slipstream properly.

They are available via my web page. xdot.tk

Edited by -X-
0

Share this post


Link to post
Share on other sites

I have now made these updates into add-ons that will slipstream properly.

They are available via my web page. http://win-x.co.cc/updates.html

Do you have the spanish version of your cabs as mentioned in yr page: http://win-x.co.cc/updates.html ?

Or can direct me on how to modify them?

I already know that yr cabs Kb890830, flash player, wga validation and xable-Windows update engne can be applied w/o modification but what about the ones for WM Player?

Are the ones on yr page for wmp11?

0

Share this post


Link to post
Share on other sites

No, they are for WMP9. You don't need to modify them if you are slipstreaming WMP11.

To make a Spanish version, just take one of mine apart and see how it's done. When you extract the hotfix you will see the different versions in different folders. Use the WMP9 ones.

0

Share this post


Link to post
Share on other sites

Hi, sorry for renewing this thread but I'm facing this problem as well...though it took me a while to find this thread.

I am wondering is there anything that can be done for people who don't use English. I use Simp Chinese for instance.

You told the person who asked for Spanish version to look at what you did and just follow through in the same manner. But all your link is linked to the addon-creation script. Does this mean I can just used my Chinese hotfix file (renamed to the English) with your script? (Though I checked the resulting file language in Property pane being English but it shouldn't be a problem, should it?) I mean it does use the same file I think, only the entry of language version is changed by your script.

I really don't want to use the regular /Integrate method...it takes up too much room.

Thanks.

0

Share this post


Link to post
Share on other sites

Sorry for the delay in responding.

I'm of the belief now that language doesn't matter. The binaries are the same. The only thing that may be different is the entries under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\.KBxxxxxx (which I've posted a screenshot below) and the catalog file. It's probably in the operating systems language.

RegistryEditor.png

If you are currently on an Simplified Chinese XP system, can you post a screenshot like the one I just posted or export a the reg key from one of the KB#'s and paste it into your next reply?

Here is a CRC comparison of KB954155. Simplified Chinese and English. Red is different. Black is identical.

languagecomparision.png

So go ahead and use the ENU one my script makes.

Let me know how it goes. :)

Edited by -X-
0

Share this post


Link to post
Share on other sites

For non English versions, I'm afraid I have no add-ons. You must use the /integrate switch instead.

Integrate Usage: /integrate:path where path refers to the folder that contains the i386 folder.

Example: C:\MyUpdatesFolder\WindowsXP-WindowsMedia-KB973540-x86-ENU.exe /integrate:C:\MyXPSource

You must extract "i386\svcpack.in_" to "i386\svcpack.inf" before executing "/integrate" operations. Not doing so will cause the "svcpack.in_" file created by nlite to be deleted!

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.