tommyp

It's not there because you're removing it with hfcleanup. Remove osoptions_wga.* and you'll be ok. You may need to keep the BITS too. Why bother removing stuff to visit windowsupdate? Use the hfnetchk tool instead. Saug - You may want to try out nlite to see what each reducer does. The reduction set is loosely based on that. With nlite, you can see dependencies for various things.

If I remember correctly, there is an option in NLITE to slipstream updates the same way that hfslip does. Nlite still doesn't slipstream IE6 into W2K and it doesn't slipstream DirectX9 into any OS (other than XP service pack 2).

It works, I tested it with 2k and xp. To search thru the setup infs, this may help you out. Manually create a folder called INFS alongside your source folder. Open a CMD window and type this: FOR /F %I IN ('DIR/B/A-D/ON source\I386\*.in_') DO EXPAND -r SOURCE\I386\%I infs & ECHO %I EXTRACTED (that needs to be one line) Once that's done, manually copy all the *.INF over to INFs. If you need to search INFs, right mouse the INFS folder and search. Piece-o-cake.

The general way of the RIN file is identify what setup infs need to be cleaned out. In the case you pointed out a few messages up, those registry entries get added in HIVESYS.INF. So, to clean it out, first you must tell hfslip what INF needs to be cleaned out. Next you have to tell what line to remove from the INF. This is done by a RIN file. The filename is specified by the filename with LESS the last character of the extension. So the filename for RIN format is HIVESYS.IN. Next, looking through the hivesys.inf you can see the entries you want. You need to specify a unique string of characters (no spaces or weird characters). In other words, think of it this way. Name_Of_File.IN;String_To_Filter_Out I'll try to clean up the info file. It's not that hard. It's just hard to explain logic and nested loops. I'm glad I don't program for a living.

Comrade - Do you remove mdac using nlite? If you remove mdac, then why bother with adding an mdac update? For my home machine, I find zero use for mdac.

Instructions are in the ZIP files you downloaded.

Saug - All the RIN files filter various INFs. Without filtering, then setup will crash all the time. True I may not have gotten every single entry, but it's a start. To get rid of those above entries, look thru the setup infs and see where those get created. It's in hivesys.inf. So, to get rid of these from the installation, you create a RIN file. First character set is the filename (less the last letter of the ext), a semicolon and a unique string. The entire line in the unique string will be deleted when hfcleanup is parsed. In other words, create a file called OSOptions_OS2Posix.rin. HIVESYS.IN;os2ss.exe HIVESYS.IN;psxss.exe HIVESYS.IN;Posix

No prob Kiki. BTW, the Jul 16th reducers are released.

You mean a reg tweak for ms-explorer two pane? I think the reg settings are here: [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Internet Explorer\Toolbar] [HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Explorer Bars\{32683183-48a0-441b-a342-7c2a440a9478}] [HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Explorer Bars\{C4EE31F3-4768-11D2-BE5C-00A0C9A83DA1}\ContainingTextMRU] [HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Explorer Bars\{EFA24E64-B078-11D0-89E4-00C04FC9E26E}] [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Streams\Defaults] You'll need to do your settings, reboot, export the reg settings save them in HFSVCPACK. I can't share the settings because these settings are different depending on what OS *and* what IE core you are running. Sorry about non-HFCLEANUP info.... let's resume the main thread. Saugatek - FYI, the HFCLEANUP reducers *do* filter INFS and HIVES.

Different people like different reg tweaks. This is why there is a separate folder to place your reg files. For example, I like the two paned and detailed view with explorer. Others like the stupid big icons. HFCLEANUP's intent isn't to tweak your system, it's meant to cleanup your system. . With the hfcleanup fileset that is posted, registry cleanups are part of the process. By registry cleanups, I mean that portions of the registry and setup INFs are deleted because they don't apply to a install with HFCLEANUP. Care was taken, but it's impossible for me to check everything out. There's too many variables to test.

Running all but the 4&5Z's will leave the IE core intact. The ZZ_IEGARBAGE reducers remove iexplore.exe and internet explorer folders, but leaves the IE core intact so you can use Maxthon or other IE core dependant browser. If you don't run the 4 & 5 Z reducers, you'll see the add/remove programs applet. What version/date of the hfcleanup.zip file are you using?

One of the reducers that has 4 or 5 Z's will cause the add/remove applet to not work. This is because it is dependant on some obscure MDAC files and IE. Typically I do not run the 4Z or 5Z reducers.

Users of HFCLEANUP have options with the current reduction set. If they want to reduce more, then run more reducers. If they want less removed, then don't run all of the reducers. For instance, of all the reducers posted in the ZIP file, I do not run all of them because I still need functionality. Others on the other hand, may not need the functionality that I need. I kind of like the modular approach.

I just took a look at the installation INF. OMFG! A 1.5 installation INF! I would say that HFSLIP should wait until it becomes gold before (maybe) tackling this bloatware proggy.

Clint, I work forward to working with you, if you want to. What OS are you looking to optimize?

In addition to the svcpack.inf file, if there's modded & repacked binaries in the source, HFSLIP may or may not replace them with the latest and greatest.

Dirt, Can you PLEASE read the instructions? 99.99% of the Q's you ask (not only on this thread) are already answered.

Dirt, As quoted from the latest readme. I'll assume that you read it, but just in case.... The contents of this ZIP file was developed using 2000 ENGLISH. Later on, 2003 was added to the mix. Don't complain to me if it doesn't work for you. If there is a problem, figure out which reducer is wrong and post *constructive* criticism. A simple comment like "it don't work" won't get you help from me. There's an old saying, God helps those who help themselves. If a reducer is wrong, then post up exactly how to fix it and it will be corrected. If you ask stupid questions, they will be unanswered. Sounds like you have to add stuff back in. Figure it out yourself which reducer(s) that does not need to run.

Actually, I kind of prefer to leave them all lumped together as one zip file. HFCLEANUP is hardcore with functionality by design. I don't plan on separating each reducer into low/mid/high performance "buckets." Maintenance on multiple filesets would be a bear. It's up to the end user to figure out what his/her system needs (maybe they need to be softcore instead) . As a case in point, with the HFCLEANUP.ZIP file, I do NOT use all the reducers myself. There are some things I need, but others may not need. Nevertheless, the option is there to use a particular reducer if they choose. Users are encouraged to test out NLITE to see what they need. It has lots of interactive menus that tell what's good/bad. The HFCLEANUP files are loosely based off NLITE. Once you figure out what you need using NLITE, just use the corresponding HFCLEANUP files. I don't plan on doing a fancy writeup telling what is good/bad to reduce. 9 times out of 10, users don't read anything anyway.

Dirt - Just read the first stickied post. It has links and lots of other information.

It amazes me how people can be so ungrateful for a free utility.

Here's what I get with 2k/ie6/dx9/hfcleanup/hfexpert/lots-o-codecs (way more codecs than I really need). This data was taken in early January 06. Things may have changed somewhat, but probably not too much, but I haven't verified it in a while. Installation takes 12-13 minutes from CD bootup to first logon screen. This is just barebones OS at this point. ISO (i386 directory) - 100 meg Handles - 1700 Threads - 127 Processes - 12 Commit - 35 meg OS footprint - 245 meg When I say hfcleanup and XP is buggy, I mean that sometimes you could get a BSOD during installation. I haven't pin pointed it (and I really don't want to figure it out either).

Yes, HFSLIP can do reg's, inf's and cmd's.

I guess the line that is right after the the modded DLLs statement is somehow unnoticed. If you don't know what either file is, then please don't HFCLEANUP. If you read through FDV's site, he tells you how to modify them, there is no need for me to hold their hand and tell them to go to a certain page. As far as directions go, one day I'll update them. But if you really need HFCLEANUP to work, put the contents of the hfcleanup.zip into a folder called hfcleanup. Next, put the modded and cabbed dll's into fix. Last, run hfslip and choose a, b or c for driver.cab compression. Further development with the reduction set with XP and 2003 has been suspended. I have no desire to create them, and I have no time to waste on OSs that I'll never use. Perhaps someday, someone else will create the reducers, test it in all variations of HFEXPERT etc, and release it.

Nlite is good at reducing the installation because it gives descriptive words and impacts about each thing to be removed. Nlite has lots more support by many users all over the world. Many of these users provide constructive feedback on what files to keep and what not to keep and what registry changes should be made. To top it off, NLITE is point and click based but the user is not presented with information all at once. With that said, HFCLEANUP can be good for people who know what they want to delete, what registry entries they want slipstreamed, what hives they want to filter themselves, etc. HFCLEANUP is pretty powerful, but it's not for the novice and it's definately not for people who can't read the instructions. At this point, HFCLEANUP is mature for 2000 (there is a few more things I added but it not released at this point). HFCLEANUP with XP is buggy, HFCLEANUP with 2003 works.