Any other program listening on the non-working port? On Thu, 2002-11-07 at 22:49, Justin Georgeson wrote: > I'm having an issue with the pilot-link/gnome-pilot tools. I have my > pilot on COM1 in windows, and it works just dandy. So I've been trying > to to do it on /dev/ttyS0 in Linux, with no luck. Running pilot-xfer -p > /dev/ttyS0 -b back immediately returns with an elapsed time of 0:00:00. > If I connect the palm to the second serial port and use /dev/ttyS1, > pilot-xfer works. So I tried the gnome-pilot stuff on ttyS1, but it > doesn't work. Rather than using the wizard, I just manually add the > serial port, and the manually add a pilot, clicking the button to get > settings from the device. But the device never connects. I have both > ttyS0 and ttyS1 perms set to 666, and have added myself to the uucp > group (which owns both device files). Please help. > > -- > ; Justin Georgeson > ; http://www.lopht.net > ; mailto:jgeorgeson@lopht.net > ; "Free the mallocs, delete the news" > > > > -- > Psyche-list mailing list > Psyche-list@redhat.com > https://listman.redhat.com/mailman/listinfo/psyche-list > -- Psyche-list mailing list Psyche-list@redhat.com https://listman.redhat.com/mailman/listinfo/psyche-list