OK, I figured out items (2) and (3). These types of errors only occur on
runs after a previous run where I hit "STOP" while running in auto mode.
Does hitting "STOP" cause some sort of data error that affects subsequent
runs? When I delete all the runs and start over, the program, works fine.
Anyone know about this?
Jesse
----- Original Message -----
From: Jesse Wills <jesse@wordex.com>
To: <geez@autox.team.net>
Sent: Thursday, March 09, 2000 10:34 AM
Subject: Palm Operating Questions
> While recording with the palm, I have noticed the following:
>
> (1) On launch, the palm recording screen ET will jump to 6 seconds,
> skipping seconds 1-5.
>
> (2) Sometimes the palm recording screen will sit for 5 or more seconds
> without sequencing the elapsed time, then the ET will fast forward to the
> "right" time and continue recording. On some of my commute runs this
> happens several times.
>
> (3) There are also times when the ET fails to sequence at all past a
> certain time, but when the run is compiled (after autostop) the apparent
> correct length of the run is saved. I am talking about differences of
tens
> of seconds, so this is not a function of my autostop which is set to 3
> seconds.
>
> Anyone with similar issues?
>
> Jesse
>
|