EVC++ 4.0, SP4, two SDKs - Tool commands lost on platform switch

windows ce


  • 1. evc3.0-evc4.0 compatibillity
    Hello I want to develop program to the PPC and i need to decide whether to use the EVC 3.0 or the EVC 4.0, i want to create the project in one of this environments and then i want to compaile the project in the other environment in purpose to support PPC 2002 (Win CE 3.0) & PPC 2003 (Win CE 4.0 /4.1 /4.2) My question is as follows 1. Is it better to start working on EVC 3.0 and then compaile the code on the EVC 4.0 or the opposite and why??? 2. Is there a big diffrence between the SDK's of the EVC3.0 and of the EVC4.0?? and what about the operating system API Thank Ronen G.
  • 2. fundamental for CHAR, Tchar._wchar
    Hi again, I've been using char* for character string. For certain Methods we've been converting those char* to tchar * cos those methods were taking parameter as _wchar or tchar. I generaly used wcstombs() method to do so. Can some one thro the light on the basics of char , tchar and _wchar and unicode stuff. -Jim
  • 3. PC Card Driver "re-loaded" after CE_REGISTRATION_COMPLETE
    Hi all First of all, I have a PC Card client driver written already for my hardware. the driver works very well with PocketPC 2002 and PocketPC 2003. It works well with my conclusion until I got a HP iPAQ H2210, 5550 and 5555 It seems that, first 1. I crashed in CardRequestWindow. It returned 0x21, "bad handle". The handle I passed was got from CardRegisterClient without any error 2. Well, to try everything possible, I put something like EnterCriticalSection before CardRegisterClient and LeaveCriticalSection afterward. Amazingly, it works but stranger things happened 3. In my callback function, I have a CreateProcess statement to open my another application. The application does open and attempt to OpenFile for my driver but allways failed 4. The most terrible thing is that, before I attempt to do anything I find that the driver is started over again!!! It crashed again at CardRequestWindow with error 0x21 "bad handle". It seems that I dunno why but my XXX_Init is run again Well, to put my driver simple, I put all the essential CardServ function (CardRegisterClient, CardGetParsedTuple, CardRequestWindow, CardMapWindow, CardRequestInterrupt and CardRequestConfiguarion) in a single function For PocketPC 2003, I have tried Dell Axim 5 (Pocket PC 2003 version) for example. It works without any problems I am much appreciated if anybody could give me some hint or suggestion. Thanks very much
  • 4. usb floppy drive
    Hi all, Looking for a compatible usb floppy drive for the Itona Windows CE.net thin client box. Anyone have any suggetions. Thanks, birwin

EVC++ 4.0, SP4, two SDKs - Tool commands lost on platform switch

Postby Charlie » Fri, 18 May 2007 06:05:10 GMT

I'm targeting multiple platforms, same CPU using a common code base.
Target 1 is a WinCE 4.1 build, target 2 is a 5.0 build.  Obviously,
each has their own SDK.  I have the project configurations established
to build each target and place it in a specific target directory.  All
is well ... sort of...

I noticed that when I switched SDKs, eVC++ had the wrong directories
for the tools under the Tools... menu.  So, I corrected the
directories.  However, when I change the SDK, I lose my corrected

What is the magic for getting eVC++ to retain the Tool settings?

Re: EVC++ 4.0, SP4, two SDKs - Tool commands lost on platform switch

Postby r_z_aret » Sat, 19 May 2007 04:46:20 GMT

I assume you mean eVC 4, not eVC 3.

I'm not sure what you mean by "Tools...menu", so I'll try both
possibilities I know about.

Tools->Options->Directories displays a list box below 3 drop-down
boxes. The left-most drop-down selects Platform (SDK). The middle
drop-down selects CPU. The right-most drop down selects type of
directory (e.g., executable). When I choose "Include files" or
"Library files" in the right-most drop-down, I see a different list of
directories in the listbox for each combination of the other
drop-downs. I don't see any changes when I choose "Executable files",
but I haven't had problems with executables. I choose added a
directory to one list, and it did not show up on the others.

Tools->Customize->Tools shows a dialog that controls the tools
available in the Tools menu. I don't see any way to vary paths
directly as the Platform (SDK) changes. However, if a command includes
only the executable (rather than full path), I'm pretty sure Windows
will search the list of directories in
Tools->Options->Directories->Executable Files, which can vary with

Sometimes I shut down eVC to make sure it remembers settings.
Especially when I'm likely to have multiple copies running (to work on
interactive projects such as my library and any app that uses it).

To reply to me, remove the underscores (_) from my email address (and please indicate which newsgroup and message).

Robert E. Zaret, eMVP
PenFact, Inc.
20 Park Plaza, Suite 478
Boston, MA 02116

Re: EVC++ 4.0, SP4, two SDKs - Tool commands lost on platform switch

Postby Charlie » Sat, 19 May 2007 09:06:07 GMT


  Yes, eVC 4.  And the menu I'm referring to is the second you list.
If I actually enter this dialog and then cancel, it warns me that the
directories are wrong.  For each and every command.... Weird

Re: EVC++ 4.0, SP4, two SDKs - Tool commands lost on platform switch

Postby r_z_aret » Sun, 20 May 2007 03:29:09 GMT

Do you have a second copy of eVC open when that happens, and does that
second copy show a different set of directories? When I make a change
to Tools->Options->Directories in one open copy, I find that just
opening the same dialog in a second copy will duplicate the changes
(sorry, not as well described as I would like).

To reply to me, remove the underscores (_) from my email address (and please indicate which newsgroup and message).

Robert E. Zaret, eMVP
PenFact, Inc.
20 Park Plaza, Suite 478
Boston, MA 02116

Similar Threads:

1.Remote tools of eVC 4.0 SP4 not working with platform 4.2

2.PPC 2002 Platform SDK for eVC 4.0 ???

Pocket PC 2002 SDK is only for eVC3

Andrey Yatsyk [Windows Embedded MVP]

"Nick" < XXXX@XXXXX.COM > wrote in message 
news: XXXX@XXXXX.COM ...
> Is there a PPC Platform 2002 SDK for eVC 4.0 ? I found it for PPC 2003 but
> not for PPC 2002?
> Thanks a lot,
> Nick 

3.Howto debug on custom ARM device - EVC++ 4.0 SP4, Standard SDK

The purpose of the Standard SDK is to deliver device agnostic headers and 
libs so that users can create applications in EVC that conform to the 
Standard SDK set of APIs. Microsoft provides one default device which is 
the emulator for the Standard SDK.

The device-agnostic design depends on a device manufacturer providing a 
real device SDK. If a PB generated SDK is "Standard SDK" compatible 
(because the Standard SDK feature is included in the OS design) then upon 
installation EVC will generate a new "shadow SDK" that has the headers & 
libs from the Standard SDK and has the device settings of the device SDK. 
This is in addition to the device SDK you just installed. 

As Steve mentioned above, you need to go back into your PB workspace and 
generate and SDK for your platform and install it on the machine that has 

Make sure that you have the Standard SDK feature in you OS design if you 
which to use the Standard SDK Shadow mechanism described above. If not, you 
will still be able to build using the headers and libs provided by your 
platform. Go to the "Platform\Configure SDK..." and set your SDK settings. 
When you configure your SDK please be sure to select ActiveSync from the 
transports and startupserver tab when you configure the SDK from the SDK. 
This will give you default device for your SDK that has ActiveSync 
available. You can even select which transport & startupservers are the 
defaults for you SDK. Now you can go to ""Platform\Configure SDK..." and 
generate and MSI file that can be installed on the machine that has EVC. 
You'll need to restart EVC to see the new SDK.

EVC uses Platform Manager for connectivity services to the device. It will 
"complain" if the SDK's Platform ID is different from the device's ID, but 
this should be a warning. If you build an SDK from the PB workspace that 
your device's OS image was built from, you shouldn't see this.

Gabriel Spil
IDE Dev Lead
Microsoft Corp

Return to windows ce


Who is online

Users browsing this forum: No registered users and 30 guest