In this technical article titled “Scripting your Windows XP Embedded components“, software consultant Hans de Vetten offers guidance on how to script Windows XP Embedded components. The article describes some steps that lead to more user-friendly components.
Scripting your Windows XP Embedded components
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
Our company has lots of wyse terminals powered by XP embedded all over pur warehouse and they are as buggy and crash prone as Windows 95. Quite sad.
Our company has lots of wyse terminals powered by XP embedded all over pur warehouse and they are as buggy and crash prone as Windows 95. Quite sad.
Assuming this isn’t just a troll, problems like this with XP Embedded can usually be attributed to whoever put together the XP build for the terminals. The OS and it’s components are quite capable of being a very stable environment, but if you put the components together wrong (since Embedded permits you to put the components together however you like, more or less), or omit necessary components, you will get a very crash-prone environment.
We have had no problems.
I’ve been creating builds for embedded devices with XPe since it came out, and previously with NTe. Once i had a stable image going, i never had any problems with it afterwards.
It has worked fine for our company we are very pleased.
Well I work for the US ARMY and in my unit we use alot of Wyse Terminals running XP embedded and I can assure you that they work just fine. Rarely do we have to reboot them because of problems associated with a buggy os. I think this guy is just a troll.
Sure I’d like to manage a Linux network but sorry we use Windows. Its not my call but this stuff works just fine.