bphlpt

This seems obvious. Doesn't make sense to have to need both versions when they could be combined. And on those rare occasions when there are more than 2 components sections, couldn't it be made to handle those, too, if indeed it is always better to only have 1 section? Just putting the cmd file(s) in HFTOOLS causes them to be run, right? No one has addressed the question "Why would you not want to run it and defrag sysoc.inf?" And if we always would want to run it, shouldn't we lobby tommyp to fold the functionality of this into HFSLIP itself? Giving full credit to Geej, of course. Then you wouldn't have to add anything anywhere. I mean, if the actions of HFSLIP causes this situation, and if it is better if this situation is cleaned up, then shouldn't HFSLIP "clean up its own house"? (Absolutly no offense meant, tommyp! ) I guess if Geej is right in his original post and both nLite and Ryan's Integrator both do something similar, it kind of implies ... Well, anyway, just a thought to consider. I realize that there could very well be extremely valid reasons that I am not aware of as to why it should be an "external" option, or maybe not be done at all. I'm interested in hearing the opinions of others, especially tommyp and fdv. After all, their thoughts are the ones that matters most, with their experience, knowledge, and control of the inner workings of HFSLIP. Cheers and Regards

Should this functionality be included in HFSLIP itself and always run, or do I not understand the purpose and usefulness of this script? Could anything bad happen if this is always run after every use of HFSLIP? Why would you not want to run it and defrag sysoc.inf? Cheers and Regards

So just to be clear, tommyp says to add the MS10-002 IE6/XPSP3 hotfix to the HF folder, and Mim0 says to extract shdocvw.dll from WindowsXP-KB978207-x86-ENU.exe and compress it with makecab.exe and put it in the REPLACE\I386 folder. Either way works? Will Mim0's file checker pick up either implementation correctly? tommyp's way seems easier, but Mim0's way seems "cleaner". I know the intention and end result should be the same. Can we get a unified consensus? And dumb question, I assume this applies to the use of the 1.7.9 version of HFSLIP in addition to the latest test release? Cheers and Regards

Is this still available, gosh? Hopefully updated for SP3? Link you posted is dead. I know most of your interest and activity seems to be with Win 7 these days, but I know there is still a large interest in XP. Cheers and Regards

Many Thanks for the quick and thorough reply! Cheers and Regards

Could someone please tell me the new link for - http://www.msfn.org/board/Gosh_s_XP_Build_Environment_t106064.html? The one I listed above is directly from Gosh's Sig. I must say that I'm extremely frustrated sometimes that after the recent board reorganization, (I'm sure that there was SOME good reason for it), that links either from Google and even ones here on the board no longer work, and I can't seem to get the search function to help me find the new location. What is the magic trick if you have the "old" location to use search to find the "new" location? I hope there is one that I just haven't found yet. Most of the time everything is fine since I usually just view my "usual" threads. The trouble happens when I start looking at older threads for the "history" of a situation, then follow a reference to somewhere else, or in this case follow a link in a Sig, and then everything breaks and I end up at the main page with no indication of whether the link was changed, or removed, or I mistyped it, or what! OK, end of mild rant. Cheers and Regards

Oh, sorry. Thanks. I misunderstood. I thought you said the code you posted was "somewhat modified". Thanks again. Cheers and Regards

I appreciate you sharing the source, I always learn something by looking through the inner workings of a software project. But would you mind also sharing a compiled copy for convenience? Thanks in advance. Cheers and Regards

bsouza - Let me get this straight. You took your original install disk, added that month's MS updates using KBxxxx.exe /integrate d:\winxp for each one, then the result was your new install disk and you effectively threw the old one away. Each month you did the same thing, adding that month's updates on top of what you created the previous month. And you've been doing this for how long? Since quite often an update replaces a previous update, but you already integrated that old update into your source, it's no wonder you have clutter on your install disk. I believe your disappointment with HFSLIP, ("If that´s true, I guess my days with HFSLIP are over even before the beginning..."), is misplaced. My understanding with HFSLIP, NLITE and RyanVM's Integrator is that they all work best when used on a fresh copy of the XP install disk, or one with just a SP slipstreamed. While they might work adding new updates on top of an install disk prepared like you've done previously, to my knowledge none of those tools will "remove" the previous updates you added. And as fdv explained, removing them by hand is going to be a LOT of work IF it can be done, depending on how long you have gone through your previous update process. You really will be best served by obtaining a new copy of the XP install disk and starting from scratch. Good Luck, and keep us informed of your progress. Cheers and Regards

It sounds as if you're talking about two different things - the install disk (the CD/DVD you use to install XP on your computer), and your installation (the resulting XP environment that you use on that computer). For both cases it will be better to start over from the beginning rather than try to modify or clean up what you have. So for your new install disk, start with a fresh copy of the original Windows XP PRO SP2 X86 install disk that you have access to, use HFSLIP to slipstream/integrate SP3 and all the appropriate hotfixes and switchless installers verified to install correctly with HFSLIP and using HFCLEANUP if you like, then use RyanVM's integrator, nLite and/or WPI to add any other AddOns or installer packages you like and perform any removals if necessary, and lastly adding any of the DriverPacks you care to add. Then you would have a clutter-free install disk. Each time you want to create a new install disk, do not try to modify the last one you built, just follow the same procedure and create a new one from scratch again. That's why it's a good idea to keep all those hotfixes and installer packages in a folder you will always have access to so you don't have to download them again every time you want to create a new install disk. You can always delete the ones that become obsolete or that you choose to no longer use. As far as your XP installation, remember that the install disk you prepare with HFSLIP is meant to be used to install a clean install of XP on your freshly formatted home computer, not to update an existing installation. I guess the procedure most of us use is to always try to keep a reasonably up to date install disk prepared along with backing up our data and installation tools and files, but apply OS and program updates to our installation as they come out, and only use our install disk to do a clean install 2-3 times a year unless something goes wrong or we move to a new computer. At least that's what I try to do. I hope I correctly understood your basic question and that this helps point you in the general direction you need to go. And welcome to the family! Cheers and Regards

I like the idea of everything in one list, and having the list and the File-checker in sync, ie covering the same things. Maybe a separate Table for "optional" Hotfixes that don't belong in your other tables? Just my two cents. Cheers and Regards

PROBLEMCHYLD, and the answer to this question????? Cheers and Regards

I know this might be a dumb question, but is there any way to "sign", or create the right key, or in some other way convince Windows that the new drivers are WHQL "certified" so they can be used automatically? Just a thought. Cheers and Regards