tommyp

I'm unsure if piko solved his problem or if he gave up. You have some non-essentials in HF. KB961742 for starters. There's something that is extracting a file called uiautomationcore.dll and wdfcoinstaller01007.dll and some others that don't follow the 8.3 naming standard. The framedyn prob creeps up once in a while (search the whole forum). It's called out when wbemoc.inf is parsed. I'd recommend to re-re-re-review your HF structure and include only the critical hotfixes for starters. Then slowly add in the optional stuff. 9999 times out of 10000 you don't need the optional hotfixes unless you want to compromise your system by making WU happy. You may want to not use hfanswer (not sure if you're using it or not).

MG2D - If your winnt.sif file has IIS or whatever optional stuff installed, then WU will prompt for an update. If it's not installed, then WU won't ask for it. However, if the iso is all up to snuff and you installed some other optional windows component later on, the latest binary will be ready to go.

Clean install = install using the hfslip created iso. Once the iso is installed, click start/run/wmp so that it "runs". Typically when wmp is run the first time, a mess of registry stuff is added. Maybe WU is looking for that stuff.

I didn't go through all the hotfixes, only the 923869. Can you check the version of wmvcore.dll? It should be in windows\system32. The version should be 9.x.x.x. If it's version 9.x.x.x, do a clean install of the iso, run WMP9, then visit WU. Maybe something w/wmp9 needs to initialize to keep WU happy? I'm just throwing darts to figure this one out. It is possible to extract the wmp9 installer, but hfslip won't process it if it's extracted. I'm glad you said "what's one more file". There's some folks out there that lose sleep with unused binaries in the sourcess folder. [yes this is true.] lol.

M2GD, I've found that WMP is a bit difficult on any OS and slipstreaming various varieties always could pose a prob, especially when it comes time for WM related hotfixes. First off, can you go through your HF folder and tell me if MPSetup.exe exists? I know it's a dumb question, but the presence of that file is supposed to trigger something. As far as the last hotfix you mention, MSFT is sloppy. Your resultant iso will not be corrupted if you include server hotfixes on a pro source. You may have a few extra files on your cd. No biggie.

Most of the answers are in the Microsoft Security Bulletin page, not the KB article. You should check them out, they often have good info. 980858 is a windows media service which is part of 2000 server, not part of 2000 pro. More than likely I missed a few server updates because, well, I never had 2000 server. 977816 is a codec thing, unrelated to wmp. The mpeg codec isn't part of the original 2000. The mpg codec is part of dx9. I'd include this hotfix if you are slipping dx9. It may work without dx9, but I'm not about to do testing on a 2000 machine without dx9. 981832. Never knew SMTP was part of 2k pro. The Bulletin says it's needed for 2k pro. Weird. DX9 - I'm not going to download the latest package to see if some files are there, but you need bdant.cab & dxnt.cab to slipstream dx9. Hopefully they are part of the latest distro.

Muppet - You can always try to do what I do. Create a HF\WMP11 subfolder, and extract only the wmfdist11.exe file there. This way, you can play WM11 encoded files on any player you like. Just make sure you include WMP11 hotfixes. It probably breaks WMP totally, but that doesn't bug me because I rip WMP out using hfcleanup . If you use WMP, then things can be funny. I still never get the point of WMP though. It never properly recognizes id tags. Once you use WMP to change and correct the ID tag, and then and then re-do the library, the new ID tag never sticks.

This prob should have been resolved quite some time ago. Please free up some disk space and re-run hfslip and while running hfslip, go outside and enjoy the spring weather for 15 minutes or so. Test out the resulting iso and confirm if you get the same error.

I won't update the x64 list. I don't have an x64 pc, xp x64 disk and don't plan on getting either. Development ended on this project.

Looking at the code, you'd need to use HFFIRSTLOGON_SW1 for an msi installer. Are you sure that you need UPHClean-Setup.msi for your machine? If you aren't experiencing slow shutdowns, then you don't need it. No use installing something if you don't need it.

All KB articles say what software is affected. In the case of the XPS printer one, the article said something along the lines of .net 3. Remember, .net3 is a separate program, just like MS Office. It's not part of the OS install disk. HFSLIP pretty much concentrates on OS specific things, not post install stuff like office, .net, other.

The intent of the wmfdist was to slipstream WM codecs. I was using that method for a number of years ago to SS codecs but sometime around 3 years back I stopped using that package. Not sure why though. Whatever the case is, it's not necessary.

Glad you got it figured out Lilla. Thanks for posting the message on the xp updates thread for mimo. Doesn't it feel good to isosize?

So with testing -e- of the main hotfixes everything works. I'd suggest that the following. If you are including MORE files in HF, you should RE-review each of the KB articles to see if you are having the described problem. Chances are extrememly slim that you are having the problem. Maybe one of the reg files is deleting something that is needed? With the sysoc thing, why not just set up your winnt.sif file to prevent the things you don't want (or include things you do want) instead of uninstalling/adding things afterward. Or perhaps it one of the hfaao's? What bphlpt describes is what FDV and I call isosizing. It's the act of creating isos and installing via vm, then changing the hfslip structure a bit and re-create an iso and install via vm. Lather rinse repeat. HFCLEANUP took my some odd 50-60 isosizes. The weather is too nice to isosize.

Can you narrow down the sysoc and ie8 issue? If it's an sysoc issue, then just don't use it. If it's an ie8 issue, I doubt I'll be able to fix the problem unless someone tells me what file is missing or if there is too many extra files. I prefer to spend my time not even thinking about hfslip.

The latest IE8 cumulative update has the same issue as before.

Don't know dude. Maybe just slipstream WMP11 and call it a day. Sorry I can't help more. This hobby don't pay the bills.

HFSLIP won't call and run the exe file if you place where you just described it. Do you run something after hfslip is run?

I'm can't say positive for mimo, but hfslip is supposed to be run on 2000, xp or 2003 (32bit). Good luck!

I know the pain it is with troubleshooting. I've been doing it for the past 5 years and cooked a few hard drives while doing so. Time is limited for me, and I can't troubleshoot. I've done very limited testing with the prob you have. I'm pretty sure that the correct part of the wm9 hotfixes are indeed placed into the sourcess folder. The QFE checker you mention isn't needed for hfslip. But if you want to have a few worthless binaries on your machine, then I suppose you can include it. Results could be bad though. I wouldn't recommend using it because it's not needed at all, besides, it's an sp1 thing. The KB954155 hotfix has only one DLL in it for wm9. You can extract it to see what I mean. If you can't extract it manually, then you got a bad download. Bad downloads happen. In fact most of the WM9 hotfixes you mention are just one or two dlls and that's it. They're codec fixes.

Feel like trying a little design of experiments? You can use a VM for this. a - Install the original install disk (non-hfslip) and then installing dotnet 3.5. This will say whether it's hfslip's fault. b - Run hfslip without the sysoc thing. c - Run hfslip without IE8.

If sourcess exists when HFSLIP is run, hfslip automatically deletes sourcess. Have you tried putting one file back at a time and test out which one causes the prob?

Well well well, can you attach your hfslip.log? Which hotfix is causing the prob? Put one back one at a time and see what happens.

Hmmm, you'd think that they would have included Shdocvw.dll with ie8 but is with the ie6. Are we all missing something?

You can't uninstall it if it's slipstreamed. You'll need to recreate your boot disk without using IE8.