Sync Woes with HTC 3D

[wbmccarty]

I'm trying to sync an HTC 3D to MM4, both the current release and beta versions. I have the following issues:

1. Often the connected device fails to show up. By a tedious and time-consuming process of disconnecting and connecting I've so far always managed eventually to coax MM into recognizing the device. Is there some way to improve the reliability with which a connected device can be recognized? If that's not known, what are the known factors that affect or might affect recognition of a connected device?
2. Sometimes the sync operation terminates with the message "Catastrophic error." Does this indicate anything specific that I can attend to or mitigate?
3. When everything else works, the sync always fails in the release version. In the current beta release the sync consistently succeeds when MM is installed portably but consistently fails when MM is installed non-portably. The failure mode is the same in each case: (1) There is no associated error or warning dialog box; (2) the sync operation just stops; and (3) when I inspect the phone, I find that the disk drive is no longer set up to be accessible. It's as though MM has hung up the disk drive. Any ideas?

Thanks!

[Lowlander]

1) Does Windows consistently recognize the device.

1, 2 and 3) Send a debug log (step 4b) to support: viewtopic.php?f=7&t=69

[wbmccarty]

Yes, I'm having no trouble at the operating system level. I can successfully manipulate files via the Windows Explorer, and so on, UNTIL I initiate a sync operation in MM. After that, the smartphone's disk drive is no longer connected to the PC at the operating system level.

I'll collect a debug package at first opportunity. Thanks for your help.

[wbmccarty]

Further study suggests that case #3, above, may be a successful, rather than failed, sync. I think I may have incorrectly extrapolated from the "Catastrophic" error. I was expecting a successful sync operation to pop up or display a message of some sort. But I now see that it doesn't. So I'm not positive the related syncs were successful but, for now, thatt seems the proper assumption.

With respect to case #2, I haven't been able to reproduce the "Catastrophic" error. But, if I figure out how to reproduce it, I'll capture and submit the proper debug information.

Thanks again for your help.

[Johan]

I think I may have incorrectly extrapolated from the "Catastrophic" error. I was expecting a successful sync operation to pop up or display a message of some sort. But I now see that it doesn't. So I'm not positive the related syncs were successful but, for now, that seems the proper assumption.

Hm. Now I see. I used to think that the message is to appear, but after reading your topic most questions have disappeared.