That sounds like a good explanation, but the Update/V3.50 directory is
empty. I would also expect real devices running 3.50 (which is what I have
on my test devices) to have the same thing happen to them.
I'm rather concerned about this issue because the code responding to that
sysAppLaunchCmdHandleSyncCallApp launch code I mentioned was a real pain to
get working right, even with the examples in knowledge base - I'm worried
that this reset thing is just a less severe symptom of a subtle bug in that
code.
I originally used this launch code for two actions - sending device info
back to the conduit on request, and completing the HotSync (integrating
databases deposited by the conduit) on request. I had to abandon using it
for the second action, and could only get the first to work with an
inexplicable rearrangement of a few lines of code (pulling code out of a
function and running it in place rather than calling the function). That
last bit has me concerned about stack corruption, even though the code being
run is very simple. The only even remotely questionable thing the code does
is call the WinScreenMode API to retrieve the supported color depths of the
device (but that seems to work).
Before this last change, weird exceptions happened during launch code
processing, or else the HotSync process would just hang during the cleanup
phase. A co-worker found a comment on the web indicating that the required
DlkControl API call for this launch code is very touchy, e.g., if not called
within two seconds of the launch code being sent, or if database
manipulations happened before calling it, bad things could happen.
Mark Peters
in article 40387@palm-dev-forum, Ben Combee at [EMAIL PROTECTED] wrote on
2/20/01 12:06 PM:
>
> "Mark A. Peters" <[EMAIL PROTECTED]> wrote in message
> news:40373@palm-dev-forum...
>>
>> While testing a conduit we're developing, I noticed that if I start with a
>> brand-new emulator session file (it happens to be a Palm IIIc running
>> OS3.5), when the HotSync finishes, the system puts up a form telling the
>> user that the system must now be reset by pressing the "Reset" button on
> the
>> form. On subsequent HotSync's with the same session file, this form is
> not
>> displayed, and it has never been displayed when synching with an actual
>> IIIc.
>
> Your problem might not be related to your application. Do you have an
> "Update/v3.50" directory where you installed your Palm Desktop software? If
> so, is there an update PRC file there? Any file in this directory will be
> autoinstalled at Hotsync time, and the OS updates require the device reset.
> Since you're starting with a clean 3.5 ROM, this mechanism would be
> triggered in an attempt to bring you up to PalmOS 3.5.2.
>
> --
> Ben Combee
> Veriprise Wireless <http://www.veriprise.com>
>
>
>
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
