Re: It worked, it broke...



I tried your observation with respect to hotsync and starting up the pilot sync modules.  Here's what I observed (Evo 1.4, XD2, RH8 - 2.4.20-18.9, treo 270) - although not exactly the same as yours, the problem may be similar:
  1. make sure that the gpilotd is not running, if so, kill the process
  2. make sure that the pilot settings/pilot-control-app is not running, if so, kill it
  3. hit the hotsync button on the treo (pilot)
  4. startup /usr/libexec/gpilotd in a terminal window under your user ID - no need to do this as root (you should get to a final gpilotd-Message indicating your Pilot ID, owner, etc.)
  5. evo ==> tools ==> pilot settings (this brings up the gui pilot settings window - assuming you have it already configured and conduits enabled)
  6. You should see a lot of messages indicating checking and syncing up of calendar, tasks, etc.  Memo's don't work.

/dc


Nigel Metheringham wrote:
On Tue, 2003-07-08 at 20:24, Joshua Paladin wrote:
  
I posted earlier with an almost identical problem.

What pilot are you using?
    

Its a Tungsten C

  
Are you using OHCI or UHCI?
    

The module loaded is usb-ohci, and I assume the config got it right :-)

I have just found today that if I hit hotsync, and then right-click on
the gnome-pilot panel applet and select "Restart" then the pilot syncs. 
But I have to do this *every* time - which is more than a bit of a pain

	Nigel.

  

-- 
____________________________________________________________
David M. Cvet 
401-159 Frederick St., Toronto, Ont. Canada M5A 4P1
CELL:+1 416 726-8314  FAX:+1 416 366-7448
____________________________________________________________


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]