[jp] Treo 650 won't sync - still need help

  • Previous message: [jp] Treo 650 won't sync - still need help
  • Next message: [jp] Treo 650 won't sync - still need help
  • Russ Button russ at button.com
    Mon Sep 11 00:06:39 EDT 2006

     

    With a new unit, you should have first used the "restore handheld" 
    option under "File" before doing your first sync.
    
    Russ
    
    Ryan Leduc wrote:
    > Hello,
    >
    > I sent the e-mail to the list below but never received a response.
    >
    > When I switched from a treo 600 (which worked fine with jpilot) to a tre0
    > 650,
    >
    > I have nolonger been able to sync.
    >
    > When I do a sync I get messages about databses being missing (but they
    > seem to be there are my treo.  Also, changes made to the treo do not show
    > up in jpilot.  See below for more details of error messages.
    >
    > It has been more than a month since I have been able to back up my treo
    > with jpilot and I badly need some help.
    >
    > Has anybody gotten the treo 650 working with jpilot?  THe thing has been
    > out for at least a year now!
    >
    > Ryan
    >
    >
    > using filez,
    >
    >   
    >>>> Syncing DatebookDB
    >>>> Fetching 'DatebookDB' (Creator ID 'date')... Failed, unable to back
    >>>>         
    > up
    >   
    >>>> database DatebookDB
    >>>>         
    >
    > exists (listed in green), 335k
    >
    >   
    >>>> sync_categories: Unable to open file: AddressDB
    >>>> Syncing AddressDB
    >>>>         
    >
    > exists (listed in green), 27k
    >
    >   
    >>>> sync_categories: Unable to open file: ToDoDB
    >>>> Syncing ToDoDB
    >>>> fast_sync_application: Unable to open file: ToDoDB
    >>>>         
    >
    > exists (listed in green), 64k
    >
    >   
    >>>> sync_categories: Unable to open file: MemoDB
    >>>> Syncing MemoDB
    >>>> fast_sync_application: Unable to open file: MemoDB
    >>>>         
    >
    > exists (listed in green), 12k
    >
    >   
    >>>> sync_categories: Unable to open file: ExpenseDB
    >>>> Syncing ExpenseDB
    >>>> fast_sync_application: Unable to open file: ExpenseDB
    >>>>         
    >
    > exists (listed in green), 4k
    >
    >   
    >>>> Syncing Keys-Gtkr
    >>>> fast_sync_application: Unable to open file: Keys-Gtkr
    >>>>         
    >
    > exists (listed in green), 5k (note, when I use the program on treo, I
    > see
    > my data).
    >
    > I remember reading somewhere that the treo 650 had changed its database
    > structure, but kept links to the old databases for backwards
    > compatibility.  Can't help but think that is related to this.
    >
    > I just did a sync and got:
    > Doing a slow sync.
    > Syncing DatebookDB
    > Syncing AddressDB
    > Syncing ToDoDB
    > sync_categories: Unable to open file: Memo32DB
    > Syncing MemoDB
    > Syncing ExpenseDB
    > Syncing Keys-Gtkr
    > Fetching 'AddressDB' (Creator ID 'addr')... OK
    > Fetching 'DatebookDB' (Creator ID 'date')... Failed, unable to back up
    > database DatebookDB
    > ReadDBList returned = -1
    > Finished.
    >
    > The funny thing is that for the first time changes to my datebook showed
    > up under jpilot.
    >
    > I then tried another sync and got:
    > Doing a fast sync.
    > Syncing DatebookDB
    > Fetching 'DatebookDB' (Creator ID 'date')... Failed, unable to back up
    > database DatebookDB
    > sync_categories: Unable to open file: AddressDB
    > Syncing AddressDB
    >
    > And it never got any further.  The treo timed out, saying connection
    > lost.
    > What's worse, the new data (from treo) that showed up after the slow
    > sync, has now disappeared!  It is still on treo though.
    >
    > I then did a: pilot-xfer --port /dev/ttyUSB1 --backup treo
    >
    > I got:
    >    Please press the HotSync button now... Connected
    >
    > Backing up treo/finger.pdb
    > Backing up treo/Quick Reference Guide.pdf.pdb
    > Backing up treo/Quick Tour.pdf.pdb
    > Backing up treo/Treo650_UserGuide.pdf.pdb
    > Backing up treo/PixerRecentRecipientListDB.pdb
    > Backing up treo/Blazer Bookmarks.pdb
    > Backing up treo/CurrentCarrier.pdb
    > Backing up treo/CarrierProfiles.pdb
    > Backing up treo/CarrierProfiles2.pdb
    > Backing up treo/Snapper-MsgContent-Snpm.pdb
    > Backing up treo/CityTimeDB.pdb
    > Backing up treo/DocsToGoDB.pdb
    > Backing up treo/Datebk3HDB.pdb
    > Backing up treo/DefaultHelperDB.pdb
    > Backing up treo/HSAdvCalcDB.pdb
    > Backing up treo/ContactsDB-PAdd.pdb
    > Backing up treo/CalendarDB-PDat.pdb
    > Backing up treo/MemosDB-PMem.pdb
    > Backing up treo/ContactsSimDB-PAdd.pdb
    > Backing up treo/TasksDB-PTod.pdb
    > Backing up treo/Queries.pdb
    > Backing up treo/RNWKDB.pdb
    > Backing up treo/SMS Messages.pdb
    > Backing up treo/SMS Messages2.pdb
    > Backing up treo/AddressDB.pdb
    > Backing up treo/Bluetooth Trusted Devices.pdb
    > Backing up treo/BrightnessDB.pdb
    > Backing up treo/Bluetooth Device Cache.pdb
    > Backing up treo/DatebookDB.pdb                Failed, unable to back up
    > database
    > RAM backup complete.
    > Time elapsed: 0:03:59
    >
    > Ryan
    >
    > _______________________________________________
    > jpilot mailing list
    > jpilot at jpilot.org
    > http://www.jpilot.org/mailman/listinfo/jpilot
    >   
    
    

     

     

    More information about the jpilot mailing list