tommyp

Kramy, to make your SATA drivers slipstreamed do it manually. Here's what I did in my source folder. Edit the txtsetup.sif to add the appropriate driver files and other settings. You'll have to makecab the binaries and throw them into the source\i386. Here's what I add to my txtsetup. This is for a via sata/raid mobo. [sourceDisksFiles] viapdsk.sys = 1,,,,,,4_,4,1,,,1,4 viamraid.sys = 1,,,,,,4_,4,1,,,1,4 [HardwareIdsDatabase] PCI\VEN_1106&DEV_3249 = "viamraid" PCI\VEN_1106&DEV_3149 = "viamraid" PCI\VEN_1106&DEV_3164 = "viamraid" PCI\VEN_1106&DEV_4149 = "viapdsk" [sCSI.load] viamraid = viamraid.sys,4 viapdsk = viapdsk.sys,4 [sCSI] viapdsk = "VIA ATA/ATAPI Host Controller" viamraid = "VIA SATA RAID Controller" All I have to say about the BTS installer is this. I read thru the bts installer a while back and what it does is replace your setup files with his own. This doesn't really lend itself nicely to slipstreaming other things. Because your windows setup files are being replaced with his, you will get NLITE problems, as evident on the NLITE boards. Just a word of caution thats all. Then again, his installer I looked at was from a while back, perhaps by now he tweaked things to make them better. See the above crazy code? That is what would have to be automatically generated by hfslip.

@mystek - Read what Tomcat said a few lines up. To rephrase, all hfslip does is pack additional files into the driver.cab file and update the drvindex.inf file. If what you are saying about NLITE making additional folders, you're probably better off just using the OEM method of drivers because it's doing the same exact thing. If you are on the quest for the smallest installation cd, I may suggest doing some homework on the link that murvun posted above. I'm in the same boat as Tomcat with driver stuff. I've been using the OEM method for years and it works 100% of the time.

Kiki - There are instructions for HFCLEANUP are here, click on the HFEXPERT link. You are on your own with XP, if you use all of the reducers, your installation may not work. There wasn't any want or need for reducing XP, so I decided not to create reducers for it. BTW, you could always NLITE the sourcess folder to remove things too.

Ever try XPze on 2k? It works. Before you ask, you can slipstream this with hfslip too.

Be careful what you wish for with the newest mdac_typ. It has lots of extras that aren't part of the original 2k build. I'm not exactly sure why it is needed, my PC works fine with only 3 out of the 80 or so files.

Are there any messages about this in your event viewer? Perhaps they can help us out. Here's something to try out. http://consumer.installshield.com/kb.asp?id=Q108312

The "integrate" command doesn't really slipstream it. Integrate just automates the modifcation/creation of the svcpack.inf so that the rollup exe file executes during svcpack.

Fix.

Yes, you can slipstream the 2k rollup. HFSLIP has been doing the 2k rollup for quite some time.

boooggy - You don't use the sysoc.inf file to register the files?

So much for all the regression testing that they do before they release something. But on the bright side, my windows update says I'm good! Yippie!

If you are using FDV's fileset, the winhttp.dll isn't installed. Try extracting winhttp.dll from your installation source and place it into the win\sys32 folder. After you do that, open a command box (start/run and type in CMD) and type this in to register the dll: regsvr32 winhttp.dll

WTF is that all about?

@fdv - Can you shed some light on setupapi.dl_? Are these different for all the OSs? With the latest round of hotfixes, there are some additional files that msft is putting on our systems. One is for the kb908531 update. Why are they forcing additional files on our systems now? Please stand by, I'm sure TC already figured out what's missing, but I sent him some tips on fixing up the script for this. Anyway, the fixes I had were for 2k only. I didn't test for XP.

Or Linux.

The purpose of the FIX folder is to replace any existing files that are in the installation source. IIRC, sfc_files.dl_ is a non-existing file to begin with. The real filname is sfcfiles.dl_. The *main* purpose of HFSLIP, as stated on FDV's site is to slipstream critical hotfixes. Application Add Ons could work, only if the author of the AAO's thoroughly test them before posting. As some HFSLIP users found out, some authors tested and some didn't. How do you specify your time zone? A winnt.sif file? Can you post the code for your winnt.sif for that section only? We don't need to see the entire file. As far as your extra icons/folders on your desktop goes, this is strange. I hate to sound like a hardnose, but you can test with the tried and true hotfixes to get a grasp at HFSLIP before adding in all the extras? We asked this numerous times already. Apparantly, you are still using some crazy hotfixes that don't slipstream correctly. If the slipstream isn't correct, then your OS could be hosed and the proper registry entries aren't made.

Approval already given for the hfsvcpack. Don't worry if they are too lengthy. For us old timers that have been using hfslip since it's inception, the script will automagically change the foldernames to this new scheme.

IIRC, you can drop FDV's fileset on top of your installation files. For HFCLEANUP, it's easiest to run HFSLIP and choose A, B or C for file compression.

It wasn't supposed to be an April Fool's release, but the April 1st hfslip was buggy, no fooling. IIRC, when using the BBIE program, it outputs a lower case filename. The commandline for the mkisofs program is case sensitive. This is HFSLIP's mkisofs commandline is written the way it is. The current version works.

A while back I ran some tests with variations of xp and 2k. Today I added to my list. This is just a barebones OS (no applications installed). All the favors that XP does for me don't work. I'm slowly getting my way down to FDV levels whilst maintaining the IE core. HFSLIP'd OS Handles Threads Processes Commit OS Footpnt I386 Size ================================================================================ XPSP1/dx9/codecs 2702 182 12 57meg 377 meg 153 meg XPSP2/codecs 2750 180 14 55meg 376 meg 150 meg 2k/IE6/dx9/codecs 1713 120 11 55meg 299 meg 125 meg 2K/FDV/dx9/codecs* 1944 149 12 49meg 379 meg 228 meg 2K/FDV/dx9/codecs** 1765 139 12 46meg 279 meg 138 meg 2KFDVIE6 1446 120 11 33MEG 2K/ie6/dx9/codecs* 1737 126 11 50meg 289 meg 228 meg <-hfslip red. 1/27/06 2K/ie6/dx9/codecs* 1700 130 12 35meg 245 meg 100 meg <-hfslip red. 1/27/06 * FDV fileset with DX9C/codecs, not NLITE'd. ** FDV's fileset with DX9/codecs, not NLITEd. It was reduced with a reduction fileset that Oleg2 and I were putting together.

Kramy, the caller in the beginning that you have in bold is from a very old version of hfslip. I would recommend to grab the latest test version (it works as far as I am concerned). Here's a tip for you, perhaps one day I'll introduce additional features. But, for instance, lets say you finished making your sourcess using hfslip. Then one day you want to replace a file or two. Instead of re-running hfslip entirely, run hfslip and instead of typing in I have read.... type in makeiso instead. The only thing that will happen is that an ISO will be created using the stuff in the sourcess folder. It's a little easter egg. Speaking of which, it's almost easter.

The sfc.dl_ on fdv's site is for 2k and I use that file all the time with 2k. It *may* work with xp, but you'll have to rename it to sfc_os.dl_, xp uses a different filename. I haven't tried it though.

HFSLIP does two things. First , it slipstreams the latest binaries to the sourcess folder and second it creates INFs files on the fly depending on what you are slipstreaming. A few months back before MSFT started adding files to your OS, the WU issues were mainly registry related. We got that part figured out. Now, the problems that generally arise are when MSFT *adds* additional files. But I think TC and I have a hold on that now. On the flip side, if you are trying to slipstream garbage, then you'll get garbage. Garbage in=garbage out.

TC, the HFSPACK folder.

dziubek - I found some coding probs and alerted TC about the fixes. There were about a half dozen or so. Please give a bit for TC to incorporate them. Camarade_Tux - Good point about the extra folder creation on initial startup. All my source folders have the latest SP level so I never really bothered to think about it.