Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

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. 


glnz

POSReady 2009 updates ported to Windows XP SP3 ENU

Recommended Posts

2 hours ago, Bersaglio said:

support of Office XP has ended in July 2011 and I believe that there were no more updates for Office XP after that date.

Yes. The same applies to Office 2000 and Office 97, both of which I still use (I have two 97 and six 2000 licences, but I'm currently using half of them).

Share this post


Link to post
Share on other sites

1 hour ago, heinoganda said:

@Dave-H

If there was a problem with KB4039384, there would have been a corresponding comment from my side. Regarding KB4039111, a fader flavor remains due to the enclosed file xpsp2res.dll version 5.1.2600.7239, whether a more current version like the version 5.1.2600.7248 should have appeared here. This will ultimately show the upcoming updates.

:)

I wasn't aware that there was any problem with KB4039384, if anyone mentioned a possible one it wasn't me.
:dubbio:
If there is an earlier version of xpsp2res.dll in KB4039111 it doesn't seem to have overwritten the newer version when it was installed, which is good (presumably).
:)

Share this post


Link to post
Share on other sites

MS must've pulled out the putative v 5.1.2600.7330 of xpsp2res.dll at the last moment, because they've found it was seriously blorked or, in the hurry which must now be their update creation proccess (because they've already fired too many of their best people), someone just forgot to compile the new file and they've tossed in the latest one they had at hand, instead, and it happened it wasn't the actual latest extant version, but the one preceding it. Incompetence, as y'all know, usually is the true explanation. :yes:

  • Like 1
  • Upvote 2

Share this post


Link to post
Share on other sites
54 minutes ago, Dave-H said:

I wasn't aware that there was any problem with KB4039384, if anyone mentioned a possible one it wasn't me.

5 hours ago, Dave-H said:

My USP10.dll is version 1.420.2600.7334, and GDIPLUS.dll is version 5.2.6002.24180.

Because the files USP10.dll and GDIPLUS.dll have been updated by KB4039384!

13 minutes ago, dencorso said:

Incompetence, as y'all know, usually is the true explanation. :yes:

Hopefully not! :D

 

Share this post


Link to post
Share on other sites

I still use Office XP (wide compatibility, and the last for Windows  98 and NT 4.0), but I am surprised to see Office 2003 listed as a supported system by Microsoft, since they dropped support for it on the same day as XP.

Share this post


Link to post
Share on other sites

Has anyone tried installing the .NET Framework updates that were released in 2014 to 2017 on a Windows XP SP3 system that has not had the POSReady reg tweak applied to it?

 

Share this post


Link to post
Share on other sites

@sdfox7

Some updates that are still published for Office 2003 Viewer can also be used for Office 2003. Currently USP10 and GDIPLUS.
Ultimately therefore still lacks many updates!
 

@pcalvert

The .NET Frameworks updates after April 2014 require the POSReady entry for download via AU / WU / MU, for the installation this is not needed!
 

:)

Edited by heinoganda

Share this post


Link to post
Share on other sites
13 hours ago, heinoganda said:

@pcalvert

The .NET Frameworks updates after April 2014 require the POSReady entry for download via AU / WU / MU, for the installation this is not needed!

Thank-you! That information may be very useful.

 

Share this post


Link to post
Share on other sites
On 15.09.2017 at 9:12 AM, heinoganda said:

The .NET Frameworks updates after April 2014 require the POSReady entry for download via AU / WU / MU, for the installation this is not needed!

Except for .NET 1.1, right?

Share this post


Link to post
Share on other sites
4 hours ago, Mcinwwl said:

Except for .NET 1.1, right?

Correctly! For .NET Framework 1.1, you could still use those for Server 2003, if the updates were manually adapted to the installation.

:)

Share this post


Link to post
Share on other sites

I use this tool to search for updates:

 

It's not perfect, though. When using it to search the Microsoft Update Catalog, it returns a long list of updates, but does not filter out the ones which are already installed. And when I used it to search for Windows XP updates, I didn't see any .NET Framework updates in the list, so the list is obviously not exhaustive. Even so, it's still very useful.

 

 

 

Share this post


Link to post
Share on other sites

We are getting almost same vulnerability as of Server2008/Vista since XP sp3 is XP sp2 with lots of vista codes .... It seems it will not be to tough to make patches till after EOL of posready2009 until Server2008 in 2020!! We are all set until 2020

Share this post


Link to post
Share on other sites
On 19/09/2017 at 9:11 PM, Just_AHD said:

So Windows XP will be a updated OS until 2020?

Yes easily unofficial patches can be made. After that some hard work will be required. 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...