Re: [coldsync-hackers] Snapshot: 2.0.0

[JD Smith <jdsmith@astro.cornell.edu>]

I see a new snapshot out, also called 2.0.0.  Perhaps it didn't merit a
version bump.  In any case, it includes those time setting patches I
submitted to SPC.pm.  If you'd like to try it, make a conduit as so
(modify or omit the "use lib"'s if your coldsync and p5-palm perl
library is on the perl search path):

################################################################
#!/usr/bin/perl -w
# Conduit SyncTime
use lib "$ENV{HOME}/palm/coldsync/perl/ColdSync";
use lib "$ENV{HOME}/palm/p5-Palm-1.2.2/";
use Palm::Datebook;
use ColdSync;
use ColdSync::SPC;

StartConduit("sync");
($sec,$min,$hour,$day,$mon,$year)=localtime;
$mon++;
$year+=1900;
my $ret=dlp_SetSysDateTime($year,$mon,$day,$hour,$min,$sec);

EndConduit();
################################################################


In your coldsyncrc file, add:

conduit sync {
        path: /path/to/conduits/SyncTime;
        type: date/DATA; 
}

Note that (hopefully), in the future, a type like "none" will be
available to specify running independently of what databases happen to
be installed.  Here I had to kludge it to run with the DateBook.

Now, perform a sync, and watch your palm crash with something like
"NotifyMgr.c, Line:846,Error waking task".  The time does get set
though.  I get about 1 second setting accuracy.

If people can report their PalmOS version and the behavior after sync
(as in, it doesn't crash), that would be helpful.  Apparently, someone
performed a workaround out there somewhere to this bug in PalmOS 3.3,
but if it's limited to a single OS version, I might just upgrade and let
it go.

Thanks,

JD

-- 
This message was sent through the coldsync-hackers mailing list.  To remove
yourself from this mailing list, send a message to majordomo@thedotin.net
with the words "unsubscribe coldsync-hackers" in the message body.  For more
information on Coldsync, send mail to coldsync-hackers-owner@thedotin.net.