tommyp

It's not really my call what you want to slipstream. I can only suggest what files to put where to get a successful installation. In fact, I have other non-essential hotfixes that aren't listed in my hotfix list but are in my HF folder to take care of USB issues and driver specific issues. Anyway, if you want msxml, then just put those files where they need to go. If you don't want it, then don't put them there. If you intentionally omit a file, things may not work (as in the case with msxml). I did a little comparison on this msxml updates. Windows 2k SP4 ships with msxml.dll and msxmlr.dll versions 8.0.6730.0. This is updated via KB955069. This is on the upper part of the list. Windows 2k SP4 does not ship with msxml3. However, if one installs IE6 OR the post SP4 rollup, you introduce MSXML3.dll and MSXML3R.dll to the system. The final version is in the post sp4 rollup. Windows 2k does not ship with msxml2.dll. However, if one optionally chooses to slipstream other msxml types, they can, and this is in the optional section of the list. I extracted the files to see what was included and you will need both files in the HF directory because the XML-SP does not include all the MSXML files needed. msxml3.msi - msxml2.dll msxml2a.dll and msxml2r.dll versions 8.30.9530.0 msxml2sp6-kb887606 - msxml2.dll version 8.30.9531.0 but does not include the required 2a and 2r files.

Tomcat76 wrote hfslip 2.0. I wrote hfslip 1.x but tomcat maintained hfslip 1.x for a while. Since life got in the way, tomcat had to put hfslip aside. In tomcat's absence, I think it's safe to say that it appears that hfslip 2.0 is stalled and/or abandoned and unsupported. May I suggest that you use hfslip 1.x instead? If so, then we can help you.

Thanks for the clarification on that outdated hotifx. Unfortunately I will not include the french pstore issue with my list. I am trying to maintain a critical update list only, just as the_guy did.

HFSLIP 2.0 was written entirely by tomcat76, who hasn't been here in quote some time. I can't say much about hfslip 2.0 other than I never saw a "final". If you are getting messages like that, it *could* be a bad cd burn, not enough space on your hard drive (hfslip requires a decent amount of hard drive space when run) or maybe even a bad sector on a hard drive. It would probably be the best bet to test out the iso image that hfslip generates on a virtual machine to isolate where the problem arises.

I'm not sure if this helps or not, but I think there may be some dependencies broken. With my hfcleanup'd ie6 core/dx9 2k source (I'm not using FDV's fileset), I'm able to register all of those files listed in the previous post except strmdll.dll and msdxmlc.dll. The others all register fine. I had many issues developing the hfcleanup fileset and being able to play media files, it was like walking a tightrope. There seems to be some sort of hidden link between files like this, or in other words, a file can't register because there's another certain file(s) missing. Other than putting the removed files back into the system32 folder one by one and retesting the register process, I'm not too sure how to handle this.

Have you looked here?

New beta released to address the pesty activex kill bit that gets overridden by ie.inf.

Thanks for testing. Looks like we'll have a new beta. I'll post it up in the beta thread later on today.

Feel like testing a test hfslip script out? Hopefully it fixes that issue. Please report back your results. Thanks in advance for your help. edit - posted the beta on the beta thread.

The ramdisk is applied pretty early IIRC. I believe that the machine would have to be at least at the desktop for the ramdisk to actually function, but I could be wrong. Extracting your .net installers and such would be an experiment you would have to do and troubleshoot (if needed).

Glad it worked out for you. And thanks to Martin for doing some additional test cases.

It's not hard. Go here: http://unattended.msfn.org/unattended.xp/view/web/16/ download the exe file and put it in the hfguirunonce. Click start/run type in CMD and navigate to the hfguirunonce folder. Since you were nice enough to post your hfslip log , type this into the dos box: d: cd dualcorebackup cd cdrive cd hfslip cd hfguirunonce modifype filename.exe -c where filename.exe is the exe file. I'd suggest to do it one or two files (make a backup first) and put the rest of the installers into a different folder, and run hfslip afterward. If it works for the one or two "test" files, then chances are that you'll need to do all of them to make hfguirunonce to work. BTW, I have run two test cases on two different OSs on a VM and do not get the copy error prob with hfguirunonce installers.

Interesting. Feel like testing something out? Try running modifype on the files in the hfguirunonce folder, re-run hfslip and report back. Maybe hfslip needs to invoke the modifype on the files in that folder for that function to work properly.

No. Sorry about that.

The 'dxdllreg.exe' call is probably redundant, but if one were to install dx9c the old fashioned way (i.e. from the MSFT distributal), the end result is a reboot now box, but if you look in the runonceex section of the registry, you'll see same 'dxdllreg.exe' call. HFSLIP just mimics the whole thing. IIRC, without the dxdllreg command, you see dx version 7 instead of 9c when you type start/run/dxdiag.exe. I could be wrong but I believe dx is tightly knit with playing media files. If too many files are removed you won't be able to play media files. I had a tricky time with that when developing hfcleanup.

Thanks Martin. Your contributions are always welcomed. I'm glad that you're double checking this stuff, there are too many variations to test out. I think the active directory one you mention is way old. 926122 was superceded by 943484 which was superceded by 949014 which was superceded by 957280 (Oct 2008). I'm not sure why WU says it's needed. You do bring up a valid one with the 938127. I'll add i to the 2K/IE5 variant.

I'll move the MSXML 3 hotfixes out of the optional and in the "upper" list. The severity rating that is presented will still be what MSFT says.

Do you have the same problem when not including XPSP2EXT?

The directx 9 portion of the script brings back many bad memories and countless test runs on a vm. The issue was that the W2K setup is pretty complex with multiple runonce's that get parsed during install. It was tricky getting custom INFs to run at the right point in time, and as early as possible so it would not interfere with the remainder of the setup. If an INF was called too late, then all the custom hfslip INFs would get overwritten. Thus the reason for the entry in the add/remove programs. If something wasn't run at the right point in time, that entry would not be there (and it put a nice little tommyp touch on the OS). With XP, it's a piece of cake. There's only one runonce called. Man, that must have taken me about 3 weeks to figure out what was happening thanks to undocumented setup routines that msft doesn't provide. Putting that into a script to autogenerate the INFs was the next tricky step. I'm surprised you were able to read through that code. May I suggest that the troublesome INF get cleaned up in the next fileset. If any entry is incorrect in an INF file, it won't run. Trust me, I found that out the hard way when coding a while ago. Sorry for rambling. Happy new year!

Thanks Martin H. It's a yes and no situation. The entire msxml "block" is optional. If you slipstream msxml, then it's critical. If you don't slipstream msxml then you don't need it. So you're right, it's optional. However, I take the ratings from MSFT's security bulletin (MSxx-yyy).

Please keep this thread on topic for windows update list corrections. It may be worthwhile to edit your hfslip.ini file to delete the NoKillBits line. Also, it maybe worthwhile for you to compare your hotfix list from what is presented on the xp hotfix page. Please start a new thread if you run into probs.

willydejoe1234 - HFSLIP already addresses this activex issue. Perhaps you have another file that is reversing this fix?

Are you using the latest beta? The beta should add in that "fix." What's the reg file you need to use?

Can you zip up your hfslip.log so we can see what you're doing? Thanks!

Another beta to fix the WMP hotfixes. Let's make this the new final soon guys. Please report back and please use the stickied windows update hotfix lists.