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: 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 | # ]