keep XP updated until 2019

J

Jon Danniken

It isn't supported by MS for consumer XP SP3. I wouldn't trust it. It
would make things worse.

You mean could make things worse. As of now, there is no evidence that
it will break anything, all we know is that it will get the updates to
your machine.

As the updates are untested on consumer XP, according to Microsoft, it
is entirely possible that it will cause problems, but we still have no
evidence of that.

Jon
 
G

Good Guy


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.
 
M

Mayayana

| 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.
|

You do realize this is an XP group? Why is everyone
here if their computers are useless? Why are you here
if you don't use XP?

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.

What do you define as "meaningful"? Perhaps
adolescent shoot-em-up games? Video games
are among the very short list of things that
benefit from having a new computer.

I happen to have a dual-CPU Win7-64 machine
that someone gave me. It's ridiculously powerful.
There's only one thing I ever use it for: Extremely
memory intensive work. I fired it up recently to
convert lectures on an audio tape to digital format.
I also test my own software on Win7 sometimes.
Other than that I find the bloat and excessive
complexity of Win7 to be unappealing compared to
XP. I like a system that's dependably responsive.
 
T

Todd


+2

Hi Mayayana and Bill,

At last count I have 12 Virtual machines (base is Linux)
to support my customers. Many of them are Windows.
Two are XP. Gives me a good chance to see how things
perform side by side. After XP, Windows got SSSSLLLOOOOOWWW.

Any remaining Windows work I still have, I do in one of my
XP machines. The rest are too slow and unstable.
Frankenstein (Windows 8) drives me nuts!

-T

Trivia: if you are using Wine in Linux, you can set yourself
up as many independent editions of Windows as you like with
the WINEPREFIX variable

For instance, Acrobat Pro 8 doesn't like my install of
Lotus Smart Suite, so it gets its own

env WINEPREFIX="/home/todd/.wine.adobe" wine
C:\\windows\\command\\start.exe /Unix
/home/todd/.wine.adobe/dosdevices/c:/users/todd/Start\
Menu/Programs/Adobe\ Acrobat\ 8\ Professional.lnk
 
M

Mayayana

| 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/
 
C

casey.o

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.


Sometimes I wonder if MS pays people like you to post responses like
this !!!!

Or else you're just joking......

I can do darn near EVERYTHING running Windows98, that any newer computer
can. If it wasn't for a lack of newer web browsers (for win98), I would
have not even bothered with XP.

And what else is there? Unless of course you love MS bloatware and can
actually use Win8 for more than posting advertising on it's desktop.
Looking at the demos in the stores, all they have are links to netflix,
ebay, amazon, and other commercial sites. That was the first thing I
noticed when Win8 hit the stores, and that alone turned me off
instantly.
 
G

Good Guy

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 need windows XP patches when all you do is " program, mostly
in VB6", and a "lot with VBScript".
 
A

Andy

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.

I will be using XP and Linux till at least 2019.

Based on O.S. statistics, XP is still in heavy use worldwide and will continue to be.

Later versions of Windows do not offer anything that most people can live without.
 
M

Mayayana

| > 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 need windows XP patches when all you do is " program, mostly
| in VB6", and a "lot with VBScript".
|
You seem to have forgotten what you wrote
and you haven't read what I wrote. So I'm not
sure how to respond.
In any case, I don't want Windows patches.
Perhaps you could read what *you* wrote and
then see if you have anything coherent to add. :)
 
M

Mayayana

| 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.
 
T

Todd

| 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/

Hi 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
 
T

Todd

| 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.

Hi Mayayana,

Rush is an Apple Guy.

-T
 
J

J. P. Gilliver (John)

In message <[email protected]>, Todd <[email protected]>
writes:
[]
Hi 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
Other than use up some resources that might have a noticeable effect on
less powerful machines, what other evils do you tell your customer Aero
does - or is it just that one?
--
J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

The voices of Radio 4 continuity and newsreading have been keeping me right
for as long as I can remember. I can call on a million different information
sources, but it doesn't make sense unti I've heard it from Peter, Harriet,
Charlotte and the rest.- Eddie Mair in Radio Times 10-16 November 2012
 
X

XP Guy

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.
 
X

XP Guy

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.

Download what?

There is nothing to download.

Just do the following:

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.
 
J

J. P. Gilliver (John)

In message <[email protected]>,
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.

There isn't anything to download: if you read what he said, there are
only four registry keys to be created/altered, but if you don't want to
do that, he made it as a .reg file: you copy the bits _of his post_
between the === lines into NotePad, then save the result as a .reg file,
then run it. (On your head be it though!) [Use his original post - or,
if you take the text from this one, remove all the ">>"s.]
[]
 
N

Nightbreaker

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.

Are you on Micro$haft's hit list now?
If so that would give a lot of credence to this info.
 
C

casey.o

Hi Mayayana,

Rush is an Apple Guy.

-T

I wouldn't think he has the brain power to know how to use a computer.
But I suppose that all depends on how much codine he is taking at the
moment..... :)
 
C

casey.o

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.

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.

BTW: Movie Maker can be downloaded separately from MS.


If I install this, I sure hope my computer becomes an ATM and spits out
lots of money! :)

I'm sure glad you specified "Point of Service" or I would have thought
it meant "Piece of Shit"...... I know someone who refers to his car as a
POS. :)
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top