Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account


Photo

POSReady 2009 updates ported to Windows XP SP3 ENU

- - - - -

  • Please log in to reply
213 replies to this topic

#1
harkaz

harkaz

    Junior

  • Member
  • Pip
  • 71 posts
  • OS:Windows 7 x64
  • Country: Country Flag

UPDATE [22/5/2014]: Sebijk reported that a simple registry tweak is enough for WU to show the latest POSReady updates on Windows XP. This method has been tested and works on any XP build.

 

Add the following registry keys (INF Format):

 

HKLM,"System\CurrentControlSet\Control\WindowsEmbedded\ProductVersion","FeaturePackVersion",0x00000000,"SP3"

HKLM,"SYSTEM\WPA\WEPOS","Installed",0x10001,0

HKLM,"SYSTEM\WPA\WES","Installed",0x10001,0

HKLM,"SYSTEM\WPA\POSReady","Installed",0x10001,1

 

and restart the computer. Then run WU to get the latest updates.

 

ORIGINAL METHOD:The latest Patch tuesday updates have been easily ported to a Windows XP virtual system - fully updated until April 2014.
 
The constraints are entirely artificial. Porting is easy as 1-2-3:
 
1. Modify update.inf file and remove the
 
condition=CompositeOp,OrOp,Prereq.XPInstallEmbedded.Section line
 
from the Prerequisite section.
 
2. Use a patched update.exe version 6.3.13.0 or later to accept the modified update.inf file. Update.exe files differ between various languages.

 

UPDATE: Instructions on how to apply the patch to any language can be found here:

http://www.msfn.org/...-enu/?p=1078363

 

3. Compress to SFX EXE file. Delta compression optional.
 
I have already uploaded the files at RyanVM.net...
 
So Windows XP can have semi-official support until 2019! :w00t:


Edited by harkaz, 21 May 2014 - 05:04 PM.

  • AndrewNi and niko32 like this


How to remove advertisement from MSFN

#2
-X-

-X-

    Member

  • Patrons
  • 2,401 posts
  • OS:XP Pro x86
  • Country: Country Flag

Donator

Yep indeed. Just tested them by manually copying the files over and rebooting. No issues.


Edited by -X-, 13 July 2014 - 09:22 AM.

Download all Windows XP Post SP3 High-Priority Updates with a simple double click @ xdot.tk post-12166-0-42859000-1399044129.png ]
               If someone helps you fix a problem, please report back so they and others can benefit from the solution. Thanks!


#3
harkaz

harkaz

    Junior

  • Member
  • Pip
  • 71 posts
  • OS:Windows 7 x64
  • Country: Country Flag

Lol.. it must be an unpleasant surprise to them

PS. By mistake, I refreshed the page when posting the thread and it has been double-posted. Please lock/remove the older one.



#4
MrMaguire

MrMaguire

    Junior

  • Member
  • Pip
  • 51 posts
  • OS:XP Pro x64
  • Country: Country Flag

Wow, this is excellent news!



#5
Flasche

Flasche

    A bottled message!!

  • Member
  • PipPipPipPip
  • 590 posts
  • OS:ME
  • Country: Country Flag

I always knew getting POSReady2009 was a good Idea :w00t:


Seeker Of Truth by E. E. Cummings                                                                                           Quote (Me)

  • seeker of truth                                                 "If you want to reach and discover the true meaning of order; You must go through chaos first."            344d0f9.jpg
  • follow no path                                 
  • all paths lead where
  • truth is here
 

#6
egrabrych

egrabrych

    Junior

  • Member
  • Pip
  • 84 posts
  • OS:98SE
  • Country: Country Flag

Donator

The here: http://www.microsoft...s.aspx?id=42774
are fixes NDP20SP2-KB2932079 for Windows XP :yes:



#7
dencorso

dencorso

    Adiuvat plus qui nihil obstat

  • Super Moderator
  • 5,779 posts
  • OS:98SE
  • Country: Country Flag

Donator

Well, Bulletin 1 in the [...] IE8 version should be immediately usable, perhaps requiring a relaxing of the .INF  "Applies To"  conditions [...]. I'm betting Bulletin 5 (the .NET one) may be directly applicable, too, perhaps requiring, likewise, some previous callisthenics... As for Bulletin 6, we'll only know, when whe know what does it contain. [...]

 

Thanks to harkaz, Bulls 1, 5 and 6 installed and running great! :thumbup

 

Long live, XP! :)


  • Tommy likes this

#8
vinifera

vinifera

    <°)))><

  • Member
  • PipPipPipPipPip
  • 951 posts
  • OS:Windows 7 x86
  • Country: Country Flag

lol who cares about neowinians

they never had brain, obviously never will


If you want true Windows user experience
try Longhorn builds: 3718, 4029, 4066

#9
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,019 posts
  • OS:none specified
  • Country: Country Flag

With reference to this:

http://www.microsoft...s.aspx?id=42774

which is related to this kb:

http://support.micro....com/kb/2932079

 

 

Introduction
This update resolves a vulnerability in the Microsoft .NET Framework that could allow elevation of privilege if an unauthenticated attacker sends specially crafted data to an affected workstation or server that has the .NET Framework Remoting feature enabled.

 

it is IMHO not a patch for a vulnerability, it is a patch for generic stupidity.

 

jaclaz



#10
the xt guy

the xt guy

    Member

  • Member
  • PipPip
  • 102 posts
  • OS:XP Pro x86
  • Country: Country Flag

Donator

First of all, thank you *very much* harkaz, this is beyond cool! Heading home from work yesterday I was almost a bit giddy seeing these semi-official patches and thinking of all the future ones that could/will be coming our way through 2019!

Let the idiots on neowin storm off in a huff! Tell them to come back in 2019.

For myself, I only get 1 patch out of the deal (I don't have IE or any version of "dontnet" installed). Hmm, I didn't think about POS not having IE6. Looks like we won't get any IE 6 patches unless somebody ports them from 2003.

Jaclaz, I agree it's a patch for general stupidity-let's hope MS doesn;'t start patching for that, as we'll all need petabyte sized drives.

(Seriously though, the link to the bulletin 42774 that you posted; under 'System Requirements' it states that Windows XP is a "supported operating system" along with Windows Server 2003. But the title at the top of the page for 42774 just says Windows Server 2003.)

#11
dencorso

dencorso

    Adiuvat plus qui nihil obstat

  • Super Moderator
  • 5,779 posts
  • OS:98SE
  • Country: Country Flag

Donator

Rest assured the IE6 and the IE7 patches for POSReady 2009 also exist! I'm sure harkaz'll release modded versions of them soon, too.



#12
jsc1973

jsc1973
  • Member
  • 5 posts
  • OS:XP Pro x64
  • Country: Country Flag
Is there any chance of getting all of the Windows Server 2003 x64 updates onto XP x64? Someone just suggested I ask my question in this thread, and TIA for any help. :)

Earlier today, I attempted to download the three available updates for Server '03 and install them manually onto my XP x64 laptop. I had no trouble with MS14-026 (using the .NET 2.0 version; I don't have 4.0 installed so I didn't try that one) or 029. However, MS14-027 failed. A check of the .inf files inside the update revealed that Microsoft put in a block in "update_SP2QFE.inf" that prevents it from installing on XP x64:

[Prereq.XPAMDInstallBlock.Section]
PresentOp=CheckReg,HKLM,"SYSTEM\CurrentControlSet\Control\ProductOptions",ProductType,0x00000000
NotEqualOp=CheckReg,HKLM,"SYSTEM\CurrentControlSet\Control\ProductOptions",ProductType,0x00000000,!=,"WinNT"
Display_String="%WrongProductMessage%"

Is this update legitimately not suitable for XP x64 for some reason, or is Microsoft just being a PITA about it? And if it's the latter, how hard would it be to hack it to run? Would like to keep this machine on XP x64 as long as I can. It's a Dell Inspiron 1545 with a T9800, and it can run 7, but feels like it's running in mud compared to XP x64.

Edited by jsc1973, 14 May 2014 - 04:20 PM.


#13
harkaz

harkaz

    Junior

  • Member
  • Pip
  • 71 posts
  • OS:Windows 7 x64
  • Country: Country Flag

The update is applicable to Windows XP x64 SP2 if you remove the:

 

    Condition=AndOp,Prereq.XPAMDInstallBlock.Section

 

line from the [Prerequisite] section and patch the update.exe file to accept the modified update.inf. Instructions can be found here: http://www.ryanvm.ne...p=115464#115464

 

The shlwapi.dll file is not an exclusive Server 2003 x64 component. In addition there are registry keys in the INF file specific for XP Professional x64:

 

[ProductInstall.ProfessionalFiles]
    AddReg=Product.Add.Reg.Professional

[Save.Reg.For.Uninstall]

HKLM,SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP%SERVICE_PACK_NUMBER%\%SP_SHORT_TITLE%

 

[Product.Add.Reg.Professional]
    HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%,"Comments",0,%SP_TITLE_XP%
    HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%,"Fix Description",0,%SP_TITLE_XP%
    HKLM,SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%SP_SHORT_TITLE%,"RegistryLocation",0,"HKLM\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP%SERVICE_PACK_NUMBER%\%SP_SHORT_TITLE%"
    HKLM,SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%SP_SHORT_TITLE%,"ParentDisplayName",0,"%PARENT_DISPLAY_NAME_XP%"
    HKLM,SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%SP_SHORT_TITLE%,"DisplayName",0,"%SP_TITLE_XP%"
    HKLM,SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP%SERVICE_PACK_NUMBER%\%SP_SHORT_TITLE%,"Description",,%SP_TITLE_XP%
 

and the relevant strings.

 

All these observations indicate that the update is applicable to XP x64 without any issues (It's not proved completely - that would require an analysis of the patch itself, something rather difficult and not required in this scenario).

 

One final note: Because these updates have been deployed on a relatively limited number of machines (XP support has officially ended and most users ignore the existance of these updates) testing any of them in VM before deploying to real hardware is strongly recommended.



#14
dencorso

dencorso

    Adiuvat plus qui nihil obstat

  • Super Moderator
  • 5,779 posts
  • OS:98SE
  • Country: Country Flag

Donator

Besides other editings needed, the "Frankenstein folder" "Windows XP Version 2003" must be corrected to "Windows XP", BTW.

#15
harkaz

harkaz

    Junior

  • Member
  • Pip
  • 71 posts
  • OS:Windows 7 x64
  • Country: Country Flag

@den It should not be corrected for Windows XP x64 edition:

 

All Windows XP x64 (Version 2003) post-SP2 updates are verified via this registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3



#16
Flasche

Flasche

    A bottled message!!

  • Member
  • PipPipPipPip
  • 590 posts
  • OS:ME
  • Country: Country Flag

Rest assured the IE6 and the IE7 patches for POSReady 2009 also exist! I'm sure harkaz'll release modded versions of them soon, too.

 

Are you sure that there are IE6 patches for POSReady? It comes preloaded with ie7. (Never tried to revert back to ie6 since I hate it)


Seeker Of Truth by E. E. Cummings                                                                                           Quote (Me)

  • seeker of truth                                                 "If you want to reach and discover the true meaning of order; You must go through chaos first."            344d0f9.jpg
  • follow no path                                 
  • all paths lead where
  • truth is here
 

#17
jsc1973

jsc1973
  • Member
  • 5 posts
  • OS:XP Pro x64
  • Country: Country Flag
The patched update.exe seems to have done the trick. The update installed and is actually listed in my list of updates as a "Windows XP" update! I guess Microsoft isn't going to let anyone on XP x64 install it the easy way unless they have paid support, though. I know there's a risk to doing this, but this isn't a mission-critical machine, anyway. Just a laptop I use when I'm away from the big iron, to go online and stuff with. If it were, I'd just update it to 7. Guess I'll just keep doing this once a month until July of next year. Thanks for the help! :)

#18
dencorso

dencorso

    Adiuvat plus qui nihil obstat

  • Super Moderator
  • 5,779 posts
  • OS:98SE
  • Country: Country Flag

Donator

Besides other editings needed, the "Frankenstein folder" "Windows XP Version 2003" must be corrected to "Windows XP", BTW.

 

@den It should not be corrected for Windows XP x64 edition:
 
All Windows XP x64 (Version 2003) post-SP2 updates are verified via this registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3


I stand corrected. Thanks! :yes: 
 

Rest assured the IE6 and the IE7 patches for POSReady 2009 also exist! I'm sure harkaz'll release modded versions of them soon, too.

 
Are you sure that there are IE6 patches for POSReady? It comes preloaded with ie7. (Never tried to revert back to ie6 since I hate it)

Yes. Harkaz made them available already, BTW.



#19
yuhong

yuhong
  • Member
  • 2 posts

Rest assured the IE6 and the IE7 patches for POSReady 2009 also exist! I'm sure harkaz'll release modded versions of them soon, too.

 

Are you sure that there are IE6 patches for POSReady? It comes preloaded with ie7. (Never tried to revert back to ie6 since I hate it)

 

There is also the older WEPOS/XPe which comes with IE6 and is supported until I think 2016 and also uses the same patches.



#20
Dave-H

Dave-H

    Friend of MSFN

  • Member
  • PipPipPipPipPip
  • 767 posts
  • OS:98SE
  • Country: Country Flag

I installed five of harkaz's modified updates yesterday.

KB2953522 (IE8), KB2932079 (.NET 2.0), KB2931365 (.NET 4.0), KB2931352 (.NET security update), and KB2926765 (XP security update).

 

All seemed well, but a while after the updates were installed, the machine suddenly blue screened.

The stop error was 0x0000004E, PFN_LIST_CORRUPT, apparently thrown by ntoskrnl.exe.

On restart, the machine seemed OK again.

 

However this morning, after booting up and leaving it for a while, I found it with another BSOD.

This time the stop error 0x00000044, MULTIPLE_IRP_COMPLETE_REQUESTS.

 

Any ideas? I am a bit suspicious of KB2931352, as that seemed to replace a lot of .NET files, including some that were from ten years ago!


Edited by Dave-H, 16 May 2014 - 11:59 AM.

Dual boot Windows 98SE SP2.1a and Windows XP Professional SP3.
Dual 3.2GHz Xeons with 4GB RAM. ATI Radeon X850 Graphics 1920x1080 32 Bit Colour with Large Fonts.


#21
submix8c

submix8c

    Inconceivable!

  • Patrons
  • 4,186 posts
  • OS:none specified
  • Country: Country Flag

Google on the first error

"PFN_LIST_CORRUPT" XP
only gives seemingly related problems in two of the links, indicating some kind of driver conflict (weird).

http://www.tomshardw...corrupt-windows

http://social.techne.../pfnlistcorrupt

Here is some further info -

http://www.reviverso...n-list-corrupt/

 

Could it be that Error#1 led to Error#2, which it seems so.

 

I'd have installed only one at a time, ran with it for a while to confirm viability, then the next one, and so on. Paricularly I would have done the IE8 one first, then the XP one, then the NT ones lowest version to highest version.

 

HTH (no, I haven't tried them yet but will eventually)


Someday the tyrants will be unthroned... Jason "Jay" Chasteen; RIP, bro!

Posted Image


#22
MagicAndre1981

MagicAndre1981

    after Windows 7 GA still Vista lover :)

  • Patrons
  • 5,941 posts
  • OS:Vista Ultimate x86
  • Country: Country Flag

Donator

share the dumps, maybe we can see anything useful.


Posted Image

#23
Dave-H

Dave-H

    Friend of MSFN

  • Member
  • PipPipPipPipPip
  • 767 posts
  • OS:98SE
  • Country: Country Flag

Thanks, I think I will be a bit more wary next month!

Touching wood, the machine seems to be stable again now.

Whatever caused the BSODs seems to have cleared itself.

I'm wondering if it was the .NET optimisation service, that runs after any .NET updates, that caused the crashes.

It seems to have done its job now, and isn't running any more.

The only other symptom I was getting was that the startup seemed to be slow (after the desktop loaded) and I was getting pop-up error messages that the Firewall wasn't running. This cleared eventually, and the startup now seems to be normal again.

I've had this before after updates, so it may or may not be relevant.

:)


Dual boot Windows 98SE SP2.1a and Windows XP Professional SP3.
Dual 3.2GHz Xeons with 4GB RAM. ATI Radeon X850 Graphics 1920x1080 32 Bit Colour with Large Fonts.


#24
Dave-H

Dave-H

    Friend of MSFN

  • Member
  • PipPipPipPipPip
  • 767 posts
  • OS:98SE
  • Country: Country Flag

share the dumps, maybe we can see anything useful.

OK, here they are!

I've given them a dummy .txt extension so the forum will let me upload them.

I hope they give some clue as to what happened!

Cheers, Dave.

:)

Attached Files


Dual boot Windows 98SE SP2.1a and Windows XP Professional SP3.
Dual 3.2GHz Xeons with 4GB RAM. ATI Radeon X850 Graphics 1920x1080 32 Bit Colour with Large Fonts.


#25
submix8c

submix8c

    Inconceivable!

  • Patrons
  • 4,186 posts
  • OS:none specified
  • Country: Country Flag

OUCH!

.NET optimisation service
I turn that bad boy off (disable the Service) IMMEDIATELY after any updates. It (IMHO) drags the system.

Someday the tyrants will be unthroned... Jason "Jay" Chasteen; RIP, bro!

Posted Image





4 user(s) are reading this topic

0 members, 4 guests, 0 anonymous users



How to remove advertisement from MSFN