Is XP Embedded the right choice for Machine Control Aplications?

[Igor]

Hello All,

We have a costumer that builds big cutting machines. Every machine movement
and operation is fully controlled by our application, that runs in XP. We
would like to "embedded" our app into the PC, so the user will not have
access to anything but the application. My question is: Is the Embedded
version the right choice for this case, since that we need is much more
blocking the user for doing anything else on the PC other than operating our
application? Shouldn't be easier to customize the local security policy for
every PC? Is it possible?
Since this custumer sells only 10 machines a year, does it make sence to
have a embedded version for such low quantities?

What do you suggest?

Thanks in advance,

Igor

 

[Mike Warren]

Hello All,

We have a costumer that builds big cutting machines. Every machine
movement and operation is fully controlled by our application, that
runs in XP. We would like to "embedded" our app into the PC, so the
user will not have access to anything but the application. My
question is: Is the Embedded version the right choice for this
case, since that we need is much more blocking the user for doing
anything else on the PC other than operating our application?
Shouldn't be easier to customize the local security policy for
every PC? Is it possible? Since this custumer sells only 10
machines a year, does it make sence to have a embedded version for
such low quantities?

What do you suggest?

You can do all that with XP Pro/Home and for small quantities that
may be the better way of going about it. XPe development can take
some time (especially in the beginning) and you will need to factor
the dev cost into the price somehow.

Keep in mind that if you change the hardware, a new image will need
to be created which can become a bit of a problem if using consumer
hardware as it changes so often.

I much prefer XPe though because it is much easier to trim the size
down to only what is required and the embedded enabling features like
EWF and FBWF which improve system reliability significantly.

 

[Sean Liming \(eMVP\)]

XPe is the best way to go. You can lock the image down with custom shells,
EWF/FBWF, custom splash screen, custom security, etc.

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
Book Author - XP Embedded Advanced, XP Embedded Supplemental Toolkit

 

[KM]

Igor,

You can certainly lock the OS (XP or XPe) so that you app is the only app accessible to end users. A bunch of known tricks there -
from custom shell settings to local and group security policies and various documented and undocumented system settings.

Although you can lock the image with XP Embedded in cleaner way than on X Pro since you are not including some components there from
the beginning, everything can be done on XP Pro too. Also, obviously, you will get the lower OS licensing costs with XPe.

Anyway, as Mike pointed out, with the low production quantities you may be better off calculating the dev costs first including the
XPe Toolkit pricing.