Registered: Dec 1999
Location:
Posts: 6

I got my Visor Deluxe 8 days ago. The unit itself works fine, but when I installed (both software and hardware) the USB cradle on my machine, I was severly disappointed.

The gist of the problem is this: With the Handspring ver. of Palm Desktop and the cradle connected to either USB port on my machine, when I press the hotsync button, the Hotsync window flashes on the screen for a split second then disappears. The visor eventually times out and says it couldn't establish a connection.

The only time this DOESN'T happen is if it is a fresh install of Win98SE. Then it 'Detects New Hardware" when I press the button, but the odd thing is it seems to detect the Visor 2 times. After detecting the hardware, the visor eventually times out saying it couldn't establish a connection.

I have tried the cradle/software on another Win98SE machine and it works like a champ, so obviously the error exists with my machine. I have used a Logitech MouseMan+ USB on my machine for some time now, so I don't believe my USB ports are bad. I have tried using the cradle without the USB mouse attached to the USB ports (I used the PS/2 Adaptor) and again, no luck.

I have reinstalled Windows98SE on my machine several times. I have tried multiple BIOS revisions for my motherboard (the Asus P2B-DS). I have tried just about everything I could think of.

I have contacted Handspring technical support regarding this subject several times via the phone, and while they haven't solved the problem yet, they certainly have tried. They are still working on the problem, and every few days they call me back asking me to try something new....

So, I present to the group, anyone have any ideas?

Thanks for your help,
seanf();

Registered: Oct 1999
Location: Columbia, MO, USA
Posts: 68

Here are the steps I would personally take next:

1) Uninstall all Handspring / Palm software
2) Boot to safe mode
3) Go into Control Panel / System and remove the USB connections completely
4) Go into the system BIOS/setup and disable the USB
5) Restart Windows
6) Shut down, go back into setup and reenable the USB ports
7) Restart Windows
8) Shut down
9) Reconnect the Visor Cradle
10) Restart Windows

In general, follow Window's instructions for installing drivers during these various steps.

I know these steps sound pretty convoluted, but I can tell you from much experience that skipping or combining any of the steps may yield radically different results.

Good luck, let me know how it goes...

LarryD

Registered: Dec 1999
Location:
Posts: 6

LarryD:

I had tried a different combination of these steps, but what the hell, I will try anything at this point...

I am at work right now, but I will post back here if I meet any success..



seanf();

Registered: Dec 1999
Location: Toronto, Canada
Posts: 14

Sean,

Be sure to post your findings! I too have a P2B-DS and just placed my order for a Visor Deluxe this week. I ordered the serial adapter just to avoid any potential problems, but will use USB once NT or Linux supports it.

One other thing to check is whether or not the "PNP OS INSTALLED" BIOS switch is on or off - this gave me some headaches too. (This allows the OS to reassign interrupts which might be what is happening).

Good luck!

../mk

Registered: Dec 1999
Location:
Posts: 6

Larry:

No joy, your procedure didn't make any difference with this problem.

seanf();

Registered: Oct 1999
Location: Columbia, MO, USA
Posts: 68

Bummer, here are some more things to do:

1) Try both USB ports if you haven't already

2) Do a soft reset on the Visor using a paper clip, not a software menu option.

3) Switch to the Standard Display Adapter. Let me know if you need specific instructions on this one. I know this sounds odd, but please go with me on it for testing purposes.

4) Press <Ctrl><Alt><Del> and get me a list of all of the applications shown in the Close Program dialog that comes up.

Hang in there, we'll get this figured out.

LarryD

Registered: Dec 1999
Location:
Posts: 9

<sigh> add me to the growing list of people who are having the mysterious suddenly-not-working-hotsync bug. someone else posted about this and concluded the problem was with his visor because he unplugged the problem unit and plugged in a different cradle and visor unit and it worked. btw, my setup is a celeron 300 oc'ed to 450 with 320 mb ram and an abit bh-6 motherboard. my pnp os setting in the bios is ON, but i will check to see if turning it off helps...i doubt it though because, a week ago, it was working fine and the PNP OS setting was on then too...

Registered: Dec 1999
Location:
Posts: 97

I had the same problem with both my Macs (one USB, one serial). When I had the "mysterious suddenly-no-longer-working hotsync bug," I traced it to the USB or serial port remaining in use for some reason. After a while it was usable again. If you don't have that much time, try going into the HotSync Software Setup, disabling HotSync and then re-enabling it. That worked for me last time.

I've also had a lot of trouble with my iMac freezing up when I try to hotsync. Anyone else have that problem?