Post a Comment
Not a big fan of the the embedded windows systems, as ive seen far to many of these BSOD.
However the bit i really don't understand is the last paragraph, why the heck would you create an embedded system that has to be activated. I thought the whole idea was that these systems are placed into kiosks and other small devices which nine times out of ten don't have an internet connection. So all of these embedded systems will need to be activated off the production line.
sometimes i really wonder who makes these sort of stupid decisions. I can understand to stamp out piracy they would stick it in the client (not a massive fan of having it in servers, but i can understand a little), but an embedded system???
Oh well, just keep pushing people over the linux.
This just proves microsoft has gone off the deep end. Activation of an OS that is burned into the unit? How would people pirate this? What would you install it on? I mean, where do you find a Windows mobile capable device without a version of Windows mobile already on it? DUMB!!!
A lot of people seem to confuse XP/Vista Embedded with Windows Mobile/CE. Embedded XP/Vista are just desktop versions stipped out of unnecessary components, you can run regular Windows apps on them, and usually vice-versa - although then can be some protection, for example for games from arcade machines (modern ones seem to mostly use XP Embedded these days) so that you can't run them on unauthorized machines.
There's still little point to have whole activation scheme but I guess OEMs will get the deals that let them skip it.





