Windows Embedded POSReady 2009

[bphlpt]

@Stefan43, you missed jaclaz's sarcasm.

Seriously, what are you really asking?

Officially, if I understand it correctly and I could be wrong, per the licenses of the effected products, you are not allowed to use MS Office apps with POSReady 2009, ie it is not supported. So for the vast majority of installations of POSReady 2009, which was intended for Point Of Sale terminals, which are often maintained through service contracts, such an installation of an MS Office app will not even be attempted.

But if you install POSReady 2009 for home use, which it was not intended for, apparently there is nothing to prevent your ability to install a MS Office app, even though it is not allowed.

Is it safe for use? I think what jaclaz meant with his appropriate sarcasm is that that it is probably just as "safe" as the use of any MS Office app, or any other software app for that matter. It's safety is more likely effected by the user's computing habits than the fact that either the OS or the MS Office app version is no longer being supported. You want a guarantee? Sorry, no one can give you that for any piece of software no matter what they tell you. Use safe computing practices and you most likely will be fine.

Cheers and Regards

[Flasche]

But if you install POSReady 2009 for home use, which it was not intended for, apparently there is nothing to prevent your ability to install a MS Office app, even though it is not allowed.

 

Ja, I never did understand that. It had something to do with copyright laws. You would think MS would try and limit POS2009 with it, but no they didn't.

 

 

@Stefan43, you missed jaclaz's sarcasm.

 

Yes do take in jaclaz's sarcasm. He is the king of it just to let you know .

[Flasche]

Ah yes I almost forgot. Any one of you who are willing to try and use POSReady 2009 should remove these registries

 

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Notify\SSOExec]
"Asynchronous"=dword:00000001
"Impersonate"=dword:00000001
"Logoff"="SSOReset"
"Unlock"="SSOExec"
"Lock"="SSOReset"
"DLLName"="%windir%\\temp\\sso\\ssoexec.dll"

 

There was a virus and Microsoft forgot to remove some of the registries.

[jaclaz]

Can I not just use it for creating Word documents and Powerpoint presentations. And not opening unkown files?

Sure you can, and very likely nothing will happen to you.

 

I mean:

How many people do you know personally that have been attacked by an Office virus ? 

How many cases have you read about people that have been attacked by an Office virus ? 

What were the consequences of these attacks?

 

The difference is only that if you are attacked by such a virus, you cannot blame anymore the fault on the good MS guys.

 

In any case, EVEN IF Office 2003 was actually still supported, you wouldn't anyway be able to have support from them, as you would be using it on POSReady 2009 which EXPLICITLY prohibits the use of "Office productivity applications".

BTW, allow me to doubt that you (or Flasche or anyone else not actually running a POS) actually have a valid license for POSReady 2009) , as those license were OEM only and were invariably released together with a "vertical" piece of hardware.

@bhplt

Now an interesting point could be whether PowerPoint can be defined as an Office productivity application .

 

jaclaz

P.S.: Flasche cited some (partial) info without quoting the source.

Here it is:

http://seclists.org/fulldisclosure/2012/Mar/17

http://seclists.org/fulldisclosure/2013/Aug/225

The "final" post:

http://seclists.org/fulldisclosure/2013/Sep/125

may be useful to understand the kind of security support the good MS guys provided in the past on the specific product.

The latter also contains a link (from the mouth of the wolf ) that may be useful to better understand the limits and extents of security related support:

http://technet.microsoft.com/library/cc722487.aspx

Edited May 31, 2014 by jaclaz

[Flasche]

P.S.: Flasche cited some (partial) info without quoting the source.

Here it is:

http://seclists.org/fulldisclosure/2012/Mar/17

http://seclists.org/fulldisclosure/2013/Aug/225

The "final" post:

http://seclists.org/fulldisclosure/2013/Sep/125

may be useful to understand the kind of security support the good MS guys provided in the past on the specific product.

The latter also contains a link (from the mouth of the wolf ) that may be useful to better understand the limits and extents of security related support:

http://technet.microsoft.com/library/cc722487.aspx

 

Thank you posting the sources. I never did know who found these.