Super-Magician

I'm not sure why this happened. I have to do more testing. It could be due my new attempts at driver integration. When I used 70111a, for the post-setup wizard, the system tries to open the MSOOBE shell through Internet Explorer (HTML file) rather than full-screen on its own. It's weird (I was presented with that IE file download dialog. Of course, everything gets stuck after that.

Have you tried redownloading the hotfix? KB920342 seems familiar; let me take a look. Meanwhile, can you still post your log file? There's still a possibility it's due to something else.

We can't really help you until you post your log file. Although your suggestion is fine, Kiki, datarelm may have wanted to slipstream some "extra" hotfixes that may or may not be supported by HFSLIP. That's why we need to take a look first.

Please post as your HFSLIP.LOG file as you were directed in the error-reporting instructions along with the contents of WU[x].TXT in a ZIP file. http://www.hfslip.org/support.html

I would also recommend... (1) That you don't jump to conclusions. (2) That you never run HFSLIP on a critical drive anyway. Put it on a secondary drive to get the most out of the program (i.e. a faster run, no risk of corruption on system drive even though HFSLIP does not cause it, etc.).

I'm sure solution (1) would be better alternative. You would probably be interested in using daddydave's DrivercabHelper, located in his signature, that automates step (3) of the driver integration method posted by Oleg II. Edit: Never mind, I see you've already tried it but encountered a few problems. I have just tried driver integration for the first time today and will report my findings as well.

Thanks for your complete and thorough report. I'm sure they will be of much help to others in need of solving this particular issue.

This is peculiar. Can I see your HFSLIP.LOG file?

Wow, this script has changed a lot since the first version! Thanks. Great job as always, Tomcat!

HFSLIP does NOT make changes to your C:\ drive. It will only make changes in the folder in which the script is contained and any subdirectories under that folder. I'm sorry you lost a lot of important data, but that is not HFSLIP's problem. You likely have a virus or your drive has become corrupt. "A bunch of ASCII characters" cannot be produced by HFSLIP. It almost clearly indicates drive corruption.

Old thread... This is the last post I've found regarding this topic. What's happened in the last six months?

It's been supported for a while now (well, since 1.2.0 and improved in 1.2.1). For Windows 2000, use the version for XP.

Thanks, N1K. Is it just me, or is it that whenever I comment on a front page news item, when I view my comment again, the author of the comment is blank, and so is the number of posts. It shows like this when I log out and look at it too. I don't see it happening for other people. What's wrong?

You know, I REALLY should get RyanVM to make that note clearer about his .NET 2.0 installer. It's stated so conspicuously there, but for some reason no one reads it!!

I see! Your version of Windows doesn't seem to have the proper environment variable settings (%WINDIR% should produce the same result as %SystemRoot%, not that exact string; the command prompt cannot recursively read variables). I think maybe Tomcat76 should change it to %SystemRoot%, or you should change somehow change the specification for %WINDIR% in your environment variable settings (System Properties -> Advanced -> Environment Variables).

If you have the right version of MAKECAB and have it in the correct folder, I can only think for you to check the following things... (1) You deleted any temporary folders created by the HFSLIP run process (i.e. SOURCESS, WORK, TEMP, etc.). (2) You are running a recent version of HFSLIP (the current one is HFSLIP 1.2.2). (3) Go to the command prompt, run the following command, and report the result. ECHO %WINDIR% Hope this solves something.

Actually, I guess hansenjr only wanted to slipstream the Windows Update Agent. Therefore, I'll issue this correction. @hansenjr, if you just want to slipstream the Windows Update Agent, then simply include WindowsUpdateAgent20-x86.exe in HF. You don't need MUWEB_SITE.CAB, and you can ignore anything I said above. The Microsoft Update Agent (MUWEB_SITE.CAB) is a separate issue.

I know, a bunch of sites are doing this. But there is DEFINITELY no change.

Isn't that what IS already posted there, just stated conversely? Anyway, I guess I should have read your post more clearly. Well, hope HFSLIP works well for you. It seems the name of that site is in MSFN's ban filter.

Want to clarify one more thing... I've found that the workaround I posted only works for XP. If you're using 2K3, you're out of luck for the moment.

@hansenjr, sorry, but I guess my workaround only works on XP. I will try to find out how to make one for 2K3. @Kiki, yes, it works on XP like I just said (I've been using it for many months). @glentium, many people prefer using Microsoft Update rather than Windows Update. The person who started this topic was looking for a way to slipstream the MU DLL.

That is true, glentium. For example, all new HP and Sony computers (to name a few) no longer come with pre-prepared recovery discs. They make you burn them yourself. Usually there is a dedicated recovery partition with all the necessary files, but you can't use the files unless you run the program that comes along with it.

@glentium Of course it wouldn't, but this version has the same exact size and checksum as the November release. Besides, you had to use the Nov. 2nd (or later) package to successfully slipstream it.

As long as you include that DataStore.exe file in HFSVCPACK, you should be fine. Report back if you have any trouble.

Wow, many posts about WU and MU today! WindowsUpdateAgent20-x86.exe is for Windows Update. You need that for many things, but I'm not sure if Microsoft Update requires it or if the MUWEB_SITE.CAB file covers it all. It's best to include both in case you want to switch back (but it's not much faster either way). It's your decision.