J
John Peterson
We have a machine controller program that is currently in DOS. We are going
to re-write to run in XP Embedded, but we want it to be ALMOST headless. We
basically want XP Embedded to LOOK like DOS (plain black screen that we can
print text to, NO DESKTOP whatsoever, etc) but we can write the code as
windows code and take advantage of things like multi-threading.
Any basic suggestions for which components to do a first test build with?
The only I/O will be some text messages to the screen, some trapped
keystrokes, serial I/O, and if I get really ambitious, TCP/IP.
Bottom line, we want the added benefit of Windows, but don't want the
customer to have any interaface with which they can load their OWN
applications, games, etc. This is a dedictated system and we don't want
customers getting bright ideas.
Thanks
(e-mail address removed)
Fenton, MI
to re-write to run in XP Embedded, but we want it to be ALMOST headless. We
basically want XP Embedded to LOOK like DOS (plain black screen that we can
print text to, NO DESKTOP whatsoever, etc) but we can write the code as
windows code and take advantage of things like multi-threading.
Any basic suggestions for which components to do a first test build with?
The only I/O will be some text messages to the screen, some trapped
keystrokes, serial I/O, and if I get really ambitious, TCP/IP.
Bottom line, we want the added benefit of Windows, but don't want the
customer to have any interaface with which they can load their OWN
applications, games, etc. This is a dedictated system and we don't want
customers getting bright ideas.
Thanks
(e-mail address removed)
Fenton, MI