I tried that on the second Treo650 and saw this output when connecting the second Treo650:
where "<blink>" is the cursor blinking waiting for something to happen. I pressed the hotsync button, and the second Treo650 synced, but the cursor stayed right where it was. After the sync of the second Treo650 finished, I reconnected the first Treo650, and pressed the hotsync button on the cable, and wallah, I saw the file being transferred on the gpilot-install-file output which now reads:
bash-3.2$ gpilot-install-file --now ~/Treo650SyncData/CardExport2.prc
gpilotd-Message: Activating object OAFIID:GNOME_Pilot_Daemon
fileconduit-Message: BrentsTreo650 completed 1169078866
bash-3.2$ <blink>
gpilot-install-file version is 1.0 (as reported from --version command line option).
There are two different PDAs listed in the PDAs panel of the gnome-pilot Settings, each with a different Name, ID, and Owner, and I verified that the Local Directory attribute on both PDA's is unique and writeable by the user. Note that the same UNIX user is being used here for both, but that should not matter hopefully.
Anyone have any ideas as to why the File conduit would be hardcoded to transfer to the first Treo650 device? I have not yet tried using two different USB ports with two different USB cables, but that should not matter should it?
Thanks!
Brent