PDA problems

[bmike1]

I downloaded evolution for my Visor PDA but it still will not sync. (if I can take
care of this one I can make my computer a Linux OS only machine!) Am I using the correct program for a Visor or can someone please direct me to one that works?
-

I run Linux 2.4.18-17.7.x RedHat 7.3 under a KDE 3.0.0-10 GUI / machine # i586

[ScottLo]

I don't have any suggestions but have run into the same/similar problem . I'm on Redhat 8 with the same kernel version as you.

what specifically are you seeing?

[bmike1]

Originally posted by ScottLo
I don't have any suggestions but have run into the same/similar problem . I'm on Redhat 8 with the same kernel version as you.
what specifically are you seeing?
One of the problems was thatEvolution doesn't work with a visor so now I use jpilot. Now that it is set up I get the error:

***********************
Syncing on /dev/pilot
Press HotSync button now
**************************
pi_bind Invalid argument
Check your serial port settings
exiting with status -10
**************************

if I click the GUI sync button first.
But if I press the visors sync button first it just says:

**************************
Syncing on /dev/pilot
Press HotSync button now
**************************

and gets stuck there.
What a pain this is.

[theevilblah]

im not very familiar with your problem but I think that in Gnome there is a PDA hotsync setup. Try that.

cheers,

Ilya

[anarcholinuxism]

Hi Mike,

I'm having the same problem, I know what the answer is sort of. You have to create a sym link from
/dev/usbtty? to /dev/pilot to get started. I did it before a couple of months ago but having a memory like a goldfish can't seem to replicate it now. Anyone else?

[bmike1]

Thanks buddy! Unfortunately /dev/pilot does not exhist. Any other ideas? I am all ears!

[mdwatts]

Originally posted by bmike1
Thanks buddy! Unfortunately /dev/pilot does not exhist. Any other ideas? I am all ears!

/dev/pilot would be the symlink from the actual device you are using.

i.e.

ln -s /dev/usbtty? /dev/pilot

Have a look through these search results for '/dev/pilot' (http://www.google.com/linux?hl=en&lr=&ie=ISO-8859-1&q=%2Fdev%2Fpilot) which should tell you exactly what needs to be done.

[bmike1]

Originally posted by mdwatts
/dev/pilot would be the symlink from the actual device you are using.

i.e.

ln -s /dev/usbtty? /dev/pilot

Have a look through these search results for '/dev/pilot' (http://www.google.com/linux?hl=en&lr=&ie=ISO-8859-1&q=%2Fdev%2Fpilot) which should tell you exactly what needs to be done.

I looked in my handy-dandy Running Linux and see that i just type the command ln -s <program> and it gives me a symbolic link.
Where do I do it from though?

That was a good question that I figured was answered with the words, going to
where I want the link to point.

I then went to /dev/pilot. Guess what I discovered? There is no /dev/pilot .
There is a dev/usb. In /dev/usb there is no usbtty. There is ttyusb0 -
ttyusb15 which are all 0 bytes in length and they are located in /dev
at 0 bytes in length also..

If the assumption that I would use ttyusb which would I use?

Thanks.
Mike

[posterboy]

because the pilot routines cannot know in advance, are you serial? What port? USB? they all require a /dev/pilot to "point" to the place where the data will be made available. In MY case I have a serial port on (DOS) comm2, so I must do this:

ln -s (target) (link name)

here : ln -s /dev/ttyS1 /dev/pilot
That creates a symbolic (s) link that the pilot software knows to follow to the actual hardware data port. Without that, nothing.

[bmike1]

Originally posted by posterboy
because the pilot routines cannot know in advance, are you serial? What port? USB? they all require a /dev/pilot to "point" to the place where the data will be made available. In MY case I have a serial port on (DOS) comm2, so I must do this:

ln -s (target) (link name)

here : ln -s /dev/ttyS1 /dev/pilot
That creates a symbolic (s) link that the pilot software knows to follow to the actual hardware data port. Without that, nothing.
You wonder what kind of connection My Visor has? My PDA is USB. Over the weekend I went to three electronics stores and tried, to no avail, to get the serial cradle. If, as it appears from your link, I use ln -s /dev/usb1 could you tell me why there is also usb0 and usb2 to usb15? While I was at the electronics store I noticed that there are usb ports that will slip into the the openings where boards go (sorryabout the lack of knowledge concerning terinology). I was thinking that perhaps each ttyUSB represented in /dev/usb (0-15) stands for how many of these new USB 'boards' I can put in. This means I have room for 30 more USB ports in my system (there being 2 USBs per 'board'. Is this correct?

ln -s /dev/usb1 /dev/pilot is what I'm thinking I should put but could you let me know if I'm correct?

One more thing~ where should I put it?
Thanks!
:-)Mike(-:

[posterboy]

Yes, at least I think so. Do this in the /dev directory, and the symlink will be made there, as it should be. Now, trying this is an easy thing to do, takes less time than talking about it, but, I have ZERO experience with doing this for a USB device. NOTE: You _may_ run into permissions issues, also, as both the symlink, and the device it points to will have to be usable by the user that needs to do so. Your symlink, if we are all wet, can simply be removed, no harm done. But, I think this is the direction to go.

[raz0rblade]

Originally posted by bmike1
You wonder what kind of connection My Visor has? My PDA is USB. Over the weekend I went to three electronics stores and tried, to no avail, to get the serial cradle. If, as it appears from your link, I use ln -s /dev/usb1 could you tell me why there is also usb0 and usb2 to usb15? While I was at the electronics store I noticed that there are usb ports that will slip into the the openings where boards go (sorryabout the lack of knowledge concerning terinology). I was thinking that perhaps each ttyUSB represented in /dev/usb (0-15) stands for how many of these new USB 'boards' I can put in. This means I have room for 30 more USB ports in my system (there being 2 USBs per 'board'. Is this correct?

ln -s /dev/usb1 /dev/pilot is what I'm thinking I should put but could you let me know if I'm correct?

One more thing~ where should I put it?
Thanks!
:-)Mike(-:

i believe each ttyUSB# is for each port. if you have a two port usb system then it would be easy as just figuring out which one it is ttyUSB0 or ttyUSB1. If you have a lot of usb ports (for example, 6 like i have ) then you might run into problems. Just put it in a port, run ln -s /dev/ttyUSB0 /dev/pilot as root and try it. If it dont work plug the hotsync thingy into a dif port till your out of ports. if it still dont work, im not sure what to do. I use mine with serial and no guessing needed here as most computer only have one 1 as long u dont have a modem

[bmike1]

Originally posted by posterboy
Yes, at least I think so. Do this in the /dev directory, and the symlink will be made there, as it should be. Now, trying this is an easy thing to do, takes less time than talking about it, but, I have ZERO experience with doing this for a USB device. NOTE: You _may_ run into permissions issues, also, as both the symlink, and the device it points to will have to be usable by the user that needs to do so. Your symlink, if we are all wet, can simply be removed, no harm done. But, I think this is the direction to go.
Well,
I tried it and the machine tells me that the file already exhists. Any ideas how I should progress from here? (I tried ln -s /dev/usb0 - usb2 /dev/pilot)

[bitcoop]

this is probably a case of the blind leading the blind but I think if you do

rm /dev/pilot as root and then
do the ln-s again it should work, failing that try /dev/pda, failing that reinstall your distro, I find that quite often helps :)

[wokoglopulator]

I had to change the symlink when I guessed wrong on the com port. I then used the f switch to change port choice when making the new symlink and it took. Did the change as su. Make sure to chmod the device so all users can use the port.

[bmike1]

On the twelfth of December, at our Linux users group christmas party, I'm having mandrake installed. I am told that this will solve the problem.