Re: jpilot
On Thu, Jan 16, 2014 at 10:09 PM, Lenore Horner wrote: > > On Jan 16, 2014, at 10:20, John Ruschmeyer wrote: > > I think you want /dev/pilot to be a symbolic link to the device for your > serial port. Something like: > > > > # ln -s /dev/ttyUSB1 /dev/pilot > > Doesn’t that mean I should have /dev/ttyUSB1 already? I don’t. > OS X creates it dynamically for USB serial devices when needed. This means it generally only exists during a sync, since that's the only time that the device is visible as a serial device on USB. You may have to make the device try to sync and then symlink to the USB tty device before it times out. In fact, jpilot somewhat depends on ancient Linux USB behavior which can be emulated to some extent with udev, but may not be easily achieved on OS X (and I recall having trouble with it even on older OS X, although it has been many years since I had a Palm device). -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: jpilot
On Jan 16, 2014, at 10:34 PM, Ryan Schmidt wrote: > > The mention of “/dev/ttyUSB1” could very well be a Linuxism not applicable to > OS X. OS X might not expose the USB ports as a device; I don’t know. This > post says it does not: > > http://stackoverflow.com/questions/11784248/mac-os-analog-to-dev-ttyusbxx I have an old usb-serial port adaptor and the driver does create a /dev/something when it's plugged in - in the distant past, I used it to sync a palmOS device with mac os x (probably in the 10.2 days...). -- Daniel J. Luke ++ | * dl...@geeklair.net * | | *-- http://www.geeklair.net -* | ++ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | ++ ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: jpilot
On Jan 16, 2014, at 21:24, Ryan Schmidt wrote: > > On Jan 16, 2014, at 21:09, Lenore Horner wrote: > >> >> On Jan 16, 2014, at 10:20, John Ruschmeyer wrote: >> >>> I think you want /dev/pilot to be a symbolic link to the device for your >>> serial port. Something like: >>> >>> # ln -s /dev/ttyUSB1 /dev/pilot >> >> Doesn’t that mean I should have /dev/ttyUSB1 already? I don’t. > > I don’t either. >From the jpilot documentation: http://www.jpilot.org/docs/manual.html > Serial Port Setup > > When syncing, J-Pilot uses the port and speed settings out of the J-Pilot > preferences screen. If the port is blank then J-Pilot will use the PILOTPORT > environment variables, as does pilot-link. If these are blank also then > J-Pilot will default to /dev/pilot. > > It is recommended, but not necessary to make a link from /dev/pilot to the > correct serial port. So, if your cradle is on COM1, this is /dev/ttyS0 under > Linux. You could execute the command "ln -s /dev/ttyS0 /dev/pilot". COM2 is > /dev/ttyS1, and so on. The Linux serial ports cua[n] are going away. You > should use the ttyS[n] ports instead. USB ports are usually /dev/ttyUSB1, or > /dev/usb/tts/1 (for devfs), but some devices use /dev/ttyUSB0, or > /dev/usb/tts/0. > > You must also give non-root users permissions to access the serial port. The > command to do this is (as root) "chmod 666 /dev/ttyS0" for the first serial > port, ttyS1, for the second, and so on. The mention of “/dev/ttyUSB1” could very well be a Linuxism not applicable to OS X. OS X might not expose the USB ports as a device; I don’t know. This post says it does not: http://stackoverflow.com/questions/11784248/mac-os-analog-to-dev-ttyusbxx ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: jpilot
On Jan 16, 2014, at 21:09, Lenore Horner wrote: > > On Jan 16, 2014, at 10:20, John Ruschmeyer wrote: > >> I think you want /dev/pilot to be a symbolic link to the device for your >> serial port. Something like: >> >> # ln -s /dev/ttyUSB1 /dev/pilot > > Doesn’t that mean I should have /dev/ttyUSB1 already? I don’t. I don’t either. > Oddly, Missing Sync will actually sync with the palm still under Mavericks — > sort of: calendar and contacts will not sync but supposedly media will. So > something lets my laptop talk to the palm when it’s plugged in but I don’t > know where to find it and how to tell jpilot what to look for. We’re talking about the jpilot port? It hasn’t been updated since 2006. Meanwhile new versions of jpilot have been released as recently as 2011. We should probably update the port to that version and then see where that gets us. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: jpilot
On Jan 16, 2014, at 10:20, John Ruschmeyer wrote: > I think you want /dev/pilot to be a symbolic link to the device for your > serial port. Something like: > > # ln -s /dev/ttyUSB1 /dev/pilot Doesn’t that mean I should have /dev/ttyUSB1 already? I don’t. Oddly, Missing Sync will actually sync with the palm still under Mavericks — sort of: calendar and contacts will not sync but supposedly media will. So something lets my laptop talk to the palm when it’s plugged in but I don’t know where to find it and how to tell jpilot what to look for. Lenore ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: jpilot
On Jan 16, 2014, at 9:52 AM, Lenore Horner wrote: >> >> For obvious reasons, Palm has not been keeping its drivers up-to-date; >> http://kb.hpwebos.com/wps/portal/kb/common/article/33529_en.html#mac is still >> downloadable but I would be very very surprised if it worked on 10.9. I did >> find this: http://pccallup.sourceforge.net which may be a working >> replacement. >> (I don’t have one to test with, sorry.) > > The Palm software hasn’t worked since 10.7. That’s why I switched to Missing > Sync. However it (and other companies) used iSync which Apple has removed > from 10.9. > > I tried the pccallup and the site still exists but there are no files > available. > > Can I copy a /dev/pilot air /dev/ttyUSB1 from a backup under an old operating > system or are there going to be other pieces that go along with that that > I’ll also be missing? > > Thanks, > Lenore As was stated earlier, these aren’t files, so they can’t just be copied. These are essentially the inputs and output of device drivers. So, when the right drivers are installed, copying /dev/pilot will cause the driver to read data from the Palm, and output the results to another file. The device driver is code that reads (or writes) data from a piece of hardware and then outputs that data to /dev/pilot (or whatever). So, that another program can read from that as though it is a file. So /dev/pilot is really a virtual file, not a real file, and trying to copy it would not cause the driver to be copied, but instead would cause the device driver to try to read some data. —Adam ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: jpilot
On Thu, 16 Jan 2014, Lenore Horner wrote: > > > > For obvious reasons, Palm has not been keeping its drivers up-to-date; > > http://kb.hpwebos.com/wps/portal/kb/common/article/33529_en.html#mac is > > still downloadable but I would be very very surprised if it worked on 10.9. > > I did find this: http://pccallup.sourceforge.net which may be a working > > replacement. (I don’t have one to test with, sorry.) > > The Palm software hasn’t worked since 10.7. That’s why I switched to Missing > Sync. However it (and other companies) used iSync which Apple has removed > from 10.9. > > I tried the pccallup and the site still exists but there are no files > available. > > Can I copy a /dev/pilot air /dev/ttyUSB1 from a backup under an old operating > system or are there going to be other pieces that go along with that that > I’ll also be missing? > No, that definitely won’t work. Your best bet might be to run an old OS version in emulation... but even that could be tricky. Alternatively, there are other hacky things you could do with the device if you’re loath to retire it, but that’s getting way off-topic for this list. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: jpilot
> > For obvious reasons, Palm has not been keeping its drivers up-to-date; > http://kb.hpwebos.com/wps/portal/kb/common/article/33529_en.html#mac is still > downloadable but I would be very very surprised if it worked on 10.9. I did > find this: http://pccallup.sourceforge.net which may be a working replacement. > (I don’t have one to test with, sorry.) The Palm software hasn’t worked since 10.7. That’s why I switched to Missing Sync. However it (and other companies) used iSync which Apple has removed from 10.9. I tried the pccallup and the site still exists but there are no files available. Can I copy a /dev/pilot air /dev/ttyUSB1 from a backup under an old operating system or are there going to be other pieces that go along with that that I’ll also be missing? Thanks, Lenore ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: jpilot
On Wed, 15 Jan 2014, Lenore Horner wrote: > Since it annoys me no end to throw away hardware that works, I’m still trying > to use a Palm TX on Mavericks. It may not be possible, but I thought I’d try > jpilot. > > When I do and try to hot sync, it tells me > pi_bind error: /dev/pilot No such file or directory > Check your serial port and settings > Exiting with status SYNC_ERROR_BIND > > That’s all very well, but I don’t find any instructions about what should be > in the file /dev/pilot or where I should set my serial port and settings. > Anyone out there still using this and able to tell me what the file > /dev/pilot should contain? > Files in the /dev directory aren’t normal files, they represent interfaces to physical devices (among other things.) So /dev/disk0 is the first hard drive, /dev/modem would be a modem, /dev/random is the random number generator, /dev/null is where your missing sock went, and so on. The lack of /dev/pilot suggests that the Palm drivers are missing. For obvious reasons, Palm has not been keeping its drivers up-to-date; http://kb.hpwebos.com/wps/portal/kb/common/article/33529_en.html#mac is still downloadable but I would be very very surprised if it worked on 10.9. I did find this: http://pccallup.sourceforge.net which may be a working replacement. (I don’t have one to test with, sorry.) ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: jpilot
On Jan 15, 2014, at 22:44, Lenore Horner wrote: > When I do and try to hot sync, it tells me > pi_bind error: /dev/pilot No such file or directory > Check your serial port and settings > Exiting with status SYNC_ERROR_BIND > > That’s all very well, but I don’t find any instructions about what should be > in the file /dev/pilot or where I should set my serial port and settings. > Anyone out there still using this and able to tell me what the file > /dev/pilot should contain? Things in /dev are not normal files; they are devices. Reading from such a "file" would actually pull data from the device — for example, by reading from a serial port — and writing to such a "file" would actually write data to the device. If /dev/pilot does not exist on your system, I don't know by what means it is intended to have been created, but that's what you would have to find out.___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
jpilot
Since it annoys me no end to throw away hardware that works, I’m still trying to use a Palm TX on Mavericks. It may not be possible, but I thought I’d try jpilot. When I do and try to hot sync, it tells me pi_bind error: /dev/pilot No such file or directory Check your serial port and settings Exiting with status SYNC_ERROR_BIND That’s all very well, but I don’t find any instructions about what should be in the file /dev/pilot or where I should set my serial port and settings. Anyone out there still using this and able to tell me what the file /dev/pilot should contain? Thanks, Lenore___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
