Windows Mobile Device Center does not connect
Possibly you have to restart the services. You can also restart your Windows (as always):
How to restart WindowsMobile WMDC services:
Windows Mobile Development and usage
Archive for December 2013
Possibly you have to restart the services. You can also restart your Windows (as always):
How to restart WindowsMobile WMDC services:
If you ever had a windows mobile device that behaved strange you might need some logging to find the cause.
Here is a collection of logging tools I wrote:
The source code of rdp_autologin has been updated and now default.rdp will now include some more lines:
WorkingDir:s:C:\Program Files (x86) AlternateShell:s:C:\Program Files (x86)\notepad.exe EnableClipboardRedirection:i:1 RDPIdleTimeout:i:0
where only EnableClipboardRedirection is working.
Will update the code of rdp_autologin and it’s tools to enable you to control the clipboard setting by the registry. Currently it defaults to ENABLED.
See also previous posts.
Recently I looked for support of starting an alternative shell when using Remote Desktop Mobile on a Windows Embedded Handheld 6.5.3 device.
MSDN says that I can to specify AlternateShell in a rdp file. As Windows Mobile devices always use \Windows\default.rdp, I added the following two lines and tested what happens.
WorkingDir:s:C:\Program Files (x86)
AlternateShell:s:C:\Program Files (x86)\notepad.exe
Unfortunately the above entries are ignored 🙁
But why? I decided to look inside wpctsc.exe I dumped of a WEH device to see which strings (used sysinternals strings app) are known to the Mobile Remote Desktop client. And, no surprise, AlternateShell is not known inside wpctsc.exe. But I saw two other interesting strings around the ones used in rdp files.
Continue reading ‘Windows Mobile: Hidden Remote Desktop Client Clipboard support’ »