tommyp

Of coarse you could always use the file listed on this link to slipstream all your updates in one shot. The subject line says w2k, but the program works with xp too. Why mess around with svcpack when you don't need to? BTW, there's some registry info that is needed when you do slipstream the installer. The script file below takes care of all of that stuff. http://www.msfn.org/board/index.php?showtopic=32125

New HFSLIP posted on 1st post. New items: Sleek/Streamlined/Slipstreamed DX9C Additional Language Support Localized IE6 integration (in other words it supports non-English builds) WindowsUpdateAgent20-x86.exe integration Added GNU License PLEASE read the directions if heavily reducing the slipstreamed source on W2K.

The new version will get posted when FDV gets back to me... within a day. DX9C integration is great and some strange issues were resolved with non-English updates. It should be good for multi-lingual slipstreaming with W2K. The program is also a hidden gem because it works for XP too. BTW, my nlited sourcess folder for w2k+ie6+dx9 slipstreamed is about 110 meg. It's heavily reduced, but fully functional. Please post comments on this link: http://www.msfn.org/board/index.php?showtopic=32125

@blinkdt - Thanks for the "peerless" comment. Nice to hear it worked for you. Which hotfixes gave you troubles? Maybe I can remedy that issue to make it work better for you. Can you run hfnetchk with the -VV switch and PM me with the details on what's missing? BTW, I plan on releasing an updated script that slipstreams dx9c in addition to the other updates. I'm just waiting on some feedback from a non-English user on some issues that have and I want to resolve that before posting the new script. It would be nice for all languages to use this script.... Oh yea, the new version kicks a**

Are you using a W2K SP4 slipstreamed source in the source folder? Did you modify any of the files in the source folder? What happens if you re-run the script without anything in the SVPK_SW and SVPL_NO_SWE folders?

Did you edit the CMD file for french? Any way you can translate the words to english?

@bololo77 - Thanks for the zip. I believe I found the issue which appears to be a non-English type of thing. If you wouldn't mind doing a quick test to see if my line of thinking is correct, PM me for details.

@bololo77. Thanks for noting the known issues with the script. The hotfixes are nuisance ones that are listed in the FAQs in the instruction txt file. Please re-read it. Oh yea, thanks for catching the spelling error. If someone with that language CD uses the script, I'll update that portion so his language is automagically selected. If you feel ambitious, can you please re-run hflslip, install the source, and make registry snapshots before and after each hotfix and send them to me. Perhaps I missed a section of the INF. Or maybe it's just a local thing. @dziubek. Please don't post how to use the cmd file. The instructions included in the HFSLIP file CLEARLY state to run the slipstream on a virgin source. I'm not sure why you suddenly are telling others the proper way on how to use it. Please don't spoil a good thing. Thanks in advance for your cooperation. @Pene. FDV may be a little late on his list of slipstream hotfixes for W2K. A1) FWIW you can probably skip that hotfix altogether as the all windowsupdate needs is a simple regedit. If I didn't include that HF on the list, people would ask "why isn't that hotfix on the list". Remember, if in doubt, add it to the HF folder and the script takes care of the hard work. A2) On the same lines, the hotfix you mention is the rootsupdate (a recommended one and NOT critical). The script can integrate it AS-IS in the HF folder. However, the rootsupdate is an ever-changing hotfix. In other words, each year, a new rootsupdate comes out. The script is now set up for the current rootsupdate. In the future if there is an issue with rootsupdate not installing, then place it into the SVPK_SW folder and you'll be OK. I was trying to think ahead with writing the script.

@dziubek. Thanks for testing. Hopefully I can answer your Q's. Hotfixes reported not installed: Can you please run the Microsoft Baseline Security Analyzer and report back on missing hotfixes (not the unconfirmed ones)? 1) I intentially made sure you don't see those hotfixes in the add/remove programs. All the hotfix binaries are slipstreamed, so you can't uninstall them anyway. I guess I could put something there if people really wanted something there. 2) Those files were copied over because I was too lazy to filter them out during the last phase of the hfslip program. It will do no harm if left in the sourcess folder. The next version of hfslip corrects that issue. 3) Thanks for noticing the blank file. Did you compare all the files manually to find that? The next version of hfslip will remove that file. 4) I'll try integrating the WindowsUpdateAgent in the next release. 5) I'm not sure what you're getting at with the CAT files. Is the OS prompting you for the original installation cd for files or something? The new files are registered once you install them via svcpack (or some other inf file). That shouldn't really be an issue... unless I am unaware of something hidden.

...a brief message. First post updated to show the new release. I was a bit fancy and added in bold text this time. One of these days I'll figure out how to use this keyboard better. Kudos to FDV for hosting.

Very odd. I have both installed here and I have no updates. Are you sure you are installing the latest and greatest .net? FYI, I use RyanVMs prepacked self extracting installation. What language are you using? The issue may be fixed when I release the next revision of the hfslip.zip file.

Electrician, Please read the instructions that are part of the zip file posted in the leading post of this thread. In there, is a set of detailed instructions for the script to work correctly. If not followed, chances are the script won't work. I'll assume you're running an english version of w2k. If so, you should get no errors. BTW, The driversignpolicy thing in the winnt.sif file was so that there would not be any nagging errors during installation. This was fixed in the latest version using a force fed registry entry during installation, thus no need for a winnt.sif file.

Electrician: The 7/11 script was 3 releases ago where some updates didn't quite work so well. You may want to get the newest version as listed on the first post, and follow the instructions, especially step #3.

Good point Lupo. D3dim.dll is part of the english w2ksp4 too. I'll have to add stuff to the instructions for having enough harddrive space. I guess you kind of need a bunch of space for this. Thanks! Also, thanks for our offline tips too. I'm thinking of some solutions. Where were you a few months ago?

I guess the cmd script only works with english versions. Like I mentioned before, it works fine with eng versions. I'll have to remove the language options when I release the next version of the script. If you prefer to do a manual slipstream, please visit www.vorck.com. He has some great info there, in fact, the script is pretty much based off of that. Please be aware that the W2K rollup only updates IE5. Bastian_W - If you're missing an mshtml.dll during the initial installation of your source, I would highly recommend installing a non-slipstreamed source. MSHTML is one of the files on a regular cd, so I can't see why yours is missing.

What were the filenames? Did you follow step #3 of the instructions? Did you add an MSXML3 installer to the HF folder?

AngelBlue - What files/infs are reported as being missing? Are you using a virgin source? Electrician - Are you still using a virgin W2K sp4 source? If you aren't please use a virgin one. I know last time you were using a modded source when you had problems. FDV and I both do not get errors, so you are obviously doing something fundamentally incorrect. Please re-read the new instructions. Edit AngelBlue. I just ran my install with just slipstreaming IE6 only. Works fine with me. I can only assume that you didn't read the instuctions. REREAD THEM PLEASE, especially step #3. One additional item, if you aren't slipstreaming the post SP4 rollup, you NEED to download MSXML3. I'll add that to the instuctions.

Electrician, are you sure that HFNETCHK is reporting older files? Or files that have the incorrect checksum? Incorrect checksums is an issue, but it's most likely an issue of HFNETCHK itself. Have you tried the microsoft baseline analyzer? Have you checked the actual versions of the files? Where do you place your setup/working folders? It should not have spaces or weird punctuation marks. Keep it simple and don't get too cute with file/folder names. For example: d:\hfslip\HFSLIP_50715.CMD

I mailed a new hfslip file to FDV for posting. Please be patient. The extracted file name is called HFSLIP_50715. I'm sure he'll post once it's hosted. The new version gives language support, better directions, and fixes the stupid rootsupdate. I only get two updates after installation (dotnet and wmp9), both obviously aren't critical updates. TP

I was testing with the baseline security analyzer. GDI is no concern if you did a windows (sourcess folder) only. If you install other microsoft software, it's up to you (I can't test for something that you install afterwards). But, the baseline security analyzer said GDI tool wasn't installed, so I installed it, and after I re-ran the analyzer, it still said it wasn't installed. Go figure. As far as the malicious software goes, I wouldn't really worry about having malicious software on a clean installation. Thanks for the shift-F10 tip. I could have used that when troubleshooting the post rollup..... TP

Pene - Yes, it 's the single line you redid yesterday. It works for XP and 2k. Don't know how you found it, but it's pretty cool. I'm sure what value that reg key takes after windows is installed, but all seems fine, just as you said. Lupo - I'm not exactly sure about the unicode. PM me offline so we can discuss. Also, has your winnt.sif file worked before? Are you sure it's named winnt.sif and not winnt.sif.txt? Did you place the file into the FIX folder? My winnt.sif file works exactly the way I set it up. dziubek - What you said was what I was expecting. Reading Lupo's post had me a bit dumbfounded for a minute. Also, some additional items... WMP9 - It IS possible to slipstream it, but I do not plan on integrating it with my script. Once you discover alternate media players, you'll stay away from the that POS memory hog of a program. I can however include the codecs for it GDI tool - MSBLA says it's not installed on a clean installation. So I ran the GDI tool on a fresh installation and it found no errors. After re-rerunning MSBLA, it still says it's not installed. Apparantly MSBLA will never be happy. Long story short, there is other software that microsoft came out with that is prone to this issue, but a clean installation of windows alone is fine. It will be up to the user to see if whatever software they install after they install windows is prone to this issue.

noisehole - thanks for the list (funny username too! hahaaha) Pene - Post 201 - (the renamed 818043 hotfix), you do NOT need it to be patched. I read that there may have been issues with that update. Google for that hotfix number and you'll see what I mean. post 203 - I meant that the rootsupdate will be fixed at the next release of my cmd script. I'm looking into that GDI thing now. I'm doing final testing now, shouldn't be too long for a release. So far W2k and XP look fine.

Lupo, I'm working on a multi-language script now. If you don't mind, please wait for a little bit (less than a day or two). The language issue should not be prob. Electrician - Thanks for the inputs, the portions you mentioned were indeed getting run, but I fixed it in the script. Pene - Your method works great. I just verified with XP and 2K. Both work like a charm. Thanks for your great input! Other stuff to be included is the stupid rootsupdate hotfix, and more cleanups to get rid of some temp files (no use cluttering up the harddrive right?) Can someone help me with the language issue? What is the full name of the rollup for languages other than english. I need the FULL filename. The english version is named "Windows2000-KB891861-x86-ENU.EXE". What are the others?

Pene, that's the most elegant solution. Thanks! Would you mind if I crafted it so it's part of the slipstreaming cmd file? In other words, automate the editing of that file?

Pene: The purpose of the lines in the winnt.sif file is needed so you don't get a few nags during installation (such as the one you mentioned in your post). I think that having the winnt.sif file is a very small price to pay to use the slipstreaming file. Perhaps you can go to your original win2kpro cd and look for a program called deploy. You can use that program to set up a basic winnt.sif file (it saves it with a different name though). Oh yea, I have a feeling that Bilou isn't using the latest. I incorporated those changes for the windowsupdate late on Tuesday afternoon.