Well.. the problem is that I dont have any /dev/ttyUSB, which I guess I need to be able to hotsync my palm...
Do I need anything in my kernel or something?? When I press the hotsync button, /dev/usb/tts/0 and /dev/usb/tts/1 are created, but no /dev/ttyUSB0 or /dev/ttyUSB1....
All suggestions are appreciated
Hi, what's the problem? why don't you use /dev/usb/tts/1 instead of /dev/ttyUSB1 ?
well... it won't work.. it's as simple as that
im beginning to think that something is missing in my kernel, but there is contact between the palm and my computer, so im pretty lost here...
ok, which program are you using for your palm connection?
if the devices are created when you press the hotsync button everything should be ok with your kernel. maybe it's a permission problem?
you can use dlpsh that comes with pilot-link to test your connection.
$ dlpsh -p /dev/yourdevice
if this works as root but not as user you should check your permissions.
ok, now i've tried that...
and it doesn't work.. unless I push the the hotsync button before using the command you've given me, and if I do push the button before, I am being asked to push the hotsync button... so something is wrong...
so if I dont push the hotsync before using the command, i am presented with "mknod" as a possible sollution", and if I push it before using the command, it doesn't finish the hotsync...
weee, progress are being made....
now I am able, to use the dlpsh -p /dev... command.. and get a connection.. but if I still can't connect to it with evolution or jpilot...
since the devices are created when you push the hotsync button you have to do this before you tell the application to start sync now.
if it works with dlpsh it should work with jpilot as well. make sure jpilot-settings point to the right device file!
can't think of anything else that could be wrong atm.
yeah, it's working... wohooo..
thank you so much... my hero