Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Which Mac / Palm combinations supported?' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Which Mac / Palm combinations supported?
Authored by: Han Solo on Sep 09, '03 11:12:00AM
What Mac / Palm hardware are you working with? If I understand the information below correctly (copied from the malsync web site), regrettably only a very small fraction of Mac users still will be able to access AvantGo -- namely those with serial ports....

I have had some requests for an OSX version of malsync, and the intrepid Douglas M. Lowder was kind enough to supply one. If you have a USB to serial Adaptor, you can try this binary malsync_2.0.7.darwin.tar.gz . Until someone is good enough to either send me a Mac with OSX or port pilot-link to Apple's USB interface if you only have USB on your Mac you a out of luck.


[ Reply to This | # ]
Which Mac / Palm combinations supported?
Authored by: Sawtoothed on Sep 09, '03 03:05:19PM
The solution is to set malsync to do a network sync, install and activate USB-TCP Bridge, then do a regular (cable/cradle) hotsync on the palm.

[ Reply to This | # ]
Which Mac / Palm combinations supported?
Authored by: bthoma on Sep 11, '03 11:34:46AM

Okay - newbie poster here... I didn't see a forum topic relating to this hint, hope this is the right place to look for help.

I miss AvantGo and I'm not prepared to pay for iSiloX yet. Beyond that, I like to make things work where I can...

I'm using a standard Palm USB cradle, plugged directly into my PowerBook. I was using AvantGo under 9.2 so it has the associated .prc files installed and configured. AvantGo worked correctly under 9.2.

I know next to zip about Unix and CLI, but I'm trying. I am unable to get malsync to work, with or without the USB-TCP Bridge app.

According to the "Readme-AvantGo" documentation in the malsync download:
"Determine the correct serial port to which your Palm device is connected. Two common options are /dev/ttyS0 and /dev/ttyS1. Do one of two things:
- set the PILOTPORT environment variable to that device, e.g.
setenv PILOTPORT /dev/ttyS1
- OR, bind the /dev/pilot port to the serial device, e.g.
ln -s /dev/ttyS1 /dev/pilot (root access required)"

Looking at Apple System Profiler I see that my cradle is plugged into USB 0, while I have a hub plugged into the other USB port (USB 1), therefore I presumed that the correct device port should be ttys0. In the supplied applescript I changed the orignal line "PILOTPORT=/dev/tty.USA19QI23P1.1" to "PILOTPORT=/dev/ttys0"

I disabled HotSync, ran the script, Terminal output said it was waiting for HotSync. I pressed the sync button on the cradle, but no connection is ever made between the device and my laptop. Eventually the hotsync operation times out with an error.

I'm at a loss and any help would be appreciated. Again, I apologize if this is the wrong place to be asking this kind of stuff.



[ Reply to This | # ]
Which Mac / Palm combinations supported?
Authored by: stiber on Sep 10, '03 01:08:33PM
Sorry, I guess I did forget a few details. I'm using a Palm IIIx, so I would imagine almost every Palm out there would work (of course, I have a very active imagination). I'm using a Keyspan serial to USB converter; you'll need to do a ls /dev/tty* in Terminal to find the device file to substitute for the /dev/tty.USA19QI23P1.1 in PILOTPORT=/dev/tty.USA19QI23P1.1. This device file is automatically created by the driver when a USB device is plugged in (and deleted when unplugged), so you have to have it plugged in to find out (as long as you always plug it in in the same place, the file name shouldn't change). I was also assuming you would set the communication rate to 115,200 baud.

Now that I re-read the question and quote from the malsync site, it seems that the implication is that your Mac must have a serial port. While mine does (an upgraded Beige G3), I'm using the USB port and a Keyspan adapter for the serial Palm hardware. I would think that this would work for Palm USB hardware, too. I haven't played with pilot-link on my Mac, but it might work --- one of the great features of Unix is the file-oriented device interface (special device files in /dev), which provides a uniform set of basic commands for interacting with any I/O device. Since USB is a serial interface, I would think that all the operations (the fcntl, etc. calls) that pilot-link does would be sufficient. This is assuming that the high-level communications (i.e., data formats, commands to Palm and responses from it) are the same regardless of whether the link is serial or USB.

BTW, kudos to the macosxhints folks for reformatting my code to fit the screen.

[ Reply to This | # ]