Re: [coldsync-hackers] Coldsync, IrDA and Mac OS X

[Andrew Arensburger <arensb+CShackers@ooblick.com>]

On Wed, Nov 21, 2001 at 11:55:25AM -0500, William Uther wrote:
> --On Sunday, 18 November 2001 12:04 AM -0500 Andrew Arensburger 
> <arensb+CShackers@ooblick.com> wrote:
> > On Sat, Nov 17, 2001 at 06:22:29PM -0500, William Uther wrote:
> >>   iv) compile coldsync.  It configures and compiles fine.  It does have
> >>   a  lot of warnings while building though.
> 
> Here is part of the log:

	Most of these warnings appear to be from the system header
files. That is, some of the files in /usr/include aren't ANSI-clean.
Not much you or I can do about that.

> PConnection_net.c: In function `net_connect':
> PConnection_net.c:256: warning: unused variable `namebuf'
> PConnection_net.c:303: warning: unused variable `namebuf'
> PConnection_net.c:425: warning: unused variable `namebuf'

	This is harmless, and should be fixed in the upcoming stable
release.

> Is -ansi really neccesary?

	No, not really, but it makes gcc emit warnings that I find
useful. You can always configure with "--disable-pedantic" to turn off
-Wall, -ansi, and -pedantic. In addition, you can set the $CFLAGS
environment variable to whichever 'cc' flags you like, before running
'configure'.

> >>   The only problem I have is that it seems extremely slow (hours for the
> >> initial sync).  Any suggestions on fixing that?
> >
> > 	That depends on why it's taking so long. If it's not
> > complaining, then I'd venture to guess that you have a lot of data and
> > it's syncing at some unreasonably low speed.
> > 	Try running it with "-dcmp:5 -dio:3". The "CMP: Got a message"
> > and "CMP: Sending type" messages should tell you how fast the Palm is
> > willing to go, and which speed ColdSync has picked, respectively. You
> > should also see ColdSync going through a set of standard speeds to see
> > whether the serial device can handle them.
> 
> well, that tells me:
> 
> ===== Waiting for wakeup packet
> CMP: Got a message: type 1, flags 0x00, v1.2, rate 115200
> ===== Got a wakeup packet
> ===== Sending INIT packet
> CMP: Sending type 2, flags 0x80, v1.1, rate 115200
> ===== Finished sending INIT packet
> Initialized CMP, returning speed 115200
> 
> it is deciding on 115200.

	Hurm. It definitely shouldn't take hours at 115200 bps. The
only thing I can imagine is that ColdSync is talking at 115200 bps to
the IrDA subsystem, which in turn is talking at 2400 bps to the IR
port on your Palm. If this is the case, I don't know how to fix it,
unfortunately.

> I'm beginning to wonder if it is my Visor's 
> IrDA.  I've never really used it much, and always thought it was slow.  Is 
> there any way to get coldsync to dump the actual throughput?

	No, there isn't, though this should be easy enough to add.
(Hm. Would this be a good use for SIGINFO?  <Points at System V people
who don't have SIGINFO and laughs>)

-- 
Andrew Arensburger                      This message *does* represent the
arensb@ooblick.com                      views of ooblick.com
		Contributes to the population problem.
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.