tommyp

Maybe there is a requirement that IE8 needs WMP11? I can't say. Obviously, you can just include WMP11 and not get the errors, or you can help diagnose things. Try this. Remove the following files from the HF folder. Let's try to isolate which hotfixes are giving a prob. a - Q282784_WXP_SP1_x86_ENU.exe b - WindowsMedia9-KB969878-x86-ITA.exe c - WindowsXP-WindowsMedia-KB952069-v2-x86-ITA.exe d - WindowsXP-WindowsMedia-KB954155-x86-ITA.exe e - WindowsXP-WindowsMedia-KB968816-x86-ITA.exe f - WindowsXP-WindowsMedia-KB973540-x86-ITA.exe g - wmfdist95.exe a - You probably saw extraction errors with this one. The filename of this one seems foreign to me. b thru f are WMP related hotfixes. g - codecs. They may not be required for WMP9, I haven't used that package in quite some time. Here is an interesting link related to a similar issue. Maybe foobar is fubar? http://www.techsupportforum.com/microsoft-support/internet-explorer-forum/359789-ie8-wont-use-wmp.html If you run into probs, please include your hfslip.log so we can see what you are doing.

Can someone point my feeble mind to a concise method of doing the sysoc defrag? There's solutions in the defrag thread that I'm sure that some work and some don't. I'm not sure which is the correct method that works 100% of the time. Actually I kind of prefer to use all CMDs instead of additional hftools.

Dumb q, but I must ask. Why use the outdated wmp9 and there are other and far better media players out there? I never had luck with wmp9 or wmp11 recoginizing mp3 id tags properly when every other media player saw them correctly. On a sidenote, if you have wmp9 installed, you can't view videos encoded with wmv11 codecs.

Please post up a clean and bug free way to do things and I'll try to integrate it. There's been a very big change in my life during the past week or so which seriously limits my computer time. So pls don't expect a quick turnaround.

MSFT does release some hotfixes that are just registry updates. HOwever, there are some cases where MSFT releases a different type of hotfix that may not be supported by hfslip extraction. Those would get processed at t-13 via the hfsvcpack folders. More than most times, hfslip supports the critical updates, because, well they are critical. Optional hotfixes and suggested hotfixes/packages are sometimes packed differently. Usually optional hotfixes and suggested hotfixes are just extra stuff that msft wants you to have for some reason. The OS will still perform fine without them. There's two or three general types of users of hfslip. There's some that can't live life normally if they see anything at all reported by WU. At one point in time, there was a fatal flaw with WU where it reported a HF was not installed unless the OLD binary was present. There's other users that will just install the critical ones. Then there's the last batch that uses reduced source (i.e. fdvfiles and/or hfcleanup). If in doubt with the zero files copied, I encourage you to verify that the hotfix isn't replaced by something else. If you see zero files extracted, I'd say that either you have either (a) a bad downloaded exe file, (B) something that isn't supported by hfslip, or © some hacked file that isn't packed to normal msft standards.

You really don't need the dx9 cabs unless you have an application that requires it. You'd know if your application needs the extra dx9's because it will prompt you to install it.

Is the logon/password issue still there if you don't slip IE8?

The "fragged" sysoc.inf works fine and has been working fine since the inception of hfslip. Honestly, I don't see the point of defragging it. I suppose it could be good for users, and if it's good, they can incorporate their own hftools\post cmd file.

Microsoft never makes mistakes.

To echo keirkei's post, if you aren't sure how to use hfanswer.ini, just don't use it. Hfanswer is more of an advanced thing and assumes that your fileset is functioning properly.

It's either one or the other when using FDV's fileset. Either you use his set -or- you use nlite. Not both.

Try re-downloading the WU cabs, or just not use them. Also, make sure your hard drive is OK (i.e. not full and no errors). Your "other" post about unexpected end of archive seems to point that there could be a hard drive error.

Both will yield the same results. I prefer to get my binaries from msft and not from someone else. I'm not knocking mimo, but it's just my preference. It ain't the end of the world, it's a mistake that msft made. They've made plenty of them. You'd think a big corporation like msft will have checks and balances for this stuff.

Maybe try doing the critical stuff first before doing the optional stuff. Try to isolate it the prob. Testing in a vm would help ya out greatly. I routinely "isosize". To isosize is to run the script with a given batch of hotfixes and/or run differnet scripts and see if all works. Isosizing is a great way to kill the day. lol. I find it weird that the txtmode does not give probs, but later on during setup it says it can't find files. A hfslip'd install generally copies all files it needs except for the ones at svcpack. From my limited experience, the constant rebooting is due to mui files not getting copied. The mui stuff is from ie8.

Sounds like it's ie8 related and/or maybe you're trying to slip something not meant for xphome. You'll need to read the kb articles to verify. I don't have xphome to troubleshoot. I'm afraid you're on your own unless someone else chimes in.

What's with the "0" for the install path? Why not leave it as default? Are you installing this with a boot cd?

I had a dumb idea that seems to work. The way HFSLIP processes the IE8 slipstreaming is as follows. It extracts the installer and all the IE8 hotfixes. It places all those into a subfolder. Next, hfslip parses the rest of the hotfixes and puts them into another folder (i386e). After all the hotfixes are processed, hfslip takes the IE8 stuff and overwrites everything in the i386e folder. So, if the OS is looking for a component of the old IE6, then we'll force feed it. From my limited research, it seems that msft is trying to segregate IE from the OS. The file that mimo found seems to be a key one. To get the organize favorites to work, add the MS10-002 IE6/XPSP3 hotfix to the HF folder. I have run this in combination of slipstreaming IE8. Things seem to work. Can anyone else confirm? [Mimo - you're the man. Thanks for your help!]

Thanks for the investigation mimo. I was mentally preparing myself to redo the ie8 slipstream in its entirety. But you saved the day by IDing the error. Now, it seems that we have a msft messup on our hands. We've had plenty of msft messups before. I have to think of a way to codify things.

Can anyone help with this issue? Does anyone care?

Slipstream it FTW! If you gotta register it, then HFEXPERT\CODECS. If you don't need to register it, HFEXPERT\WIN\SYSTEM32.

aj - if you install IE8 on top of what was slipstreamed, does that error still happen?

The filenames are based off of nlite. The fileset assumes you are familar with reducing (nliting) your source. Read the readme file file if in doubt of what files are removed.

This isn't the forum to ask that sort of question. Please ask in the correct forum.

Problem - What happens when you go to start/run and type in dxdiag.exe?

I certainly hope you aren't using a warez xp disk. To get your hotfixes, please see the stickied thread on the hfslip forum. Mimo has written a nice utility that tells you what hotfixes you need. As far as what else is needed, you'll need to visit hfslip.org for details.