VisorCentral.com (http://discussion.visorcentral.com/vcforum/index.php)
- How To / Troubleshooting (http://discussion.visorcentral.com/vcforum/forumdisplay.php?forumid=2)
-- Can't purge Palm Desktop from my PC (http://discussion.visorcentral.com/vcforum/showthread.php?threadid=2843)

How do I completely, 100% remove all traces of Palm desktop from my computer? EasySync (Lotus's conduit for Notes) completely fouled up hotsync but after removing easysync and reinstalling palm desktop things are still messed up.

The weird thing is that is seems like my old data is being kept somewhere on my PC. Data I entered into Palm desktop that did not sync up to the Visor is somehow showing up on a fresh install after all of my attempts at removing the original installation.

Several people have said that a hard boot is the only way out of this but I stand to loose quite a bit of data if I do. Any help would be greatly appreciated.

There are a couple of nasty little files left on the Visor by Easysync. If you remove these files (two of them), then your hotsync will start working "normally" again.

We saw this here in the office on two Visors. Unfortunately, I can't remember the names of files on the Palm. SyncDB was one of them... let me do some research and get back to you.

Don't hard reset, it isn't necessary. Wait a couple of hours for me!

-- Michael

Okay... I'm back. <g>

When Easysync was installed, there were two data bases loaded onto the Visor:

-- SyncAddrDB
-- SyncMailDB

We installed BeamBox onto the Visor and then used BeamBox to delete these data bases. At that point, hotsync with the Palm Desktop software started working again.

The symptoms we were seeing (with these data bases on the Visor) was that we couldn't sync any of the Address data in the Visor with the desktop. Changes made in either place did not exchange with the hotsync. In fact, we could completely delete the entire address book on the Visor and it'd come back (unchanged) with the hotsync. Of course, it was all the wrong data.

Again, deleting those data bases off the Visor restored everything to normal function with respect to the Palm Desktop software.

Hope this helps!

-- Michael

Bingo. That did the trick- thanks so much for your help.

Oh thank you VisorCentral people!!!!!

I have been pulling my hair out all day trying to figure this one out!
I loaded EasySync on friday and thought "boy this is a piece of junk" and went back to hotsync. Since then my datebook has been hopelessly screwed!

I got beambox and nuked the easysync remnants and now I am back in business!!!!

THANKS!!!
BeamBox can be found at http://www.palmgear.com/software/sh...amp;prodID=1535

These discussion groups are awesome for this kind of troubleshooting. I just ran into this same problem this afternoon and I thought I would check here to get some assistance and sure enough there are a couple threads on the issue.

So, now I know how to solve the problem of not being able to synchronize with Palm Desktop. However, what if I want to synchronize at work using EasySync and synchronize at home using Palm Desktop? Is this possilbe. If I remove those two Easysync Databases from my Visor will Easysync no longer function properly?

Thanks for your assistance.

Well, I spent a couple hours fixing this problem and I have settled on this solution. I uninstalled Easysync and then reinstalled Palm Destop, to replace the Palm Desktop conduits. I then reinstalled EasySync selecting only the Notes Mail and Notes Calendar conduits. This way I can sychronize my datebook with Notes Calendar and my Mail with Notes mail and I can synchronize the address book, to do list and memo pad with the Palm Desktop.

Thanks again for your solution to getting the visor sychronizing with the Palm Desktop again. I think I finally have it working the way I like.

P.S. In the meantime, if anyone comes up with a solution so that I can still synchronize the Date Book with the Palm Desktop on my home computer and with Lotus Notes on my work computer then please let me know.

quote:

---

In the meantime, if anyone comes up with a solution so that I can still synchronize the Date Book with the Palm Desktop on my home computer and with Lotus Notes on my work computer then please let me know.

---

I don't have those two databases...

I have 4 in there (according to FPSUtility 4)

SyncAddressDB
SyncDatabookDB
SyncMemoDB
SyncToDoDB

The question is...are those the same files from EasySync, or are those on every visor, and if I remove them, am I dead in the water??? (of course, considering i haven't synced in months because of this issue...)

-Silk

Silk,

As near as I can tell the data bases you've mentioned are part of whatever it is that Easysync is doing to sync up with Notes.

Which data bases you have on your Visor depended on which functions you wanted to sync with Notes. In the instance in which I was involved, only the address book and the mail was to be synced into the Visor. In your instance, it looks like you went for the whole enchilada.

If you remove those data bases, I think you'll find that when you hotsync, your data will be exchanged with the Palm Desktop software as opposed to the Notes data bases.

Another possibility is to rename the data bases if you have the registered version of the FPSUtil software and then to try a hotsync. Then if you have hotsync problems you can rename the data bases back to their original names.

Of course, your mileage may vary, but I don't think you'll have problems if you delete those data bases on your Visor as long as you aren't trying to hotsync with Notes.

Hope this helps!

-- Michael

I had a similar situation on my visor (I also got rid of Easysync and had problems afterwards that nothing worked any more).
I deleted SyncAddressDB (which was quite large) and SyncMailDB and now things hotsync again.
Thanks for the help - saved my day.
Bluf

[This message has been edited by Bluf (edited 03-21-2000).]

Yay!!! It worked for me as well!!

Thank you all!!

I just wanted to let everyone know that I have experienced the same problem (and solved it using the method above) on my Palm. So it seems that it's not just a Visor problem. I was really happy to find a solution. Thanks!