VisorCentral.com (http://discussion.visorcentral.com/vcforum/index.php)
- Springboard Modules (http://discussion.visorcentral.com/vcforum/forumdisplay.php?forumid=10)
-- The hell that is hagiwara (http://discussion.visorcentral.com/vcforum/showthread.php?threadid=14421)

I'd like to share a story about my experience with the Hagiware 16meg module. I purchased a Visor Solo for my friend's birthday. After realizing that it had 2 megs, my friend ordered the 16meg module. After receiving it, he put it in immediatly (as soon as I got it to him, long story). I starte beaming progs to him, and he started moving them to the module. After an hour or so, the beaming function on my Visor suddenly stopped working correctly. I got a message saying that make sure the visors are in range and that the connection has not been broken. At this point I was very suprised, I have beamed tons of things before, and never seen this message. I tried beaming from my friend's Solo to my VDX and the beam wouldn't work. At this point I was very startled. Both Visors could no longer beam to each other.We both did a hard reset and tried beaming (with the module out in his just in case). Same thing. Now we were both pretty scared. We immediatly called Handspring. Handspring sent over to me a new VDX, and I returned my friend's Visor Solo and exchanged it for a VDX at his request. Today I received my replacement VDX and decided to test the module. I proceeded to put the module into the VDX that is being replaced and started beaming from it to my new replacement VDX. Sure enough,after about an hour, I could no longer beam anything no receive.

As you can imagine, I am VERY PISSED OFF. This module was a lot of money, and so far all it has done is destroy a key feature of my VDX. If my new replacement VDX is damaged also, I'm pretty much screwed.

Does anyone know what the hell is going on here? Or has this happened to you? Please reply as I am totally clueless on what to do. I emailed hagiwara and told them the whole story.

__________________
I swear, she told me she was 16!

How is the battery doign when the beaming stops to function. It sounds like to me that you're batteries have simply died because of all of the stress that you're putting on the battery during beaming. Try installing new batteries, or waiting a while, and see if it works then.

BEN

This won't solve your beaming problem, but a faster way to get all those files to your friend's Visor would be to pop that 16MB module in your Visor, copy the stuff onto there, and give the module back to him. Most of my friends with PDAs have Visors, and I hardly ever beam anything. I have my 8MB Handspring module, and I just copy it to there and hand the module over. Works great, no worrying about lining the Visors up or too much/too little light, and it's faster, which makes a big difference on anything over 30K or so.

__________________
Soul Raven - "Sm� hjerne, stor gl�de"
Wherever you go, there you are.

Suspect

I suspect that the problem is battery related like Ben said. I don't see how the module would affect your beam at all. I think its pure coincidence. I am willing to bet that you would probably have the same problems without the module installed.

This may be basic but I always think of the movie Sling Blade where the main mentally challenged character asks if the mower has gas after the non-mentally challenged head mechanic says he cannot figure out what is wrong.


On the preference screen, are both Visors set with the beam "ON?" I know sometimes after a hotsync or loading a new program, or hack reset that it turns my beam off.

Just a thought.

__________________

[email protected]

If you're using an unregistered version of Afterburner 3.0 beaming doesn't work unless you disable it.

__________________
<div align="left"><font size="+2" color="#FF8000">Mike</font>
<hr width="200">
<font color="Red"><i>Programming is the struggle between programmers<br> building bigger and better idiot proof systems<br> and the universe building bigger and better idiots</i></font>
<hr width="200">
<b><a href="http://enhanceyourlife.com">http://enhanceyourlife.com</a><br>
<a href="http://www.furrbrain.com">http://www.furrbrain.com</a></b></div>

I agree

I agree with the rest that the problem did not originate from the module. I have the 16mb module for over 3 months and have not encounter any beaming problems. I believe your problem may be software related or battery related.

Oh yeah, I just remember I encountered a problem of "out of range..." when I tried to beam a data that was very large something like >300K. The visor to module to visor transfer is the best and quickest way to trnsfer data.

__________________
Fat's

Both of the batteries in the Visors were brand new. Beaming option is on, duh. The receiving visor connects but in the middle of the send the message pops up. Also, I have tried waiting an hour or more and it doesn't help.

Honestly, at this point I don't care anymore, I got my replacement visor from hand, so bleh, I'll just move on and forget about it. I love how hand still lets me get a replacement visor even with my warranty being expired.

__________________
I swear, she told me she was 16!

Beaming anomolies

I have had problems receiving beamed data that is used with a resident app. An example of this is OmniSky content files that are used by OmniSky. Seems I can really only get it through a sync. Having someone else sync it to their visor and beam it to me doesn't work.

I had some beaming problems too. After beaming for awhile, you tend to hold the units closer and closer together. Try moving them about 10 to 12 inches apart. I find that when they are too close together (6-7 inches or less) I get alot of beaming interruptions. Once held about a foot apart, no probs.