bphlpt

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

Hi Kiki Burgh! You might want to correct your link you mentioned in the post above. It goes nowhere! Cheers and Regards.

I hope everyone has a very enjoyable and happy holiday seaon. Merry Christmas and Happy New Year! Cheers and Regards

Well, at least you identified the culprit! You probably ought to post your question on their forum, too, to see if they have any idea what nLite did that causes MU/WU to think you need an English update. Hopefully it's something simple. Keep us informed. Cheers and Regards

Hi Mimo! I hope you are having a Happy Holiday! Any update on the following? These are still showing as unknown using the latest list and File Checker. Cheers and Regards.

I totally agree with tommyp. Let's get things working with HFSLIP only without nLite, and probably best to pretty much empty your HFSVCPACK, HFSVCPACK_SW1, and HFSVCPACK_SW2 folders to try and figure out where this error is coming from. It's very telling to me that since it says you need KBwindowsxp-kb905474-enu-x86.exe (English) while very clearly you have added in what appears to be all the correct updates in Portuguese that something is messed up. It's just a matter of finding out the culprit. Please let us know if you find out where the problem was. Cheers and Regards PS: Mimo's File Checker is a great tool!

This is actually the first basic step that all the good list creators use to create their lists. Then, if they want to add more, they begin to add features, such as DirectX, and the optional additions, such as IE8, and keep going back to WU/MU to check for any necessary updates. To be thorough, they might also comb through the various KB articles for advice and look for feedback from other users, like the ones on this forum and others. The difference between the lists is usually how far they choose to go with the additions they choose. Whether they want to try and add it all for the user's convenience, or they choose to stick with the basics, and let anything else be at the user's discretion. I haven't looked at Muppet Hunter's list in detail since he resumed his updates, so I don't know if there is any real difference between his and Mimo's approach/content. It will be interesting to hear directly from them about that. Cheers and Regards

Thanks for the explanation, TommyP. I had thought that Mimo had gotten involved at your and FDV's request about a month ago due to Muppet Hunter being busy elsewhere? Is there any particular difference between the 2 lists in content and/or approach? I wish that Tomcat76's Dynamic Hotfix lists were still maintained. I used to use it a couple of years ago with Win2K. This reminds me of the different versions of Post XP SP3 Update Packs available. I know of versions by RyanVM/user_hidden, redxii, Xable, Onepiece, and Ricktendo64 (Spanish only). And code65536 and 5eraph used to make Update Packs I believe, but don't currently. I hope I didn't leave anyone out, if I did, it was not intentional and I apologize. Anyway, though there are various versions available, For the most part, there are defined distinctions between them in regards to content/approach, from conservative to "kitchen sink". And of course, this doesn't even include other approaches such as Windows Updates Downloader. It's perfectly OK to have more than one update list, but it'd be nice to know if there is any real difference between them. If there's not much of a difference, maybe everybody should work together on a single list, saving the users from confusion, and helping out on the list developer's work load? I personally have thought a lot of Mimo's list and his File Checker program, but I got involved with it during the time when Muppet Hunter's list wasn't being updated as often. That's just my opinion. Any others? And please, this is NOT intended to start any kind of flame war in any way whatsoever. Cheers and Regards

Yes, WIC is in SP3, but MS has chosen not to indicate that there are updates available for it in XP, while they have updated it for Vista. YumeYao has graciously put together an AddOn with these updates that can then be applied to XP to keep WIC more up to date. His AddOn can be found here - Windows Imaging Component (WIC) 1.0.2. Hope this helps explain things better. Cheers and Regards

submix8c, I owe you at least a partial apology. Though I still haven't found them as a separate download, as you correctly said, the SP3 support tools are indeed in the ISO you pointed us to. The SUPPORT\TOOLS\SUPPORT.CAB seems to have all the updated tools, and the deployment tools are also there in DEPLOY.CAB, though the deployment tools ARE available as a separate download for some reason. I guess it's possible the SP3 boot disk is there, too, but I didn't see it. Would you mind pointing it out to me? If you go to the MS site you will find How to obtain Windows XP Setup disks for a floppy boot installation. It provides links to get boot disks for both Home and Professional versions of XP Original Release, SP1, and SP2, but NOT SP3. I suppose if it came down to it that I could make my own by using an SP2 version and substituting SP3 files from an SP3 working system. Any other suggestions? Thanks again. Cheers and Regards

Yes, just go search MS website I hate to be a pest, but I have searched the MS site and Googled the Web in general. If there are SP3 specific versions of these 2 files, I sure wish someone would kindly point them out, because I sure can't find them. Cheers and Regards

I thought so. I thought so, again. No real problem. It's just that if I had followed the File Checker's advice and removed WindowsXP-KB969898-x86-ENU.exe and replaced it with KB973346 as suggested, when I ran File Checker again it would have then told me that, no, KB973346 is obsolete and it has been replaced by KB973525, as shown in Table 7 by this line - So while the File Checker is "correct", it could have saved me a step. Anyway, again, it's no problem. The Tables are correct now, as far as I know. Thanks again for your hard work and for this wonderful, time saving tool! Cheers and Regards

WOW! and I mean WOW! What an absolutely incredibly complete list of potential Restricted Hotfixes! I had NO idea. But then again, as many people have had problems with .NET over the years, it really shouldn't surprise me at all. But, WOW! Well not having any idea if any of those apply to me, not having had any particular problems with .NET myself, wanting to have a reasonably sized install package, not wanting to spend the next umpteen hours/days reading all that info, (lazy at heart, I know, my own fault), really appreciating all the time and effort you spent collecting, evaluating and distributing this info for us, (wild applause erupts!), and yet wanting to head off the most likely potential issues, can anyone possibly suggest a reasonable subset of those to request, or at least read about further? Kind of a top 10 most likely issues you've seen? I would assume that it is very likely that adding too many unnecessary hotfixes is just asking for trouble, so I don't want to do that, but I do want to be as appropriately prepared as possible. Suggestions? It is a shame about the info removal. We definitely want and need to obey all forum rules, but it was useful info. And it seemed very democratic, I wasn't aware of anyone you missed in your references. I would have thought they would have all appreciated the referrals. And after you added that mammoth list of restricted hotfixes, I wouldn't have been surprised if many people just decided to use one of those pre built alternatives. Of well. Keep up the great work! It'll be interesting to see this continue to evolve. Maybe some kind of file checker front end where you could check off the various options you want, or designate them in the ini, then the program would verify that the necessary hotfixes are correctly in place, and if not, would either just let you know or offer to download them for you? Kind of like the HFSLIP file checker program by Mimo? I can dream. Thanks again for this wonderful program. Cheers and Regards

Hi Mimo! Thanks for keeping this so up to date. Minor confusion - WindowsXP-KB955069-x86-ENU.exe and WindowsXP-KB954459-x86-ENU.exe are still shown in Table 2 as Critical and Important under an entry dated 2008-11, while in Table 7 it shows that they are included in KB973687. Also, WindowsXP-KB969898-x86-ENU.exe is shown in Table 2 under an entry dated 2009-06, the HFSLIP File Checker says this is replaced by KB973346, but that is shown in Table 7 as itself being replaced by KB973525. I don't mean for this to be a double post, here and in the File Checker thread, just wanted anyone not using the File Checker to be aware of the above apparent discrepancy. (And everyone definitely should try the File Checker - it's going to be a really great addition to HFSLIP - maybe it even should be folded in so HFSLIP always runs the checker unless specifically told not to, and if it finds any problems, displays them and then gives the user a "Are you sure you want to continue?" kind of option. Might prevent some wasted runs, speeding things up overall. Just a thought!) Anyway, again, Thanks for all your hard work! Cheers and Regards

Almost forgot ... In Table 7 you list that (KB943729) needs XMLLite (KB915865). Therefore, would there be any reason why we would not want to include KB915865 in HF? Also, while this hfslipfc nopause >hfslipfc.log is easy enough, the few times I've run the tool I've usually forgotten and had to run it again or cut and paste from the command window. It might be nice for there to be a Log - Yes or No line in hfslipfc.ini perhaps. Your thoughts? Thanks again. Cheers and Regards