VisorCentral.com
Show 20 posts from this thread on one page

VisorCentral.com (http://discussion.visorcentral.com/vcforum/index.php)
- How To / Troubleshooting (http://discussion.visorcentral.com/vcforum/forumdisplay.php?forumid=2)
-- USB Win2000 HotSync Problem - help! (http://discussion.visorcentral.com/vcforum/showthread.php?threadid=3119)


Posted by ofo on 07-27-2000 10:27 AM:

Question

I have a Visor Deluxe, Win2K (build 2195) and USB ports. I have downloaded the Win2K update from the Handspring site. It is installed ok (I'm logged on as admin), but when I try to HotSync (also as admin), the "Found New Hardware Wizard" pops up every time, and displays a message after a few seconds that: "Handspring USB. Can't find file specified." -and there's no file specified. The HotSync works allright(the log says "ok" on all subjects), but this message is displayed every time I try to HotSync. So the problem is that it tries to install new hardware every time.

The Handspring support has told me to uninstall software, uninstall hardware (display hidden devices in the add/remove hardware facility and remove handspring USB), remove all visorusb.* files from my computer and unplug my USB-port, reinstall software, plug in the USB-port when promted for it by the installation, then try to HotSync. But no matter what - it's the same. I don't know what to do!?
(I have Win2K installed on H:, not C:, but don't think THAT would be the problem, would it?)
I would be VERY thankful for help!!


Posted by frasej on 07-27-2000 02:45 PM:

Post

Try this.
The next time you get the message about new device found, it should allow you to find the driver you need. Direct it to you Palm folder (usually C:\Program Files\Palm) and into the Drivers folder from there. In the Drivers folder you'll find the visorusb.dll and visorUsb.sys files that the installation is looking for.

------------------
Jay


Posted by ofo on 07-28-2000 10:45 AM:

Question

Unfortunately, I'm not able to do that. What happens is that the Found New Hardware Wizard displays a first window "installing new hardware", and then another window with an error message with the text "Completing the Found New Hardware Wizard. Handspring USB. An error occured during the installation of the device. The system can't find the file specified. To close this wizard, click finish." : I have no options, and can't chooce, redirect or do anything else.
Help, please!!! :-\

quote:
Originally posted by frasej:
Try this.
The next time you get the message about new device found, it should allow you to find the driver you need. Direct it to you Palm folder (usually C:\Program Files\Palm) and into the Drivers folder from there. In the Drivers folder you'll find the visorusb.dll and visorUsb.sys files that the installation is looking for.





Posted by SuperStream on 07-28-2000 11:40 AM:

Post

quote:
Originally posted by ofo:


The Handspring support has told me to uninstall software, uninstall hardware (display hidden devices in the add/remove hardware facility and remove handspring USB), remove all visorusb.* files from my computer and unplug my USB-port, reinstall software, plug in the USB-port when promted for it by the installation, then try to HotSync. But no matter what - it's the same. I don't know what to do!?
(I have Win2K installed on H:, not C:, but don't think THAT would be the problem, would it?)
I would be VERY thankful for help!!



I had the same problem. It was very frustrating. If I remember correctly, the way I fixed it was to follow handspring's instructions above about removing the Handspring USB devices from the control panel-> system-> device manager, and ALSO remove ALL the other USB devices, including non-handspring ones. Then at some point I was able to choose the driver file and pointed it at the Palm directory one as also described above.

Superstream


Posted by ofo on 07-28-2000 12:12 PM:

Post

I've thought about that, but the ones I have are called (I have two under "USB controllers" in Device Manager:
1.Intel 82371SB PCI to USB Universal Host Controller
2. USB Root Hub
...and I hesitate to remove them; aren't they smth that came with Win2K? Are you sure I should remove these?
Thanks for your input, anyway!
/ofo

quote:
Originally posted by SuperStream:
I had the same problem. It was very frustrating. If I remember correctly, the way I fixed it was to follow handspring's instructions above about removing the Handspring USB devices from the control panel-> system-> device manager, and ALSO remove ALL the other USB devices, including non-handspring ones. Then at some point I was able to choose the driver file and pointed it at the Palm directory one as also described above.

Superstream




Posted by frasej on 07-28-2000 02:09 PM:

Post

Try putting VisorUSB.dll into the System32 folder, and VisorUSB.sys into the System32/drivers folder.

------------------
Jay


Posted by ofo on 07-28-2000 08:57 PM:

Question

...they are already there... :-(
(They are in fact in two places: in Palm\Drivers, and in the places you named.)

quote:
Originally posted by frasej:
Try putting VisorUSB.dll into the System32 folder, and VisorUSB.sys into the System32/drivers folder.





Posted by Twitch on 07-29-2000 04:55 PM:

Cool

I got the following advice from Handspring Tech Support and it's been working for me ever since.

You can also try:
1.Check to make sure you are connected directly to the computer, no hubs.
2.Check to see if USB ports are enabled and working properly go to (Start, Settings,
Control Panel, System, Device Manager, click on Universal Serial Bus Device) make
sure there are no x or !
3. If you physical have 2 USB ports in the back switch them, and try putting the
USB cradle in a different ports.
4. Uninstall software.
5.Delete the VID file, click the start button, then go to run, type regedit in this
directory and delete the file (HKEY_LOCAL_MACHINE\Enum\USB\VID_082&PID_0100, or any
VID_000&PID_0000)
reboot computer.
6. Reinstall the software, in the setup make sure that you do not select Local Serial.
7. Last resort is to try the software and hardware on a another computer, if possible.

8. If all this doesn't work it is a defective cradle.
If you are still having difficulty, please call Handspring's Technical Support department
at 1-716-871-6448.

------------------


Posted by SuperStream on 07-31-2000 10:58 AM:

Post

quote:
Originally posted by ofo:
I've thought about that, but the ones I have are called (I have two under "USB controllers" in Device Manager:
1.Intel 82371SB PCI to USB Universal Host Controller
2. USB Root Hub
...and I hesitate to remove them; aren't they smth that came with Win2K? Are you sure I should remove these?
Thanks for your input, anyway!
/ofo




Of course this is at your own risk, but I removed the intel USB drivers and then installed the Handspring. It worked and the Intel came back. In fact, this is one of the reasons I just love W2k. It is very hard to kill. One time I deleted all the network drivers, and rebooted. The system automatically reinstalled them on bootup and connected to the network like nothing happened! I don't think it can hurt to try, if all else fails.


Posted by Samurai on 08-02-2000 05:59 PM:

Cool

I'd also suggest getting Service Pack 1 for Win2k. I had only moderate success HotSyncing before that, now it works first time, every time.


Posted by ofo on 08-02-2000 06:09 PM:

Post

Hi!
I haven't done anything, because I'm waiting for support's answer. I got this reply from handspring:
..."your problem really seems to be a huge one. That's why we sent it to the engeneers in America. It takes a little
time. "
When I get their answer I'll post it here!
For now, I've changed my priviliges so I'm admin, and so I'm able to hotsync, but get the error message every time.


Posted by HorusIVD on 08-10-2000 01:36 PM:

Lightbulb

OFO,

I had similar problems with Win2K USB but not with my Palm...It had a hard time recognising any of the USB devices I had...Since I built the machine I had to support myself and what I found out is that WIN2K doesn't alway install the right USB drivers for your motherboard chipset. Any idea what motherboard you have including the chipset? This may help since as soon as I downloaded the newest drivers from VIA (the group that made the MB chips) everything worked fine after that. I hope this helps...and if you have any questions feel free to ask.

Horus

------------------
"Caution: Cape does not enable user to fly."
~Batman costume warning label


All times are GMT. The time now is 02:49 AM.
Show 20 posts from this thread on one page

Powered by: vBulletin Version 2.3.4
Copyright © Jelsoft Enterprises Limited 2000 - 2016.