James_A Posted February 18, 2009 Share Posted February 18, 2009 I guess I was a bit too brief.I haven't actually set up a VM and run the experiment exactly as you asked BrainwreckedTech to do. What I have done is take a live system with all other patches installed and then installed KB954600. The results of my run are as I have reported.All I was trying to say is that, as and when someone actually carries out the experiment I think that is what they will get, because that is what I already have. I'm near enough to what you asked that the results should be identical.As already reported by BrainwreckedTech, WMP9 does not completely replace WMP6, so the results are messy. We have WMP9 using/updating logagent.exe in system32, but WMP6 using/updating a different version of the file (same name) in Program Files/Windows Media Player.. Link to comment Share on other sites More sharing options...
okram98pive Posted February 26, 2009 Share Posted February 26, 2009 strmdll.dll should be copied to the system32 folder?I've just finished a test with HFslip on a italian Windows 2000 Pro. As reported, the only hotfix missing is 954600, so I've made a little trick and it worked. I've checked that both version of logagent are 9.xxx (in system32 and program files), and almost all other files of the hotfix are in the same versions of that altready present in system32.The only file different is exactly strmdll.dll, that without the 954600 is in version 4.1.0.3936 in the system32 forlder. The same file is provided in version 4.1.0.3937 in the wm41 folder of the hotfix. Manually replacing the file in system 32 with the same one extracted from the hotfix makes MU happy, and the 954600 hotfix is non listesed anymore.Maybe it's possible to implement some line on the script that force this file to be copied from the "wm41" folder. And I agree, this is the first hotfix wth this strange structure.Just my 2 cents, maybe this info are useful. Link to comment Share on other sites More sharing options...
tommyp Posted February 27, 2009 Share Posted February 27, 2009 okram98pive - I think you nailed it on the head. I'm assuming that there is some hotfix out there where strmdll.dll is version 4.1.0.3936. The filedate of that file is newer than the one in the troublesome hotfix. There is already code in the script (line 1369) that copies things over from the wm41 folder. Things will need to get modified somewhat to force copy it instead. Can someone determine what hotfix has strmdll.dll version 4.103936?Funny story. When I first wrote hfslip it was fun. Now it's more of a job. I want to quit this job. Link to comment Share on other sites More sharing options...
okram98pive Posted February 27, 2009 Share Posted February 27, 2009 I need to run some other test, but I just from extracting some file I've only noticed:from kb954600 -> strmdll.dll version 4.1.0.3937 date 19 june 2008from kb925398v2 -> strmdll.dll version 4.1.0.3936 date 24 august 2006I'll check all other component, but that strange, the date are so different. Link to comment Share on other sites More sharing options...
fdv Posted February 27, 2009 Share Posted February 27, 2009 Funny story. When I first wrote hfslip it was fun. Now it's more of a job. I want to quit this job.Oh no you don't, if I'm here, you're here: misery loves company, pal (Though your 'job' is a HECK of a lot more work, I know) Link to comment Share on other sites More sharing options...
James_A Posted February 27, 2009 Share Posted February 27, 2009 I get the same result as okram98pive.However, for strmdll.dll (4.1.0.3936), I have a date of 21-August-2006, (not 24-August, as given by okram98pive) but maybe that was just a typo.The previous version of strmdll.dll (4.1.0.3936) comes from KB925398 and is almost two years older. The dates are right, because that's a 2006 update (KB925398=MS06-078).Makes no difference whether you had v1 or v2 of that update. When KB925398-v2 was released, in 2007, strmdll.dll did not change from v1 to v2. . Link to comment Share on other sites More sharing options...
okram98pive Posted February 27, 2009 Share Posted February 27, 2009 I get the same result as okram98pive.However, for strmdll.dll (4.1.0.3936), I have a date of 21-August-2006, (not 24-August, as given by okram98pive) but maybe that was just a typo.Yes, it's a typo, 24 august Using the replace folder with the new version of the file solve the problem, it's a simple workaround for the moment.Very strange, but if you need, I can make a lot of test: HFslip is the best way to create an update disc of Windows 2000, a must have. Link to comment Share on other sites More sharing options...
tommyp Posted February 28, 2009 Share Posted February 28, 2009 Is this an non-english hotfix prob? Here's my update list. It only flags the new autorun hotfix and the malicious software tool, which I didn't include in my HF folder. I don't consider either a mandatory hotfix. I am not using hfexpert or replace. Anyone want to verify that we are running the same files? I don't intend on being the one to compare lists. If it means anything, I am using the D beta. Constructive criticism appreciated!Files in your HF folder:directx_9c_redist.exeIE6.0sp1-KB905495-Windows2000-x86-ENU.exeIE6.0sp1-KB938464-Windows2000-x86-ENU.exeIE6.0sp1-KB958215-Windows2000-x86-ENU.exeIE6.0sp1-KB960714-Windows2000-x86-ENU.exeMDAC253-KB927779-x86-ENU.exeMPSetup.exemsxml2.msimsxml2sp6-kb887606-x86-enu.exemsxml4-KB954430-enu.exemsxml6-KB954459-enu-x86.exeOE6.0sp1-KB951066-Windows2000-x86-ENU.exerootsupd.exeWindows2000-KB842773-x86-ENU.EXEWindows2000-KB891861-v2-x86-ENU.EXEWindows2000-KB893756-x86-ENU.EXEWindows2000-KB896358-x86-ENU.EXEWindows2000-KB896423-x86-ENU.EXEWindows2000-KB899587-x86-ENU.EXEWindows2000-KB899589-x86-ENU.EXEWindows2000-KB900725-x86-ENU.EXEWindows2000-KB901017-x86-ENU.EXEWindows2000-KB901214-x86-ENU.EXEWindows2000-KB905414-x86-ENU.EXEWindows2000-KB905749-x86-ENU.EXEWindows2000-KB908519-x86-ENU.EXEWindows2000-KB908531-v2-x86-ENU.EXEWindows2000-KB911280-v2-x86-ENU.EXEWindows2000-KB913580-x86-ENU.EXEWindows2000-KB914388-x86-ENU.EXEWindows2000-KB917008-x86-ENU.EXEWindows2000-KB917537-x86-ENU.EXEWindows2000-KB918118-x86-ENU.EXEWindows2000-KB920213-x86-ENU.EXEWindows2000-KB920670-x86-ENU.EXEWindows2000-KB920683-x86-ENU.EXEWindows2000-KB920685-x86-ENU.EXEWindows2000-KB921398-x86-ENU.EXEWindows2000-KB922582-x86-ENU.EXEWindows2000-KB923191-x86-ENU.EXEWindows2000-KB923810-x86-ENU.EXEWindows2000-KB923980-x86-ENU.EXEWindows2000-KB924270-x86-ENU.EXEWindows2000-KB924667-x86-ENU.EXEWindows2000-KB925902-x86-ENU.EXEWindows2000-KB926436-x86-ENU.EXEWindows2000-KB927891-x86-ENU.EXEWindows2000-KB928843-x86-ENU.EXEWindows2000-KB930178-x86-ENU.EXEWindows2000-KB931784-x86-ENU.EXEWindows2000-KB933729-x86-ENU.EXEWindows2000-KB935839-x86-ENU.EXEWindows2000-KB935840-x86-ENU.EXEWindows2000-KB938827-x86-ENU.EXEWindows2000-KB941569-x86-ENU.EXEWindows2000-KB942831-x86-ENU.EXEWindows2000-KB943055-x86-ENU.EXEWindows2000-KB943485-x86-ENU.EXEWindows2000-KB944338-x86-ENU.EXEWindows2000-KB945553-x86-ENU.EXEWindows2000-KB950749-x86-ENU.EXEWindows2000-KB950974-x86-ENU.EXEWindows2000-KB951071-x86-ENU.EXEWindows2000-KB951698-v2-DX9-ENU.exeWindows2000-KB951748-x86-ENU.EXEWindows2000-KB952954-x86-ENU.EXEWindows2000-KB953155-x86-ENU.EXEWindows2000-KB954211-x86-ENU.EXEWindows2000-KB955069-x86-ENU.EXEWindows2000-KB956802-x86-ENU.EXEWindows2000-KB957097-x86-ENU.EXEWindows2000-KB957280-x86-ENU.EXEWindows2000-KB958644-x86-ENU.EXEWindows2000-KB958687-x86-ENU.EXEWindows2000-KB960715-x86-ENU.EXEWindows2000-WindowsMedia-KB952069-x86-ENU.exeWindowsInstaller-KB893803-v2-x86.exeWindowsMedia64-KB954600-x86-ENU.exeWindowsMedia6-KB925398-v2-x86-ENU.exeWindowsMedia9-KB936782-x86-ENU.exeWindowsMedia-KB911564-x86-ENU.exeWindowsUpdateAgent30-x86.exewmfdist.exewmp6cdcs.exe Link to comment Share on other sites More sharing options...
okram98pive Posted March 1, 2009 Share Posted March 1, 2009 In the next few day I'll repeat my test in VM with 1.7.9D without the replace folder workaround (I need a cd ready for a real install, so that was the fast way). The hotfix list I use is the almost same (I've no checked every single hotfix, but only that are related to winmedia), of course using italian hotfix. Also, I use basic DX9 cab and not the full redist, but I think that is not relevant.Pheraphs is not relevant, but I use winxp as OS, and the file in HF folder are sorted in different way that in 2000 environment: here's the sorted list that windows explorer show me.WindowsMedia6-KB925398-v2-x86-ITA.exeWindowsMedia9-KB936782-x86-ITA.exeWindowsMedia64-KB954600-x86-ITA.exeIn a Win2000 environment, the file are sorted exactly as your list.Maybe is that the cause? In my next test I'll try to follow every step of the script. Link to comment Share on other sites More sharing options...
TallSkinnyCatSmurf Posted July 25, 2010 Share Posted July 25, 2010 Although not doing a slipstream at this time,am having problems updating Windows 2000 SP4with the 954600 hotfix.Also, very strange: Belarc Advisor seems tothink that I need: KB952069_WM71even though am running Windows MediaPlayer 6.4954600 I run this file WindowsMedia64-KB954600-x86-ENU.exe (MD5 = 287c62f7da267b7bb5a4caa181a9c540) and get no errors. But the update doesn't appear in "Add/Remove Programs" or qfecheck: C:\WINNT\system32>qfecheck | grep 9546000 Looking into it further, by extracting the file, WindowsMedia64-KB954600-x86-ENU.exe /x looking into the resulting file, update.inf and the appropriate Micrsoft link (http://support.microsoft.com/kb/954600), I find that the affected files are: logagent.exe msv1_0.dll netlogon.dll sp3res.dll strmdll.dll Comparing the versions in the update with the existing ones on disk, I find that most files on disk are newer, 2 the same, and 1 older: logagent.exe Update: Version: 4.1.0.3937 Date: 2008 June 19, Thursday, 07:39:26 Size: 65,055 bytes MD5: f5d23e5b355389eae2ef3ce0a409b876 Disk: Version: 9.0.0.3287 Date: 2005 December 26, Monday, 23:50:44 Size: 103,936 bytes MD5: afa5ef36f9a027a4264e198e88dd793a msv1_0.dll Update: Version: 5.0.2195.6926 Date: 2005 April 7, Thursday, 15:21:18 Size: 125,200 bytes MD5: 1dfa06dea950dff34c57d04b7392d29e Disk: Version: 5.0.2195.6926 Date: 2005 April 8, Friday, 09:51:18 Size: 125,200 bytes MD5: 1dfa06dea950dff34c57d04b7392d29e netlogon.dll Update: Version: 5.0.2195.7011 Date: 2005 April 7, Thursday, 15:24:32 Size: 366,864 bytes MD5: be8fc3c74ab5212cd4067e8973764ad6 Disk: Version: 5.0.2195.7011 Date: 2005 April 8, Friday, 09:54:32 Size: 366,864 bytes MD5: be8fc3c74ab5212cd4067e8973764ad6 sp3res.dll Update: Version: 5.0.2195.7151 Date: 2008 February 29, Friday, 05:26:00 Size: 6,276,608 bytes MD5: 2ad9fd55b4798ad8964afee0158a8fbe Disk: Version: 5.0.2195.7295 Date: 2010 June 5, Saturday, 14:32:25 Size: 6,350,848 bytes MD5: bf075d9ebe37a2541eb7594ef2769ee9 strmdll.dll Update: Version: 4.1.0.3937 Date: 2008 June 19, Thursday, 06:28:12 Size: 247,326 bytes Disk: Version: 4.1.0.3938 Date: 2009 August 21, Friday, 17:06:52 Size: 247,326 bytesSo, my questions are: A. How to get 954600 to apply and show up in "Add/Remove Programs" and qfecheck? B. How to get Belarc to not show the problem with KB952069_WM71. I'm running 6.4 WMP not 7.1 C. Should I manually update the 1 older file?Thanks much in advance for any light you can shed. 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