On Feb 8, 2011, at 2/8 4:03 AM, Greg Gobleman wrote:
> My inept attempts simply caused me more frustration in trying to
> deal with getting macros to work consistently, and I think it's all
> because Windows sucks for RTTY.
Re: "Windows sucks": unless Windows had BSOD in the middle of a QSO,
it does not make sense to blame it because a program did not do what
you expected it to do on RTTY.
Re: "work consistently": computer algorithms do not change by
themselves from second to second or from year to year. If anything,
computer programs are consistent to a fault.
You just need to be consistent in how you use the programs.
Remember that a program cannot guess what you have in your mind; well,
perhaps Watson can do that, watch Jeopardy! on February 14th :-). You
need to be explicit when you describe the contents of a macro, which
is just a sequence of commands that you have told the program to use.
Don't assume that a program will be in a certain state unless you
yourself have explicitly placed it in that state.
Operator errors can happen with any program that you are not familiar
with.
You need to figure out what you should include in the macros to do
what you want, and all will be well. Get on the bands when there is
no pileup and test split operating with a buddy/elmer, or with a dummy
load.
That being said, the best known way of not transmitting on top of a
station who is operating split is to get a rig with two receivers (or
an SDR that covers both the DX and the pile frequencies). That is
true with CW and is also true with RTTY. Use a program that will
decode and print from two sound cards or two channels of a sound
card. Or, you can create two instances of the same program which are
connected to separate sound cards.
73
Chen, W7AY
_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty
|