tommyp

Kiki - This is why I don't create hfexpert automagically. Please read here. http://www.vorck.com/hfexpert.html.

This was a non-problem problem at one time with HFSLIP. I haven't seen this since last year. All works fine with my system as far as my winnt.sif file goes. I use the winnt.sif file and a regedit to disable some IE desktop stuff. Works great. BTW, why not just create all your users on the single pc, login to each acct and delete the icons?

Tomcat and I are having some serious discussions about hfslip and life in general. We decided that too much love was put into the script and so far, more people are happy about the result. At first I was hesitant to add things/extras in, but the general vote as seen in this thread is that people like it. All I have to say about this now is that things are getting tweaked and cleaned up and the new version of HFSLIP is..... Don't be a baby about it.

RBCC - HFSLIP takes care of the base OS. It's up to you for applications. If you are using an OEM structure, just be sure to use a winnt.sif file to copy the stuff over. But to answer your Q, yes you can use your OEM structure.

Kiki - why not make a silent & switchless installer for this and throw the file in the hfsvcpack folder?

Kiki - HFSLIPing your codecs works with 2k/xp/2k3. For example, you can copy your HFEXPERT\CODECS from 2k to a xp to a 2k3 HFSLIP workign directory and all will work fine. There may be newer ones out there. If you really need bleeding edge codecs, you can create the update yourself, but you'll have to visit a slew of sourceforge websites to grab them. It's not that hard, except for creating the INF file. FYI, I've been using the same codecs for the past 8 months or so without a hitch. Once Tain gets back up and running after his laser eye surgery, maybe he'll update things.

Kiki, Sounds like you are on a quest for a small installation CD. Here's a hint for you. If you are working with xpsp2 in your source, you can delete your WIN**UPG folders. I don't think that there are any "normal" hotfixes that add/remove to these folders, should not get recreated when hfslip is run. I am unsure of the ASMS folders. I suppose this can be incorporated into HFCLEANUP though. Let me think about this one for a bit. IIRC, there may be some other folders you can remove as listed on unattended.msfn.org. As far as the USB program goes, I don't feel it is required for this script. Why not install this one when you install your other programs?

Bâshrat the Sneaky - Welcome to the HFSLIP forum. Tomcat76 and I are the developers of HFSLIP. In case you are not familar with HFSLIP, we use a CMD file and we strive to slipstream in the "pure" sense. Meaning, we replace binaries with updated ones, and try to leave the overall structure of the windows setup intact. Of coarse we have to modify the txtsetup.sif, dosnet.inf, sysoc.inf, and svcpack.inf. We overwrite the svcpack.inf original with our own depending on what the user wants to slipstream. Typically our svcpack.inf have no executables in them. If you have any detailed Q's drop me a PM so we can discuss. BTW, is there a tag/switch we can use when running your driver packs so we can specify the working directory of the windows source? I'd be interested in calling your driverpack setup files from HFSLIP (also a CMD file). Thanks!

Sorry, but HFSLIP needs a virgin source, just like NLITE and the other slipstreamers. You could always *try* it, but remember HFSLIP is designed around using an unadultered source. Maybe you can try running his driver packs *after* running HFSLIP?

@Aluminum - Of coarse HFSLIP will support FDVs fileset. It's a must!

I asked the thread-starter an important Q yesterday. I eagerly await his reply. For the records, TC and I are rapidly comparing notes, optimizing, tweaking, and things are looking good. After seeing the love that was put in, I can't see why to remove anything, well some things will be removed anyway.... stay tuned.

Actually I'm to blame with the documentation. Per the stickied post, I don't have tons of time to code or even sit back and scratch my ......

TC - please update your links to that macromedia stuff. all - please stay on topic. if there are codec issues, please post on the codec thread. No need for you to apologize and I'm sorry to sound like a butthorn. I just want to keep it clean and on track for the test releases.

Thanks for noticing my missing #4. Maybe the there are readers out there still. Here's what I see as a "base" HFSLIP, with rationale. service pack slipstreaming - an HFSLIP must hotfix integration - this is what HFSLIP is all about ie6 integration - an HFSLIP exclusive codec slipstreaming - I use this all the time your HFEXPERT section - I use this all the time driver integration - in honor of Oleg2 HFCLEANUP - a personal favorite of mine msxml slipstreaming - this is needed for some of my apps wga slipstreaming - it's only a few lines of code and is worthwhile media player 10 slipstreaming - it's easy so why not directx9c and the stupid new directx9 dlls - needed for some things I use windows update agent - seems to be needed windows update catalog - seems to be needed microsoft update catalog - seems to be needed questionable mdac_typ - unsure about this one. I don't see how this is really needed. application add-ons - there seems to be too many untested ones out there that cause probs xpize - does this seem buggy or is it me when using svcpack? After sleeping on it last nite and not thinking about it during the day, it seems that there really doesn't seem to be much to remove. Perhaps lots of script cleanup. Yzowl, what exactly did you have in mind on what to keep and what to exclude. I'm on Tomcat's side trying to figure out what you mean with something else calling hfslip. YOu said that you like to rewrite cmd files, and you stated one time that you redo HFSLIP on occasion. Perhaps you can post a cleaner section of the HFEXPERT section. I had tons of troubles with the last script that you sent me (which is why that part looks like a kid with a coathanger sticking out of it's head).

Yes, you can put a pause in there to delete your files manually. How many meg of space do you expext to reclaim?

Kiki - I'll take it you haven't tested the waters with codecs yet. The codec instructions work for 2k/xp/2k3. If there are newer [dll, ax, etc] files, it's up to you to obtain them. If there's more codecs you need, then you'll have to add codecs. I work with the set listed in my post (except the real media stuff). I have not had issues playing any types of videos (except real media stuff).

Methinks Yzowl and I are on the same page. I kind of prefer the external add-ons too. TC - how hard is it to move the add-ons to run from the hftools instead?

Around this time last year, I was calling the script "slipstreamer". I emailed FDV out of the blue asking if he could host the file. I figured it was a perfect -and- ironic mix. It was a script where the user had the choice of either slipstreaming IE6 -or- removing IE all together. It was a strange request, but FDV liked the idea. He asked for some catchy name. I thought about it over a smoke, and said HFSLIP, as in HotFixSLIPstreamer. All I wanted was a lightweight hotfix slipstreamer. Once NLITE didn't honor some requests that I had for about a year, I came up with HFCLEANUP to reduce my source. This fit all my needs. As we all see, over the past year, it does far more than intended. I am nearing the opinion that it is getting a bit bloated too, and I prefer that no additional features get added. It's getting waaaaaay beyond the scope of the project. As a surprise to many of the readers, I'm on Yzowl's side on this one. Lately, I've been thinking. Some of my dislikes the past few months. 1. Alternate expand utility. This brought me over the top. It was like Coca Cola changing their recipe after 100 years. The main dislike I have now after viewing the code is useage of the alternate windows expand file. I see absolutely no reason why to use the alternate version. Right now, the script looks awefully messy with all the %expand% variables, and I would prefer to see it the way HFSLIP was intended, using as many built in windows applications as possible. If the end user of hfslip is knowledgeable enough to use an alternate expand utility, they should be smart enough to put the file in their win\sys32 directory. Heck, you could even make hfslip copy the file from hftools to the sys32 folder! However, if the masses (not one or two people) prefer the alternate expand utility, then I'll have to rethink my opinion. Hopefully TC will adjust this accordingly. I just would like a clean script. 2. Application Add Ons. I know lots of people love them and some dwell on them. I hate them. I knew from the start that they would be bad news. You are entrusting people with preparing and hosting error-free add-ons. If there was any error in the add-ons, then the installation just-won't-work. As evident in the past two months or so, some of the fixes is due to modifying the script to accept these addons. However, a majority of the posts in the hfslip forum seem to be because of faulty addons. This isn't HFSLIP's fault. If I were an outsider trying to make a decision on whether or not to use hfslip, I'd read horror stories about these addons and get instantly turned off. I don't want to turn off new users. Maybe the add-on script can be removed and placed into the HFTOOLS as a separate entity? Maybe make a specific hfslip-aao integrator subforum? I don't know. 3. Worthless Windows Updates. It astounds me why people are gung ho that equate "recommended updates" with critical updates. These recommended updates typically add files to your installation CD. If there are crazy files to add, then the script needs code inserted. It drives me crazy when I see posts about this. Case in point, the latest round of updates. People download the file and don't bother reading the KB article. The article says something along the lines that if you have both flash 6 is installed AND Adobe installed, then you should apply the update. Sometimes reading things helps, people have been reading for centuries. This leads to the next item... 5. Reading directions. For some reason or another, people are brain dead sitting in front of PCs. They don't read and they expect things to be served on a silver platter. Sounds great, but unfortunately, I'm a pleb and have no platters to pass out. True the general instructions aren't up to snuff now, but 95% of the problems are from people who don't RTFM. They are prompted on the screen on what to do if something happens, what goes where. Usually I feel like a skipping record asking for log files when people report issues. Thanks to super magician, I don't have to do this now. (Thanks super, you're a lifesaver!) Would you know that most of the fixes last year was to id*** proof the script. I may have missed stuff though. BTW, if anyone reads the script code, you'll notice a variable called AHTEST. I won't say what the total meaning is behind it, but all I'll say is the 2nd word is HOLE. So you could see my frustration waay back then too. On a sidenote, I've been running the standard HFSLIP, with hotfixes, ie6 integration, directx, codecs, hfcleaup and a slew of regedits. I steer clear of the obnoxious and unpredictable add-ons and other worthless programs. Results? I've been error-free. In closing being a cmd script, there aren't many additional utilities required for the script to run, so it still is relatively lightweight. But like I said, the script is getting way beyond the scope of the project. My vote is to keep it lightweight and request no more additions. KISS is the name of the game with this project. (sorry if I offended anyone)

There's no plans on removing single files from the driver.cab alone using hfcleanup. This goes a bit out of scope for the hfcleanup portion of the project. IMHO, you should worry more about what is installed, then the size/amount of files on the cd. There's an old saying, if it ain't broke.........

You need to make a directive file, or you can just use a file compression program that does cabs.

From the readme.... 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, layout.sif, syssetup.inf and sycoc.inf * HFSLIP automatically generates the driver.inf file

6. Tread these waters carefully if you do. There are registry hives that get installed for these. Your best bet would be leave that alone (or rip them out). I guess you could always try it out. I never have. 7. You can slipstream codecs on 2k/xp/2k3.

HFSLIP.LOG?

Tux - You can do delete these extras with a RIN file in HFCLEANUP. Read up on the hfexpert page to see how to do it. You'll need to do a driver merge option to take advantage of the reduction. Hint on the file creation... 1394bus.sy 1394vdbg.sy abp480n5.sy acpi.sy acpiec.sy etc

FYI, Nlite doesn't remove some things when selected. I'm not sure if this is by design or what. I have asked Nuhi a bunch of times to remove some additional files, but the requests fell of deaf ears (or maybe eyes). This is why I created HFCLEANUP. With HFCLEANUP, I can create a ultra slim and updated 2k with no need for nlite. Total duration is about about 8 minutes. . It was my answer to fixing a fully slipstreamed 2k with the least amount of keystrokes and programs to install on my system. HFCLEANUP can be tailored to XP too, a majority of the reducers can be used on 2k/xp/2k3 at this point. All I can say is that if you won't need something in your source, don't slipstream it in the first place. For example, why slipstream wmp10 and then remove it with nlite? Seems foolish IMO. Also, FWIW, an NLITEd HFSLIP works best when selecting the merged cabs (A, B or C). This will eliminate a bunch of dupes in the cabs and produces the smallest footprint i386 folder. Camarade_Tux - OT - What is your favorite flavor of linux?