Hi,
I use eMbedded Visual C++ 3.0 and develop a application for Pocket PC 2002.
Now I want to debug my applikation on an iPAQ with Pocket PC 2003.
But eMbedded Visual C++ 3.0 has a problem while connecting to that device: "The Platform Manager Server failed".
What must I do to be able to debug PPC 2003?
Thanks for all solutions !!!
Have a nice day!
Franz
use evc4++
Hi,
thanks for your reply.
Is the migration from evc 3.0 to 4.0 smooth or painfull ?
don't know yet.
there are issues with having both compilers installed, I think in some cases
you have to reinstall evc3 to get it to work again.
I use eVC+3
I have no problems with eVC+3
I installed PPC2003SDK
and since this time I can debug for PPC2003 devices too, and connect via PlatformManager too.
btw: I have VS#NET installed in this same partition. Dont know if it changes anything.
Related
i need the software to run some program if anyone can send that or any links to download thanks
Hi,
The SDK for Pocket PC is actually available for free at Microsoft!
You just have to search a little for it: use "Pocket PC SDK 2002" as keywords at www.microsoft.com, or try this direct link:
http://www.microsoft.com/downloads/...4a-bd94-4167-b817-2b2e548b2e92&DisplayLang=en
The SDK for Pocket PC 2003 only includes VC++ 4.0, but the SDK for Pocket PC 2002 contains both VCC++ 3.0 and Visual Basic CE 3.0.
For VB Apps to run, you need to install the VBRUN-Runtime library on the PDA.
Be aware that embedded VB has some severe drawbacks, compared to VB6:
- you don't have the DoEvent command, so no "multitasking"
- you don't have VAR() and VAL()
- you don't have many of the controls
- it is VERY slow
More info's about it:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vbceide/htm/evbstart.asp
Cheers,
vma
VBRuntime.cab
VBRuntime.cab
Note that it is better to write your apps in Visual C++ rather than VB, as VB will not be supported on future devices...
eMbedded Visual Basic can run on WM 2003, just use the following link to download the runtime library from the following link:
http://msdn.microsoft.com/mobility/windowsmobile/downloads/evb_eula.aspx
This will allow any applications written using eVB 3 to run on your device!
Hi,
I'm very new to programming, but I will do anything to make the eten bluetooth manager function correctly (thanks to vijay to have uploaded it to us) I think this will be the ultimate ms stack upgrade..
BUT
I searched a lot, and still haven't found anything simple that simply debug those bt manager files (exe and dll)
Anyone know anything good? Usable? Practical? :lol:
Any help is welcome; I've already looked to VB6 app but is way too complex.. I only wan't to debug, nothing else (for the moment )
Cheers, MocciJ
Unfortunately the only widespread pocketpc debugger is IDA (trial version available).
If you only need to get access to resources etc, check out Resource Hacker etc. Or use the Visual Studio resource viewer.
V
I need to write an app to run on Windows CE .net 4.2. I would like to get platform builder for Windows CE .net 4.2, but it doesn't seem to be available on the microsoft site. Can someone help me find it?
It is not the .net that was 4.2, it was the version of CE. This appeared as WM 2003 and WM 2003 SE. The .NET compact framework for the machines was 1.0 or 1.1.
To test the app in an emulator use the standalone emulator. Now at version 3.0
http://www.microsoft.com/downloads/...AF-12E3-4B2F-A394-356E2C2FB114&displaylang=en
The WM 2003 SE images for it are here
http://www.microsoft.com/downloads/...b5-f2a2-47d7-a41d-825fd68ebb6c&displaylang=en
To write .net 1.0 and 1.1 WM apps you will need VS2003 PRO.
VS 2005 and VS 2008 can be forced to create .net 1.0/1.1 executable images but it's a total pain in the ...., you have to hack the build files to get it to work.
For C++ Win32, AFC or MFC you can use the free version of EVC 4.0
http://www.microsoft.com/downloads/...3D-50D1-41B2-A107-FA75AE960856&displaylang=en
Dont forget to apply SP4 to it after install. (Same page, use the link at the bottom)
Thank you very much for the help!
How about modifying the BSP or kernel, which version of tool would you use for that?
For that you will require the CE 4.2 Platform Builder package. Microsoft pull superceded versions off their site, the current version is for CE 6.0
The evaluation version works fully for six months then you have to licence it.
Search in Google for "CE Platform Builder 4.2". Some non Microsoft sites may have a copy of it, but some of these sites could also be of a rather dubious nature. i.e warez peer-to peer file sharing etc.
The documentation for it can be found here
http://msdn.microsoft.com/en-us/library/bb851528(v=MSDN.10).aspx
actually that's what the guy asked for in the first post
Hallo,
I have the question, if VB (not the sdk, only a program) could run on WM 6.5? I know there is a eMbedded runtime, to use VB, but only for the Version WM 3 ... Does anybody know, if VB program run also with these eMbedded runtime and WM 6.5?
Thanks und regards,
Flo
If the program has been written in VB .NET Compact Framework (Visual Studio 2002 onwards), then it should run on your device, without the need for a runtime, as the .NET CF is the 'runtime' for the program. All mobile devices have one version of .NET CF installed in rom on the device. Later versions can be installed. Even if the program was written for an earlier version of .NET CF than that on your device, if the device can JIT compile it successfully against the version installed then it will run. If serious differences exist between the methods used in the program's CF version and the device, then it will report that you will need a later version installing.
The moral of the story here, is keep your app as 'simple' as possible, and it increases the range of devices on which it will run.
A 'runtime' version of VB was used in Embedded Tools Version 3.0 (VB and EVC 3.0), before EVC 4.0 replaced it. It is no longer on Microsoft's website but other copies of it exist on the web if you search for it.
There is no reason why a program written in Embedded Tools 3.0 should not run on WinMo 6.5, though some of the dll 'import' definitions may be getting a bit long in the tooth. Like a lot of previous development environments, it's just been dumped at the side of the road.
ive got wince 3.0 but it goin to expirer and a friend on here gave me wince the portable one, but cant get it to work with my win7 64bit even after changin to run in winxp service pack3 and run as admin. if anybody could help me find one u can pm me thanks..
LiquidXed said:
ive got wince 3.0 but it goin to expirer and a friend on here gave me wince the portable one, but cant get it to work with my win7 64bit even after changin to run in winxp service pack3 and run as admin. if anybody could help me find one u can pm me thanks..
Click to expand...
Click to collapse
Try QuickCab v2.0 free!
I initially also used QuickCab but since it lacked some features (for one the ability to use a custom setup.dll was removed in version 2.0) and IABovine apparently stopped development I searched for alternatives:
Pocket PC Setup Creator - free for non commercial usage
Phone Setup Creator - not as much featured but author seems open to suggestions
Extendir Cabs - a cabarc GUI made for creating cabs for extendir
MSCEInf - excelent cab setup extractor (it preserves the file names and setup structure)
There's however no free cab setup "editor" that I know other than WinCe Cab Manager...
PS: QuickCab version 1.0 is not in the original thread so I attached it bellow.
thanks man, ive got a hex edited version of wince 3.0. does that Pocket pc creator have an expire. ?
No expiration date, nag screens or anything else... You get the complete version (almost since you can't use a custom setup.dll) not just a trial.