Workaround for Blackberry USB Sync
I've been able to sync my Blackberry 7250 consistently by following these steps:
First launch the Blackberry Desktop Software (4.2.2.14). Double-click Synchronize. In the Synchronize Tab make sure Automatic Synchronization is checked. Then attach the handheld to your USB connection. With Automatic Synchronization checked, the connection doesn't have a chance to time-out.
The steps for Backup/Restore are a little different. Launch Blackberry Desktop Software. Double-click Backup and Restore. In this case DON'T use Options/Automatically Backup My Device Every 7 days. Instead, attach your device. Select Backup. When you come to the Save dialog, you have already timed-out, so unplug the device. Plug it back in and click Save IMMEDIATELY! If you hesitate, you'll lose the connection. I haven't tried a Restore using this method.
I run a MacBook Pro Core Duo with OS 10.4.10 and Windows Vista Business. I'm at the latest Parallels build, 3.0 (4560). I use a Boot Camp partition.
My feeling about these time-outs is that the Mac is fighting with Parallels for the Blackberry connection. Go to System Profiler while the Blackberry is connected and you'll find RIM drivers listed under Hardware/USB. I've read other posts on this, but no one seems to know how to stop this behavior. There is also an unanswered post on Apple's Support Forum. I don't believe that Blackberry's drivers are at fault, as some others have said.
I've only been running Parallels for about a week. If any of the developers read this forum, let me tell you that this is a great product! Every feature has worked as advertised. I haven't had any of the connectivity problems I've been reading about. I've been able to burn discs, transfer large amounts of data to external USB drives, and run Retrospect backups and restores via the virtual machine without a single problem. There is some loss of speed, however.
In fact, the only thing about Parallels that I find annoying is purely cosmetic. Is there any way to stop the windows from resizing the way they do while the VM initializes?