You are not logged in.
I wouldn't usually ask, but I could really do with some more cash at the moment (couldn't we all) if you find my work usefull please feel free to make a donation, any amount will help and will be much appreciated. Thank you.
Have a Merry Christmas and a Happy New Year. If not before, I'll see you on the 11th ;)
bbmak wrote:I have problem with "Boooggy's WMP 11" when applying the December pack.
The WMP11 will not start after the XP installation. It said i need to reinstall wmp11 because the WMP11 is not correctly installed.I don't know if this is related to the December Pack or not, when i switch back to Ryanvm pack, i am fine with Boooggy's WMP11.
I use both and have no problem as long as I run WMP11 slipstreamer before anything else (but after SP2 slipstream)
I did try your method by slipstreaming wmp11 first, then the xable pack. However, it still gives me the same error. WMP11 cannot run after XP installation. It asks me to go to the Microsoft Website and reinstall the WMP11 again.
Offline
hmmm I just realised, forgot to mention, that at WMP11 slipstreaming, I also include the following updates:
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-KB936782-x86-ENU.exe
windowsmedia11-kb939209-x86-intl.exe
WindowsMedia11-KB939683-x86-ENU.exe
windowsmedia11-kb942264-x86-intl.exe
windowsmedia11-kb944110-x86-intl.exe
Maybe that's the key to solve the problem...
And that actualy brings up the following question:
is it possible include critical updates for WMP9, WMP10 and WMP11 into update pack for every version at the same time?
Last edited by V@no (19-12-07 14:26)
Offline
Update: I fixed the KB941569 issue by integrating all WMP11 updates with nLite instead of WMP11 Slipstreamer. So WMP11 Slipstreamer v0.96 seems to be a bit buggy with this hotfix.
The install order I used (for the ones interested): First integrate Xable's Pack, then any other stuff you might want to integrate (like the DirectX9.0c November update), then WMP11 with WMP11 Slipstreamer (WMP11 only though!) and finally integrate all of the additional WMP11 hotfixes with nLite.
Offline
@Xable :
I'm about to make a new stripped down CD, as my last where with XUDPack v3.0.2, but now since you said that you where going to change something about one of the updates(install it from svcpack or hide the cmd window), then i'm not so happy about downloading and using your current version, if it will be changed again a little after.
I know that it's not a problem, but still, i would preffer to use the latest version of your pack for my CD. So when/if you change the pack(or if you allready have ?), then would you please mention it here, so that i know when i can download it.
Btw, i personally do not mind any windows showing, and especially seeing as there allready is windows showing a few times during the install for other stuff(reg.exe at T-13 i.e. svcpack.inf), then i don't see the point in hiding some of the windows, when others are still present.
Also i would myself preffer the direct integration method instead of the svcpack.inf method, but no matter what you decide to do, then i just would like to use the final version of your pack for my CD.
Thank's in advance.
Offline
I have changed the way the timezone update is installed, redownload the pack if you can`t handle a few command popups during setup. Otherwise nothing has actually been fixed so there`s no need to upgrade if you already use the current december pack.
So what did I change and why? Well, the timezone update is differant from a standard update in that it adds/modifies a lot of registry entries, manually capturing all of these takes a long time and because of the volume of them human error has more chance to creep in despite the extra testing measures taken in this situation. So, the next best thing to slipstreaming the update as aposed to running the origional update from svcpack is to slipstream the executable that adds the extra registry entries and run it during setup. This causes a few command windows to popup which aren`t popular. So my conclution is to add it to svcpack, while I prefer direct integration, in this special case the update doesn`t actually update any source files negating the advantages of slipstreaming plus it eradicates the possibility of human error while captuing the extensive amount of registry entries. These are the main reasons I considered installing it via svcpack in the first place like I said earlyer.
is it possible include critical updates for WMP9, WMP10 and WMP11 into update pack for every version at the same time?
In a word, no. 941569 patches the same file(s) for each wmp version. In any case it`s pointless because you can only have one version installed at a time and my update pack patches the default version as it should.
beats, So you found the issue to be with WMP11 Slipstreamer. I`d appreciate it in future if you took all WMP11 Slipstreamer issues to boooggy. I don`t use wmp and he has a lot more knowledge about both wmp and how the slipstreamer works, so he`ll be able to help better.. he`ll appreciate that bug report too I`m sure.
I`d just like to say I appreciate all of your feedback, good and bad. It`s been nearly two years since I started making this pack public and in that time not a single bug has made it into a release. Sometimes I update the pack, test, test, test and find no bug, while it`s expected deep down It makes me uneasy because knowone`s perfect but, when you do something for so long it gets harder and harder to slip up so I just have to trust myself.
Offline
Thank you very much for your fast service and explenation, Xable
Offline
Yup, I appreciate your works, and the people who have maintained these update packs
Last edited by bbmak (20-12-07 04:34)
Offline
Indeed, thank you very much for all your efforts Xable.
I'll send Booogy a mail regarding the WMP11 Integrater issue.
Offline
Great! Now its working. Thanks.
Regards.
Offline
Xable,
Not sure if you already seen this, but 942615 for IE6 has a bug and needs a registry fix as a workaround.
See this knowledge base article for details.
Cheers
Offline