tommyp

HFSLIP will still generate those HFSLIPxx.inf files. Can you think of a better way to make registry changes without adding or modifying a file? I'll bet you can't. I'll bet most computer guys can't. Once HFSLIP is installed, it will leave very little behind on your harddrive (I think it's 3 or 4 files or 4kb). However, if you installed IE6 the old fashioned way, the microsoft installation will deposit far MORE files on your drive (more like 15meg). If that window bothers you too much during installation either look away or turn your monitor off. Countless others do not have problems with that dos window that pops open. Oh, and you DO need the rollup for a proper IE6 slisptream.

What about this. I can probably make HFLSIP do this (if you want it). What I can do is once installation is complete, I can rename the sfcfiles.dll (the one being used) to zsfcfiles.dll. Then I can rename the original dll back to sfcfiles.dll. So once you reboot, you'll have your original sfcfiles.dll. Is this worthwhile to incorporate?

The ERROR_REPORT.TXT file is located in the same folder where you ran HFSLIP once it's completed. It also resides in the SOURCESS folder.

Cool suggestion Oleg. As Pene asked the other day, does the AutoIt method work with 2k? I'm confused on this too.

@Siginet - That file is part of FDV's fileset. Link. It was generated for W2K, so I'm not sure if it works for XP and newer OS's (I haven't tried it).

@viinno - We can gladly help you out. Please post your ERROR_REPORT.TXT file to this thread so we can see what you're doing. In the meantime, please see the "what goes where" thread in this forum. HFSLIP isn't geared for slipstreaming programs like virtual machine, but can do *some*.

@Crash - To summarize, HFSLIP falls into four categories: 1) (2k) Slipstream the latest hotfixes, optionally slipstream DX9 and integrate FDVs fileset (2k only). With this setup, you have IE removed from your system from the start. You cannot run NLITE on this configuration, because FDV was nice enough to remove all the worthless stuff right from your installation source plus add in lots of valuable additional security. 2) (2K) Slipstream the latest hotfixes, IE6, OE6, WAB6 and optionally slipstream DX9. With this setup, you can optionally run NLITE to reduce the source to your liking. If you don't run NLITE, you'll end up with a source that is fully patched right off the bat. 3) (2K) Slipstream the latest hotfixes, IE5 updates and optionally slipstream DX9. With this setup, you can optionally run NLITE to reduce the source to your liking. If you don't run NLITE, you'll end up with a source that is fully patched right off the bat. 4) (XP and 2003) Slipstream all the latest hotfixes (DX9 is already part of these OS's). With this setup, you can optionally run NLITE to reduce the source to your liking. If you don't run NLITE, you'll end up with a source that is fully patched right off the bat. With all catagories, you can slipstream other stuff too like codecs and a host of other things. HFSLIP does not currenly slipstream drivers into your source. BTW, I run option 2 and my w2k installs in about 12 minutes. I have run option 4 with XP and was able to install in less than 10.

@Daemonforce - Can you do yourself a favor and run HFSLIP and then take a look at the SVCPACK folder. Do you see a folder full of hotfix executables and IE6 installers? I'll bet you don't. HFSLIP slipstreams right from the beginning and applies the appropriate registry entries for what you want to slipstream. Why don't you test things out before you convict programs are junk.

If you want to slipstream your stuff, go with HFSLIP. It pretty much does it all; for W2K: IE6, OE6, WAB6, DX9C, WindowsUpdateAgent & WindowsGenuineAdvantage and the rest of the other updates. If you're crafty, you can create a CMD file and HFSLIP will parse the CMD file(s) during the installation. You can even do reg tweaks too.

@saugatak - I'm not going to release it just yet. Why not open a dos window in your HFSLIP folder. Type in IF EXIST FIX XCOPY /H /R /Y FIX\*.* SOURCESS\I386 and see what happens. Also, check to see if those files have a hidden attribute and/or check capitalization.

@murvun - Cool suggestion. Can someone test? I had an idea, perhaps it's a capitalization issue? I believe both my files are upper case.

@ saugatak - Thanks for the info on the hotfixes. I guess that http://www.msfn.org/board/index.php?showtopic=31886 doesn't want to support W2K hotfixes anymore. @All, the new hfslip version is up. It was a small correction for some directx slipstreaming. The prob was that when HFSLIP is run on a 2k source, it decides which version of directx you are using, and it slipstreams the correct files. Pending future microsoft directx hotfixes, this version should be good for quite sometime (unless I feel like adding in another feature). If anyone has ideas for additional features, please PM me.

There needs a slight tweak to HFSLIP for the directx hotfix. FWIW, HFSLIP juggles various versions of directx and leaves the latest stuff there... as I said before, slipstreaming XP is a piece of cake, but with W2K, there is lots more variables (I guess that's why others haven't attempted it). Don't worry it's under control and I expect to send FDV the new version before the end of the day.

@Oleg - Thanks for the FF tips. I'll test them out tonite. Also, I de-cluttered the codec thread.

@Oleg - That batch file mods the mdac.inf file too. It's automated. Here's that site I based that mdac removal stuff. http://jdeboeck.msfnhosting.com/ His batch files are for XP, but most of the 2k file names are unchanged. Try giving it a try and test with VM. Report if you find something good. FWIW, FDV's fileset is pretty **** lean. I like it, but I'm hopelessly hooked to IE6 w/maxthon. I tried firefox and mozilla, but I can't get the favorites/bookmarks to stay resident on my d partition when I reinstall.

Would it be worthwhile to have mini-codec packs instead of a monster one? I mean, separate infs for each type of codec. Like divx is one, xvid is another, etc? I guess it could be further separated by specifying the dlls/axs for each codec. Good idea? Anyone feel like stepping up to the plate?

Dumb question, but why are you trying to slipstream wm9 codecs when WMP10 has them already? Also, I gave the fileset needed to have the latest and greatest in the above post, but you continiously want to do something else? I don't mean to be a ball buster, but you are confusing me by asking for help and not listening.

Yes, you manually replace the two files into the SOURCESS\i386 folder. However, if you get a BSOD again. you have the wrong files.

You can remove tons of junk from the mdac too. I wrote a script to yank it off the source, which I typically run after running nlite. I based this script from something I read a while back... the pre-nlite days. I attached the file. It's a destructive process.... because it deletes files from the sourcess folder. To run, place this file alongside the hfslip.cmd file and run it. It creates a folder called optional and puts all the crapola there. z4_mdac.cmd

Glad it all works for you now. In the future, you may want to consider renaming your files back the way you got them from microsoft if you want to run a future version of HFSLIP.

I used the mega pack only because I had it and didn't feel like downloading another file. I don't plan on slipstreaming real media or quicktime because I dislike them (and don't use them either).

If the switch is /Q:A /R:N, then yes.

Dumb question, but are your 100% sure that the files you placed in the FIX folder are from an XP cd?

@Yzöwl - I kind of assumed that if a file prefix is changed, it was the addition of a few characters and not rename the entire file. For your XP installation, here is what your HF folder should be. If you use this fileset, then you are good to go. msxmlcab.exe WindowsInstaller-KB893803-v2-x86.exe WindowsXP-KB873333-x86-ENU.exe WindowsXP-KB873339-x86-ENU.exe WindowsXP-KB884020-x86-enu.exe WindowsXP-KB885222-v2-x86-ENU.exe WindowsXP-KB885250-x86-ENU.exe WindowsXP-KB885626-v2-x86-enu.exe WindowsXP-KB885835-x86-ENU.exe WindowsXP-KB885836-x86-ENU.exe WindowsXP-KB886185-x86-enu.exe WindowsXP-KB886677-x86-enu.exe WindowsXP-KB887742-x86-ENU.exe WindowsXP-KB887797-x86-enu.exe WindowsXP-KB888113-x86-ENU.exe WindowsXP-KB888240-x86-ENU.exe WindowsXP-KB888302-x86-ENU.exe WindowsXP-KB890046-x86-ENU.exe WindowsXP-KB890175-x86-ENU.exe WindowsXP-KB890859-x86-ENU.exe WindowsXP-KB891781-x86-ENU.exe WindowsXP-KB893066-v2-x86-ENU.exe WindowsXP-KB893086-x86-ENU.exe WindowsXP-KB893756-x86-ENU.exe WindowsXP-KB896358-x86-ENU.exe WindowsXP-KB896422-x86-ENU.exe WindowsXP-KB896423-x86-ENU.exe WindowsXP-KB896428-x86-ENU.exe WindowsXP-KB896727-x86-ENU.exe WindowsXP-KB898461-x86-ENU.exe WindowsXP-KB899587-x86-ENU.exe WindowsXP-KB899588-x86-ENU.exe WindowsXP-KB899591-x86-ENU.exe WindowsXP-KB901214-x86-ENU.exe WindowsXP-KB903235-x86-ENU.exe wmfdist95.exe If you want HFSLIP to work, put those files in the HF folder. Please visit FDV's site for details on the wmfdist95.exe file.

If you want hotfixes slipstreamed, please rename your KB file names BACK to the way you originally got them from Microsoft. Apparantly you downloaded the hotfixes from a source other than microsoft or you renamed them. If on the other hand you only want XP with WMP10 slipstreamed, delete the wrongly named hotfixes from the HF folder and leave MP10setup there. FYI, HFSLIP doesn't work if you rename files (the instructions on FDV's site say this too).