news | articles | reviews | software | modules | accessories | discussion | faq | mobile | store
VisorCentral.com >> Discussion >> Visor Related >> How To / Troubleshooting
Hotsync problem

Post a New Thread | Post A Reply

  Last Thread   Next Thread
Author
Topic: Hotsync problem    
Marfu
Member

Registered: Dec 1999
Location:
Posts: 89

Question

I have a strange hotsync problem. I can only hotsync my Visor immediately after my computer is rebooted. I'm using windows 98 and a USB cradle.

I called tech support and they had me edit the registry and reset my Visor and finally sent me a new USB cradle, but I'm still having the same problem. I've even had my Visor replaced and that didn't solve it.

Does anyone have a solution?

Marfu is offline Old Post 02-29-2000 04:41 PM
Click Here to See the Profile for Marfu Edit/Delete Message Reply w/Quote
yucca
Member

Registered: Jan 2000
Location:
Posts: 434

Question

I assume that you've tried running your PC with nothing else on USB other than the cradle?

My last guesses would be an IRQ conflict, or a short in the USB port(s) on the motherboard or in the cable.

yucca is offline Old Post 03-01-2000 09:09 AM
Click Here to See the Profile for yucca Edit/Delete Message Reply w/Quote
Marfu
Member

Registered: Dec 1999
Location:
Posts: 89

Post

The cradle is the only USB device I'm using on this particular PC. I've switched USB ports, Visors and cradles. If it were an IRQ conflict wouldn't it give me problems immediately after boot up and not develop after the machine has been running more than 5 minutes?

Marfu is offline Old Post 03-01-2000 03:59 PM
Click Here to See the Profile for Marfu Edit/Delete Message Reply w/Quote
yucca
Member

Registered: Jan 2000
Location:
Posts: 434

Arrow

Some motherboards permit IRQ sharing (typically on the PCI bus), and this may or may not apply to your USB port. If it is, then the problem might not manifest until first access (by the other device), or until the system gets around to polling the conflicting device. Even a straight-out conflict might not get noticed until the system has had a chance to run through all of the startup code in Win98 - - this could take several minutes (or more on an older machine).

Shorts inside the computer case are still a possibility (though unlikely). The connection of the USB ports to the motherboard might be worth checking.

Sorry. Can't think of anything else.

yucca is offline Old Post 03-03-2000 07:00 AM
Click Here to See the Profile for yucca Edit/Delete Message Reply w/Quote
Marfu
Member

Registered: Dec 1999
Location:
Posts: 89

Smile

Thanks for the help.

Marfu is offline Old Post 03-03-2000 04:58 PM
Click Here to See the Profile for Marfu Edit/Delete Message Reply w/Quote
All times are GMT. The time now is 02:55 AM. Post New Thread    Post A Reply
  Last Thread   Next Thread
[ Show a Printable Version | Email This Page to Someone! | Receive updates to this thread ]

Forum Jump:

Powered by: vBulletin Version 2.3.4
Copyright ©2000, 2001, Jelsoft Enterprises Limited.