Sorry to hear that bones. I spent three hours on the phone with Verizon and Blackberry Tech support...with no avail. Here is what was done: We tested connecting the DM 4.2.2 to my Pearl with 100% success. We put on a fresh copy of DM 4.2.2 (this assured we had no corrupt files and provided the drivers for the BB). We wiped the BB 8830 competely clean and were able to connect it to the Virtual Machine and the DM's application loader. When it connected it showed up in the USB controller simply as "blackberry" (vs. RIM Mass Stroage Device or RIM Composite Device which are the usual ones). We then used the App loader to reinstall the BB's software. We disconnected the device and tried to reconnect and the same problem returned. What this boils down to: Xenos, BB says the drivers are all the same for the devices so if the 8100 Pearl can connect the 8830 should too w/o a problem. This is somewhat confirmed by the fact that the Parallels and the DM were able to hook up the the device itself (when the device was in its simples "hardware" state and didn't have any of the application software on it). Once the Blackberry's app software was loaded back up Parallels failed to connect. It went into the endless connect/disconnect loop. VM Ware doesn't have this problem. All BB devices and Palm devices I've tired work no problem. I think Parallels is getting confused by the BB's multiple modes (mass storage, composite device, etc). This results in the loop. Why this doesn't happen when I connect the Pearl I don't know. Any ideas?