Mahesh's Blog

Mahesh's profileMahesh's BlogPhotosBlogLists

Blog list


Mikehall's Embedded WEblog Get cool stuff on Windows CE & Windows XP Embedded

Blog

Windows Embedded CE 6.0 R2　製品発表

11月16日（金）、パシフィコ横浜に行われるEmbedded Technology（ET) ２００７展示会でWindows Embedded CE 6.0 R2のラウンチイベントが開催されます。

Windows Embedded CE 6.0 R2 はさらに魅力的な技術を装備していますので、より容易に Windows Vista, Windows Server 2008 や他の組み込み機器との接続が簡単にできるようになります。

お早めに、WINDOWS EMBEDDED CE 6.0 R2 ラウンチイベント　にてご登録ください。

10/30/2007 1:41 PM | Add a comment | Read comments (3) | Permalink | Blog it

Microsoft Mobile & Embedded DevCon 2007

Heading for Microsoft Mobile & Embedded DevCon 2007.

Looking for great technical stuff on Windows Embedded.

Catch this

http://www.microsoft.com/japan/windowsmobile/medc2007

6/4/2007 9:21 AM | Add a comment | Permalink | Blog it

はじめてのWindows CE...　日本語での書籍！

Windows CEを学びたい...　Windows CEをもっと知りたい...　Windows CEでこんなことできますか...　

お答えは...　「はじめてのWindows CE」　

OSの設計からアプリケーション開発までということで、大川善邦　氏の　「はじめてWindows CE」をお勧めします。

詳細は下記リンクを御覧ください。

http://www.kohgakusha.co.jp/books/detail/978-4-7775-1262-1

以上。

Internationalization : Replace the default Windows CE fonts with other fonts!

For some platforms or applications, you may need to be able to replace the default Windows CE fonts with other fonts, including custom fonts. This is required especially when you are trying to support specific language fonts. You can modify the Windows CE registry to replace default fonts, to replace fonts used on a platform, and to replace raster fonts with TrueType fonts.

Windows CE uses a default set of fonts that exist in ROM. You can replace these fonts by modifying the Windows CE registry. The replacement font must exist in the \Windows directory on the target device.

The following table shows the locations of the fonts that you can replace through the Windows CE registry.

Font location             Registry key
System                    HKEY_LOCAL_MACHINE\SYSTEM\GDI\SysFnt
Menu bar                  HKEY_LOCAL_MACHINE\SYSTEM\GWE\Menu\BarFnt
Pop-up menu               HKEY_LOCAL_MACHINE\SYSTEM\GWE\Menu\PopFnt
Out of Memory window      HKEY_LOCAL_MACHINE\SYSTEM\GWE\OOMFnt

To change a font in the Windows CE registry
1. Modify your Project.reg project registry file by adding the registry keys listed in
the preceding table for the fonts you want to replace.

2. Under each registry key, add the following variables and values:
       "Nm"=font-name
       "Ht"=DWORD:height
       "It"=DWORD:italics-flag
       "Wt"=DWORD:weight
       "CS"=DWORD:character-set

The following table describes each of these variables.
Variable Description
font-name Font name, not including the extension.

For example, to load the Arial font, Arial.ttf, use the following value for the font-name variable:
"Nm"=Arial

   height             Font height, in pixels.
   italics-flag       Set to 1 for italics; 0 for no italics.
   weight            Font weight, which can be one of the FW_* values.
   character-set Defines the character set, which can be one of the *_CHARSET values.

3. Rebuild your image.

How to connect Windows CE device to Visual Studio Remote Tools without ActiveSync!!!

When ActiveSync is not available, Visual Studio 2005 does not automatically copy required connectivity files to the device. Use the following steps to install these files on the device, modify the Visual Studio connection configuration, and establish device security.

The first two steps, preparing the device and Visual Studio, need to be done only once. The last set of steps, setting security and establishing the connection, must be repeated any time you want to connect from a new instance of Visual Studio.

To prepare the device for connecting

Using whatever connection with the device you have, copy the following files to the \Windows\ folder on the device. These files are located on the development computer by default at \Program Files\Common Files\Microsoft Shared\CoreCon\1.0\Target\wce400\<CPU>.
- Clientshutdown.exe
- ConmanClient2.exe
- CMaccept.exe
- eDbgTL.dll
- TcpConnectionA.dll
From the command prompt on the device, run conmanclient2.exe.
Determine the IP address of the device.

To prepare Visual Studio for connecting

On the Visual Studio Tools menu, click Options, then click Device Tools, and then click Devices.
Select Windows CE Device, and then click Properties.
To the right of the Transport box, click Configure.
In the Configure TCP/IP Transport dialog box, select Use specific IP address, and then type the device IP address.
Close the dialog boxes.

A message box might appear prompting you to reset your device. If so, a soft reset is sufficient.

To set security and establish the connection

At the command prompt on the device, run cMaccept.exe.

Within three minutes, connect to the device.

If you establish your first connection within three minutes, you can continue deploying and debugging indefinitely as long as you are using the same Visual Studio instance. If you need to connect from another instance of Visual Studio, you need to perform these security steps again.

*** Security Note
You can eliminate the cMaccept step by disabling security on the device. To do so, use the Remote Registry Editor to set `HLKM\System\CoreConOverrideSecurity = 1` DWORD value. Disabling security exposes your device to malicious attack and is not recommended unless you have provided appropriate safeguards.

View more entries

Book list


Programming Microsoft® Windows® CE .NET, Third Edition by Douglas Boling

Windows Mobile 5.0 アプリケーション開発 Beginner's Book (大型本) by 高橋忍　氏

はじめてのWindows CE by 大川善邦　氏

Categories