Registered: Nov 1999
Location: Paterson,NJ
Posts: 10

I constantly hav eproblems beaming. The process starts out fine, but end in an error message stating beaming has been interrupted. Nothing is done in the process.

Registered: Dec 1999
Location:
Posts: 9

I am also having a problem beaming to a friends new Palm IIIxe. I could beam to his old IIIe but I get the beam interuppted error when I try to beam the IIIxe. I beamed an app to a demo Visor at CompUSA with no problem. I emailed Handspring support about this and they gave me a generic answer about beaming distance and that the Visors are compatible with Palms. I too would appreciate any help or insight to this issue.

Registered: Jan 2000
Location:
Posts: 434

Try disabling the usual culprits: Afterburner, Hacks, third-party IR software (IR print, BeamBox, etc.) and keyboard drivers. Then try placing both PDAs on a flat surface with their IR ports facing each other with a separation of about 9 inches.

Registered: Feb 2000
Location:
Posts: 62

Warranty Replacement

Have a Blue VDX, and had no problems beaming. When I dropped it and broke it, Handspring replaced it. The new one (now about 90 days old) was never tested for Beaming. I was at a conference and tried to beam something to someone. It failed, giving me the message "beaming interrupted - " I tried to beam with another Palm III that I had beamed to successfully with my 1st visor. It failed too, same problem.

I called support. After several suggestions, they sent me a new one.

It beams just fine, thank you. Maybe there are specific problems with the IIIxe, but my problem was a faulty visor.

larry

Registered: Apr 2000
Location:
Posts: 266

My father in law got a Visor not to long ago...I could beam over without a problem except for my contact that is set as my business card....everytime it crashed his Visor with a Fatal Error. I tried it a few days later on my brother in laws Visor and no problems.....never did try again on the father in laws......

__________________
Ryan Clayton
www.girlandgeek.com
<A HREF="http://www.girlandgeek.com"><IMG SRC="http://www.girlandgeek.com/images/gag_logo.gif">

Registered: Dec 1999
Location: Atlanta, GA
Posts: 114

Jquil,

I had the same beaming problem before. My solution is to use Afterburner to set the CPU clock to some value greater than the default 16MHz (mine works for 20-28MHz). It's quite strange but it does work. ---- conclusion: too fast cause problem, too slow too.