tommyp

I'm not sure why they call it a slipstream. Installing via svcpack isn't really a slipstream. Anywho, it is easier to run these via switchless installers with WXP than W2K. This is because svcpack is a little better with WXP. Here's how to do those intallers. Download those cab files you linked, and extract them. Place the EXE file into the switchless installer directory. Done. They make a big deal about installing software at svcpack. This feature was available with HFSLIP for quite some time.

You are using a buggy & old version of HFSLIP. Please download the latest version and all *should* be ok.

Try this also. Sorry I can update and upload for a day or two. http://www.msfn.org/board/index.php?s=&sho...ndpost&p=454417

No hfnetchk = no idea on what's wrong and how to fix your issues. Strange that you say it's no longer supported. It works fine for me (and others too).

We can help if you post your error_report and hfnetchk logs. BTW, SP2 already has WMP9. There is no need to install it. As far as the 898461, there is a residual error when I went to town modifying HFSLIP this past weekend. Line 1343 has an extra space. Edit as follows and you should be OK. is ECHO 1000 = system32\PreInstall\WinSE\%PKG% >>SOURCESS\I386\TXTSETUP.SIF should be ECHO 1000 = system32\PreInstall\WinSE\%PKG%>>SOURCESS\I386\TXTSETUP.SIF

The HFEXPERT issue was resolved with the Jan 22 release (the current one). I went a little too wild when editting the other day. As far those other hotfixes go, can you attach your error_report file and the results from an hfnetchk report?

Your source folder should not be an issue. Does windowsupdate report the 885836 missing too? I seem to remember that hfnetchk reported that one missing for me too.

mag01 - Welcome to the board. A few Q's for you. 1. Are you using a virgin SP2 source? Did you run any other slipstreams on your source already? 2. Can you give me a direct download link to your problematic hotfix? I only have the english one (which slipstrams fine). The Localization thing will get fixed in the next release (thanks for pointing that out). I haven't had any feedback from your language to confirm your language. Thanks for the tip. Changing that will only affect the windows update agent. The other variable was originally set up to decipher some hotfixes at one time.

New version posted 1/22/06. Lots of miscellaneous bugs removed. Post any issues or submissions. Thanks!

Thanks dude and thanks from the HFSLIP folks. I'll stay in tune with your other thread for any updates. We also have hotfix lists that are stickied on this subforum if it helps. Keep up the good work.

jcarle - In simplest terms, HFSLIP is a commandline utility to rip apart the hotfixes and slipstream them into an installable source. If you generate a commandline (cmd) file that does something that HFSLIP doesn't currently do, I can add that into HFSLIP. Or, another possibility is for HFSLIP to call on an EXE so the EXE can do its magic silently (i.e. no clicking or minimal clicking required). Your hotfix downloader seems really promising (and pretty cool I must add). I kind of prefer to have everything pretty much silent so the user would run HFSLIP answer a few Q's and come back 10 or 15 minutes later for the slipstreaming to complete. Here's some ideas to throw out there. Constructive criticism is appreciated. HFSLIP call XPDOWN (your utility; an exe file) with commandline switches (switches could be to optionally delete old hotfixes, update new hotfixes from HF folder, redownload all fixes, etc) HFSLIP or XPDOWN to see if an internet connection is available XPDOWN does its magic (if it sees an internet connection it will automatically update the files) Once XPDOWN is complete, it exits silently HFSLIP resumes dissecting and slipstreaming the hotfixes into the source. If XPDOWN can support 2k, xpsp1, xpsp2, 2003 and 20003sp1 it would be really cool. For 2k there are plenty of variations... IE5 or IE6; DX9C. I haven't tested your utility, but who is the "keeper" of the overall latest and greatest hotfix list?

Yzowl, with all due respect, you do know your stuff with cmd scripts. However, the submission you PMd me a few months back for the HFEXPERT section didn't function properly. When I told you that it didn't work, you told me the same thing you told Tomcat76. When I asked you to test things first before submitting them to me, you got a little PO'd. But getting back to the scripts you do send, by modifying them a bit, they work nicely.

Sorry I have to disagree dude. Not everyone uses XP, not everyone wants to wait a few days/weeks for a new RyanVM pack release after patch day, and some don't use English. HFSLIP does it all: 2K, XP, 2003 (all languages too). Nlite can't do "all" of 2k. I'd like to script this into HFSLIP, but I don't have the mental capacity to do it.... or the time.

I saw that utility the other day. I like Nuhi's idea of using that mssecure.cab. I'm afraid I won't be able to script it in. It's beyond my knowledge base. However, I do accept tested "plugins" for those who generate them. By tested, I mean code that is tested so I can drop it into HFLSIP. If someone submits a script, I would prefer something that does not need tons of plug-ins. My goal is to keep HFSLIP as lean and mean as possible.

You do not need to reload just because of that error message. Download the SDK pack, extract the EXE with your favorite decompression program, put the CAB files into a folder called HFCABS. Keep only the cab files specifed on either tomcat's or the_guy's list. If your error window was looking for that particular DLL, then open the Apr2005_d3dx9_25_x86.cab or whatever cab file that corresponds to your error. Put the dll file into your system32 folder. You do not need to register these dlls. You may as well do all the d3dx9_*_x86 files, there's only 4 or 5 of them. Point taken about placement of the wga cab, it needs to go into the HFCABS folder.

You're not SOL. I think you may have to either remove (or rename) your svcpack.in_ file and/or remove (or rename) your svcpack folder.

http://www.vorck.com/2ksp5.html step 12.

Dirt, who said you were a pain? Oleg2's set is pretty good, but it's a bit much for my tastes. I only use a subset of what he offers. So you can configure it however you like. The more patience you have, the more rewards you'll get with a fast system. And if your clever, you can help Oleg2 out with more reduction.

It's pretty straightforward to what is being reduced. If you want java removed, then put the java files in HFCLEANUP. If you want MSAGENT removed, then put the MSAGENT files in HFCLEANUP. If you want it removed, the put the file in HFCLEANUP. If you don't want it removed, then don't put into HFCLEANUP. The removal process is very similar to NLITE, but is more configurable.

Oleg2's reducers: http://www.msfn.org/board/index.php?showtopic=65537

Glad you're up and running. Keep us posted on how you make out.

HFSLIP will only be processed if both of these conditions are true 1. if you select A, B or C for the driver compression (this is the merged cab option) 2. your HFCLEANUP folder must be manually created and filled with the reducer files.

.....or use HFSLIP to slipstream it.

I understand that you said that your SP4 works, but I'll have to ask you this one again to be sure. Did you do a test of your SOURCE folder via a virtual machine (or another boot cd made from the SOURCE folder)? What I am trying to point out is that sometimes when you copy files from a CD over, they all do not copy over properly. I've seen it numerous times. If any files didn't copy over properly, HFSLIP won't work, FDV's fileset won't work either. A simple file comparison won't work, you need to test it. BTW, how much free disk space do you have? You'll need a few gig for HFSLIP to work properly. Have you tried this method? What you do is copy your source folder somewhere else and drop FDV's fileset into the I386 folder.

Per Bilou's request, the setup files were cleaned up, and an optional update cab feature was added in the latest HFSLIP (HFSLIP_60117.CMD). Any tips or updates appreciated.