It isn't supported by MS for consumer XP SP3. I wouldn't trust it. It
would make things worse.
Why do you want to keep using XP until 2019? What exactly do you use
your computer for? By 2019, it is very likely you won't be able to use
XP for any meaningful work because all the new applications won't run on
your dilapidated/obsolete XP machine. Either you are an hobbyist in
which case it doesn't matter whether you get any patches or not or that
you are keeping a machine just for show. You can't be doing anything
meaningful on your computer.
I do photo editing, web design, writing, email,
Internet and programming on my XP machine. I
also do various basic things: Downloading articles
and such to read and store.
I program, mostly in VB6, which is currently among
the most widely supported tools, working with
no needed support files on virtually all currently
running Windows machines. I also do a lot with
VBScript, which is also nearly universally supported
on Windows machines.
I don't do much "office" work, but I do my taxes
and I also write out business contracts and receipts
on my XP PC, using Libre Office.
Why do you want to keep using XP until 2019? What exactly do you use
your computer for? By 2019, it is very likely you won't be able to use
XP for any meaningful work because all the new applications won't run on
your dilapidated/obsolete XP machine. Either you are an hobbyist in
which case it doesn't matter whether you get any patches or not or that
you are keeping a machine just for show. You can't be doing anything
meaningful on your computer.
I think you are mistaken.Good Guy
| After XP, Windows got SSSSLLLOOOOOWWW.
That makes sense. There's a lot more running on
NT6 by default, and Win8 adds the Metro mess,
which seems to need a multi-core CPU and 1 GB
RAM just to sit there.
Some may remember the scandal and court case
around "Vista Capable", which is a good example of
what NT6 takes to run:
Microsoft was planning Vista as a bloated mess that
would require people to buy new computers. That
was great for the OEMs. MS warned them to make
sure they were ready, with more powerful machines
that could handle Vista. As it turned out, the minimum
Intel chipset that could handle the Aero techno-kitsch
GUI was the 945. But Intel had truckloads of their 915
chipset that they wanted to dump. Finally MS decided
to create Vista Capable as a second "approved for Vista"
logo to go on machines that couldn't handle Vista. Then
OEMs could install Vista with no Aero on those machines,
and Intel could sell off their 915s. There was lots of
confusion. All the more so given that the new GUI was
the only notable selling point of Vista in the first place.
It had been 6 years coming, after the total failure of their
plan to create Windows as an even more bloated .Net
OS, yet it wasn't even really needed.
http://blog.seattlepi.com/microsoft/2008/02/27/full-text-microsoft-execs-on-vista-problems/
| Sometimes I wonder if MS pays people like you to post responses like
| this !!!!
|
| Or else you're just joking......
I'm beginning to wonder, too. I suspect
GoodGuy may just be doing his homework
assignment for the Rush Limbaugh School
of Public Speaking.
Other than use up some resources that might have a noticeable effect onHi Mayayana,
You do not believe how many of my customer go
for me turning Aero off when I tell them what it
does. At least Frankenstein (Windows 8) got rid of
it.
M$ makes my head spin at times.
-T
Ammammata said:(what-ever)
I'm saving this message for reference. This sounds useful. But I
question whether one can activate this as a private individual.
You did not post a URL to download it.
[]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
Or use notepad to copy the following and save as .reg file and run it:
==========
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WindowsEmbedded\Pr
oductVersion]
"FeaturePackVersion"="SP3"
[HKEY_LOCAL_MACHINE\SYSTEM\WPA\WEPOS]
"Installed"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\WPA\WES]
"Installed"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\WPA\PosReady]
"Installed"=dword:00000001
===========
Restart your computer, and make sure WindozeUpdate service is running.
You will see there are updates for you to install! And your XP PC will
continue to recieve MS patches until the year 2019.
This is for 32-bit XP. There is a different method for 64-bit version
of XP (by spoofing Windows 2003 server).
You did not post a URL to download it.
Ammammata said:(what-ever)
I posted the full details of this hack back on May 22 in a thread with
the subject:
"A few registry key entries will allow XP to update itself via
Windows Update until the year 2019"
For those that are too afraid or simply don't know about how this works
- there is something that is really just an alternate version of XP-SP3
that Micro$haft calls "POSReady 2009".
POSReady 2009.
Nobody in a thousand years searching for XP related updates or hotfixes
would ever think to search for "POSReady 2009". Very good move for
Macro$haft to call it POSReady 2009 instead of "XP for POS 2009" or some
such.
POS means "Point of Service". It's what cash registers and bank teller
computers are running. I think ATM's and gas pump machines too (as if
they couldn't be running DOS).
POS2009 came out in 2009 (I think that's when SP3 came out for XP). It
will have full security updates for 10 years (hence EOL in 2019).
POSReady 2009 is exactly the same as XP-SP3, but with a few trivial
differences - such as no help files, DotNet installed by default, no
Movie Maker, etc. You get the idea.
Micro$haft will tell you that POS2009 and XP-SP3 are two different
products. Of course they are! You take an XP CD, slap a new label on
it, give it a new SKU or product number, ->CREATE A SPECIAL LICENSE
AGREEMENT FOR IT<- and voila - you have a different product.
Yes - the only real difference is the license agreement. And who here
really pays attention to that stuff anyways?
So the security updates and fixes that Milkro$oft will be making for
POS2009 for the next 5 years are fully compatible with every XP-SP3
system out there.
Meekro$oft will tell you that POS2009 updates ARE NOT INTENDED FOR XP -
of course they're not! Not if Macro$haft had it's way and was in
control of your computer!
But of course you all realize that saying "not intended" is not the same
thing as saying "they won't work".
===============
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
Or use notepad to copy the following and save as .reg file and run it:
==========
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WindowsEmbedded\ProductVersion]
"FeaturePackVersion"="SP3"
[HKEY_LOCAL_MACHINE\SYSTEM\WPA\WEPOS]
"Installed"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\WPA\WES]
"Installed"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\WPA\PosReady]
"Installed"=dword:00000001
===========
Restart your computer, and make sure WindozeUpdate service is running.
You will see there are updates for you to install! And your XP PC will
continue to recieve MS patches until the year 2019.
This is for 32-bit XP. There is a different method for 64-bit version
of XP (by spoofing Windows 2003 server).
To be on the safe side, you should probably be running XP-SP3 (but who
wouldn't be?) and you might want to select "manual" updating and have a
look at the updates and DO NOT EVER download anything called "WGA" or
"Windows Genuine disAdvantage" if anything like that ever comes down the
pipe.
Hi Mayayana,
Rush is an Apple Guy.
-T
Ammammata said:(what-ever)
I posted the full details of this hack back on May 22 in a thread with
the subject:
"A few registry key entries will allow XP to update itself via
Windows Update until the year 2019"
For those that are too afraid or simply don't know about how this works
- there is something that is really just an alternate version of XP-SP3
that Micro$haft calls "POSReady 2009".
POSReady 2009.
Nobody in a thousand years searching for XP related updates or hotfixes
would ever think to search for "POSReady 2009". Very good move for
Macro$haft to call it POSReady 2009 instead of "XP for POS 2009" or some
such.
POS means "Point of Service". It's what cash registers and bank teller
computers are running. I think ATM's and gas pump machines too (as if
they couldn't be running DOS).
POS2009 came out in 2009 (I think that's when SP3 came out for XP). It
will have full security updates for 10 years (hence EOL in 2019).
POSReady 2009 is exactly the same as XP-SP3, but with a few trivial
differences - such as no help files, DotNet installed by default, no
Movie Maker, etc. You get the idea.
Micro$haft will tell you that POS2009 and XP-SP3 are two different
products. Of course they are! You take an XP CD, slap a new label on
it, give it a new SKU or product number, ->CREATE A SPECIAL LICENSE
AGREEMENT FOR IT<- and voila - you have a different product.
Yes - the only real difference is the license agreement. And who here
really pays attention to that stuff anyways?
So the security updates and fixes that Milkro$oft will be making for
POS2009 for the next 5 years are fully compatible with every XP-SP3
system out there.
Meekro$oft will tell you that POS2009 updates ARE NOT INTENDED FOR XP -
of course they're not! Not if Macro$haft had it's way and was in
control of your computer!
But of course you all realize that saying "not intended" is not the same
thing as saying "they won't work".
===============
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
Or use notepad to copy the following and save as .reg file and run it:
==========
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WindowsEmbedded\ProductVersion]
"FeaturePackVersion"="SP3"
[HKEY_LOCAL_MACHINE\SYSTEM\WPA\WEPOS]
"Installed"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\WPA\WES]
"Installed"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\WPA\PosReady]
"Installed"=dword:00000001
===========
Restart your computer, and make sure WindozeUpdate service is running.
You will see there are updates for you to install! And your XP PC will
continue to recieve MS patches until the year 2019.
This is for 32-bit XP. There is a different method for 64-bit version
of XP (by spoofing Windows 2003 server).
To be on the safe side, you should probably be running XP-SP3 (but who
wouldn't be?) and you might want to select "manual" updating and have a
look at the updates and DO NOT EVER download anything called "WGA" or
"Windows Genuine disAdvantage" if anything like that ever comes down the
pipe.