[coldsync-hackers] probs with p5-palm / memo-test

[Apex Chin <apexchin at yahoo dot com>]

Hello folks,

I'm new to the list and checked the archives, but didn't see a reference
to this particular problem.  I apologize if I missed it somehow.

I've recently installed coldsync (and p5-palm) for use with my USB Visor, 
and (nearly) everything is working great.  I have successfully connected 
to the Visor and downloaded everything from it, and now I'm trying to 
get conduits working properly.  

The first I tried was memo-text, and it is giving me a rather ugly error
message.  When I first run it, the dump mode correctly creates $HOME/Memos
which I can read perfectly.  It's when the fetch mode is run that I get
the following error:

Warning: no device on /dev/visor. Sleeping
Please press the HotSync button.
Can't use string ("Unfiled") as a HASH ref while "strict refs" in use at
/usr/local/share/perl/5.6.1/Palm/StdAppInfo.pm line 355.
Can't use string ("Unfiled") as a HASH ref while "strict refs" in use at
/usr/local/share/perl/5.6.1/Palm/StdAppInfo.pm line 355.
pdb_LoadHeader: read: Illegal seek
Can't load header.
Error: read_backup: Can't load "/home/user/.visor/backup/MemoDB.pdb".
Error: GenericConduit: Can't read MemoDB backup file.
Warning: Conduit [generic] exited abnormally. Continuing.
No handler defined for creator "", type ""
No handler defined for creator "", type ""

If anyone can help me with this, I'd greatly appreciate it.  I'm not sure
if it's a p5-palm thing, a memo-text thing, or a general perl module install
problem I've noted from the archives.  Anyway, below I have included
additional information.  Thanks in advance,

Jeff

1.  System/vesion stuff

Coldsync version 2.2.5
p5-Palm version 1.2.4
Debian woody
perl version 5.6.1
Handspring prism, USB

2.  p5-palm and coldsync.pm install locations

/usr/local/share/perl/5.6.1/ColdSync
/usr/local/share/perl/5.6.1/ColdSync/SPC.pm
/usr/local/share/perl/5.6.1/ColdSync.pm
/usr/local/man/man3/ColdSync.3pm
/usr/local/man/man3/ColdSync::SPC.3pm
/usr/local/lib/perl/5.6.1/auto/ColdSync
/usr/local/lib/perl/5.6.1/auto/ColdSync/.packlist

/usr/local/share/perl/5.6.1/Palm
/usr/local/share/perl/5.6.1/Palm/Raw.pm
/usr/local/share/perl/5.6.1/Palm/Address.pm
/usr/local/share/perl/5.6.1/Palm/Datebook.pm
/usr/local/share/perl/5.6.1/Palm/StdAppInfo.pm
/usr/local/share/perl/5.6.1/Palm/PDB.pm
/usr/local/share/perl/5.6.1/Palm/ToDo.pm
/usr/local/share/perl/5.6.1/Palm/Mail.pm
/usr/local/share/perl/5.6.1/Palm/Memo.pm
/usr/local/man/man3/Palm::Raw.3pm
/usr/local/man/man3/Palm::Address.3pm
/usr/local/man/man3/Palm::Datebook.3pm
/usr/local/man/man3/Palm::StdAppInfo.3pm
/usr/local/man/man3/Palm::PDB.3pm
/usr/local/man/man3/Palm::ToDo.3pm
/usr/local/man/man3/Palm::Mail.3pm
/usr/local/man/man3/Palm::Memo.3pm
/usr/local/lib/perl/5.6.1/auto/Palm
/usr/local/lib/perl/5.6.1/auto/Palm/.packlist

3.  coldsyncrc

########################################
### Options block
########################################
# You may specify global options and variables here if you wish.
# Useful options are:
# CONDUITDIR: a colon separated list of directories, in which conduits may
#             be found.
# LOGFILE:  the log file where information is printed. (If none is specified,
#           logs go to stdandard error.)
options {
	CONDUITDIR: "$(CONDUITDIR):$(HOME)/.palm/conduits";
}
########################################
### Listen block
########################################

# Your .coldsyncrc should begin with a listen block. This tells
# ColdSync which device to listen to, at what speed the sync will
# place, and so forth.
# If you omit the listen block, ColdSync will substitute defaults. The
# following listen block is equivalent to the defaults:


# However, if you're syncing a Visor under Linux, and using the "make
# the USB bus look like a serial device" hack, you should use "serial"
# anyway:

listen serial {
	device: "/dev/ttyUSB1";
}

########################################
### PDA block
########################################

# If your Palm doesn't have a serial number in ROM (e.g., a PalmPilot
# or Visor), use the empty string (of course, if you have more than
# one such Palm, they'll all use the same PDA block):
pda "Visor" {
	snum: "*Visor*";
	directory: "/home/user/.visor";
	username: "Jeff Carneal";
	userid: 3130;
}

# The 'default' keyword specifies that this PDA block should be used
# if no others match. In the following example, the backup directory
# for the Palm III will be /home/arensb/.palmIII; the backup directory
# for old Palms with no serial number will be /home/arensb/.palmPilot;
# and the backup directory for anything else will be
# /home/arensb/.allPalms .

pda "Default for everything else" {
	directory: "/home/user/.allPalms";
	default;
}

########################################
### Conduits
########################################

# Conduits presently come in three flavors: Fetch, Dump, and Sync.
#
# Fetch conduits are run before the main sync. They are intended to
# gather data from files and create or update the databases with which
# ColdSync will then sync.
#
# Dump conduits run after the main sync. They are intended to convert
# the newly-synchronized databases back into whatever form is most
# useful on the local machine.
#
# Sync conduits run during the main portion of the sync, and can run
# instead of, or in addition to the built-in generic conduit. They are
# intended for cases too complex to be easily handled by Fetch and
# Dump conduits.
#
# Other than that, conduits run in the order in which they appear in
# the .coldsyncrc

## Example 0:
# If you do not have a .coldsyncrc file, the following is equivalent
# to the defaults. It says to run the built-in generic conduit on all
# databases unless another one has been specified.

conduit sync {
	path: [generic];
	type: */*;
	default;
}

## Example 1:
# 'memo-text', when run as a Fetch conduit, converts the file
# /home/user/Memos into a .pdb file; when run as a Dump conduit, it
# converts the .pdb file back into text format in /home/arensb/Memos.

#conduit fetch {
#	type: memo/DATA;
#	path: "/usr/local/libexec/coldsync/memo-tidbits";
#	arguments:
#	Directory: /home/user/tidbits;
#}

conduit fetch, dump {
	path: "/usr/local/libexec/coldsync/memo-text";
	type: memo/DATA;
    arguments:
	File:	/home/user/Memos;
	Delete: no;
}







__________________________________________________
Do You Yahoo!?
Yahoo! Health - your guide to health and wellness
http://health.yahoo.com

-- 
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.