Re: World Clock bug

Ken Wallich <wallich@ncd.com>
Errors-To: brian@grot.starconn.com
Date: Mon, 31 Jan 94 12:21 PST
Message-id: <199401312001.MAA09038@hemlock.ncd.com>
X-Comment: Zoomer PDA List
Originator: zoomer-list@grot.starconn.com
Errors-To: brian@grot.starconn.com
Reply-To: <zoomer-list@grot.starconn.com>
Sender: zoomer-list@grot.starconn.com
X-Listserv-Version: 5.5 -- Copyright (c) 1991/92, Anastasios Kotsikonas
From: Ken Wallich <wallich@ncd.com>
To: Multiple recipients of list <zoomer-list@grot.starconn.com>
Subject: Re: World Clock bug 
Status: OR

>It's a little hard to fault the application for this, but I'll do it anyway.
>Your system clock can get stuck in the wrong time zone under the following
>circumstance:

>(1) Set "destination" to a location in some other time zone than your "home".
>(2) Set the system clock to "destination".
>(3) Crash GEOS :-).

Facinating.  Just went on my first trip with the Zoomer, and had
exactly that happen.  Fortunately I copied some stuff from
'PRIVDATA/STATE' to a backup directory so that when I had to do my
next soft reset, I could get my application state back.  All I did was
copy the world clock status back (after finding out the time was
hosed).

On one hand I was pleased to find out there really wasn't a memory
leak, but on the other was disappointed that this directory is just
cleared on reset.  Must be some good reason, like files tend to get
corrupted when the app is running and the Zoomer crashes, I'd guess.