Replies

Microsoft are, in effect, continuing support through Windows Update for XP by still supporting Embedded versions through to 2019 (POSReady 2009). Updates are still available through Windows Update so obviously MS are still patching XP. http://blogs.msdn.com/b/windows-embedded/archive/2014/02/17/what-does-the-end-of-support-of-windows-xp-mean-for-windows-embedded.aspx

I think you’ll find that a large proportion of POS systems (I’m not up on ATM software) actually use a POS specific version of the relevant Embedded OS. We use POSReady 2009 which actually is supported to 2019 – and is based on XP Embedded. The moot point however is that I reckon AV vendors will stop pattern file distribution well before then.

In a meeting with MS UK around the time of Vista RC I was told the reason that reboots were done was that because the code developers were specialists in one area they didn’t know what effect their changes made on other developers code so they used a ‘better safe than sorry’ regime.

In a meeting with MS UK around the time of Vista RC I was told the reason that reboots were done was that because the code developers were specialists in one area they didn’t know what effect their changes made on other developers code so they used a ‘better safe than sorry’ regime.

In a meeting with MS UK around the time of Vista RC I was told the reason that reboots were done was that because the code developers were specialists in one area they didn’t know what effect their changes made on other developers code so they used a ‘better safe than sorry’ regime.

In a meeting with MS UK around the time of Vista RC I was told the reason that reboots were done was that because the code developers were specialists in one area they didn’t know what effect their changes made on other developers code so they used a ‘better safe than sorry’ regime.

In a meeting with MS UK around the time of Vista RC I was told the reason that reboots were done was that because the code developers were specialists in one area they didn’t know what effect their changes made on other developers code so they used a ‘better safe than sorry’ regime.

In a meeting with MS UK around the time of Vista RC I was told the reason that reboots were done was that because the code developers were specialists in one area they didn’t know what effect their changes made on other developers code so they used a ‘better safe than sorry’ regime.

In a meeting with MS UK around the time of Vista RC I was told the reason that reboots were done was that because the code developers were specialists in one area they didn’t know what effect their changes made on other developers code so they used a ‘better safe than sorry’ regime.

In a meeting with MS UK around the time of Vista RC I was told the reason that reboots were done was that because the code developers were specialists in one area they didn’t know what effect their changes made on other developers code so they used a ‘better safe than sorry’ regime.