Please try the new Remote Desktop Autologin code at http://www.hjgode.de/wp/2010/06/23/automated-login-for-remote-desktop-mobile-ii/

There is a registry option to control fit-to-screen. Please try setting this to 1 instead of 0 and see if it fixes your issue. Remember that manually changing options in RDM will be overwritten with settings from RDM AutoLogin code.

~Josef

the code is written to kill an existing RDM beofre it starts a new instance. Cannot actually say, waht is wrong with my kill code. Will have a look later.
I will take also a look at your “fit remote desktop to screen issue”.

regards

Josef

So I have been able to get the application to work. I have found that it is not terminating the existing wpctsc.exe (RDM) before it starts and is freezing up. If I kill the wpctsc.exe process before I execute the RDP_autoLogin.exe it works fine. The other issue I am having is, it is not retaining my screen size. I want the “fit remote desktop to screen” to stay selected but it will not. As a result, I keep getting that box within a box to scroll the screen when I am connected remotely. This little program is great. I hope I can get it work. Would you want to open an email communication so I could send you screen shots? Thanks for your help!

I am using windows mobile 6.1 pocket pc. Where and how should I be installing your application?

here is an update to post: There is a nice RDP client in a separate installer cab. If you dont like the one installed on your device, try this one (called also RDP Finster or Crossbow RDP). Install it to DEVICE nor memory card. The Crossbow RDP also supports some keyboard mapping, see tscscan.txt. The function keys are currently not mapped. According to this site (http://www.quadibloc.com/comp/scan.htm) the HW scan codes for the function keys F1 to F10 are 0x3B to 0×44, the virtual windows key codes for F1 to F10 are 0×70 to 0×79. So function key mapping should look like this:

0x3B 0×70 // 0×70 – VK_F1
0x3C 0×71 // 0×71 – VK_F2
0x3D 0×72 // 0×72 – VK_F3
0x3E 0×73 // 0×73 – VK_F4
0x3F 0×74 // 0×74 – VK_F5
0×40 0×75 // 0×75 – VK_F6
0×41 0×76 // 0×76 – VK_F7
0×42 0×77 // 0×77 – VK_F8
0×43 0×78 // 0×78 – VK_F9
0×44 0×79 // 0×79 – VK_F10

Hopefully function keys are accepted by Crossbow RDP and are sent over to the host.

Crossbow RDP: http://forum.xda-developers.com/showthread.php?t=292895

regards

I am sorry, but even if you free manage to ‘free’ the function keys, the Remote Desktop Mobile (RDM) app will not forward them to the host. The RDM is a very restricted implementation and lacks many usefull features of the Windows CE Terminal Service Client or the desktop one. As MS stated, RDM is only for occasional use.

Hopefully all will get better with phone 7 enterprise edition.

sorry

Josef

I am sorry but I dont know the MC9090. It sounds like it runs Windows CE and not Windows Mobile. If so, you dont really need the rdp-autologin, as most WinCE devices come with an RDP client featuring autologin (depends on how the OEM compiled RDP in there OS build). Why do I think you are using WinCE? Cause double tapping a reg file in WM will NOT import the registry settings.

Sorry

and hopefullly you will find some more help at Motorola’s community.

Josef

I’m also trying to use the Remote Desktop Mobile on CK3 and found that the function keys had no action in the remote session. I tried to release some keys using your FuncKeys tool, but it didn’t work. Have you experienced this ? Do you I need to remap F1 to F12 into special values ?

Thanks for your help.
Fred.

Right now, I’ve dropped the .exe in /application/. As well as the registry file. I clicked on the registry file and it put an RDP_autologin entry in the HKEY_LOCAL_MACHINE.

Thank you for your help,
Steve