VisorCentral.com (http://discussion.visorcentral.com/vcforum/index.php)
- How To / Troubleshooting (http://discussion.visorcentral.com/vcforum/forumdisplay.php?forumid=2)
-- HotSync Problems (http://discussion.visorcentral.com/vcforum/showthread.php?threadid=24900)

HotSync Problems

I am having problems hotsyncing. I have re-installed the software, cleaned the terminals, checked and changed the USB port, used the USB registry cleaner from Handspring, but I am still unable to get any more than one sync. Rebooting doesn't seem to make a differnce. Handspring support will likely tell me to buy a new product.

Does anyone have any suggestions?

Thanks.

Can you give me some more detail. Infomation I need:

-Type of Visor
-OS on your system
-Your USB Chipset (for this go to the Device Manager, click on the USB Controllers and Write down exactly everything you have in there)
Also make sure it's connected directly, you have Local USB checked in the Hotsync Manager, simle things like that

Get back to me with all the specs, and we'll do some more work

quote:

---

Originally posted by Limitles
Can you give me some more detail. Infomation I need:

-Type of Visor
-OS on your system
-Your USB Chipset (for this go to the Device Manager, click on the USB Controllers and Write down exactly everything you have in there)


Also make sure it's connected directly, you have Local USB checked in the Hotsync Manager, simle things like that

Get back to me with all the specs, and we'll do some more work

---

what happens after the first sync?
are there any messages in the hotsync log?
is there any sign of the hotsync manager responding when you sync? (mine beeps).
have you got any overclocking software going?
Does it respond to something like PilotInstall (a utility for installing software without going through a complete hotsync).

__________________
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GS d-(+) s: a C++ UX++++V++S++ P+>+++ L>+++ E+>++ W++ N++(+++) o? K? w !O !M V-- PS PE Y+ PGP++ t++ 5++ X++ R+ tv++ b++(+++) DI++++ D+ G++ e+++>++++ h--- r+++ y?
-----END GEEK CODE BLOCK-----

VIA Technologies Inc.
VIA Tech 3038 PCI to USB Universal Host Controller

Windows 98: No Test Data
Windows Me: Basic Compatibility Requirements
Windows NT4 x86: No Test Data
Windows 2000: No Test Data
Windows XP: No Test Data
Windows XP 64-Bit: No Test Data

This is off of the Microsoft website
The NO TEST DATA MESSAGE means your USB chipset is not fully compatible with Windows 98 and that means you may not be able to hotsync period, or you may not be able to hotsync consistently

quote:

---

Originally posted by imabug
what happens after the first sync?
are there any messages in the hotsync log?
is there any sign of the hotsync manager responding when you sync? (mine beeps).
have you got any overclocking software going?
Does it respond to something like PilotInstall (a utility for installing software without going through a complete hotsync).

---

quote:

---

Originally posted by Limitles
VIA Technologies Inc.
VIA Tech 3038 PCI to USB Universal Host Controller

Windows 98: No Test Data
Windows Me: Basic Compatibility Requirements
Windows NT4 x86: No Test Data
Windows 2000: No Test Data
Windows XP: No Test Data
Windows XP 64-Bit: No Test Data

This is off of the Microsoft website
The NO TEST DATA MESSAGE means your USB chipset is not fully compatible with Windows 98 and that means you may not be able to hotsync period, or you may not be able to hotsync consistently

---

I hear a lot of this problem.... Trust me...

I mean if you want you can try a few more things, not sure if they will work.
Try going into the registry
First back it up - Registry - export file, save on desktop and name somethign simple like regbackup, then make sure to choose all
When your'e done go to
HKey_LocalMachine\Enum\USB|
In that folder you'll see different VID keys.
If you find that you have
VID_0000&PID_0000 or VID_082D&PID_0100 the delete them, reboot and try synching.. that might fix it.

Also sometimes, plug an playing your USB (given you don't have a USB keyboard and mouse) works as well. Basically the goal is to trick it into working again, but because of the incompatibility there's no guarantee it'll work consistently or at all.
Try a serial cradle or something if you're desperate or go up to ME... dunno

I've just suffered something similar, following a fatal crash / hard reset of my Prism. The first HotSync went fine, then it refused to communicate, despite the Visor not having been moved, let alone taken out of the cradle.

All I did was shut down the HotSync software on my PC (running Win2K BTW) and restart it. From thereon, it seems to be fine. I have done another 3 HotSyncs in a row without any communication problems.

Got to be worth a try?

Jules