You can debug programs written for the Symbol 1500 and 1700
on POSE with any of the release or debug ROM's for the Palm OS.
You can't use the ROM's from the 1500 and 1700 as they crash POSE.
You also need to make sure you don't call any scanner specific
functions when the ROM extensions for scanning aren't present.
Fortunately Symbol provided a function for that.
Example:
if (ScanIsPalmSymbolUnit()) // Disable the scanner, if present
ScanCmdScanDisable();
This also allows you to get the benefit of Gremlins, except for the parts
of your code that are entirely scan specific.
Roger Stringer
Marietta Systems, Inc.
Creators of the Marietta PDE (tm) development software for Palm OS(r)
>----------------------------------------------------------------------
>Subject: Re: Symbol 1700 Debugging
>From: "Geoff Shepherd" <[EMAIL PROTECTED]>
>Date: Fri, 30 Jun 2000 13:00:42 -0700
>For debugging with the scanner enabled, you'll have to use the device
>itself. However, if you are needing to debug portions of your app apart from
>the scanner, you can put code in to detect when you are not running on
>Symbol ROMs and then not use the scan library. Since you can now run Symbol
>ROMs on POSE, this trick isn't reliable and you also need to see if you are
>running on POSE. I test for both situations (non-Symbol and/or POSE) so that
>I can also run our app on devices not having the scanner.
>
>..Geoff
>
>----- Original Message -----
>From: Matthew Johnson <[EMAIL PROTECTED]>
>To: Palm Developer Forum <[email protected]>
>Sent: Thursday, June 29, 2000 12:01 PM
>Subject: Re: Symbol 1700 Debugging
>>
>> Yeah, that is how I am doing it now. I just would rather not debug on the
>> device...
>>
>> - Matt
--
For information on using the ACCESS Developer Forums, or to unsubscribe, please
see http://www.access-company.com/developers/forums/
