Spoke too soon. Latest version 1.0.3 won't allow non valid callsigns.
ANON is no more.
Back to tests with G9BOF
'jnt
On 8 January 2012 22:35, Andy Talbot <[email protected]> wrote:
> also noticed, from my playing around on Saturday, if you enter a
> callsign in the wrong form and/or a prefix it can't understand, even
> when transmitting that doesn't get forwarded. Try ANON as a callsign
> and see if it sends anything.
>
> 'jnt
>
>
> On 8 January 2012 20:50, Andy - KU4XR <[email protected]> wrote:
>> If this is any benefit to you:
>>
>> Monitors only: put no callsign in the operator section.. The software will
>> not communicate with the internet,
>> but it will still receive, and decode.. You will not see the bars at the top
>> of the screen telling you when
>> a station fires a shot, nor will you see the info on the right side of the
>> screen showing you who got hit..
>>
>> Transmit Stations: A " ham " format callsign ( legitimate or not ) must be
>> typed into the callsign slot for the
>> operator, or the software WILL NOT let you transmit... If a callsign is
>> input into the operator callsign section;
>> you can go stealth by unpluging your LAN cable, or disabling your LAN
>> connection... As long as a callsign
>> is there, the software will let you transmit, even if not connected to the
>> internet, and no one will know you are
>> there over the internet reporting stuff..
>>
>> for what it's worth: ..... 73 all:
>>
>> Andy - KU4XR - EM75xr - Friendsville, TN. USA
>> Coordinates: N: 35º 43' 54" - W: 84º 3' 16"
>> http://lwca.org/grabbers/ku4xr/
>> http://www.myspace.com/beaconxr
>> http://ku4xr.webs.com
>> http://lwca.org/community/YaBB.pl
>>
|
