COM Ports on Emulator vs. Active Sync

I am hoping someone can help with my question. I have tried Google
searches but either can't come up with the proper search words, or
there are no pages that address this...

We are developing a Windows Mobile 5.0 application that communicates
with another device via Bluetooth. The device is not yet ready, so I
wrote a simulator that can communicate with our application running on
the emulator through the COM ports (The simulator runs on a separate
laptop that connects to the development workstation through a serial
cable). When we eventually use Bluetooth for the communication, we
will treat it as a Serial Communication connection (opening the com
port as a file and writing/reading to it). We are not to the point of
actually implementing the Bluetooth yet - perhaps by next month.

So, our application can run on the emulator and is working (mostly)
with the device simulator. I say mostly, because from time to time
the system hangs. We believe it is because the application running on
the emulator cannot keep pace with the messages sent by the device to
the app.

We would like to take the emulator out of the loop and connect the
device simulator to the application on actual WinMobile 5.0 hardware
(we do have the application running on actual hardware - as far as it
can go without communicating with the device). However, I cannot find
any information on how to configure ActiveSync to treat COM ports in a
manner similar to what we can do with the emulator (which has some
configuration screens on which to change settings for peripherals).

Can this be done? Is it possible to set properties in ActiveSync to
communicate with a device in a manner similar to the settings in the
Emulator? Is there a different way (not ActiveSync) to do this without
using Bluetooth? I notice that the ActiveSync help has some
information about connecting to Bluetooth devices through a COM port,
but that information is based upon a device actually being available
(configuring the device in the Windows XP control panel).

Any advice will be appreciated!

John
.

Relevant Pages

  • Re: COM Ports on Emulator vs. Active Sync
    ... You can't do this with ActiveSync - it's not a serial passthru. ... wrote a simulator that can communicate with our application running on ... When we eventually use Bluetooth for the communication, ... our application can run on the emulator and is working ...
    (microsoft.public.windowsce.app.development)
  • Re: Hardware musings
    ... then the emulator would also have the boot ROM! ... entire RWTS setup on a microcontroller and simply communicate this back ... protection, and it remains to be seen whether or not this is feasible ... some point I can study the USB specs and see what's feasible. ...
    (comp.sys.apple2)
  • Re: Bluetooth chat example
    ... physical hardware. ... > so for bluetooth development, the only way to debug is to use the real ... >> emulator does not support bluetooth. ... >>> Can I run the example between my development PC and PPC emulator? ...
    (microsoft.public.pocketpc.developer)
  • Re: Hardware musings
    ... then the emulator would also have the boot ROM! ... you're interested only in unprotected disks, ... entire RWTS setup on a microcontroller and simply communicate this back ... some point I can study the USB specs and see what's feasible. ...
    (comp.sys.apple2)
  • Re: Bluetooth
    ... and in Device Manager under Bluetooth there are 2 drivers loaded, ... Truemobile 355 and MS Emulator. ... This is my first Vista OS comp and I seem to recall that under XP there were ...
    (alt.sys.pc-clone.dell)
Loading