I tried this package with a Motorola A780, XP SP1, and an iogear-branded Widcomm 220.127.116.116 driver. The A780 has the same limitation as other Motorola phones of one bluetooth "connection" at a time. If it means anything, I had almost exactly the same experience with a V3, except that pc.net managed to download the phonebook.
The UI for pc.net seems to be very flexible, touchscreen-friendly, and visually attractive. Kudos.
However, how can you possibly convince anyone that this program is worth $$ with that stupid headset button?!? One should not have to push it when the call ends, and a handsfree device should never get out of sync with the phone to the point of requiring this action of the user. As for the suggestion of plugging in a cable to get an alternate serial connection, that alleviated some of my problems, but pc.net was still a bit on the unresponsive side. Besides, if you're going to plug it in, what's the point of bluetooth?! Two thumbs down, you can't seriously call this "compatible" with Motorola phones!
The whole thing would also benefit from some echo cancellation, perhaps like gnomemeeting/ichat seem to do in software.
The Widcomm audio gateway implementation appears to be the major problem here. The Bluetooth HFP 1.0 spec makes one very clear statement on page 14:
The service level connection is described as an RFCOMM serial port type data link over which AT commands are sent. There should not need to be a secondary SPP connection to control the phone functions! Whether the Widcomm AG implementation will expose this or not is another matter.
Whenever an "Audio Connection" exists, a related "Service Level Connection" shall also exist.
Those who still don't understand my complaint, get a Motorola phone and go try a commercial bluetooth car kit -- the usability difference is night and day.