Windows CE and Windows XP Embedded ???

We're going to be talking about Windows Embedded operating systems in this eBlog, taking a look at Windows CE and Windows XP Embedded - that wild man of the west Jon Fincher already has a Windows XP Embedded QFE blog up and running - go check it out -

- Mike

Comments (3)

  1. Mo says:

    Thank goodness 🙂

    There’s not nearly enough proper discussion about CE about on the ‘net at the moment. All the talk revolves around the cool devices that ship with it, and there’s practically nothing of any use for people building systems with it (the same applies to XPe too, I guess).

    I suppose that’s why there’s so many reams of printed material on CE 🙂

  2. Mo says:

    Actually, here’s a question for you (a slightly strange one): Is there really no ExitProcess under CE?

    According to the integrated help collection in VS.NET 2003, the CE.NET 4.2 docs appear to say that there is, and it was supported since CE 2.0, but bizarrely that it’s declared in Mkfuncs.h which only exists (AFAIK) in CE.NET.

    eVC++ 3.0’s docs and headers show no trace of it, unsuprisingly.

    There are no issues sticking in a #ifdef UNDER_CE block in the code I’m working on, so I’m happy with a workaround – but I can’t actually *find* a workaround. I can TerminateProcess(), but that risks DLL state, and I can ExitThread, which will do the same provided it’s called from the process’ main thread (and I can’t guarantee that).

    So, the question is, I suppose: Is there a way to (at least semi-cleanly) emulate ExitProcess() in CE 2.11 onwards, and if not, is it supported in CE.NET?

  3. Mike says:

    ExitProcess is defined in winbase.h

    #define ExitProcess(code) TerminateProcess (GetCurrentProcess (), (code))

    The docs are incorrect (and will be fixed for Macallan) – you simply need to include Windows.h and all should be good.

    Calling ExitProcess will signal the attached DLL’s to clean up and terminate.

Skip to main content