nope.... that didn't work..... So as I sat here I figured I wold 'mkdir /dev/pilot' and it gave me a new error. It told me that it is a directory. That means it is looking for a file called pilot. Could someone send me the file called 'pilot'? (and please... no viruses) On 1/27/07, Donn L Washburn <n5xwb at hal-pc.org> wrote: > On Sat, 27 Jan 2007 04:51:49 -0700 > "Michael Havens" <bmike1 at gmail.com> wrote: > > uh-ohhhhh > > Visor isn't found until the lsmod command. HAHA I think that means I > > have the module loaded but the hardware isn't seen. That is strange! > >I > > tried it with kpilot about a month ago and it asked me for some > > settings with an option for auto-detect. I selected the latter > >option > > and it did detect the settings. It wouldn't sync but it did detect > >the > > settings on the device. I think that means it sees the device. > _________SNIP a bunch > > Well another thing to try is plug and unplug your device. > Then try lsusb again. Sometimes that seems to wake it up. > Also if you have a Hot Sync button push it and again lsusb. > Once found I hit the Jpilot "Sync" button and it works. > That assumes the device name is set correctly. > 73 de Donn Washburn Hpage: " http://www.hal-pc.org/~n5xwb " > Ham Callsign N5XWB Email: " n5xwb at hal-pc.org " > 307 Savoy St. HAMs: " n5xwb at arrl.net " > Sugar Land, TX 77478 BMWMOA #: 4146 > LL# 1.281.242.3256 " http://counter.li.org " #279316 > _______________________________________________ > jpilot mailing list > jpilot at jpilot.org > http://www.jpilot.org/mailman/listinfo/jpilot >
More information about the jpilot mailing list