Larry, No, the ttyUSB1 in my example is from my computer. On yours, the second port connecting to the visor module is ttyUSB3 and that should have worked. You probably have some other USB device connected to your machine because visor in not binding itself to ttyUSB0 and ttyUSB1. If that is the case, try removing the other USB device and try the experiment again to see if the visor module picks up USB0 and USB1. If that is the case, try J-Pilot with USB1 and see what happens. BTW, when you pressed the HotSync button on step 8 below, did the Treo chime/beep? Do you have any data in either J-Pilot of the Treo? Good luck. Faisal On Tue, 2008-05-06 at 08:53 -0500, Larry Alkoff wrote: > Faisal Islam wrote: > > Hello Al, > > > > Would you please try the following and see what happens? > > > > 1. Connect your Treo to your computer via USB and turn it on > > 2. Open a Shell and log in as root (type in su and the root pwd) > > 3. Type in the following and see if visor shows up > > lsmod | grep visor > > -- if it does, proceed to step 5 > > -- if not, proceed to step 4 > > 4. Type the following in the shell prompt > > modprobe visor > > -- you should not get errors > > -- go to step 3 above > > 5. Type the following in the shell prompt > > tail -f /var/log/messages > > 6. Press the HotSync button on your Treo and check the output in step 5 > > above. This will show you what the computer sees. The following is an > > example: > > > > May 6 07:43:49 localhost kernel: visor 1-1:1.0: Handspring Visor / Palm > > OS converter detected > > May 6 07:43:49 localhost kernel: usb 1-1: Handspring Visor / Palm OS > > converter now attached to ttyUSB0 > > May 6 07:43:49 localhost kernel: usb 1-1: Handspring Visor / Palm OS > > converter now attached to ttyUSB1 > > > > 7. Type in /dev/ttyUSB1 in your J-Pilot preference tab under serial > > port and click OK. > > > > 8. Re-load J-Pilot and cancel Hotsynch on the Treo (from step 6 above). > > Press hotsynch on the Treo, wait 2 seconds, press hotsynch on J-Pilot. > > You should hear the device beep and start to synchronize. > > > > 9. If this doesn't work, let us know what happened and we will try to > > trouble shoot. If this works, send money to Judd Montgomery. > > > > Good luck, my friend! > > > > Faisal in Dallas TX USA > > > > > > > > > Hello Faisal. > > When I reset Preferences to /dev/ttyUSB3 and reloaded J-Pilot > the Pilot still did not synch. > > From your reading of my lsmod, should I have set the port to /dev/ttyUSB1? > > I'm happy that jpilot.rc seems stable in the sense that the user and > user_id are not being wiped out. > > Larry > > _______________________________________________ > Public archival of this list without permission is prohibited. > http://lists.jpilot.org/mailman/listinfo/jpilot
More information about the jpilot mailing list