Steve Sabram wrote:
>Scott Simpson wrote:
>>I presume that I cannot use the Serial Manager since HotSync will own the
>>COM port on the Windows side.
>That is a false assumtion. Nothing is "seized" on the action of inserting
the
>device into the cradle unlike other more unsocial environments.
Yes, but what I meant was that a typical user will always have the HotSync
Manager running in the background of their Windows session since it's in
their startup group. This (I thought) meant that I cannot count on getting
control of the COM port myself.
>> Or is there a simpler way of doing this?
>Yes there is. First, you can use the Serial Manager when the device is in
the
>cradle. HotSync is just another application that communicates with the
>desktop.
[snip]
>I assume you don't desire to work with the desktop HotSync Manager. That
is
>fine. You'll just need to make sure that your Windows application is
running
>and has control of the cradle serial port before you Palm application
starts
>up.
Indeed, there is my problem. I want to work alongside the HotSync app (I'd
like to transfer a few bytes of data while a user is inside an app (not
through a HotSync)). The problem is that the HotSync is likely to always be
running so I cannot listen in on COM1 for my few bytes of data :-(...
>A good first try of this is to write a program that sends and receives
>characters on the Palm and then startup a terminal emulator on the desktop
to
>make sure it is communicating across the serial port.
Good advice. I do, in fact, already have a perfectly working app as long as
I can get control of the serial port (i.e. I shutdown the HotSync manager
before I run my app).
Thanks for your reply,
Scott
