Thursday, July 12, 2007

Remote Tools Framework for Windows CE

You want to use the Remote Tools but you do not want to install Platform Builder 6.0 extension, on your computer. So the Remote Tools Framework for Windows CE is the solution to your need.
That Framework also provides tools and facilities to implement your own Remote Tools.

[Update 7/12] : You still need to install Visual Studio 2005 to use the framework

- Nicolas

Wednesday, July 11, 2007

Adeneo gets EMEA Windows Embedded Partner award

Adeneo has received the Windows Embedded Partner Excellence Award for 2007, for the EMEA (Europe, Middle East, Africa) region. The company received this award in the System Integrator category, as part of Microsoft's recent Mobile & Embedded Developers Conference (MEDC) in Berlin.

- Nicolas

Customise your x86 device splash screen

Some of you are using the CEPC or x86 targets and wants to customize the splash screen displayed by the Bios Loader at startup. This loader can only display bmx files.
But what is the type of those files !! Is there any editor available for these files ??
Mike Hall has the answer and wrote an article about those files, this article is available here.

Thanks to mike !!


Monday, July 9, 2007

Dealing with OAL IoControls

I found a good reference article on the differences between Windows CE 5.0 and Windows CE 6.0. One of the paragraph is linked to the KernelIoControl call restrictions under Windows CE 6.0.

So I give you more details about it.
On the previous version of Windows CE, user mode code could use any valid OAL IoControl code when calling KernelIoControl. But it's not the case under Windows CE 6.0, as it provides security enhancement, now you can only call IoControls listed in a callable OAL IoControl code list. This list is predefined and limited to a small subset of all IoControls code supported by the OAL. This list can be extended by modifying a Dll provided as public code in public\common\oak\oalioctl folder of Windows CE 6.0. Its main purpose is to intercept all OEMIoctl calls coming from user mode before they are routed to OAL code.
So your application might generate a failure if you are trying to call one of the OAL IoControl that is not listed. In your BSP, if you want user to be able to use those IoControls, you will have to explicitly add them to the list.
For example, under Windows CE 6.0 calling IOCTL_HAL_REBOOT in your application might failed until this code is added to the list by the OEM.
The default OAL IoControl callable codes is limited to the same list that would have been callable by un-trusted applications in Windows Mobile :

- Nicolas

Monday, July 2, 2007

Welcome to a new MVP

Microsoft just awarded Fabien Decret, a friend of mine, as MVP in Windows Embedded technology... So now Adeneo count 4 awarded MVP employees.
Here is the link to his personnal blog :

Well done guy, and welcome.

- Nicolas