What additional software does one have to load to enable JSR-82 (Java bluetooth) dependant midlets to run? I have already updated my TOA midlet manager to the latest version 1036, but it seems some WM5 functionality is still missing. Are there modified DLL's or additional JAR files required that will provide this?
Related
Hello all,
Attached is a simple CAB file that should have set the PIE user-agent stuff to be identifying the thing as IE6. I think there may be others around, I know I've seen it in a larger cab, so don't worry about this specific function. My question is regarding the fact that when I try to run it on my HTC Wizard (running WM5), I get "Installation of PIE_as_IE6.cab was unsuccessful".
I built the CAB off of the "CAB Template.cab" from http://forum.xda-developers.com/viewtopic.php?p=113615#113615 - just in case I'd run into that version issue with WM5.
Any thoughts out there on what's wrong with the CAB? Or is there a different reason it won't install?
Hi, what CSP are you using to change those settings and how are you deploying it to the device? Chances are access to that provider is restricted to a higher security role than what the cab file has permissions to do. RAPI still has access to most service providers by default but if you're downloading the cab over the air to the device it'll probably need to be signed with a suitable certificate before it's allowed to make setting changes. Mobile 5.0 security has been beefed up and its now a bit of a mission to do what was reasonable simple to do on 2003. All cpf files need to be signed if not deployed over RAPI as well, for even something trivial like adding a browser favourite.
editor is OCP Software's WinCe Cab Manager (version: 1.1)
deploy method is copy over USB cable by ActiveSync through Total Commander+WinCe Device access plugin. Execution of CAB is on the device itself through Total Commander CE or Explorer.
No CSP in use (err.. afaik).
You may be right that the part of the registry in question may simply be unavailable to access without special signing. I'll have to dig for those keywords a bit.
Yeah...the more I research Mobile 5.0 security the steeper it gets. It seems security permissions extend all the way to file IO access. Writing certain recognized system files (like theme files) without adequit permissions effectively renders those files as untrusted and they stop behaving in their expected manner. Its a pain.
is there a namespace to get the list of progams currently running on the smartphone ????
and if there isn't what dll should i interop to do that ?!!!
thanks!!!
ToolHelp Reference
If you just want to do it once, use the remote tools that come with Embedded C++ or Visual Studio. If you want to get it within your program, see the ToolHelp Reference. (search for toolhelp at microsoft.com) You'll find such functions as:
CreateToolhelp32Snapshot
Process32First
Process32Next
Since you asked for the dll, toolhelp uses toolhelp.dll
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
Hi guys. I've been playin around with Visual Studio 2008, making a project for SmartDevices and my X1 using Visual Basic. I run the application in the built-in WM6Pro emulator provided, and it works fine. But when I make a CAB out of it, and try to install on device, it is unsuccessfull. When I compile it as EXE and run on device, it starts. But as soon as I try to click something within the program I get an error message saying "Cannot find file 'Micrsoft Visualbasic Resources" or something. I'm guessing I need to tell the application what dll's to reference..? But how? Anyone got a moment to explain? Thanks in advance,
//Fred
What .net compact framework version is your application targeted at?
I assume where you were working with the emulator, you were doing debugging/deployment inside visual studio? When you are doing this visual studio will automatically deploy the required files such as .net compact framework 3.5 I think.
Since if you are using .net compact framework 3.5, then you will need that installed for you X1, since WM6 naively only includes .net CF 2.
Give that a try and let us know about your results?
I have used 3.5 when emulating in VS. I have 3.5 installed on my device.
When you are testing your application out in the emulator, have you ever tried installing it with the same cab files?
And what is the result? (make sure when you install the cab file, that the directory is not the same as the 1 you have been deploying when debugging, otherwise if they are the same clean up the folder first)
It the cab file doesn't work when it is being installed on the emulator, then at least we can isolate the problem to the actual configuration on your X1 rather than the cab file.
I assumed you used the Smart Device CAB Project template in visual studio?
If that is the case you might have not configured the settings properly yet.
Hi,
I extracted several executables (EXEs and DLLs) from the firmware image of a WinCE6 device.
In addition to that, I also build my own WinCE6 image with VS2005 that is running in the Device Emulator.
Now, what I'm planning to do is copy some of the extracted executable files to my emulator image and run them there.
For instance, it already worked to copy the "zlib.dll" to the emulated image and then load it with some customly written code.
However, this only works for a few DLLs. Most of them just crash.
I believe this is because of the memory mapping.
As you might know, WinCE6 has its own address space for shared libraries.
Typically they are loaded to the 0x40000000 region whereas libraries that are not shared are loaded to the address space of the application itself (i.e. 0x100000000 region).
While the DLLs from my own image mostly map to the 0x100000000 region, most of the extracted DLLs are loaded to the shared memory region which seems to cause problems.
Initially, the extracted zlib.dll did not work in the emulator image either.
However, increasing the RAM size of the emulator image did the trick.
Yet, the emulator supports at most 256MB of RAM. So further increasing the RAM size for DLLs that do not work yet is not an option.
Did anyone else try to run extracted binaries in an emulator environment ?
My ultimate goal is to run these extracted executables inside my emulated environment, so that I can debug and reverse engineer the code.
Is it possible to change the memory mapping of a DLL so that, instead of being loaded to the 0x40000000 shared region, it is loaded to the process space ?
There is a nifty freeware PE editor called CFF Explorer currently version VII.
http://www.ntcore.com/exsuite.php
One of the options under the Rebuilder tab is to change the Image Base of an object and rebuild it.
Make sure you are only doing this to a copy of your DLL. It's a long shot but it may work.
Good Luck.
Hi,
stephj said:
There is a nifty freeware PE editor called CFF Explorer currently version VII.
One of the options under the Rebuilder tab is to change the Image Base of an object and rebuild it.
Click to expand...
Click to collapse
cool, thanks !
I just tried it, but unfortunately the "New Image Base" functionality is greyed out.
I guess it's because the DLL I'm trying to change is not for x86_32/x86_64, but for the ARM platform.
Do you also debug WinCE stuff ?
I'm currently trying to get IDA Pro working with WinCE.
It seems to have debug support through ActiveSync.
The 5x5 and Life programs listed in my signature both have a separate CE version, but they were ported over to CE after I had shaken all the bugs out of the WinMo version in the WinMo Emulator and on the device itself.
The CE versions were only tested on the CE emulator, and given a quick spin round the block to make sure it all works. I do not have a 'real' CE device to test them on.
I have a copy of IDA Pro, but is only the freeware version, not the full blown paid-for versions. I don't know whether the free version has full CE debug support, I'll have to have a try sometime.
Testing in CE-Emulator is not enough at all
stephj said:
The CE versions were only tested on the CE emulator, and given a quick spin round the block to make sure it all works. I do not have a 'real' CE device to test them on.
Click to expand...
Click to collapse
Probably these CE-Emulator tests were not enough at all, because for example your SUDOKU does NOT work properly on my 800x480px sized unit based on CE 6.0 Professional. FileDialogs not populated, etc pp
Do not worry, I mainly are playing flash games, IMHO the better type of gaming applications ...
Only 5x5 and Life have versions specifically built ising the Windows CE SDK.
The others don't, as they were built using the Windows Mobile SDK.
Is it really surprising that it looks crap or doesn't work properly, if you try and run it under the wrong platform?
Likewise, CE versions look crap when run under Windows Mobile.