tommyp

Making a small installation source is tricky and sometimes it feels like I'm walking on thin ice to be sure all applications & networking works. Like Oleg2, I want my system to be bloat free and barebones. This barebones approach does seem to improve speed somewhat too... unless it's just a mirage. @Tomkat, perhaps you can reduce the percentage of your recycle bin size? Here's my regedit that I run in my HFSVPK folder so it works for all users. This limits the size to 3% instead of the default 10%. [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\BitBucket] "Percent"=dword:00000003

FDV, Dumb comment, but the original shell.inf file has a reference to the quick launch. In fact, it appears to be the only INF that references quick lanch. Also, will you test out the hfcleanup to do the IE cleansing for 2k3?

This error is fixed in the current release (Nov 15).

HFSLIP is meant to be installed from a CD, just as stated in the ZIP file you downloaded. However, some guys tweaked their source to install from a network. I'll leave that one to the network guru's for your solution. I only tinker so I can't answer.

HFSLIP is really a HotFixSLIPtreamer. The messenger and highmat cd program are add-on's and not hotfixes. With that said, HFSLIP won't process those at this point in time. Your best bet would be to manually install them via svcpack, or repack them with a self extracting exe file. Sorry dude.

That deploy tool is a POS. It's good for starters, but tinkering and reading the forums here are the best bet. Here's the code you need for your winnt.sif so you get prompted on what partition you want. It works for xp and 2k. [Data] AutoPartition=0 MsDosInitiated="0" UnattendedInstall="Yes" [unattended] Unattendmode=FullUnattended OemPreinstall=Yes TargetPath=WINDOWS Filesystem=LeaveAlone OemSkipEula=Yes Repartition=NO WaitForReboot="No" DriverSigningPolicy=Ignore

Has anyone ever used the HFEXPERT folder to slipstream their drivers? It *may* work, but I never really tried. Anyone up to test it out and report back?

Thanks Lupo, I see the error in that last line. I'll update the script tonite...

Willi, I tried integrating your suggestions into the script and I got array errors. In a day or two when the new version comes out, can you modify it and test it out?

Perhaps you need IE5 or IE6 to use WMP? Why not try a different media player, practically every media player is better than WMP.

Shall I place this in the program? If HFSLIP detects these files, it will run it. It's easy enough to add. Let me know. I appreciate the help Willi.

Where in here does it have the following files to be placed into the HF folder? WindowsMedia9-KB885492-x86-ENU.exe WindowsMedia9-KB891122-x86-Global-ENU.exe windowsmedia9-kb892313-x86-intl.exe

I'm not certain that the integrate works with 2k. But if you want, try it out and see what happens. BTW, the integrate switch only adds size to your svcpack folder and does not slipstream it.

The first step for us to help you, is for you to read the stickied posting and how to report errors. Without some files, we can't help you.

Confessions... * My old car wasn't street legal * Things were getting hot and heavy with a GF and I told her I didn't love her, for some funny reason she wanted to go home after that. * Things were getting hot and heavy with a different GF and I told her I didn't love her, for some funny reason she said that's ok, someday you will. Oleg, Can't you just use a runonce command to run the INF at every turn on instead?

@dirtwarrior - FDV has one in his fileset for 2k. If you need one for XP, you're best bet would be to run nlite on a sample source and grab the modded file from that.

I'm not sure if the HFSLIP followers knew this or not, but if you want to install programs, you can do this... Visit this link and download the cab file you like. Open the downloaded CAB file with winrar or equivalant. Place the exe file in the HFSVCPK folder (the exe file is inside the CAB). Please be aware that this is not slipstreaming, it's only integrating via svcpack.

You can only use this on the HFSLIP_051109.CMD file and newer. Well, here's the latest UNSUPPORTED modification for your slipstreaming needs. It's a file reducer and an inf filter. It's geared toward the advanced users. I do not plan on making this official because quite honestly, it would take too much time. It works good enough for my needs. This is an open source NLITE alternative that runs via a cmd file. Nlite is a great program, don't get me wrong, but I like the idea of having an open source to reducing files. There's lots of people smarter than me with respect to this, so I can only bring so much to the table. HOWEVER, I'll leave it up to the community to develop the reducing files. I posted a few sample working files to get you rolling and a few sample files that are questionable. Too much time needs to be invested in this reduction stuff, and if you are really into it, then you[/] will craft the fileset you need. Like I said, I do not plan on developing reducing files, so you are on your own with the help of this forum. If you run into problems, you either reduced too much or you have a blank line in your file removal set or you don't know what you're doing (sorry but did I mention it's for advanced users?) If these files give you too much grief, don't complain to me as I do NOT support it. The files are supplied AS-IS. To summarize on how it works, as taken from the README.TXT file in the zip archive. !!!! If you are NOT using FDV's fileset, you need a modified SETUPAPI.DL_ file in your FIX folder for the cleanup to work properly. !!!! !!!! DO NOT CREATE A FILE WITH AN EXTRA BLANK LINE IN IT !!!! In other words, do not place an extra carriage return at the end of the file. Create a folder alongside the HFSLIPxxx.CMD folder called HFCLEANUP. Unzip and/or create files and place into the HFCLEANUP folder. HFSLIP will not automatically create this folder for you. Three types of files are processed here: 1. RDV=REMOVE DRIVERS * File generated with notepad * List of files with 2 character extension ex driver.sys should be driver.sy * Files listed here are deleted from the extracted driver cab and the i386 folder * Entries are removed from txtsetup.sif, dosnet.inf, layout.sif, syssetup.inf, sycoc.inf * HFSLIP automatically generates the driver.inf file B. REM=REMOVE FILES * List of files with 2 character extention, ex driver.sys should be driver.sy * Files listed here are deleted from i386 folder * Entries are removed from txtsetup.sif, dosnet.inf, layout.sif, syssetup.inf, sycoc.inf C. RIN=REMOVE INF SECTION FILES * Semicolon delimited list * Used as an "INF filter" * Example of a typical line: infname.in;text_to_remove infname.in.... Note it is .in, not .inf text_to_remove..... a string of characters on a line of the infname.inf that you want to remove * Do not use semicolons in your text_to_remove string * HFSLIP will open The infname.inf file, and remove any line with the text_to_remove character string How does it work? Timeline... 1. The RDV files are processed first and deletes the driver files from the extracted driver cab and the i386 folder. 2. The REM files are processed and deletes files from the i386 folder only. 3. The txtsetup.sif, syssetup.inf and sysoc.inf files are processed. 4. The RIN files are processed. When the RIN file is parsed, it looks for a corresponding REM file with the same name. When file ABC.RIN is processed, it looks for a ABC.REM file. If the ABC.REM file is present, it uses the contents of the ABC.REM file as an additional filter. 5. Once the inf file is processed, it is recabbed and placed into the sourcess\i386 folder (unless it was deleted already). 6. HFSLIP recabs the extracted driver.cab, and generates a new driver.inf file. Notes: 1. See example RDV, REM, RIN files. 2. RIN files can have a dummy text_to_remove section (I used qazwsx), but the intent is to prepare the INF file for cleaning via the corresponding REM file. For example: File Cursurs.rin has a dummy section. contents: accessor.in;qazwsx Cursors.rem has a list of files. HFSLIP will open accessor.inf and filter out the filenames listed in cursors.rem 3. You can alter hivexxx.inf using the RIN method (as long as you find a unique string in the file). 4. Strings cannot have a semicolon. 5. Be careful with what you remove. Do not arbitrarily delete files you *really* need. 6. Did I mention that you need a modified SETUPAPI.DL_ file? (post edit - please refer to here).)

Yzöwl - I was using the %SVCPATH% to help out the multiboot guys. Would the script still work with that "other" path?

Easy. Went to google.com, typed in windowsupdate v4 cab download and clicked search.

If it clears things up, I meant that the folder has to be created alongside the HFSLIP.CMD file. Tomkat, all these instructions are on FDVs site. This is a beta thread & there isn't any beta proggies to test at this point.

Please read the end of step 5 of this: http://www.vorck.com/2ksp5.html Google for flashplayer7_winax.exe and read the same site listed above.

It took 4 minutes to google for this: http://v4.windowsupdate.microsoft.com/CAB/...7861.8992013889 Extract the files and place into the hfexpert\codec folder (the codec folder copies to system32 and registers the dlls). I'm not sure if it will work or not though. I never tried it (and never will).

That pesty IE icon... I think this works. Open FDV's HIVESFT.INF and de-comment the 9th line: HKLM,"Software\Clients\StartMenuInternet\IEXPLORE.EXE\InstallInfo","HideIconsCommand",0x00020000,"""%SystemRoot%\system32\rundll32.exe"" ""%SystemRoot%\system32\shell32.dll"",OCInstall HideIE"

Miscellaneous ramblings..... txfaux.dll pop up error: on a real w2k install, it does not appear that this file is registered. es.dll pop up error: perhaps the way to install this should be similar to the comnt5.inf msiprov.dll pop up error: perhaps change the way to install like the wbemnt5.inf slayerui.dll pop up error: this does not seem to be registered on a real w2k install. IE icon: add this to the registry: [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\CLSID\{871C5380-42A0-1069-A2EA-08002B30309D}\ShellFolder] "Attributes"=dword:00100024