Registered: Feb 2001
Location:
Posts: 134

Anyone see this...

Have a friend that just got a new Visor...I turned her beam function on...but she can't seem to hold on to a beam. Tried different locations, different Visors...but I always get the beam interrupted message. She can beam fine...just cannot receive properly...it won't hold the signal more than a second or two.

Anyone see this before?

Thanks.

Alan

__________________
I saw that everyone else had a signature and I felt left out, so here is mine.

Registered: Sep 1999
Location: Sydney Australia
Posts: 1883

does any of you have accelerator software installed? that sometimes causes problems beaming...

__________________
<IMG WIDTH="200" HEIGHT="50" SRC=http://www.visorcentral.com/images/visorcentral.gif> VisorCentral Discussion Moderator
Do files get embarrassed when they get unzipped?

Registered: Mar 2000
Location:
Posts: 98

Keey the devices apart - like 4 or 5 feet.

__________________
Visor Enthusiast and Innogear/Geodiscovery basher.

Registered: May 2000
Location: Arlington, VA USA
Posts: 4

seen this too

I have a fairly early model of the Visor Deluxe. My wife's brand new deluxe arrived today. She can beam out,
but cannot receive. "Waiting for Sender" is replaced by "Beam interrupted". Be interested to know if this
is a known issue, or any serious fix suggestion

Registered: Sep 2000
Location:
Posts: 5

One of my co-workers got a new Visor Deluxe from WalMart. He is having the same problem. I can beam him programs only if I hold my Visor about 18" away and 30 degrees away from being directly in line with the Ir window. I suspect something is blocking the Ir sensor (a piece of plastic, etc) I told him his Visor has a cataract.

Registered: Apr 2000
Location: Oakland, CA USA
Posts: 61

Soft reset usually helps. Personally I've found the optimum distance is about 6"-8" or so.

I have also noticed often that it is difficult to beam between different handheld models, and especially between different OS versions. For example, VDX to VDX usually works, but Prism to VDX often has trouble.

Registered: Jan 2001
Location:
Posts: 42

Alan,

I had the same problem a while ago, and it is was due to the internal speed of my visor which was not right. (Probably due to the quality of some clock components used).

Anyway I solved the problem by installing afterburner and using a default speed of 16 or 20Mhz.

Regards,

Bobrus

Registered: May 2001
Location:
Posts: 7

My dad has a Palm IIIxe and I just got a VDX. We tried beaming stuff to each other and it worked perfectly first try.

__________________
"It takes two to lie. One to lie and one to listen." Homer J Simpson