MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically.
Everything posted by piecko
"Windows XP SP3 does not include Windows Internet Explorer 7, although Windows XP SP3 does include updates to both Internet Explorer 6 and Internet Explorer 7, and it will update whichever version is installed on the computer." ..from the "Overview of Windows XP Service Pack 3" available here: http://www.microsoft.com/downloads/details...;displaylang=en It is a good read and contains the answers to pretty much everything one requires. I use OnePiece's "OnePiece_IE7AddOn_2.1.1_ENU" with no errors. Hi RickSteele, like I rode, I slipstreamed SP3, IE7 and WMP11 into my XP-SP2. And, yes SP3 contains the update, but when I slipstream the IE7 into my XP-CD with SP3, it does not apply this update to my IE7. I tried to evade the OS-Check of the KB947864 to get installed into my not updated IE7 under XP-SP3, but then the integrity-check fails. I think I have to wait, until the next cumulative IE7 update comes up ;-) I can just recommend everybody to include the KB947864 into your nlite-XP-SP3-CD, if you also include IE7, to have a workaround for this problem. I cannot use the OnePiece thing, because I need my IE7 and the updates in german. Thanks for your help
Hi Guys, I've got also the problem with the ie7 hotfix kb947864. I slipstreamed XP-SP3 with IE7 and WMP11. It works fine, but I always get notified about the update kb947864 and its installation fails. When I downloaded manually and ran setup, I got the message that the patch isn't compatible with my system. I think the problem is, that this update is already included in sp3, so patch is not made for XP-SP3 and fails to install. The IE7 I seems to be not patched with sp3, because it is slipstreamed, but I cannot install the patch because of the OS-Version Check of the Update. Including the patch to the nlite-cd could solve the problem, but I don't have the facilities to test this idea.