Re: Searching for the right solution
- From: "Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam DOT com>
- Date: Wed, 1 Oct 2008 10:32:04 -0700
That thread was the right place for this. It gives context to anyone trying
to give a good response to you.
It sounds, based on what you've described, like you'd be most-comfortable
with an OS that you can customize, but one that runs on existing
PC-compatible hardware. Windows Embedded Standard matches that. Or, you
could just use Windows XP and write your code to take over as much of the
user interface as you can. Windows Embedded Standard will require
substantial effort on your part to do a customization that will actually run
and do what you want. It's useful, when you have highly-customized and
closely controlled hardware (you're building the hardware), and absolutely
must keep people out of the OS, but 90% of what you want to do can pretty
easily be done with just an application running on a PC, written
appropriately, and you can choose whatever OS you want. You'll have to
weigh the cost of several months of effort to properly configure and test XP
Embedded (Windows Embedded Standard, XPe), versus what you actually get from
that. If you want more-detailed info on what the effort is or how to do
what you want, the XPe group is a better place; it's completely different
than Windows CE, both in how you build it and what you get when you're done.
One could easily say, "Please don't start another thread on the same topic
as previous threads". You're the newbie here. It wasn't completely clear,
since you changed your name in that thread, that you were the right person.
Paul T.
"Krickster" <Krickster@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:158BBD8D-7AF0-44B8-B8C5-4FB7C7403755@xxxxxxxxxxxxxxxx
Paul,
I have only 1 other active thread inquiring about WEE.
This one is simply a broad request for direction towards a solution,
whether
it be XPe, CE or whatever.
And, why are you so rude to someone who is simply trying to get more
information to make an informed development (and business) decision on our
development of embedded units? Would you rather have interested parties
goto
Linux instead of exploring their WE options?
Please don't respond to me unless you have productive information
regarding
my inquiries. It is a waste of my time and your bandwidth.
Ken
"Paul G. Tobey [eMVP]" wrote:
Why do you keep starting new threads on the same topic? You *are* the
same
guy who has maybe four or five active threads right now, right?
Paul T.
"Krickster" <Krickster@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:FC644AED-A283-41D5-BB9A-974B65DEA856@xxxxxxxxxxxxxxxx
We have a Winforms app built for Vista (vb.net). We will soon be
migrating
it to be a full WPF app.
The application currently runs on dedicated\proprietary laptops each
controlling 6 peripherals. So far, we have taken steps to prevent the
user
from doing anything on the laptop except running the main app.
Obviously,
this application would be better suited and managed in a tightly
controlled
embedded environment.
Do to various reasons, we would like to keep the overall structure of
our
system the same (laptop + peripherals), but switch to an embedded
environment
where nothing but our App is running (no win shell or Windows
Applications
available).
This decision was made in the 11th hour. So, we are looking for the
cleanest and simplest transition for the time being. My initial
research
focus was on Windows Embedded CE for embedded laptops (thin client
units).
I
looked into XPe, but again we do not want to rework our Vista app any
more
than we have to.
Then I found Windows Embedded Enterprise consisting of Vista Business
for
Embedded. Although we would have to use a more netbook\thin-client
hybrid
approach, it would alleviate our concern with app reworks and
additional
driver development. At the moment, we are not concerned with footprint
size.
Therefore, this solution seemed to fit our needs.
In reading more about the WEE platform, I was thrilled to see that it
was
geared towards "fixed function" devices such as "kiosks, ATM systems,
POS
devices, complex industrial automation controllers, and complex medical
devices.". This statement told me that we could control the User UI
by
disabling or changing the Windows GUI or shell. Or at least it seemed.
I queried this group about it and was told that this is not the case.
That,
in fact, it was equivalent to the standard pc OS and did not provide
controls
by which we could provide our app as the sole functionality and UI of
the
system.
What would the experts here recommend in researching this scenario and
which
Embedded solution do you think would best address our immediate
concerns?
Solution requirements:
1) Must be able to run our current Vista .NET winform app without major
rework
2) Use on a small embedded netbook or thin-client laptop
3) The ability to Hide, disable or make inaccessible the windows
desktop\shell\GUI
Hope this makes sense as I am new to the Windows embedded world.
Thanks,
Ken
.
- References:
- Searching for the right solution
- From: Krickster
- Re: Searching for the right solution
- From: Paul G. Tobey [eMVP]
- Re: Searching for the right solution
- From: Krickster
- Searching for the right solution
- Prev by Date: Re: Searching for the right solution
- Next by Date: RE: Searching for the right solution
- Previous by thread: Re: Searching for the right solution
- Next by thread: RE: Searching for the right solution
- Index(es):
Relevant Pages
|
