Re: Pilot synch issues

[Andrew Greig <algreig bigpond net au>]

I now have some interesting stuff happening on the path to achieving a
libusb solution to my Palm Synch.

Check this out, please:

Started gpilotd as user

bash-3.1$ /usr/lib/gpilotd
gpilotd-Message: gnome-pilot 2.0.15 starting...
gpilotd-Message: compiled for pilot-link version 0.12.1
gpilotd-Message: compiled with [VFS] [USB] [IrDA] [Network]
gpilotd-Message: Activating CORBA server
gpilotd-Message: bonobo_activation_active_server_register = 0
gpilotd-Message: Watching Cradle (usb:)

	Plugged LifeDrive into usb port hot synch not activated yet

gpilotd-Message: Found 0830, 0061
gpilotd-Message: Using net TRUE
gpilotd-Message: setting PILOTRATE=57600

	Now I pressed the hotsynch button on the cradle

(gpilotd:5394): gpilotd-WARNING **: An error occurred while getting the
PDA's system data	
(gpilotd:5394): gpilotd-WARNING **: error -201 from pi_close.
gpilotd-Message: setting PILOTRATE=57600
	
	Cancelled the hot synch from the LifeDrive

(gpilotd:5394): gpilotd-WARNING **: An error occurred while getting the
PDA's system data
(gpilotd:5394): gpilotd-WARNING **: error -201 from pi_close.
gpilotd-Message: setting PILOTRATE=57600

	Pressed Hot Synch button on cradle again

(gpilotd:5394): gpilotd-WARNING **: An error occurred while getting the
PDA's system data
(gpilotd:5394): gpilotd-WARNING **: error -201 from pi_close.
gpilotd-Message: setting PILOTRATE=57600

Question now is: Is that line "Using net TRUE" a correct result?
and What is error -201 , Google showed nothing.

I think we are getting warmer.

Cheers
Andrew