Jump to content

RyanVM

Member
  • Posts

    2,756
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by RyanVM

  1. I'm going to put them in my upcoming hotfix pack.
  2. And now for some good news... If you take the following 13 files from the cabs downloaded from the image above, compress them and put the files in your i386 folder (replacing the old ones), Windows Update v5 works as if everything was installed. cdm.dll iuengine.dll wuapi.dll wuau.adm wuauclt.exe wuauclt1.exe wuaucpl.cpl wuaueng.dll wuaueng1.dll wuauhelp.chm wucltui.dll wups.dll wuweb.dll well that's neat and easy to do
  3. Hey, I was just coming here to post my success with ERD! So what if I was 5 minutes slow
  4. Is there a way to edit a computer's registry in BartPE? I'm trying to fix a friend machine who had a spyware removal go bad, but regedit only brings up the registry for BartPE. Is there a way I can edit his registry from there?
  5. , $23M is pennies to Symantec
  6. Google Resource Hacker
  7. I think it's ProductID for SP2, not ProductKey EDIT: But maybe not.
  8. I think you're misunderstanding me. You can use the /integrate switch to integrate the hotfix into the Windows install source. However, the hotfix will still run from svcpack.inf in order to create the needed registry entries (which tell WindowsUpdate that the hotfix is installed). When it runs, it'll overwrite the patched tcpip.sys you put in i386. So, you have two options: 1.) Copy the patched tcpip.sys AFTER the svcpack.inf stage of Windows setup. You'll need to copy it to both dllcache and system32\drivers. 2.) Put the patched TCPIP.sys in your i386 directory without using the /integrate command, so the hotfix doesn't run. If you do that, you'll need to create the registry entries that the hotfix would normally create so it doesn't appear on WindowsUpdate.
  9. I've created an INF file that installs as a Windows component. I'm trying to get it to be hidden from the list of components, so I put a hide in it's line in sysoc.inf, but it still shows up in Add/Remove Windows Components. Is there a line that has to be in my component's INF file to have it hide? I've been looking through the component INF files, but I can't find anything.
  10. kb884020.exe /integrate:c:\xpcd adjust the filenames/folders appropriately If you want to use the patched version, you have to add the registry entries that tell WU that the update's already installed. Otherwise, add it after the fact by overwriting the copies in dllcache and system32\drivers
  11. OK, I've got them all. Time for playtime B)
  12. hmm, this could be integrated pretty easily at this point
  13. Thanks for letting me know. Shoot me an IM for an updated test (and hopefully final) version.
  14. Glad to hear that it all worked out for you
  15. try using a one word MSI (hey, it's worth a shot )
  16. , I'm beginning to think Symantec is just messing with my head.
  17. The more I look at it, the more I think you can't make those go away. Those messages have always come up with Windows Update.
  18. My bet is that it doesn't like config.txt. Try creating it in Notepad and be sure to save it as UTF-8. EDIT: Heck, you can probably open the existing config.txt and just do a File...Save As to convert it.
  19. Why do you say wierd? Do you doubt it's authencity? Not at all. Check your private messages.
  20. You might be able to whitelist the site
  21. For the record, the version floating around as "9.0.1.1100" is actually 9.0.1.1000 (as I thought). That's the way it shows up within SAV. People were probably confused because some file versions do show as 9.0.1.1100, but the overall program version is still 9.0.1.1000. For the record
  22. http://www.msfn.org/board/index.php?showto...=expand+makecab
  23. Do you guys have any suggestions/programs for me to test and verify that MSXML 4.0 is properly installed?
×
×
  • Create New...