Jump to content

Super-Magician

Member
  • Posts

    969
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by Super-Magician

  1. OK, thanks for trying the RunHiddenConsole thing. Never mind...
  2. WindowsUpdateAgent20-x86.exe is not the Microsoft Update Agent. That's just for Windows Update. If you want Microsoft Update, that's a separate file, MUWEB_SITE.cab, which belongs in HFCABS. Check Tomcat's hotfix list for the link. If you do plan to slipstream MUWEB, keep in mind that you can't change the link unless you create your own CMD file or switchless "installer." On the same token, simply slipstreaming it won't cause WU to recognize the DLL. Instead, you must import something else, which I've attached here (place this in HFSVCPACK). If you do decide to create something to modify the link for you, it obviously won't work unless... (1) You slipstream the right things (both WindowsUpdateAgent20-x86.exe and MUWEB_SITE.cab), and (2) You include the file I attached. If you don't follow (1) and/or (2), clicking on any WU link, modified or not, will redirect you back to the Windows Update page.
  3. Try that post again. The board upgrade (IPB 2.2.x) changed the way files are embedded in posts, so I had to edit it.
  4. Well, I see you've found the MSFN forums as well. Welcome! And thanks for using my pack. Anyway, I would like to say that what you are mentioning already exists on the HFSLIP website. In fact, it's stated on that very page to which you referred. Important things to know I hope this helps a bit. HFSLIP cannot slipstream IE7 because of many problems that exist within the package itself. As of this point, we have not been able to find a way around these issues. Tomcat76 will be doing more testing, however, in the weeks/months to come. Even with IE7 installed at GUIRunOnce or T-13, there are still issues. I can't think of a way around having to activate before installing IE7. Someone else might be able to shed some light on this. Again, welcome to MSFN and thanks for using HFSLIP! I'm interested in how you used my pack in conjunction with this because it isn't designed to be supported by slipstreaming programs.
  5. I don't think there is one best way to go about this. HFSLIP only supports clean sources, but that doesn't mean you can't try it with others. Since your source already has a SVCPACK folder, it has entries in SVCPACK.INF already. HFSLIP cannot deal with this. Instead, it will create a completely new SVCPACK.INF file, as far as I can remember, and overwrite any that you might already have. If some updates are slipstreamed as well, as is the case with many OEM installations, there will at any rate already be information contained in TXTSETUP.SIF and DOSNET.INF. If you don't slipstream any updates that the CD already has, things should be fine. But you never know. I'm sure TommyP and Tomcat76 can give a much more thorough answer to your situation. This is just my take on it. You mentioned that you wanted to determine which files are changed from a fresh copy of SP2. If I can, I'll try to compile a list of MD5s from an unmodified retail source directly from MS.
  6. MUWEB_SITE.cab itself does not force Windows Update to recognize the presence of the MUWEB.DLL file. Instead, you must import another file, which I have attached here. Put this in HFSVCPACK. If you are also slipstreaming/integrating/installing IE7, you may encounter additional problems with slipstreaming of the Microsoft Update Agent.
  7. I'm sorry, but this version is not new. It has been out since beginning of November if I'm not mistaken.
  8. Like many people in this forum have often said, please search before posting. Windows Updates Downloader
  9. Technically, that version you are using is a warez copy, so we can't provide support for it here (and neither can nLite if it doesn't already work with it, I presume). The only way to find out is to try it! I'm not quite sure how he creates his version, so I can't give a definitive answer.
  10. Since CMDOW causes problems with quite a few virus scanners, can you provide support for hidec? Thanks for the script by the way. Wondering if you can add in .NET 3.0 some day...
  11. One last thought...obviously, if there's something wrong with your source, HFSLIP can't do anything about it. Bad source = bad HFSLIP run
  12. If your IE7 installer is fine, then try installing without that WINNT.SIF file. If it doesn't work, we may need to look at some additional files, but it shouldn't make a difference there. You said you're using a volume-license source, right? Make sure your CD key is valid too so it activates properly. If you want, compare your installer's MD5 with that on my list (it's somewhere near the bottom of the topic list right now; will be updated again soon).
  13. Can I take a look at your WINNT.SIF file? This time, please zip it up using a compression program such as 7-Zip or WinRAR. Block out any personal information first.
  14. Glad you solved everything. Just one more clarification: You need modifyPE.exe if you include OPUC4.CAB (Office Update Engine) or HFEXPERT.
  15. @Kiki This functionality was removed quite a few months ago. A few people complained about how bloaty the script was becoming, and that's when some extras were moved into HFSPLUG1 (now obsolete). At some point later, I believe MAKECAB and EXPAND could no longer go into HFTOOLS and had to be put in the SYSTEM32 directory.
  16. @gokalp Welcome to the forums! A few minor things I noticed: Like Kiki said... (1) You have an extra KB890830-v1.17. (2) KB920213 and KB923980 are not for Windows XP. In addition... (3) WindowsXP-KB898461.exe should be renamed to WindowsXP-KB898461-x86-enu.exe. (4) modifyPE.exe is no longer needed. (5) EXTRACT.EXE is only needed if slipstreaming application addons. Now, aside from that, as far as IE7 is concerned, your file should be copied over into SOURCESS\I386\SVCPACK as "IE7_INST.EXE". However, the reason this isn't occurring is that you have your HFANSWER.INI file in the wrong directory. It belongs in HFTOOLS, not the root. Because of this, your installer would instead be cabbed, copied to I386, and installed at first GUI logon (i.e. when the Welcome screen appears). Simply move your file and everything should be fine . By the way, the installer still belongs in HF. The HFSVCPACK folder is only for silent switchless installers. Edit: Correction to (4) above and added (5).
  17. Can you post your HFSLIP.LOG file? Some situations can break the RunOnceEx routines.
  18. Thanks for implementing that user summary/login mod on the front page. By the way, where can I download it?
  19. HFSLIP no longer checks for MAKECAB in the HFTOOLS folder. Please copy it to your WINDOWS\System32 directory.
  20. Thanks for providing those instructions, but it would be more appropriate to link to them than to copy them onto the website. @Tomcat, like Yzöwl noted, it is necessary to register on RogueSpear's forums. I don't really see what the concern is. The files are located in the linked forum under the thread "RogueSpear's Runtime Collection".
  21. I have made at least three posts in this exact forum linking to RogueSpear's .NET 2.0 installer. Please search more closely before asking.
  22. The taskbar option also works perfectly for me on a WMP11 slipstreamed install. Is your Windows activated properly?
  23. You have to minimize WMP to the mini player at least once before that option appears in your taskbar context menu.
  24. Are you sure this is a Windows 2000 error message and not some error message injected into the system by 3DMark? I doubt it's caused by HFSLIP or FDV's fileset.
  25. Look at the last few lines of the script. :EOFETIMEM% GOTO EOF Whoops!
×
×
  • Create New...