When I only had bootcamp windows, I could hotsync my Treo 700 without a hitch. I installed parallels and now I cant hotsync. At startup, a hotsync manager window pops up and says that COM1 is unavailable and hotsync will retry when it becomes available. I cant sync w/ USB connection or bluetooth. Help.
Install the app
How to install the app on iOS
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Hotsync Manager ticking me off!
- Thread starter ajanke
- Start date
lesedwards
Bit poster
I've had intermittent problems with parallels recognizing my Treo 680, plugged into a cradle. One solution that seems to work (so far) is to pull down the DEVICES from the top menu, select USB and then click PALM.
al_ctsurgpa
Bit poster
USB hotsync
I had some intermittent problems with my Palm T3 in the past, All was better with the build prior to 3188, Then I upgraded to 3188 , I would get the connection tone and then nothing.
I just noticed that when I right clicked on the hotsync tray Icon that there was no checkmark next to the Local USB,
after re-checking that as my conncection all worked.
This may be over simplistic and your problem may be more complicated ,but I missed it until now and I can hotsync as I was before my upgrade to 3188
Al
I had some intermittent problems with my Palm T3 in the past, All was better with the build prior to 3188, Then I upgraded to 3188 , I would get the connection tone and then nothing.
I just noticed that when I right clicked on the hotsync tray Icon that there was no checkmark next to the Local USB,
after re-checking that as my conncection all worked.
This may be over simplistic and your problem may be more complicated ,but I missed it until now and I can hotsync as I was before my upgrade to 3188
Al
johnq@internode.on.net
Junior Member
What works for me, although very clumsy is the following:
Start the VM,
Push the hotsync button and listen for the "connection" sound,
Cancel the hotsync on the palm,
Press the hotsync button again,
voila, the hotsync application starts up in parallels.
I have not worked out how to make the connection persistent when you close the VM.
Regards
John
Start the VM,
Push the hotsync button and listen for the "connection" sound,
Cancel the hotsync on the palm,
Press the hotsync button again,
voila, the hotsync application starts up in parallels.
I have not worked out how to make the connection persistent when you close the VM.
Regards
John
Treo 680 is an ACTIVE USB device, that is, it makes contact to the host computer even before you press the SYNC button.
This can cause strange results if you connect through a USB hub, for example. I have a 680 - used to have a 650 - and am finding similar 'problems'. My 650 (and I think 700p would be the same) was eaiser since it was a PASSIVE device. And I just had to press SYNC, select it in the DEVICE list, cancel Sync (unless I could do the first two steps in less than 7 seconds or so) then press SYNC again. The second press is necessary because the passive Palms, after their initial contact attempt, go into various alternative modes that are not likely to ever connect.
Anyway, for the passive devices, having the USB set to autoconnect should work best. It should work fine for the active devices too.
The down-side is every OTHER USB device you plug in will first go to Windows. And that could really confuse cameras and some USB keys.
This can cause strange results if you connect through a USB hub, for example. I have a 680 - used to have a 650 - and am finding similar 'problems'. My 650 (and I think 700p would be the same) was eaiser since it was a PASSIVE device. And I just had to press SYNC, select it in the DEVICE list, cancel Sync (unless I could do the first two steps in less than 7 seconds or so) then press SYNC again. The second press is necessary because the passive Palms, after their initial contact attempt, go into various alternative modes that are not likely to ever connect.
Anyway, for the passive devices, having the USB set to autoconnect should work best. It should work fine for the active devices too.
The down-side is every OTHER USB device you plug in will first go to Windows. And that could really confuse cameras and some USB keys.