tommyp

@Pene, You don't need to include those files with the "o_" prefix. The choice is yours whether or not to include those, either way, WU will report all is up to date with critical updates even if you don't do the "o_" files. BTW, I found those files while cleaning up my harddrive with worthless hotfix files. I just wanted to make a mental note to myself on which files weren't included before the incredible hulk did his 2k hotfix listing, so that was why I put that prefix there. I had a hard time locating one of those hotfixes for FDV to post, but not sure which one. Lastly, the Windows2000-KB818043-x86-ENU.EXE I have, I somehow downloaded about a year back....

@marko2511: The scripten/js56nen hotfixes will install a later and greater version of some DLLs that IE6 uses. I figured it would be best to have IE6 installed correctly from the beginning. Hope it's not a prob. However, I'll verify whether or not those files are really needed if I get some free time @pene: You have lots of Q's. I'll try to answer them. 1) The issues you raise on item 1 are quirks of using the winnt.sif file. Sorry you have to use it, but it's needed for the script to run. The window you see that is copying files is somethign that is needed to completely slipstream your system. The dos box you see after that is a script that cleans up some files that are left over after installation. 2) Refer to the links that Delprat has on his post. Bottom line, you need those two lines in the winnt.sif file for the script to work. 3) The roots update will be installed at the next round of my cmd script. BTW, it is only a recommended hotfix and NOT a critical one. I guess you need it if you do lots of B2B stuff. 4) You need to put those two files in the HF folder to get them to slipstream. You may want to re-download the last version from the first post of this thread. That ought to do the trick.

There's no drawbacks for not running Nlite, you'll just have a slipstreamed system. Nlite just slims the system down while maintaining the latest binaries/registry information. My typical installation cd is 100 meg, fully slipstreamed. For your reading pleasure refer to FDV's site. Oh and if you're worried about MSXML, verify that you see msxml files in your i386 folder. There's two for msxml3 and three? for msxml4. If you're really worried, but don't put the msxml4 installer in the HF folder. It works fine for me though.

KojotXL, Thanks for the feedback. It's ok to see those errors. With all the hotfixes and other upgrade files that MSFT produces, there is loads of junk that come with the executable. Case in point was yesterday's critical update for outlook. I forgot the exact filesize, but all you had to do is incorporate a single registry entry. I can't see the point of downloading a file larger than 1k for something like that. Anyway, the CMD file copies the important stuff over and discards the junk. The errors you see flashing by is the filtering that's happening. I could have just made the cmd window a plain black screen, but I like to see what's going on. I'm not exactly sure with the MSXML issues you state. If you installed the source and MSXML works, then no need to worry about it. I ran the script numerous times and have no issues with MSXML. With the oeexcep.cab error, thanks for pointing that out. I'll have to remove that line from the code. I guess I found out a while back that the oeexcep.cab was also packed with non-essential garbage.

That should be it. Place the winnt.sif file into the FIX folder and you're good to go.

A rehash of the instructions... a bare bones winnt.sif file that will work: [Unattended] DriverSigningPolicy=Ignore save it as winnt.sif and not winnt.sif.txt

To make KB903235 seem like it's installed, put this in the registry.... For the INF file people HKLM,"SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{03D9F3F2-B0E3-11D2-B081-006008039BF0}","Compatibility Flags",0x00010001,0x400 For the regedit people: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{03D9F3F2-B0E3-11D2-B081-006008039BF0}] "Compatibility Flags"=dword:00000400

See first post. The file slipstreams all hotfixes including the post SP4 rollup. No more Critical Updates reported via WindowsUpdate.

@Pronstar: Thanks for the constructive criticism. Will correct the patches/integration on the next iteration of the CMD file. As far as the MSXML goes, give a try with the alternate version of the MSXML. I believe all you need for MSXML4 to be installed is 3 dll files to be present in your system32 folder and you register 2 of them using regsvr32. I'm not sure really what you want to do there. @Bastian_W: There may be an issue with the hotfix itself. Read the ramblings at http://www.msfn.org/board/index.php?showtopic=49527&st=0. Personally I use hfnetchk and the microsoft baseline analyzer to see if the hotfixes are installed. Windowsupdate only checks registry values and not file versions.

@Billou: Yep, yesterday I modified the cmd file for all the updates and IE6/OE6/WAB6 integration. I mailed FDV the zip file for uploading on his site. Hopefully he'll post once it's uploaded. I haven't verified it with the famous (registry-checking) windowsupdate, but the (file checking) microsoft baseline analyzer and hfnetchk report all is OK.

@chuangfeng: re-read the instructions in the zip file. If you don't follow the instructions, you'll have a failed installation. @dziubek: I cannot test other languages, so I cannot really say. But, give it a try and report back.

@FDV: Thanks for answering that create shortcut wizard question. @XLShadow: I noticed that directx message also when running the last two versions of nlite. A workaround is to just install directx after windows has installed (like when you run your unattended program installations). Something in Nlite is doing something the dsound.dll... not sure what, but it only started the last two versions of Nlite.

I'm not sure where you going with this. If you don't want to slipstream sp4 with w2k, it seems that you don't want the latest updates. If you don't need the latest updates, then why are you visiting windowsupdate? However, I'm not sure with doing SP3 with w2k, all I can say is try it and test it with microsoft baseline analyzer.

The script works with SP4 (you have to slipstream it yourself, the script doesn't do it).

Try re-reading the instructions and follow them exactly. When I run the script and install that source, I only get one hotfix when visiting WU... I forgot the exact one exactly, but if I check all the affected files, the updated files are there as are the registry entries. Strange.... BTW, I'm not sure if the script works on other languages. It *may* work, but I can't confirm.

Try the baseline microsoft baseline analyzer. If it makes you feel better, windowsupdate pretty much checks registry entries and not files.

@ DonJuan: I re-ran the script and the installer seems to have installed correctly. In other words, if I install XP with all the fixes, and then if I install the installer hotfix, there isn't substantial changes done to the machine to warrant a change of the script. Sorry pal, but it must be a fluke of the microsoft hotfix itself. TO answer part 2 of your Q regarding the turkish version. The script was based on using a english version of the source. It *could* work with other languages, but I'm not sure. However, most of the INF files seem pretty general that don't seem to be language specific. Sorry I kind of ended the answer open-ended. I'm by no means a computer weenie. I only dabble in this stuff as a hobbie. @Cliphead: The only thing I would suggest is that you move the folder structure of the slipstreamer closer to the root of the drive and get rid of any spaces in any folder names. I have a feeling that the script has a problem with spaces in folder names. I don't plan on fixing that issue either.

Give me a few days to review it. I've been a bit swamped lately.

If you don't want for xpcreate, and you want to slipstream all the hotfixes, you can try my script here. It works for XP and 2k (even integrates IE6). Works great with Nlite too.

I posted a cmd file to integrate all hotfixes for xp and for 2k (integrates ie6 too). I have automated the file modding you suggest in your first post.... If you want, check out the file at this link. I'm sure that your files can be easily implemented in my cmd file. Oh yea, if you have all the hotfixes in the folder structure all set up, there is no need for RyanVM's update pack. And yes, it works with Nlite too. Cheers TP

The latest files are copied with xcopy and the appropriate switches. If in doubt, run the script, install the source and test it with the Microsoft Baseline Analyzer or the hfnetchk program.

I posted a thread a while back about integrating hotfixes, works for xp and 2k. It even integrates IE6 on a 2k install. Link

Snowbeach, may want to try a slipstreamer that I wrote up. It works for windows 2000 and windows xp. http://www.msfn.org/board/index.php?showtopic=32125

Kudos, to FDV for hosting that file. Hopefully more can benefit from the lack of SP5 and for those who want to slipstream IE6 or even eliminate IE all together. I'll update the first post of this thread when new versions come out.

@bololo77: Thanks for the feedback. I'll incorporate that folder generation in the next round. The hotfix you mention is the only I can seem to get to make windowsupdate happy. If you do a file comparison between a cd installation using that sourcess folder, no files are changed if you manually doubleclick that 890859 hotfix. Weird.