VisorCentral.com (http://discussion.visorcentral.com/vcforum/index.php)
- How To / Troubleshooting (http://discussion.visorcentral.com/vcforum/forumdisplay.php?forumid=2)
-- Lost Datebook Conduit (http://discussion.visorcentral.com/vcforum/showthread.php?threadid=19527)

Lost Datebook Conduit

Well, my syncing problems have been solved since my batteries ran dry, but I just noticed my Datebook is emtpy on the Visor. My entries are still there in the Palm Desktop application, but they don't sync into the Visor. When I hit HotSync -> Custom, Datebook is not one of the choices to change the settings. There is a copy of the Datebook database in my user folder on the desktop, but nothing shows up on the Visor. Any ideas?

did you ever find out anything on this problem? It just happened to me. My mail conduit disappeared too.

- Burns

__________________
Check out my page on Visors:
Burn's Visor page

Re: Lost Datebook Conduit

quote:

---

Originally posted by rmorlino
Well, my syncing problems have been solved since my batteries ran dry, but I just noticed my Datebook is emtpy on the Visor. My entries are still there in the Palm Desktop application, but they don't sync into the Visor. When I hit HotSync -> Custom, Datebook is not one of the choices to change the settings. There is a copy of the Datebook database in my user folder on the desktop, but nothing shows up on the Visor. Any ideas?

---

I had exactly the same problem, and lost some data because I did a hard reset without realising that the desktop Datebook was not up to date. I contacted Handspring and got a response within 24 hours, as follows:

Thank you for your email.

I understand you are unable to restore the Datebook data from the Desktop
back into the Visor. According to your observation of the conduits, you
found out the Datebook conduit is missing. This is the cause of the problem
because once a conduit is missing, that conduit does not take part in the
Hotsync process. Please try the following steps to resolve this problem:

1. Exit the HotSync Manager by clicking on the HotSync icon in the system
tray and selecting Exit.
2. Click Start | Run | Browse... and navigate into "My Computer", then to
the folder: C:\Program Files\Palm or C:\Program Files\Handspring (it could
be either path).
3. In the Palm or Handspring folder you will see an executable program
called hotsync.exe. Select that file and then click the Open button.
4. Now, in your Run text box, it should have the following text string
(including the quotation marks): "C:\Program Files\Palm\hotsync.exe" You
need to add a space, a minus sign and the letter "r" to the end of that
string. Do this by following these steps:
i. Click once in the Run text entry box. This should highlight the entire
run line path in blue.
ii. On your keyboard, press the cursor right key until you see the cursor
flashing just after the right-most quotation ( " ) mark.
iii. Press the space key to place one single space after that quotation
mark.
iv. Type in the two characters -r (minus r, which stands for "rebuild").
v. Now the path should look like "C:\Program Files\Palm\hotsync.exe" -r
5. Click the OK button. This will start the HotSync Manager program and
should reset the conduits so that they will appear in the Custom list and be
ready for synchronization.

Now check the Custom list and the Datebook conduit should be back. Please
double click on it and change the conduit setting to "Desktop overwrites
Handheld" to ensure data is restore back to the Visor. Once this is done you
can perform a Hotsync.

This solution worked fine, but I then enquired as to why the problem had occurred, and got the following prompt reply:

With regards to this question,
we're still looking into why this happens. We have various versions of the
Palm Desktop installed on our crash computers for two years now, and have
not lost any of the Conduits. The only conclusion that we came up with is
that the Palm Desktop was not properly installed from the beginning. So it
does happened to some users, while others never had a problem.


In other words, this has happened to quite a few people but they don't know why.