VisorCentral.com (http://discussion.visorcentral.com/vcforum/index.php)
- Visor Prism (http://discussion.visorcentral.com/vcforum/forumdisplay.php?forumid=19)
-- Unable to Beam (http://discussion.visorcentral.com/vcforum/showthread.php?threadid=14532)

I am new to the use of this type of device. I have had the Visor for about a month, but due to the lack of time, I have not been able to use all the available options. I found today that I am unable to Beam my Bus. Card to anyone, although those around me can beam to each other. I was able, only once, to Beam, all other times the beam fails either to find another user, or to send the data once it finds them. Where should I start looking?

This is an issue that a lot of Prism owners have reported. A typical and easy fix is to allow some distance between the two devices. For some reason, if the Prism is close to the other PDA the BEAM function will not work well. Try holding them 9 to 13 inches apart and see if you have access.

Also make sure you check that BEAM RECEIVE is on:

SYSTEM
PREFERENCES
GENERAL
BEAM RECEIVE: ON

If you continue to have problems you might consider contacting HandSpring, or perhaps someone else may offer some better information.

__________________
In my Father's house are many mansions: if it were not so, I would have told you. I go to prepare a place for you. JOHN 14:2

I had this problem just the other day. I figured out it was the FastCPU/GoBar launcher combo I am using. I set FastCPU to speed up GoBar since GoBar is my launcher. When I have it set like that I cannot beam or recieve. (Most of the time) Somtimes it works but it is unreliable. I found that if I go into OmniRemote and out then try to beam it works. But that was too much of a hassle so I just turned off FastCPU on the GoBar app and have not had a problem since.

So you might check your Hacks and Overclocking apps if you have any. Hope this helps.

OrionNE

I'd try the first solution. I have X-Master and about 12 hacks running concurrently. The Prism for some reason likes distance between the units. a foot to 14 inches should be the MINIMUM distance you should try to beam. If the units get too close, you get the dreaded "Beam interrupted" message.

I don't understand why a lot of people don't get this about not just beaming, but computers in general: you have to BELIEVE! Modern chips are set to detect when a user just doesn't BELIEVE! It's very important not to let them down....

Ah, I'm too much of a wiseguy, eh?
Seriously, though, something IR seems to "like" is when AMBIENT LIGHT IS NOT TOO BRIGHT; it "likes" low-light and shadow, etc. It's usually mentioned in the manuals.

__________________
"Great Spirits Have Always Encountered Violent Opposition From Mediocre Minds." -- Albert Einstein

unable to beam

I've been unable to beam to other Visors but to Palms no problem. I'll try the distance fix. I don't have any hacks but XMaster going (and I still don't know what that does...)