Taiwan – what a hoot…

The WEE in Taiwan is over, we had an excellent turn out and some really great questions during the Ask the Experts (which turned out to be “Ask Mike and Ravi“) and after sessions - Doug Boling couldn't make it over to Taiwan but will be joining the tour in South Korea, I ended up covering Doug's application development session and lab for Taiwan - the session is really good fun to present - there are just a handful of slides and most of the session is coding Win32, MFC and C# “Scribble“ applications to show the advantages of each method of applicaiton devleopment.

I need to persuade Doug to make the session in South Korea a “double act” I think that could be a blast!

It would appear that some folks have found the eBlog and have started posting comments and questions, excellent ! - welcome aboard ! - one of the questions deals with an API call ExitProcess( ) - the Windows CE .NET documentation shows that you need to #include mkfuncs.h to get the function prototype - if you examine the contents of mkfuncs.h you will find that the function ExitProcess( ) is actually commented out - the API is defined inline in winbase.h, like so...

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

so you simply need to #include Windows.h to get this - the Windows CE .NET 4.2 documentation is in error and will be fixed for Macallan.

BTW - did anyone understand the code names used for the Windows CE products ?

In the beginning, long before any public tools were shipped we had the OEM Adaptation Kit, or OAK (whch is a tree...)

So , the first versions of Windows CE were named after trees...

Alder, Birch, Cedar (Windows CE 3.0) - at this time there was a seperate tools team, so the tools also had codenames, after things that cut down trees

Axe, Buzzsaw, Chainsaw (Windows CE 3.0) - makes sense, right - so what about Windows CE 4.0 ? - this was also going to be named after tree/tools - DougFir, and Dozer (bulldozer) - at Windows CE 4.0 the tools and O/S teams were merged, so the code name for the operating system also changed to be named after Whisky.

Windows CE 4.0 - Talisker

Windows CE 4.1 - Jameson

Windows CE 4.2 - McKendric

Windows CE (next version) - Macallan

I found a web site that appears to have a list of the Microsoft codenames on it http://www.bitzenbytes.com/101/r119-wcn.htm

ok, time to pack - the airport shuttle arrives at 7am - I can't remember whether there's a Starbucks at Taipei airport... here's hoping...

- Mike

Comments (1)

  1. Mo says:

    Many thanks for the answer! The fact that TerminateProcess (GetCurrentProcess (), (code)) will sort out attached DLLs was the killer with the docs.

    If memory serves, OAK build logic dates back at least as far as MS-DOS 6.0/Win3.1 (though I could be wrong, IANAME [I am not a Microsoft Employee]. On a related note, the Bitzenbytes page doesn’t mention Astro, which I’m informed was MS-DOS 6.0, though it can be forgiven for that, as the page was entitled "Windows Codenames" – even if it was around that time that combined DOS/Windows ideas were the "in" thing back then 🙂

Skip to main content