Re: Bug#3042: memo file not gtting memos correctly (fwd)

[Vadim Strizhevsky <vadim optonline net>]

Michael Katz-Hyman writes:
 > Thanks
 > 
 > That worked...
 > 
 > Now, if I edit the memos on my computer, will they sync back to the pilot?
 > 

Yes, they should. One warning though, there's a bug in the rpm
version, that on every sync, each memo grows by one byte, "\n" in the
end. This is fixed in CVS already.

-Vadim



 > mike
 > 
 > /------------------------------------------------------------\
 > |Michael Katz-Hyman			   mkatshym@erols.com|
 > \------------------------------------------------------------/			
 > 
 > On Sun, 24 Oct 1999, Vadim Strizhevsky wrote:
 > 
 > > 
 > > Hi,
 > > 
 > > Thanks for the bug report. The problem is most likely due to the fact
 > > that FastSync is being performed all the time. The first time
 > > should've bee a SlowSync, but for some reason it isn't. Until we solve the
 > > problem in general you can remedy it by forcing a SlowSync
 > > once. To do this simply change SyncPCid on the PilotLink control panel or
 > > by the attached script. After that the next sync should be SlowSync
 > > and all your memos from pilot should be copied to the host. All the
 > > following sync _should_ correctly update any changes.
 > > 
 > > If the above doesn't work please let us know.
 > > 
 > > -Vadim
 > > 
 > > -------------
 > > #! /bin/bash
 > > CFG=~/.gnome/gnome-pilot.d/gpilotd
 > > HOSTID=`cat $CFG|grep sync_PC|sed 's/sync_PC_Id=//'`
 > > NEWHOSTID=$[$HOSTID + 1]
 > > echo $NEWHOSTID
 > > mv $CFG $CFG.tmp
 > > SEDSTRING=s/$HOSTID/$NEWHOSTID/
 > > cat $CFG.tmp | sed $SEDSTRING > $CFG
 > > rm $CFG.tmp
 > > ------------------
 > > 
 > 
 >