Database Users

Embedded Visual C++ Version 3.0

Hi,
I've been using emBedded visual C++ for 2-3 years writing application for pocket PC ( Mainly Ipaq'a).
I've recentrly invested in a Xda but when I attempt to "update my remote output file" from with embedded VC ++" i get the following error:
" Microsoft Active sync connection server failed, Please make sure active sync is running and retry the download etc.."
Of course Activate sync is running, and running correctly, Has anyone had this issue before ?
I can manually copy my executable to my device and run it,but then I can't debug. I'm in the process of download VC 4.0 and going to try that, but really wold like to runing in under the 3.0 version.
Any comments would be appreicated.

Bad news dude, eVC++ works only with PocketPC 2000 + 2002. The development environment you'll need to develop on 2003+ is either eVC++ 4.0 or Microsoft Visual Studio.NET.

Thanks for the update,
I've installed Embedded VC 4.0 and the SP3, Now I can download to my XDA which is great.
Now I want to maintain backwards compatiable and download to my ipaqs in 2002, I can't change the actiive configuration to PPC2002
Is there a way to compile my application for both 2002 and 2003 using VC 4.0 or do I need to maintain both IDE's

Sorry but there's no way to maintain both 2K2 and 2K3 targets from eVC 4. You can have the same set of source code but eVC 3 + 4 have different project file types. Have a project per IDE containing the same source code. Just remember when you add files to the project you're working on, remember to add the files to the other platform's project as well.
Happy coding!
-Timbo.

RTCDLL.DLL on the HTC Universal?

Could anyone of you who's so lucky to already own an HTC Universal please post if the ROM of this device contains a file called RTCDLL.DLL?
If anywhere, it's probably located in the \Windows folder (or one of its subfolders).
This file is a library that can be used by developers who want to create real-time communication applications. It is part of the Windows CE 5 operating system, but no all Windows Mobile devices include it on their machines.
I would like to make use of this library to write a SIP-based videophone application for the HTC Universal.

Hm...couldn't find it..sorry

I've found that file for you. It's part of the "Windows Real-Time Communications Client API SDK 1.3" wich can be found here: http://www.microsoft.com/downloads/...15-FD1C-4BF7-A505-3F8FAF1E120A&displaylang=en
Hope it helps
Eric

Eric,
That SDK contains the Windows XP version of the DLL.
What I'm trying to find out here is whether the ROM of the HTC Universal contains the Windows Mobile version of the RTCDLL.DLL which can be used to create SIP compatible realtime communication apps for Windows Mobile devices.

I'm sorry it was the wrong one. Have you also looked at the Windows Mobile 5.0 Pocket PC SDK? There is some support for the .dll in Windows CE 4.3. One other source could be www.opennetcf.org
Eric

.NET CF v2 installation

I've tried to install .NET CF v2 on my Qtek 9000. (NETCFSetupv2.msi) . It gives me "Application manager cannot install this application on your mobile device due to an invalid setup file. Reinstall and try again". Did anybody manage to install .NET CF v2 ?

I had real troubles with this! I asked a friedn at Microsoft and his advice was to check that ANY .NET files that had been installed were DELETED before trying again. When an install fails on this it leaves asome bits hanging around and then the next try fails!
I cleaned any .NET stuff off, installed again and WOOHOO it worked!

It doesn't works. I found the damn thing (netcfagl1_0.dll) in the Windows folder. I was able only to see it (could not copy or move it, (even tried to change properties with Total Commander CE)). The file still remains "protected". Strangely I can't see it with "Explore PocketPC" from ActiveSync even with "Show hidden files and folders" and with "Hide protected operating system files" unselected.

YOOHOO!! I did it!
I found an article and bang! http://pluralsight.com/blogs/jimw/archive/2005/10/12/15504.aspx
I’ve wanted to get this post out for a couple of weeks but I guess better late then never.
A lot of you may have heard of the great Pocket PC device offer that was announced at PDC. At the event, Microsoft was subsidizing the sale of a limited number of iMate Jasjar Pocket PC Phone Edition devices at a remarkably discounted price of US$149. This price represents a more then 85% discount off of the list price of US$1,180.
The iMate Jasjar is quite cool because it has a high-resolution display (640 x 480) that can be viewed in both landscape and portrait. It also has a QWERTY keyboard, WiFi, Bluetooth, GPRS phone, 520MHz processor and has two, count ‘em, two cameras. And what makes it especially cool is that runs Windows Mobile 5.0 so it supports all of the latest Windows Mobile 5.0 managed APIs. Basically it’s a pretty cool device offering all the latest and greatest features. (see pictures)
Since PDC is a developer event, many of the folks who were lucky enough to successfully purchase one of the Jasjar devices wanted to try using Visual Studio 2005 to build a .NET CF 2.0 app and run it on their new device. For the people who didn’t have device experience, successfully building their first WM 5.0/.NET CF 2.0 app required a little more housekeeping to get started then they realized.
What I’d like to go over in this post is two of the more common issues I saw people encounter in trying to build their first .NET CF 2.0/Windows Mobile 5.0 application and run it on a real device.
Visual Studio 2005 doesn’t support Windows Mobile 5.0 out of the box.
As bizarre as this may sound its true. When you install Visual Studio 2005 it automatically installs .NET CF 2.0 along with the Pocket PC 2003 SE and Smartphone 2003 SE SDKs. It does not install the Windows Mobile 5.0 SDK. As a result you can’t build applications that take advantage of the Windows Mobile 5.0 APIs. To do so requires that you download and install the Windows Mobile 5.0 SDK for Pocket PC and/or the Windows Mobile 5.0 SDK for Smartphone. Once those SDKs are installed you can build Windows Mobile 5.0 projects that can access the Windows Mobile 5.0 managed libraries. If you install both of the 5.0 SDKs you’ll also add about 10 more emulators representing the various Windows Mobile 5.0 device form factors.
The absence of Windows Mobile 5.0 from Visual Studio 2005 isn’t a pre-release issue. Last I heard, it’s very unlikely that that the Windows Mobile 5.0 SDKs will be included in the RTM version of Visual Studio 2005 either. I’ve never heard an official reason for why the SDKs aren’t included but the prevailing theory is their size. Apparently the combined size of the two SDKs is large enough that if included, the Visual Studio 2005 install would no longer fit on a single DVD which would of course significantly complicate the production and distribution. Again just a theory, but if its true leaving the 5.0 SDKs as separate downloads does make sense.
Running a .NET CF 2.0 application on a WM 5.0 device, throws an exception indicating that a newer version of .NET CF is required.
There are actually two issues at work here. First, Windows Mobile 5.0 devices ship with .NET CF 1.0 SP3 installed in ROM, not .NET CF 2.0 therefore before a .NET CF 2.0 app can be launched .NET CF 2.0 must be installed. When Visual Studio 2005 would push the .NET CF 2.0 CAB file down to the device and attempt to initiate the CAB install onto the device, the installation of .NET CF 2.0 fails because of the new WM 5.0 security model.
As many of you probably know, one of the big changes in Pocket PC 5.0 was the addition of the one-tier security model (as opposed to the two-tier model on Smartphone 5.0). One of the features of the new security model is that remote actions performed on the device by the desktop can be restricted. In the case of the Beta 2 or pre-September CTP versions of .NET CF 2.0, the CAB file is signed by a test certificate that is not recognized by the Pocket PC 5.0 device. As a result,the remote installation fails.
The best way to eliminate this problem is to upgrade your Visual Studio 2005 installation to either RC1 or to a September or later CTP. In these newer versions of Visual Studio 2005, the .NET CF 2.0 CAB file is signed by a properly trusted cert and therefore installs fine. If you don’t have access to a newer version of Visual Studio 2005 you can still get around the installation problem by using either the Mobile Device folder on My Computer or the ActiveSync Explore feature to manually copy the .NET CF 2.0 CAB file1 down to the device. Once you’ve copied the CAB file down to the Pocket PC you can then use the File Explorer on the Pocket PC to launch the CAB file manually by just tapping on the file name. Now the CAB is still signed by an unknown cert but because you’re launching the installation interactively you are simply prompted with a warning indicating that the signer is unknown and then asked if it is OK to proceed. Simply select “Yes” and the CAB is installed as normal. Your .NET CF 2.0 app will now run fine.
Wow – there was still a bunch more stuff I wanted to talk about but this is already longer then I meant for it to be - Check out the pics of the Jasjar below if you haven't already.
1C:\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\CompactFramework\2.0\WindowsCE\wce500\armv4i\NETCFv2.wm.armv4i.cab
Click to expand...
Click to collapse

Update of JVM on Qtek S200

I have a Qtek S200 with:
Microsoft Windows Mobile 5.0 OS 5.1.195 (Build 14928.2.2.0).
and
intent Java MIDlet Manager Runtime MIDP 2.0: v10.1.7.545 (Build 20051117)
I want to develop a MIDlet which needs file access and/or camera access. I know that device needs the optional packages (JSR-75 PDA-API and JSR-135 Mobile Media API) to accomplish that. And it seems that these optional packages are not supported by the MIDlet Manager.
I have tested this MIDlet already on a smartphone (Nokia N73). The Java Micro Edition of this Phone supports several Optional Packages. It can not be possible that a PDA provides less functionalities than a Smartphone.
1. Is it possible to upgrate the JVM (MIDlet Manager) on the device? So that I can use these optional packages.
2. Does anybody know which MIDlet Manager supports these functionalities?

I have found a newer version of the intent Java MIDlet Manager
Runtime JTWI 1.0: v11.1.7.1023 (Build 20060907)
This version provides the optional package JSR-75 which is needed for file access.
I found a download here: http://wronek.wikidot.com/java-wm
But this version does not provide the Multi Media API JSR-135 which is needed to use the devices build in camera.
So if anyone knows an other MIDlet Manager please reply.

I've found an other MIDlet Environment which supports file access (JSR-75).
It is the IBM J9. The installation of this Environment is a bit tricky but the GUI of this MIDlet Environment is more beautiful than that of the intent Java midlet manager.
Here you can find a good installation discription:
http://www.markus.brosch.net/?p=111

Problems deploying apps in MS Studio 2005

I have QTek 9100, running CE OS 5.2.1413 (Build 17913.0.3.0) NBD v7.4.
I have problems when I build an application under my MS Studio 2005 SP1, I try to deploy the image to my device and I get an error saying that my device's security configuration prevents MS Studio from connecting to it and deploy fails.
I turned my device's security off with the tool provided by MS, still nothing could be deployed. Also, I've uploaded the developers certificates provided by MS, still no sucess.
I bought the device originally with Windows Mobile 5, then deployment and everything else was OK. But now I don't want to revert back to 5 version because I like this build I have so much.
Pls, help how to get around this error.
Thanks