tommyp

CMD file updated, see first post. Lots of changes this go around. No more setupapi or sfc files needed. Windows update seems to work OK. File works with 2k and XP. It doubles as an alternativce to RyanVM's update pack (if you want to control what gets installed). New MSI installer works great. Any constructive critism appreciated. As usual, use at your own risk.

With the old Norton, I just extract the exe package as suggested above. However, I place the contents of the extracted files to the VIRDEFS folder of the installation source. Works like a champ for me.

I'm working on a new version that makes the windowsupdate people happy. Well, at least it will report practically no updates are needed if you put the right files in the right folders. I should post it sometime early next week as I'm doing a bunch of test runs. Oh yea, it will only require to edit ONE file instead of a whole mess of them.

Try Nlite B)

Yes you are absolutely correct. When you open IE and click Help/About, the information displayed (the version number and the Update Versions) from the registry. Weird huh? So if you wanted to, you can make an IE version 600 instead of 6. HAHA. Thanks for pointing out the issues with NLITE, and the issue is solved. Apparantly, NLITE likes to see a compressed syssetup.in_ instead of a renamed text file. I updated the instructions, and changed the CMD file a bit for the XP hotfix integration to function now too.

Edit the CMD file with notepad (or whatever text editor you have).

@At0mic - You're absolutely correct. I re-read those instructions and realized that they were a bit vague. I recrafted the instructions a bunch and it seems to flow a lot easier now. The new download is available on the first of these threads. With the help of the electrician, I found a little bug that needed to get exterminated, thus the need for a little "correction" to the cmd file. Also, the post service pack inf file is best described on www.vorck.com. In brief words, it's the "essential" regedits that windows needs to be secure. BTW, being a dumb computer user, what is the purpose of the MDAC version 2.8? What benefits does that have over the one that comes with W2K?

I attached a typical INF file that makes windowsupdate happy. For this particular one I attached, it shows the one that electrician discusses. If you save the file, do a right mouse click and select install, and then revisit windowsupdate, it will say the patch is installed. However, if you look at the contents of the INF file with notepad, you can see that windowsupdate only checks for the registry entries that the inf makes. So, if you really want to make a "secure" system according to windowsupdate, all one would need to do is do a regedit for the ones that it checks. How's that for security? This is why I ditch windowsupdate and use an alternate program.

No disrepect taken. If you think the instructions need to be a bit clearer in some sections, then please ask and I'll update the instructions.txt file. I have tried to put the important tips in the instructions, and even put some key items on the top few lines of the file. I haven't really taken more time for the instructions because I only do this for the fun of it (i.e. not paid to do it). If you want more details please visit FDV's hotfix site @At0mic - You may want to try xpcreate as an alternate windowsupdate friendly windows updater.

@fistandantilus Please re-read the instructions.txt file. It also happened to be the same file you you closed without reading when you ran the cmd file. The 9th line talks about windowsupdate website. ALL WINDOWSUPDATE.COM does is verify registry entries. It doesn't verify all critical update dll/exe/binaries. So if you want to make windowsupdate.com happy, then please use an alternate slipstream method. If you have repacked your netfxsp11.exe and specified the switch in the cmd file? There's also instructions for that too in the instructions.txt file.

I get those errors too, it's nothing to be alarmed about. The reason why there are errors is that it's trying to delete non-existing "dummy" file(s). I guess if I have the echo turned off then you won't see anything, but then again, it's nice to see something happening on the screen at the same time. Did you try out the slipstreamed folder?

New download available. Removed the need for files from an XP cd. Constructive criticism appreciated.

Extract the IESETUP.DL_ from the xpsp1 cd and place it in the "FIX" folder and rerun the cmd file. Or you can just extract the IESETUP.DL_ and place it in the slipstreamed source (sourcess folder). Also, no need to add additional files into the SVCPACK folder, all you need is the HFINFS folder setup per the instructions. The cmd file takes care of the rest.

Commandline Hfnetchk utility

http://www.msfn.org/board/index.php?showtopic=32125

I read that link that discusses the RDM and QFE and it left me extremely puzzled. Is there someone that can put that in layman's terms?

Looks like batch file is getting some constructive criticism. That's a good sign. A few things... @Bilou - The inf file/regedit you did on post 2 of this thread is a great start, however, some hotfixes need a bit more. I have the inf file of the "important" stuff. As far as that bandaid fix, well, I guess that's why I called it a bandaid. It seems that with every new IE hotfix coming out, there is a new folder generated. Strange. However, if you are put a bunch of pause statements in the cmd file, I noted the following with shlwapi.dll revisions: I386E ver 1605 rtmgdr ver 1612 rtmgfe ver 1612 xpclnt_qfe_binarydrop - incorrect type of file xpsp2_binarydrop ver 1584 From dissecting the XP hotfixes, it seems that the contents of the xxxGDR are the ones that are the latest revisions. So, perhaps with w2k, they will also need the contents of the xxxGDR folder? @Honnes - The %%J variable is used to loop through all the various folders in the extracted hotfixes. I was meaning to take that out portion out in the next revision as it seems that it's not needed. On the flip side, I would hate to see that part of the code leave since it was a fancy nested loop.

From my experience, it seems to make windowsupdate happy, all you really need is some key registry entries. In other words, it doesn't really check the presence of the updated dll/exe/etc. Well, that's the case with a majority of the hotfixes anyway. The registry entries are nestled in the inf files for the Type 1 hotfixes. Type 2 and the MDAC hotfix infs need a little digging to get the proper registry entry. Personally, I prefer using the HFNETCHK program to detect proper installation of the hotfixes because it looks at the dll/exe/etc files for the latest acceptable revisions as opposed to windowsupdate looking for an "is installed" in the registry. Windowsupdate seems to be more of a registry checker than anything else. I don't think that your svcpack inf file is running your inf files that you extracted from your hotfixes. Without editting the inf files, you will probably get error windows during the last phase of the windows installation process. With proper editting of the inf file you won't get copy errors AND you'll make windowsupdate happy. One thing I found out is that if an INF file isn't correct, it won't make any registry changes at all. Making the proper INF file can be a tedious process though, especially with the Type 2 hotfixes. I have accomplished making all the hotfix INF files once before. If you have integrated your hotfixes manually without integrating IE6, you will run into difficulties with the shlwapi.dll and some other dlls. Installing IE6 via svcpack or later will add a variety of files, and will replace some of your integrated updated dlls with old ones that are in the IE6 installer. After IE6 is installed, then you have to install the IE6 rollup updates to correct and update the dlls. I prefer to just use my cmd file to integrate IE6 and all the w2k post sp4 updates. Far easier and works like a champ for me. BTW, What hotfixes are you having trouble with? Good luck.

Download the zip file in the first post and unzip it. You'll find all the the instructions you need.

You are partially correct.... if you only want to slipstream IE6 into your W2K. You need a few files from an XPSP1 cd and some files from www.vorck.com (aka FDV's site). All the instructions are in the instructions.txt file.

DonJuan & Hirudin: About the windows installation showing uninstalled updates, please read the 8th line of the instructions. The only thing windowsupdate needs to be happy is a few worthless registry entries (which I don't plan on incorporating at this time). I have suggested a tool to be used to check for windows updates (which checks the actual version numbers of files). Hirudin, If you follow the instructions, the inf file is automatically run during installation. Bilou Gates: Thanks for the tips on the msxml registration codes.

Updated download. Refer to first post. Thanks for the suggestions/critiques.

Yep, that's how you install inf files via a commandline. In fact, you can also do a right click on them and click install. And yes, you can include the registry hives for the same updates too. Yesterday I was working on another iteration of that cmd file. I wrote up a set of instructions on what's needed so it should help a bit, which will be included in that zip file. The nice part about this version is that you can run all the infs without typing in any commandlines. It even works for xp too!!!! I just have to check a few more things out before I post it.

It sounds like the answers I gave before you took it like I was being sarcastic, which I wasn't. I certainly hope that encouraging others to read isn't a bad thing. Whatevs. Part one. OK Part two. An icon isn't the only way to tell a type 1 and type 2 fix apart. However, by viewing the icon, it is easily noticable and the best way. If you go to the sticky for critical hotixes and downloaded them all, you will notice that there are two types of icons. A type 1 has a plain old box and the type 2 has a yellow box in front of another. The icons you show have the correct descriptions, exactly as I said in my first reply to you. For example, KB870669 is a type 2 hotfix; KB329115 is a type 1. Part three. I'm not sure of your question here, but if you editted it and it works, don't complain. On the same unattended.msfn.org site is a ton of information about setting up the svcpack.inf file. Part four. MSXML: a compressed binary usually has an underscore at the end. Sort of like this sfc.dl_.

If you are a bit unclear on hotfix types, I encourage you to visit unattended.msfn.org However, the pictures you show in your post show the correct type 1 and type 2 fix icons. I do not plan on integrating WMP9 or any other WMP. On the same lines, I don't plan on integrating .net either. Download the latest zip file I posted last nite. With that, you can put your SFX packages in a folder called EXE and you can edit what the proper switch is. As for what's needed for msxml, I have it spelled out already on what's needed in the CMD file. You will need to register them after you install the slipstreamed source. Hope this helps