Tomcat76 Posted October 8, 2006 Author Share Posted October 8, 2006 I experienced the same WMP10 problem and it isn't related to the problem I posted above. This'll need a bit of work. Also, WU complains about KB883357 and KB839645.Not ready for XPSP1 yet... Link to comment Share on other sites More sharing options...
Super-Magician Posted October 8, 2006 Share Posted October 8, 2006 It seems that KB914440 (Network Diagnostics Tool) is not slipstreamed properly.The file is supposed to appear as %systemroot%\Network Diagnostic\xpnetdiag.exe, but instead, it is placed in %systemroot%\system32 and named as xpnetdg.exe. Link to comment Share on other sites More sharing options...
Camarade_Tux Posted October 8, 2006 Share Posted October 8, 2006 PM me if something is needed.I can do quick tests but I don't have enough time to visit forums during the week. Link to comment Share on other sites More sharing options...
Tomcat76 Posted October 8, 2006 Author Share Posted October 8, 2006 * Have found multiple problems with WMP10 on XPSP1 -- not fixed yet* BITS update on XPSP1 -- fixed for upcoming version* KB839645 is a mystery; it's superseded -- need to find good reg hack* Network Diagnostics Tool for XPSP2 (was this ever supported?) -- fixed for upcoming version Link to comment Share on other sites More sharing options...
the_guy Posted October 8, 2006 Share Posted October 8, 2006 @Tomcat: Would this reg hack work for 839645?[Version]Signature=$Windows NT$[DefaultInstall]Addreg=839645fix[839645fix]HKLM,"Software\Microsoft\Windows\CurrentVersion\Internet Settings\ZoneMap\ProtocolDefaults","shell",0x10001,0x0the_guy Link to comment Share on other sites More sharing options...
Tomalak Posted October 8, 2006 Share Posted October 8, 2006 * Network Diagnostics Tool for XPSP2 (was this ever supported?) -- fixed for upcoming versionIt was not officially supported, but you showed how to do that here:http://www.msfn.org/board/index.php?s=&...st&p=537452I always added that manually to the script, and it worked without problems. You can now compare that old suggestion with the new support you added to the upcoming version ;-)Regards,Tomalak Link to comment Share on other sites More sharing options...
Tomcat76 Posted October 9, 2006 Author Share Posted October 9, 2006 We're getting somewhere. Most problems with WMP10 on XPSP1 are fixed; remaining:- playlists don't work (won't fix this)- window pops up at T-13 to complete installation of WMP10 (normally appears on first run)@the_guy: thanks; that did it @Tomalak: that manual trick won't work properly anymore for DOS-based installs with the current test releases when including WMP10 because of the double custsat.dll files. A workaround will be implemented.I want to test this one more time with XPSP1 and XPSP2 and will release a new version tomorrow at the latest because that's probably the last day you'll be able to check if all hotfixes are slipstreamed properly on XPSP1. Link to comment Share on other sites More sharing options...
Super-Magician Posted October 9, 2006 Share Posted October 9, 2006 @Tomalak/Tomcat, seems I forgot that support for KB914440 was never in the actual script. When I mentioned it briefly in the New updates thread or something, someone said it was supported so I never bothered to check Thanks. Link to comment Share on other sites More sharing options...
Tomcat76 Posted October 9, 2006 Author Share Posted October 9, 2006 OK. Check the new version You still have the WMP10 popup at T-13 for XPSP1 (the one you normally get when starting WMP10 for the first time) but at least the installation isn't broken anymore. At this point, you can still choose between following the wizard or closing it. I'll try to get rid of it in the next few days.Also, the Documentation Update is finally slipstreamed, completing support for XPSP1. Windows Update should be cool now Link to comment Share on other sites More sharing options...
glentium Posted October 9, 2006 Share Posted October 9, 2006 (edited) hey Tomcat76, you've been very busy with HFSLIP this past few days. thanks for all your hardwork. very much appreciated!btw, the latest test release works great for me.. am with XPSP2.thanks again! Edited October 9, 2006 by glentium Link to comment Share on other sites More sharing options...
tain Posted October 9, 2006 Share Posted October 9, 2006 I ran into a problem with wmfdist.exe in HF. Never had this trouble before, and by looking at the code it seems that this may be because of the WMP10 changes. During GUI setup, I got this error:(Window Title: Advanced INF Install)Error creating process <"C:\winnt\system32\logagent.exe" /regserver>. Reason: The system cannot find the file specified.Which comes from line 168 in WMFSDK.inf in wmfdist.exe: [RunPost]"""%11%\logagent.exe""" /RegServerSo I made another run without HFAAO, HFCABS, HFEXPERT, HFSVPCPACK, HFSVCPACK_SW or HFCLEANUP and I still got the error. The file, logagent.exe, is in a reducer and that is reflected in the script. I got the same error with and without that reducer.In addition, on my test runs with HFCLEANUP taken completely out of the picture, I got a new error that I hadn't seen before:(Window Title: Windows Update)An error ocurred calling "DllRegisterServer" in "C:\winnt\system32\inetcomm.dll". (HRESULT = 80004005)But adding HFCLEANUP back fixed that (part of the OE reducer).Back to the wmfdist problem, I also tried adding the cabbed file (logagent.ex_) to FIX but that didn't help. Also tried different Compression Types (A and C) as well as test release 6a and 8a but got the same results.The only fix for this for me is to remove wmfdist.exe. What am I doing wrong? Link to comment Share on other sites More sharing options...
Tomcat76 Posted October 9, 2006 Author Share Posted October 9, 2006 Thanks, TAiN.It had nothing to do with the recent WMP10 changes.Windows 2000 copies logagent.exe and laprxy.dll into the Windows Media Player folder by default, but WMP9 and WMP10 expect it in the system32 folder. I worked around this problem when WMP9 is slipstreamed, but forgot that wmfdist.exe also has these files and also expects them in system32.Fixed now. Link to comment Share on other sites More sharing options...
Tomcat76 Posted October 9, 2006 Author Share Posted October 9, 2006 (edited) Working on the inetcomm.dll problem.The IE5 section from the Update Rollup's INF isn't taken account of properly. I fixed it in an internal build and am testing it out in a VM right now.Otherwise, Win2K with IE5 is AOK (WMP9 too).Malmsteen's Odyssey album is helping me keep up the pace... Edited October 9, 2006 by Tomcat76 Link to comment Share on other sites More sharing options...
Tomcat76 Posted October 9, 2006 Author Share Posted October 9, 2006 Hmm... This inetcomm.dll problem is also there with the current final. Would the OE5.5 hotfix be causing this? This needs some thorough testing.... Link to comment Share on other sites More sharing options...
Tomcat76 Posted October 10, 2006 Author Share Posted October 10, 2006 Yup... It's the hotfix. Will see what can be done about it. In the mean time, don't include it... or use IE6, heheh. Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now