WinCE 6.0 Remote Management with Windows 7

Question

I am trying to find a tool to remotely control a Motorola MC3190 device running Windows CE 6.0 from a Windows 7 computer.

I already used Mymobiler with the Intermec CN3 device, so I tried the answers in this question , but I can't get it to work.

• I tried both remote.exe.40 and remote.exe.50 in the Mymobiler folder
• Using the Task Manager in CodeProject , mentioned in the question on the superuser, it seems that remote.exe exits very quickly (or crashes silently).
• There is a MyMobiler entry in the "My Start / Programs" MyMobiler , so somewhere along the line something seems to be installed.
• But when I launch Mymobiler on the desktop, it cannot connect, its icon in the system track remains gray, and when you hover it says Not Connected /
• In Proof MyMobiler works for WinCE video processor is ARM920T-PXA270M , while my device has Marevell, PXA32X-P ( image link ) Perhaps the reason for this was the processor?

I also tried ActiveSync Remote Display from Windows Mobile Developer Power Toys . It is installed, but at startup a window appears with the message "OS or CPU of this device is unknown to this application"

How to get MyMobiler to work with a Motorola MC3190 device running Windows CE 6.0? Is there another tool, preferably free, to remotely control this device?

EDIT: I came across EveryWAN and found the installer . It works out of the box, but it is not available for commercial use, and the website seems to be non-existent.

_{PS: I understand that the tags are not accurate, but I wanted to use something that would catch the attention of experts in these similar tags.}

Answer 1

I want to clarify one answer to the above which is correct. When using the Microsoft PowerToy activesync remote screen, there should be an application on both sides - the host (phone) and the remote (PC). The same is true for MyMobiler.

Install powertoy on the PC.

For the original poster: this is what your error message means:

In the case of the Activecync Remote display for newer devices (anything higher than ARM4 cpus - which means 2008 and higher or more than 200 MHz - as a very general guide), the display software cannot determine which device you have (it is too new, not listed).

For motorola mc3190 your processor is compatible with arm5,

and should work with software that has components compatible with arm4. ARD has 4 options. see here ...

To fix it:

You must use the file explorer on your computer and go to the application folder: c \ Programs ... \ Windows Mobile Developer ... \ ActiveSync ... \ Devices \ wce400 \ armv4t and copy the two files. <w> While you are still on the computer, you must go to the Windows folder on the device (with activesync running or the phone configured to view the hard disk), use Windows Explorer on the PC to go to the device.

Vaguely, it will look like this: Explorer. > Device (e.g. HTC Phone :)
Or X: \, where x is the drive letter. The first subfolder you select must be Windows. Insert two files there.

Two files are now copied to the phone.

At this point, you must use the phone to download the file explorer and go to this Windows folder in the internal memory and manually run cerdisp2.exe, which you just copied.

With the launch of activesync and the phone connected to the PC,

Now you can start the active remote powertoy display on the PC, and it will interact with exe, which works on the phone.

ActiveSync on Xp or Windows Mobile Device Center for Windows Vista / 7/8 must work for this to work.

In addition, the application allows you to use a network ip connection instead of activesync, but I did not use it.

When you finish using this application, you must run kill.exe on the phone in the Windows folder (the second file that you copied) in order to unload the executable dll.

I can verify that this setting works on Xp, Win7 and Win8 - using the Xscale ARM11 528mhz cpu phone.

For MyMobiler, visit their website and get the latest version.

This will fix the connections that are not made if you have an older version installed. It's free. They no longer support him.

My Mobiler should have activesync activated and show the connected device.

My Mobiler is significantly superior to ActiveSyncRD. * It will automatically install the PC application and drag the remote application to the phone through activesync. * In addition, when activesync is running, and when you connect the phone, the MyMobiler application will automatically download on the phone. Thus, whenever you launch MyMobiler on the desktop, it will connect to the phone and download it straight up. * My Mobiler allows you to display full screen, while ARD is limited to 320x400 or similar. 640x800 looks much better. * MyMobiler also allows you to send mouse gestures, as well as copy and paste. ARD offers very limited mouse gesture compatibility.

MyMobiler also supports IP connections, but they indicate that it is slower.

Now I use MyMobiler with Win8 and the touchpad with multi-touch, and the mouse gestures are sent very well.

For Windows V / 7/8, you may need to run compatibility mode in the Mymobiler.exe file. Go to the MyMobiler folder, which may be on your desktop. Wake up until you find exe. Right click and select properties. Compatibility. Run compatibility mode for this file and select XP.

Additional notes:

These applications are slow because USB is slow.

If you enable Fast USB on your phone, it will greatly speed up any remote display - however, Fast USB is unstable and does not work in some configurations. For me, this does not work on XP, but on Win8 - although a little unstable. On the device: Start> Settings icon> Connections icon> USB computer icon. Check the box to enable.

In addition, MyMobiler on Win8 sometimes refuses to connect. Unload mymobiler completely, disconnect the phone, reconnect the phone and watch the activation to confirm the connection. Then restart mymobiler. Sometimes a complete reboot is required, but so rare.

---

The Windows Mobile Remote Controller app on CodeProject - as above, looks great. This is for Windows Mobile 7 and 8 - it's fantastic. It provides the ability to use rapi for use with WinMo 6 / 6.5 devices, which also looks promising.

Answer 2

I never used MyMobiler, so I can not help there, but what about other options?

Have you seen the Windows Mobile Remote Controller app on CodeProject?

I was lucky in the past with the SOTI Pocket Controller . It used to be free, or you had a free version. Not sure what they are still doing.

Windows CE introduced a tool called CERDISP (short for remote CE display) that could be built using Platform Builder. I saw that it is available as a binary download ( like here , for example) on the Internet before, so there is no need to actually build it yourself.

Answer 3

I used MyMobiler (remote.exe.50) on my Windows Mobile 6.5 mobile device. It sounds like you started it. Have you launched the MyMobiler client in your Windows 7 window and connected to your PDA by IP address? (Right-click on the icon in the notification area in Windows 7 and select "Connect IP ...".)

The default address is ActiveSync (169.254.2.1?), So if you have not connected and started ActiveSync, it will not be able to connect initially (but manual connection should work). Misread - - you could start the client, but not the server.

You can also choose to launch a VNC server on your PDA and use a regular VNC client to connect to it. I built this one for Windows Mobile 2003 without any hitch in Visual Studio 2008. You might have the same luck with Windows Mobile 6.5.

EDIT: If you get a message that reads:

 '%s' is not a valid Pocket PC application. 

when starting the MyMobiler client, this means that your type of processor (or OS) is incompatible with the application - so I don’t think your PXA32X-P is to blame; all the more so since the MC3190 is apparently capable of running Windows Mobile 6.5 (that is, the processor should be "pretty" modern, with support for armv4i). But since you did not mention an error that looks like this, I would suggest that your build of Windows CE 6.0 does not contain all the necessary dependencies.

The first thing I checked is that all MyMobiler dependencies are present in your build of Windows CE 6. Windows CE is very customizable; as such, not all software components will be the same across Windows CE builds. MyMobiler is designed to target Windows Mobile, not Windows CE, so it’s very likely that your build of Windows CE on the MC3190 does not have what it needs while the linked video does.

As for ActiveSync Remote Display Power Toy, the message you received, similar to a desktop application, does not know which version should be deployed to your device.

In the readme.txt file in the RemoteSync Remote Display package:

If you see the error message "OS or CPU of this device is unknown this application", this usually means the type of CPU of the current device, usually this Windows CE device, is not recognized by this tool. Workaround 1. Find the processor type of the device (from the manual or manufacturer). 2. Copy \ Devices \ wce400 \\ cerdisp2.exe to the \ windows folder of the device. 3. Run "cerhost2.exe -m" on the desktop / laptop. 4. Run cerdisp2.exe on the device. 5. When the remote display is no longer needed, shut down cerdisp2.exe on the device.

You should be able to choose the version of armv4t; if not, use armv4 version.