Jump to content

ThunderM

Member
  • Posts

    9
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    country-ZZ

About ThunderM

ThunderM's Achievements

0

Reputation

  1. Hehe, sorry Here is exactly what I mean: LATEST VERSION - HFSLIP_60422.CMD Changelog for 60422: - implemented the KB918165 fix for problems with KB908531 This lines can be removed from hfslip: SET VAL918165={A4DF5659-0801-4A60-9607-1C48695EFDA9} {000214E6-0000-0000-C000-000000000046} IF NOT "%VERSION%"=="2000" SET VAL918165=%VAL918165% 0x401 Why? KB908531-v2, update.inf (here for example the w2k version used) ; Plugin.ocx HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%SP_SHORT_TITLE%","DisplayIcon",0x00020000, "%windir%\System32\msiexec.exe" HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Shell Extensions\Cached","{1cdb2949-8f65-4355-8456-263e7c208a5d} {000214e6-0000-0000-c000-000000000046}",0x10003,0x1 HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Shell Extensions\Cached","{1e9b04fb-f9e5-4718-997b-b8da88302a47} {000214e8-0000-0000-c000-000000000046}",0x10003,0x1 HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Shell Extensions\Cached","{1e9b04fb-f9e5-4718-997b-b8da88302a48} {000214e8-0000-0000-c000-000000000046}",0x10003,0x1 HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Shell Extensions\Cached","{750FDF0E-2A26-11D1-A3EA-080036587F03} {000214E8-0000-0000-C000-000000000046}",0x10003,0x1 HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Shell Extensions\Cached","{A4DF5659-0801-4A60-9607-1C48695EFDA9} {000214E6-0000-0000-C000-000000000046}",0x10003,0x1 ThunderM
  2. The hotfix KB908531-v2-x86 for W2K and WXP has been updated to revision v2. The previously built in addons in hfslip are now in the patch and can be removed from hfslip. ThunderM
  3. Ok, it seems that noone is interested in it or even verify himself. It`s ok, I solved the problems myself. You get msxml3x.dll signing errors only, if you slip WUA on W2K, if you do not slip it and install manually later everything is fine (or use HFSVPK_SW dir) I also reported this error: Error: Setup could not register the OLE Control C:\WINNT\system32\danim.dll because of the following error: LoadLibrary returned error 126 (7e). This problem occurs if you slip IE6.0sp1-KB905915-Windows-2000-XP-x86-ENU hotfix, again with manual integration everything goes fine. A small tip for the guys who leave SFC intact (that´s why I went to 2K): After installation you should browse you %Windir% for setuperr.log and see what really went wrong. My error report is on page 2 for those interested. Anyway hfslip at least works for WXP without problems. Thunder
  4. The point is that you should not be including those updates as they are intended for a different version of Outlook Express. Have you always had this problem with the OE updates? When did you try HFSLIP for the first time? Exactly how did you determine Windows Update Agent wasn't slipped? Are files missing on the CD?Is Windows Update Agent slipstreamed when including IE6? To 1: I have tried with IE5 on Win2K for 3 times, all yseterday (always checking with MBSA/WU). I used hfslip almost since beginning, mostly on wxp. To 2: In SVCPACK dir the wuxxxx.cab was missing, mbsa told me that WinUpdateAgent wasn`t installed -> that´s how I even recognized it. To 3: Yes, WUA was slipped when including IE6.
  5. Back again, The problem with the msxml3x.dll`s is still present, have to revise my info from yesterday. Today I have created another Win2k Pro CD, this time with IE6, got problem again and even another one, check setuperr.log. Rechecking my cd from yesterday without IE6 and without msxml3x.dll errors I recognized that the WindowsUpdateagent wasn`t slipped. So, there is def. a problem with hfslip and Win2K. Other users who slip the same config as I should have the same entries in their setuperr.log. Guys, please take a look. Thx. There is no need to change anything on OE, slipping the 2 mentioned updates runs flawless and WU/MBSA is happy. ERROR_REPORT.TXT setuperr.txt
  6. Hmm, something strange happened. As you wrote above I moved the mp6xxxx.exe from HFSVPK to HFSVPK_SW, everything else has not changed, and did reHfslip and a reinstall. The msxml3x.dll errors are no longer existant. Weird Edit: @Tomcat76: The Updates of OE I PM'ed you are requested by WU/MBSA. If I slip the 2 ones mentioned WU/mbsa is happy
  7. I am using the Updaterollup revision v2, the version for "IT-Pro's". I tried several times, always getting this error. Off topic: Are there any reported problems with MP9 and latest updates? setuperr.log reports a .dll couldn`t be registred?
  8. The problem occurs wether I slipstream IE6 or not, always got this error. @Tomcat76: Btw, check your PM, your Win2K update list if keeping IE5 on W2K is incomplete!
  9. Hy, I am using hfslip on W2KPro en and always get these errors: setuperr.txt: Error: Setup detected that the system file named [c:\winnt\system32\msxml3.dll] is not signed properly by Microsoft. This file could not be restored to the correct Microsoft version. Use the SFC utility to verify the integrity of the file. *** Error: Setup detected that the system file named [c:\winnt\system32\msxml3r.dll] is not signed properly by Microsoft. This file could not be restored to the correct Microsoft version. Use the SFC utility to verify the integrity of the file. *** Msxml3 comes with our beloved security rollup v2. So, is there a bug or something that hfslip does? Thx! ERROR_REPORT.TXT setuperr.txt
×
×
  • Create New...