Vista - Palm Desktop HotSync Manager v7.x software install on 64-bit

What is the proper process for installing the Palm Desktop and HotSync Manager v7x (by ACCESS) on Vista 64-bit? I have Vista Home Premium x64.

I've heard rumor that the best way is to promote a non-priviledged user to ADMINISTRATOR and have that user install using 32-bit compatibility mode and perform an initial hotsync of their handheld device. Once that is done the user can then be demoted to a normal user account and successfully HotSync from that point forward. I'm not sure if this process is the same if the handheld device (PDA or SmartPhone) is Windows Mobile or Palm OS.

Does this sound like a proper installation/setup process? Are all the steps necessary? Should any steps be added (e.g. rebooting, starting/stopping services, etc.)? Can anyone explain why each step is necessary? Does this process need to be repeated for every Vista account on the computer?

In addition, I know that ACCESS has not (and will not) provided a 64-bit USB driver for any current Palm OS Garnet and older devices, so direct connected HotSync is not possible (Bluetooth, IP, IrDA have been proven to work). I'm not looking to solve that issue. Just the software installation to Vista x64.

I will be watching the thread as I have the same question. Have a new 64-bit OS and need to get Hotsync running on it so I can sync with Outlook 2007. Beginning to wonder if I should just dump Outlook and use Palm's Desktop!

Well, I did it. First, some background on my issue. Months ago, after buying this new laptop that came pre-loaded with Vista Home Premium 64, I attempted an installation of Palm Desktop by ACCESS v6.2 (which includes HotSync Manger 7.0.2). I did it using the primary "Administrator" account. I then attempted to use Palm Desktop with a "Standard User" account.

That is the point when I discovered the lack of 64-bit USB driver. Also, when HotSync Manager would start-up, it would complain about the following files being "missing":

AnnaNotifier.dll
EASNotify.dll
pdn20.dll
AlarmNotify.dll

I later came across a post suggesting using a Bluetooth dongle.

So after posting here, I was looking around the web and ran across this little tidbit:

Missing Files: AnnaNotifier.dll and EASNotify.dll - Software - Community Help Forums

So, I took the plunge. I bought an Iogear, Class 1, Bluetooth dongle and crossed my fingers.

Using the Administrator's account, I uninstalled Palm Desktop. I then changed the "Standard User" that was going to use Palm Desktop to an administrative user and turned off UAC as was suggested.

For me, I did not have any of the items in Step 3, except for the fact that I had a folder in C:\Users\[user name]\AppData\Local\VirtualStore\Program Files (x86)\Palm (where [user name] is the "Standard User"), but it was empty. As you can see, my path was slightly different than suggested (no "Program Files\PalmOne).

I re-installed Palm Desktop using the promoted user account, configured the Bluetooth connection and performed a HotSync (yipeeee, it worked!). I then demoted (changed it back to a "Standard User") the user account and turned on UAC. I've been able to successfully continue to HotSync. Also, no more "missing file" errors.

I've found that the Administrator/UAC trick needs to be used for several pieces of software. I needed that configuration for AvantGo, Pocket Tunes (integration to Windows Media Player), and Trillian 3.1. Using a Standard User account and relying on the UAC prompt and entering the Admin password at the correct time will not work for the programs I've listed. They need to be installed using an administrative account. The UAC part may be optional, but I've just turned it off for convienence. Each time, I've reverted that user account back to a "Standard User" and turned UAC back on and have had no issues running the programs.

The only question I still have is, if another user account needs to use Palm Desktop, do I need to perform some type of re-install using that other account? Or will this one install now work for all users on the system?