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.

Activesync 4 Problem...

Can someone help me?
I was using Activesync 3.8 with no problem. But recently I installed Activesync 4.0 and I can no longer sync my Mini with my PC...
I even tried uninstalling 4 and reinstall 3.8 but it got worst. The Activesync software won't even run...
Anyone can help?

having exactly the same problem. Cant connect my S100 (jam) or Smartphone c500. This is after I loaded AS4 then removed the software and re-installed AS3.8. Nothing connects anymore. Infact, you can't even get into
AS3.8 now! might try AS3.7.1. Any ideas any1?

This was a know issue with the early beta release of 4.0. Have you tried the official release from a few days ago?

I thought I did download the official release, however, I cant find it now. So are you saying the old beta release stopped you going back to AS3.8?
by the way tried AS3.7.1 and nothing.
I hate microsoft!

Official release? And where would that be available? So far 3.8 is the latest version I can find for download at www.microsoft.com/windowsmobile.

I tried the 4.0 beta and it wouldn't let me use AvantGo so I tried to revert, but I had to reinstall Windows before I could solve it. 4.0 beta is a big no-no.. Wait a week or something and it will come a 4.0 final.

Cleanup folder programfile AS
after install as4 need
Cleanup folder programfiles AS
Install AS3.8

Re: Cleanup folder programfile AS
terilly said:
after install as4 need
Cleanup folder programfiles AS
Install AS3.8
Click to expand...
Click to collapse
Terilly, what exactly do you mean by cleaning up program files?

Re: Cleanup folder programfile AS
bolasz said:
Terilly, what exactly do you mean by cleaning up program files?
Click to expand...
Click to collapse
delete directory C:\Program files\Microsoft ActiveSync

Re: Cleanup folder programfile AS
[quote="some0NE]
delete directory C:\Program files\Microsoft ActiveSync [/quote]
I've done that (well, sort of, I didn't delete the whole directoy, only the the files and the drivers directory in it and kept the folders for the installed programs) and it didn't work out, AS 3.8 still wouldn't open or set up a partnership.

I am assuming most guys are using XP, if that is the case, you could also delete the application data files
c:\ -> docs and settings-> [user profile] -> application data -> microsoft -> active sync -> profiles
you can delete the profiles folder or the entire active sync folder, and if you cannot see the application data folders, you will need to show the hidden files tools -> view -> show hidden files
Hope that helps
rgds
jim

Active Sync 4.0
bamse said:
Official release? And where would that be available? So far 3.8 is the latest version I can find for download at www.microsoft.com/windowsmobile.
Click to expand...
Click to collapse
I am assuming they mean the official developer preview version which can be found here:
http://msdn.microsoft.com/mobility/windowsmobile/downloads/default.aspx

Let me clarify on Active Sync 4. Active Sync 4 final is not out yet. What is out is Developer preview version (ActiveSync4.0 Build 4343 to be exact)
This version has lot of quirks. Unless you are using Microsoft® Windows Mobile Version 5.0 it is not advisible to shift to it yet.
As of now ActiveSync 4.0 is compatible with the following operating systems and applications and nothing else:
• Microsoft® Windows® 2000 Service Pack 4
• Microsoft® Windows® Server 2003 Service Pack 1
• Microsoft® Windows® Server 2003 IA64 Edition Service Pack 1
• Microsoft® Windows® Server 2003 x64 Edition Service Pack 1
• Microsoft® Windows® XP Professional Service Packs 1 and 2
• Microsoft® Windows® XP Home Service Packs 1 and 2
• Microsoft® Windows® XP Tablet PC Edition 2005
• Microsoft® Windows® XP Media Center Edition 2005
• Microsoft® Windows® XP Professional x64 Edition
• Microsoft® Outlook® 98, Microsoft® Outlook® 2000 and Microsoft® Outlook® XP, and Microsoft® Outlook® 2003 messaging and collaboration clients
• Microsoft® Office 97, excluding Outlook
• Microsoft® Office 2000
• Microsoft® Office XP
• Microsoft® Office 2003
• Microsoft® Internet Explorer 4.01 or later (required)
• Microsoft® Systems Management Server 2.0
The following mobile device operating systems are supported by ActiveSync 4.0:
• Microsoft® Windows Mobile Version 5.0
• Microsoft® Windows Mobile 2003 Second Edition
• Microsoft® Windows Mobile 2003
• Microsoft® Pocket PC 2002, Microsoft® Windows CE OS version 3.0
• Microsoft® Smartphone 2002, Microsoft® Windows CE OS version 3.0
Known Problems which you can encounter with active sync 4.0 are
• ActiveSync 4.0 does not support remote synchronization.
• ActiveSync 4.0 does not support Backup/Restore of mobile device data.
In order for ActiveSync 4.0 to properly display extended characters in some languages, you might need to change the language that is used for non-Unicode programs.
To change the language that is used for non-Unicode programs, perform the following procedure.
1. From the desktop Start menu, select Settings, select Control Panel, and then select Regional and Language Options.
2. In the Regional and Language Options dialog window, select the Advanced tab.
3. Choose from the available languages in the Language for non-Unicode programs list, which determines the language that ActiveSync 4.0 uses.
When a device is connected to a PC over an USB connection that goes through an external USB hub, you might experience connection instabilities such as drops in the connection, or an unresponsive desktop PC. For more information about this issue, see article 817900, "USB port may stop working after removing or inserting USB device" in the Microsoft Knowledge Base at http://support.microsoft.com.
To successfully uninstall ActiveSync 4.0 and reinstall a previous version of ActiveSync on your desktop PC, perform the following procedure.
1. Uninstall ActiveSync 4.0.
2. Open File Explorer, navigate to the System32 directory in your Windows directory, and then manually delete the dynamic-link library Rapi.dll.
3. Reinstall the previous version of ActiveSync.
Other Problems
• If the desktop PC operating system is upgraded, or a Service Pack is installed, you must perform a repair installation of ActiveSync in order to enable the expected ActiveSync functionality.
• If the Windows Media Player application is upgraded to Windows Media Player 10 after you have installed ActiveSync on your desktop PC, you must perform a repair installation of ActiveSync. This enables successful Media Synchronization to a Windows Mobile-based device.
• If the desktop PC operating system is Windows XP SP1, EHCI USB 2.0 host controllers might cause unexpected drops in the USB connection between the PC and a device.
For information about successfully resolving this issue, see article 822603, "Availability of the Windows XP SP1 USB 1.1 and 2.0 Update" in the Microsoft Knowledge Base at http://support.microsoft.com.
• Multiple simultaneously running user sessions on a desktop PC that is running ActiveSync are not supported.
• If non-Microsoft firewall software is installed and running on your desktop PC, you might need to configure the software to allow the following ports in order for ActiveSync to function: 5678, 5679, 990, 26675, and 5721.
• Sometimes antivirus software that is installed on your desktop PC can conflict with ActiveSync functionality.
• In rare cases, some LAN configuration tools might also conflict with an ActiveSync connection. To enable your Windows Mobile-based device to successfully synchronize with your desktop PC, you might need to disable the LAN configuration tools.
In most of the time it is outlook which is going to cause problem if it is not the default e-mail client. If you get error in synchronising then go to outlook help menu and choose detect and repair followed by reboot which should solve the problem

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

Run PocketPC 2003 application in PocketPC 2002

I have developed an application that runs on PocketPC 2003 (in Visual Studio 2003). When I try to run it on PocketPC 2002, I am getting error:
Unsupported System Version:
The Program is not compatible with the current operating system and, therefore, may not run on this device. Do you want to continue installation? [Yes] [No]
If Click on [Yes] button, installation is done, but while running that application I got following error.
SampleApp.exe
Cannot find ‘SampleApp’ (or one of its components). Make sure the path and filename are correct and all the required libraries are available.