Res2Res Errors During CE 6.0 Makeimg

Once again we are hitting problems during makeimg with

ERROR: Res2Res: WriteResFile: xxxxxxxxxxxxx

The problem can be “fixed” by either

1.       Disabling virus scanning of the temporary directory

2.       Emptying the temporary directory

My temp dir was full of rubbish so I used option 2.  The command line below is much quicker than using Explorer

del /q /f /s %temp%\*

This worked for me.  However, if the problem persists then try option 1.  It worked for a colleague.

Hope this helps!

Debugging CE7 apps using VS2005

If you want to build apps for a CE7 system using visual studio 2005 you can (normally you’d use 2008) if you have an SDK for the Windows Embedded Compact 7 (WinCE7) platform and you follow these steps!

I was getting the following error on linking:

corelibc.lib(armsecgs.obj) : fatal error LNK1103: debugging information corrupt; recompile module

To work around this:

- Install the hot fix for VS2005 from http://support.microsoft.com/kb/949009

- Fix any build issues in the project arising from defines not available in VS2005, i.e.:

From imm.h for instance:

DWORD WINAPI ImmGetGuideLineW(HIMC, DWORD dwIndex, _Out_bytecap_(dwBufLen) LPWSTR, DWORD dwBufLen);

To

DWORD WINAPI ImmGetGuideLineW(HIMC, DWORD dwIndex, LPWSTR, DWORD dwBufLen);

Basically removing all “_Out_bytecap_(dwBufLen)” from anything that doesn’t build…

- In the top of one of my files I needed to set

#define __INLINEISEQUALGUID__

As there seem to be two defines for the same named GUID equality function and it causes a link issue.

As the meerkat would say…Simples!

Windwos Embedded Compact 7

Direct Insight was recently involved in running a Windows Embedded Compact 7 event at the UK Microsoft Campus. From which an article has been written including information and quotes from me and colleagues.

You can find the article here at http://www.mtemag.com/ArticleItem.aspx?Cont_Title=Real-Time+Operating+Systems%3a+Take+seven

Please have a read and let me know what you think.

>> Nigel

Visual Studio 2005 deploy error after downloading a managed code application to a Windows CE6 R3 device

Thanks to William White for this:-

After deploying a managed code application to a windows CE6 R3 device you get a deployment error something like:

Deploying ‘C:\will\VBProjects\CEApp\bin\Debug\HelloWorld.exe’
Deploying ‘C:\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\CompactFramework\2.0\v2.0\windowsce\diagnostics\System_SR_enu.cab’
Post-deploy error 0×00000001 returned after calling ‘\Windows\wceload.exe /noui \Windows\System_SR_enu.cab’.
========== Build: 1

Visual Studio 2005 will attempt to download the .NET CF 2.0 cab file (System_SR_enu.cab) and automatically install if the device does not already contain the run time (however the OS dependencies for the .NET CF 2.0 must be included in the WinCE6 image). It appears that the version of .NET CF 2.0 included with Visual Studio 2005 SP1 is not compatible with the R3 release of Windows CE6. To fix the problem, shutdown all instances of Visual Studio 2005 and simply download and install .NET CF2.0 SP2:

http://www.microsoft.com/downloads/en/details.aspx?familyid=AEA55F2F-07B5-4A8C-8A44-B4E1B196D5C0&displaylang=en

Try again and everything should be fine.

A successful deployment should then look something like:

DeviceApplication1 -> C:\Documents and Settings\XPMUser\My Documents\Visual Studio 2005\Projects\DeviceApplication1\DeviceApplication1\bin\Debug\DeviceApplication1.exe
—— Deploy started: Project: DeviceApplication1, Configuration: Debug Any CPU ——
Deploying ‘C:\Program Files\Microsoft.NET\SDK\CompactFramework\v2.0\windowsce\wce500\armv4i\NETCFV2.wce5.armv4i.cab’
Deploying ‘C:\Documents and Settings\XPMUser\My Documents\Visual Studio 2005\Projects\DeviceApplication1\DeviceApplication1\bin\Debug\DeviceApplication1.exe’
Deploying ‘C:\Program Files\Microsoft.NET\SDK\CompactFramework\v2.0\windowsce\diagnostics\System_SR_enu.cab’
========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==========
========== Deploy: 1 succeeded, 0 failed, 0 skipped ==========

Keeping your Smartphone alive for background processing

Want to keep your windows mobile smart phone alive, even if the user is trying to force it off?

This can be achieved by using the unattended mode, the power manager on Windows Mobile has an unattended state that will effectively look like the phone is off but the CPU will be running in the background with the LCD off. This is used for playing music, downloading emails etc. To invoice this

PowerPolicyNotify(PPN_UNATTENDEDMODE, 1);

To release this do

PowerPolicyNotify(PPN_UNATTENDEDMODE, 0);

Whist in this state you may need to poke the device to stay on by calling the above function again. If you want to wake up the device then use another power API:

// Force backlight and power on

SetSystemPowerState(NULL, POWER_STATE_ON, POWER_FORCE);

This will force the system to wake up fully if you want to display information to the user after your background processing.

Why's my Alpha blend not working!!

That was what I was saying as I do an AlphaBlend() of a 32 bit bitmap nicely saved in Photoshop, the result was a bitmap with white as the 'background' instead of a nice transparent edge.

I've seen this before and moving between Desktop and WinCE I seem to have slightly different results with Alpha blending and image factory stuff. Anyhow I found a few people mentioning that you need to pre-multiply any alpha per pixel before using the Alpha blend (which has an alpha on the image as well). Sceptical but tried it and hey presto my bitmaps now render perfectly.

Here is what I do in Win32:

HBITMAP hbmp = CreateDIBSection(hdcScreen, lpbi, DIB_RGB_COLORS, &pvImageBits, NULL, 0);

const UINT cbImage = cbStride * height;
if (FAILED(ipBitmap->CopyPixels(NULL, cbStride, cbImage, static_cast<BYTE *>(pvImageBits))))
{
// couldn't extract image; delete HBITMAP
DeleteObject(hbmp);
hbmp = NULL;
}

// Pre multiply RGB on alpha channels else alpha blit won't work!
//
if (lpbi->bmiHeader.biBitCount == 32)
{
 BYTE* linePtr = (BYTE*)pvImageBits;
 for(int y=0;y<height;y++)
 {
  BYTE* ptr = linePtr;

  for(int x=0;x<width;x++)
  {
   BYTE alpha = *(ptr+3);
   *(ptr+0)=(*(ptr+0) * alpha) / 255;
   *(ptr+1)=(*(ptr+1) * alpha) / 255;
   *(ptr+2)=(*(ptr+2) * alpha) / 255;
   ptr+=4;
  }

  linePtr += cbStride;
 }
}

Then just AlphaBlend on my bitmap...perfect, but why doesn't AlphaBlend handle the 32 bit bitmaps anyhow that's what I don't understand.... !

Adding custom notifications to the WM6.5 lock screen

If you are wondering how your application can add information on the new WM6.5 lock screen, this can be done easily by utilising a few registry entries! There are two OEM lockscreen entries reserved for OEM applications that will allow applications to register an icon to show on the lock screen with an optional number of unread or unhandled events, when the user slides this to the right or left the application is invoked to deal with the unread events.

The regsitry entry all of this appears under is:

HKLM\Software\\Microsoft\\Shell\\LockScreen\\Notifications\\Notif0

HKLM\Software\\Microsoft\\Shell\\LockScreen\\Notifications\\Notif1

Add the settings like this:

"Command Line"="\program files\myapp\myapp.exe"

"Image"="\icon_notclicked.png"

"FocusImage"="\icon_clicked.png"

"Notification Count"=dword:0

The command line should point to your application, this will be executed when the user slides your cusom slider to the right. The Image and Focus image are two icons which are shown on the lock screen with and without you pressing them. The notification count should be more than 0 to show your icon and 0 to hide your item. The number in the noticication count is displayed on the lock screen so this could be the number of unread messages or emails you've received, whatever you are counting in your application.

You should check that Notif0 and 1 aren't already used by another application and use the appropriate one.

Happy screen locking!