How to install the new Aceeca 64bit drivers on a TX

[frav]

Wyrenut, greetings from Brazil. From what I understand, you are the master in Palm TX.
Well, I had all the problems of other users with the hotsync on Win7-64bit, only to find the solution here: Aceeca drivers for USB.
I updated the drivers in device manager, and realized the hotsync with partial success: with Contacts, Memos and Notes, the hotsync worked, but the calendar does not update at all.
The Palm is trying to synchronize the calendar for more than 30 minutes, not ending synchronization. If the interrupt, both the HotSync Manager and Palm TX lock, and I need to restart them.
Any idea, my friend? Thank you for your attention and sorry for bad English.

[ddv]

I got this laptop before the Aceeca drivers were available, so I've been using bluetooth and wifi with Vista 64. Flash forward to last week, hard drive melted down, had my data all backed up, but the OS recovery disks had a bad spot, so now I'm running Windows 7 Home Premium 64 bit.

I thought I'd try the USB drivers, d/l and unzipped them. Plugged in the USB cable and got the expected failure. So far, so good...

Opened Device Manager. Now things get strange: I don't have any "Other devices". What I do have is an "Unknown Device" listed under whichever USB root hub I happen to have connected it to this time.

I tried opening DM with the SetDev.bat script, viewing by connection and by type. No difference.

Ok, so right click, update driver software, browse my computer to the extracted folder, click next. No joy: "The best driver software for your device is already installed. Windows has determined the driver software for your device is up to date."

The definition of insanity is doing the same thing over and over again expecting a different result. I came close before I decided it was time to break out of the mold and strike off into uncharted territory. So I tried "Let me pick from a list of device drivers on my computer" then "Have disk". Browse to the .inf file in the folder, hit OK and:

"The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."

I may not be all that bright -- as I said, at this point I've pretty much proved I'm borderline insane -- but I am stubborn. Sitting here scratching my head trying to figure out something new to frustrate me, I idly observed the nice flat wire of the retractable TX synch cable I've been using as an emergency charge cable off the USB port. Hmmm. Flat. Two wires. Damn.

So off I go to play with the dust bunnies behind the old desktop. Eventually my coughing fits exposed the mass of black round USB cables enough to start tugging on them seeking a free end with a TX synch connector.

Connecting the TX and laptop with the factory cable changed "Unknown Device" to "Palm Handheld". Eureka! Two minutes later, I had the drivers installed!

It still didn't hotsync though. WTF? In place of the yellow triangle and ! mark, I now had a light grey circle and ? mark. Oh, turn on USB in the hotsync manager connections... That's better.

Now it hotsyncs, albeit with errors: two files failed to backup. Blazer Field Autofill and PMTrace Database -- both return "Protocol Error: Handheld file could not be opened. (4004)"

However, I'm getting the same errors when synching via wifi or bluetooth, so I guess it's nothing to do with the USB drivers. NVBackup will deal with those anyway. I just need to be able to get appointments and contact data back and forth, and now I have a third way to accomplish that if all else fails.

My thanks to those that worked this out and posted their solutions. Hopefully my little comedy of errors will help someone else.

[hankroberts]

rats, trying to use Win7 since Mac OSX 10.7 won't support Palm Desktop.
I've got a Sony Clie TH55, not a Palm TX, hoping the same approach works.

but I"m using VirtualBox; this is a virtual machine. It does see the USB port and does see the "Palm Handheld [0100]" accessible.

In Windows , I get as far as opening the Device Manager and eventually, after a while -- it's showing "Sony Handheld" -- but error 10, cannot start