Hi Ian,

This is not a bug, he-he...

If the calling operator thinks that you busted his call, hit F5 (His Call)
and F3 (TU), no need to re-enter the callsign or re-send the exchange. The
program remembers the last saved call until you enter a new one.

73 Alex VE3NEA





> All,
>
> Have any of you experienced this? I wonder if it's possible to go back to
> an
> earlier rev., say, 1.4.. .
>
> When running a pileup using 1.5, I am frequently running into the
> following:
>
>
> 1. I call CQ
> 2. I pick out a station to answer
> 3. I CORRECTLY copy/enter the call, give the exchange, and hit enter to
> log
> 4. The calling station then starts going on as if I've busted his call,
> and...
> 5. The only way to stop him from sending is call again and again is to
> enter
> it again
>     As though I was answer a new station, give the exchange again, let him
> say "r"
>      And have to listen to him give his report all over again. At this
> point I can hit
>      F3 and the "NIL" on the previous line will go away.
>
> Is this a flaw or one of Alex's "improvements" to the LIDs feature??
>
> I LOVE the adjustable monitor level, although I'd love it even more if it
> could go one notch lower ;) But with this new and most irritating
> situation,
> I'd happily go back to 1.4 (where I never had this issue come up) and sit
> there with the phones halfway off my head :)
>
> 'zm
>
> --
> Parsons... Ian Parsons

Hehe.. Tnx. Now my head won't hurt so much next time ;)



   _____

From: dxatlas_group@yahoogroups.com [mailto:dxatlas_group@yahoogroups.com]
On Behalf Of Alex, VE3NEA
Sent: Sunday, 05 June, 2005 6:27 PM
To: dxatlas_group@yahoogroups.com
Subject: Re: [dxatlas] oddity in MR 1.5



Hi Ian,

This is not a bug, he-he...

If the calling operator thinks that you busted his call, hit F5 (His Call)
and F3 (TU), no need to re-enter the callsign or re-send the exchange. The
program remembers the last saved call until you enter a new one.

73 Alex VE3NEA





> All,
>
> Have any of you experienced this? I wonder if it's possible to go back to
> an
> earlier rev., say, 1.4.. .
>
> When running a pileup using 1.5, I am frequently running into the
> following:
>
>
> 1. I call CQ
> 2. I pick out a station to answer
> 3. I CORRECTLY copy/enter the call, give the exchange, and hit enter to
> log
> 4. The calling station then starts going on as if I've busted his call,
> and...
> 5. The only way to stop him from sending is call again and again is to
> enter
> it again
>     As though I was answer a new station, give the exchange again, let him
> say "r"
>      And have to listen to him give his report all over again. At this
> point I can hit
>      F3 and the "NIL" on the previous line will go away.
>
> Is this a flaw or one of Alex's "improvements" to the LIDs feature??
>
> I LOVE the adjustable monitor level, although I'd love it even more if it
> could go one notch lower ;) But with this new and most irritating
> situation,
> I'd happily go back to 1.4 (where I never had this issue come up) and sit
> there with the phones halfway off my head :)
>
> 'zm
>
> --
> Parsons... Ian Parsons




   _____

Yahoo! Groups Links

* To visit your group on the web, go to:
http://groups.yahoo.com/group/dxatlas_group/

* To unsubscribe from this group, send an email to:
dxatlas_group-unsubscribe@yahoogroups.com
<mailto:dxatlas_group-unsubscribe@yahoogroups.com?subject=Unsubscribe>

* Your use of Yahoo! Groups is subject to the Yahoo!
<http://docs.yahoo.com/info/terms/>  Terms of Service.



[Non-text portions of this message have been removed]

You're evil.  I like it.   :)

Now, if we could just customize the keys to match different contesting
programs...

73!
--Mike  WQ5C



At 08:27 PM 6/5/2005, Alex, VE3NEA wrote:
>Hi Ian,
>
>This is not a bug, he-he...
>
>If the calling operator thinks that you busted his call, hit F5 (His Call)
>and F3 (TU), no need to re-enter the callsign or re-send the exchange. The
>program remembers the last saved call until you enter a new one.
>
>73 Alex VE3NEA
>
>
>
>
>
> > All,
> >
> > Have any of you experienced this? I wonder if it's possible to go back to
> > an
> > earlier rev., say, 1.4.. .
> >
> > When running a pileup using 1.5, I am frequently running into the
> > following:
> >
> >
> > 1. I call CQ
> > 2. I pick out a station to answer
> > 3. I CORRECTLY copy/enter the call, give the exchange, and hit enter to
> > log
> > 4. The calling station then starts going on as if I've busted his call,
> > and...
> > 5. The only way to stop him from sending is call again and again is to
> > enter
> > it again
> >     As though I was answer a new station, give the exchange again, let him
> > say "r"
> >      And have to listen to him give his report all over again. At this
> > point I can hit
> >      F3 and the "NIL" on the previous line will go away.
> >
> > Is this a flaw or one of Alex's "improvements" to the LIDs feature??
> >
> > I LOVE the adjustable monitor level, although I'd love it even more if it
> > could go one notch lower ;) But with this new and most irritating
> > situation,
> > I'd happily go back to 1.4 (where I never had this issue come up) and sit
> > there with the phones halfway off my head :)
> >
> > 'zm
> >
> > --
> > Parsons... Ian Parsons
>
>
>
>
>Yahoo! Groups Links
>
>
>
>

Hi Mike,

You have yet to see some other evil tricks MR has learned :-) For example,
in the new version the op does NOT always correct you if you bust the call.
Guessing callsigns is now dangerous, like in the real world.

Perhaps I can make the mapping between the F keys and the messages
configurable, but I cannot allow editing the message text. Remember that
there are not human operators behind the calling stations. The program can
copy what you send, but it cannot understand what the message means, it just
checks which F key you pressed. When I figure out how to write a program
that understands free format messages, I will probably create a robot that
will work in the contests for me ;-)

73 Alex VE3NEA






> You're evil.  I like it.   :)
>
> Now, if we could just customize the keys to match different contesting
> programs...
>
> 73!
> --Mike  WQ5C
>
>
>
> At 08:27 PM 6/5/2005, Alex, VE3NEA wrote:
>>Hi Ian,
>>
>>This is not a bug, he-he...
>>
>>If the calling operator thinks that you busted his call, hit F5 (His Call)
>>and F3 (TU), no need to re-enter the callsign or re-send the exchange. The
>>program remembers the last saved call until you enter a new one.
>>
>>73 Alex VE3NEA

Alex,

Entering European Field Day the weekend just past led me to think about my
top twenty examples of incompetent contestants that you might like to
simulate in Morse Runner.  This is - unfortunately - only a partial list:

1) Alligators (all mouth, no ears) who either hear nothing at all or ask for
repeats, sometimes more than once, sometimes once more ...

2) Touch-typos who get our call wrong (and sometimes refuse to acknowledge
the call correction), and occasionally get their own call wrong, forget the
/P, send the wrong serial number (any digit wrong)

3) Sonically-challenged lids who start calling CQ on 'our' frequency with no
QRL?, or who are selectively deaf if we respond to the QRL? with anything at
all (you've got those already Alex, but how about letting us tell them to
QSY, or QSY ourselves a bit to slide out of trouble, if there is room to
move without colliding with someone else?)

4) Squinters - off-channel callers (MR does this well already, but sometimes
they move frequency between overs to keep us on our toes!)

5) Red Zone callers who push the rig and amp to the very limits of
performance and often well beyond.  Their sigs are as far from perfect sine
waves as it is possible to get.  Raspy T1 notes, drifty wanderers,
multiple-tones, we hear the lot in every Field Day and many fixed contests
too, so it's not all down to battery power.

6) Dupes we've already worked already.  We have already worked them.  We
have worked them before.  But still they keep calling back.
6a) Phantom Dupes who claim we've worked before, but haven't (often because
of a busted QSO) ... and yes, this includes those who answer our CQs
6b) Phantom Dupes who want to correct the serial number they gave us one or
two QSOs ago  [Alex, is it too difficult to be able to move the cursor up a
few QSOs to correct the log?  Doing this well without messing up the QSO in
progress is another hard-won contesting skill.]

7) Me Me's who try to complete a QSO even when we are quite clearly and
adamantly working someone else, causing loads of QRM

8) Tone Deaf tuner-uppers who choose 'our' frequency to try to melt their PA
valves

9) QRPers and DX callers who specialise in drifting vaguely around the noise
floor

10)  Meter-misers whose electricity runs out half way through a QSO and
suddenly go QRT (maybe to re-fill the generator?) leaving us hanging ...

11) CBers who want to tell us their name, rig, QSL info and so forth, and
have no idea we are in a contest, nor what a contest is

12) Slotters who want us to QSY and work them on another band, often when
there is no propagation

13)  Zero Beaters who call at exactly the same time and frequency as each
other on each over

14) QLFs who send dots, dashes and other indeterminate bits and gaps in a
random sequence not resembling any known Morse characters

15) Repeaters who send their calls several times, and sometimes our call too
for good measure

16) Autobiographers who seem to want tell me their entire life stories:
"G4iFB DE M0LID - TNX RPRT OM - UR RST 599 5NN 599 - OP HERE SIMON SIMON -
QTH BIGGINSWADE - WX WET AND WINDY - GL IN CONTEST ..."

17) Life's-too-shorters who don't leave gapsbetweenwords, and even worse
don't leave gaps between charactrz because it saves a few milliseconds

18) Gadget-boys who love to send 5NN and TEST at a zillion wpm but can't
receive at the same speed

19) Strokers who try all possible variations of bits and spaces in a
desperate attempt to send /P [after too few hours sleep, I'm usually in this
category myself by Sunday morning!]

20) Breakers on QSK who drop bits into our stream in an attempt to stop us
sending, but then get all mixed up when we actually stop for them

One thing I've noticed in MR but almost never in Real Life is that if we
send a partial call but the real caller doesn't respond, MR leaves us
hanging in silence, listening to white noise, QRM and QRN.  In Real Live,
usually, someone else will jump in to any gap within a short while with
their own call, even though it bears no relation to the partial.  They
usually call during the first quiet period more than a few milliseconds
long, and almost always it's a complete free-for-all on the second partial
attempt (as if we have just called CQ all over again).  Usually a "?" will
coax them out of hiding if it all goes quiet, but not in MR.

But the biggest request of all, Alex, is for a new mode: S&P
(search-and-pounce).  I suspect even the biggest of monster stations with
the most exotic callsigns don't CQ all the time but need to hunt around for
new mults etc. from time to time.  There's definitely an art to S&P
efficiently.  I have in mind a QSY facility that works just like the
'tuneable IF' idea you already have, perhaps, or else a pair of QSY up/down
buttons.  Then we can zero beat on people calling CQ and try to work them.

My trusty old Morse Machine runs the Doctor DX program to simulate contests.
It lets you change bands, and makes a reasonable attempt to change the
callers to reflect the different propagation on each band ... This maybe
just a bit sophisticated for free MR but it's maybe another idea to
consider.

With all those wish-list items off my mind, let me just say that I am not
trying to overload the poor programmer and certainly don't expect to see
these wishes met unless others agree.  Most of all, I would hate to
compromise MR's beautifully realistic audio simulation that beats any other
morse sim I have *ever* used hands-down.  And all this for free!  Alex,
you're a star.

73
Gary
G4iFB  (also the weaker half of G3GRS/P and an insignificant element of M6T
GW8GT G0FBB/P XT2DX  GJ2A etc. etc.)


[Non-text portions of this message have been removed]

Hi all, hi Alex.

I already writen about this subject and as I didn't change my Operative
system yet, it is already affecting me.

On my computer runs Win 98 SE, with a very large Hard Disk, 256 MB/Ram
within 500 Mhz Celeron Processor CPU.

The Sound Card is from Creative, type SB Live 1024.
I'm blind so I pay lots of attenction to everything regarding Sounds world,
soundblaster configuration and so on... I'm using a Screen reader in order
to access to my computer output and I love whole things regarding audio
editing like Goldwave or SoundForge softwares. I have a large experience in
it and all these programs never gave me incompatibility troubles with my
SoundCard, no one except from Morse Runner.
In the past, when I worked with DOS system I was a FAN of RUFZ from DL4MM
since that moment I never find a good CW-trainer like that. Now I discovered
your Morse runner but it doesn't work properly on my SoundBlaster.
I wonder if you have discovered where the problem is... And if it will be
possible for you to fix it easly... to give me the opportunity to use it on
this PC.
If you thing would be necessary, I can give you details about my SoundCard
configuration.

Thanks in advance and best 73 to you and family all.
IZ4APU - Gabriel - North-East Italy.

Hi Gabriel,

The programs that you mentioned are very different from Morse Runner. They
are not real-time programs, i.e., they load a huge amount of audio data in a
buffer and then play it smoothly even if the sound card (or its driver, as
on Windows 98), is very slow.

Morse Runner has to react instantly to the user actions. For example, when
you hit F1, it should start sending CQ immediately. If MR had a 2-second
buffer, you would have to wait 2 seconds until you CQ starts! Since MR is a
real-time program, it can afford only a very small audio buffer. Because of
this, it requires a relatively fast audio card/driver. In the last few
versions of Morse Runner, you can trade the reaction time for stable audio,
please see the readme file for details. Most people who run MR on Win98
increased the buffer size as instructed, and fixed the problem completely.

73 Alex VE3NEA



> Hi all, hi Alex.
>
> I already writen about this subject and as I didn't change my Operative
> system yet, it is already affecting me.
>
> On my computer runs Win 98 SE, with a very large Hard Disk, 256 MB/Ram
> within 500 Mhz Celeron Processor CPU.
>
> The Sound Card is from Creative, type SB Live 1024.
> I'm blind so I pay lots of attenction to everything regarding Sounds
> world,
> soundblaster configuration and so on... I'm using a Screen reader in order
> to access to my computer output and I love whole things regarding audio
> editing like Goldwave or SoundForge softwares. I have a large experience
> in
> it and all these programs never gave me incompatibility troubles with my
> SoundCard, no one except from Morse Runner.
> In the past, when I worked with DOS system I was a FAN of RUFZ from DL4MM
> since that moment I never find a good CW-trainer like that. Now I
> discovered
> your Morse runner but it doesn't work properly on my SoundBlaster.
> I wonder if you have discovered where the problem is... And if it will be
> possible for you to fix it easly... to give me the opportunity to use it
> on
> this PC.
> If you thing would be necessary, I can give you details about my SoundCard
> configuration.
>
> Thanks in advance and best 73 to you and family all.
> IZ4APU - Gabriel - North-East Italy.

Hi Gary,

Thank you very much for your excellent analysis of operators' behavior. I
was laughing and crying at the same time as I was reading your posting...
#16 is the most impressive: it becomes obvious at the end of the guy's
message that he knew you were in a contest! I will certainly use some of
your suggestions in the future versions of Morse Runner.

73 Alex VE3NEA



----- Original Message -----
From: "Gary Hinson" <Gary@...>
To: <dxatlas_group@yahoogroups.com>
Sent: Tuesday, June 07, 2005 10:22 AM
Subject: [dxatlas] MR wish-list


> Alex,
>
> Entering European Field Day the weekend just past led me to think about my
> top twenty examples of incompetent contestants that you might like to
> simulate in Morse Runner.  This is - unfortunately - only a partial list:
>
> 1) Alligators (all mouth, no ears) who either hear nothing at all or ask
> for
> repeats, sometimes more than once, sometimes once more ...
>
> 2) Touch-typos who get our call wrong (and sometimes refuse to acknowledge
> the call correction), and occasionally get their own call wrong, forget
> the
> /P, send the wrong serial number (any digit wrong)
>
> 3) Sonically-challenged lids who start calling CQ on 'our' frequency with
> no
> QRL?, or who are selectively deaf if we respond to the QRL? with anything
> at
> all (you've got those already Alex, but how about letting us tell them to
> QSY, or QSY ourselves a bit to slide out of trouble, if there is room to
> move without colliding with someone else?)
>
> 4) Squinters - off-channel callers (MR does this well already, but
> sometimes
> they move frequency between overs to keep us on our toes!)
>
> 5) Red Zone callers who push the rig and amp to the very limits of
> performance and often well beyond.  Their sigs are as far from perfect
> sine
> waves as it is possible to get.  Raspy T1 notes, drifty wanderers,
> multiple-tones, we hear the lot in every Field Day and many fixed contests
> too, so it's not all down to battery power.
>
> 6) Dupes we've already worked already.  We have already worked them.  We
> have worked them before.  But still they keep calling back.
> 6a) Phantom Dupes who claim we've worked before, but haven't (often
> because
> of a busted QSO) ... and yes, this includes those who answer our CQs
> 6b) Phantom Dupes who want to correct the serial number they gave us one
> or
> two QSOs ago  [Alex, is it too difficult to be able to move the cursor up
> a
> few QSOs to correct the log?  Doing this well without messing up the QSO
> in
> progress is another hard-won contesting skill.]
>
> 7) Me Me's who try to complete a QSO even when we are quite clearly and
> adamantly working someone else, causing loads of QRM
>
> 8) Tone Deaf tuner-uppers who choose 'our' frequency to try to melt their
> PA
> valves
>
> 9) QRPers and DX callers who specialise in drifting vaguely around the
> noise
> floor
>
> 10)  Meter-misers whose electricity runs out half way through a QSO and
> suddenly go QRT (maybe to re-fill the generator?) leaving us hanging ...
>
> 11) CBers who want to tell us their name, rig, QSL info and so forth, and
> have no idea we are in a contest, nor what a contest is
>
> 12) Slotters who want us to QSY and work them on another band, often when
> there is no propagation
>
> 13)  Zero Beaters who call at exactly the same time and frequency as each
> other on each over
>
> 14) QLFs who send dots, dashes and other indeterminate bits and gaps in a
> random sequence not resembling any known Morse characters
>
> 15) Repeaters who send their calls several times, and sometimes our call
> too
> for good measure
>
> 16) Autobiographers who seem to want tell me their entire life stories:
> "G4iFB DE M0LID - TNX RPRT OM - UR RST 599 5NN 599 - OP HERE SIMON SIMON -
> QTH BIGGINSWADE - WX WET AND WINDY - GL IN CONTEST ..."
>
> 17) Life's-too-shorters who don't leave gapsbetweenwords, and even worse
> don't leave gaps between charactrz because it saves a few milliseconds
>
> 18) Gadget-boys who love to send 5NN and TEST at a zillion wpm but can't
> receive at the same speed
>
> 19) Strokers who try all possible variations of bits and spaces in a
> desperate attempt to send /P [after too few hours sleep, I'm usually in
> this
> category myself by Sunday morning!]
>
> 20) Breakers on QSK who drop bits into our stream in an attempt to stop us
> sending, but then get all mixed up when we actually stop for them
>
> One thing I've noticed in MR but almost never in Real Life is that if we
> send a partial call but the real caller doesn't respond, MR leaves us
> hanging in silence, listening to white noise, QRM and QRN.  In Real Live,
> usually, someone else will jump in to any gap within a short while with
> their own call, even though it bears no relation to the partial.  They
> usually call during the first quiet period more than a few milliseconds
> long, and almost always it's a complete free-for-all on the second partial
> attempt (as if we have just called CQ all over again).  Usually a "?" will
> coax them out of hiding if it all goes quiet, but not in MR.
>
> But the biggest request of all, Alex, is for a new mode: S&P
> (search-and-pounce).  I suspect even the biggest of monster stations with
> the most exotic callsigns don't CQ all the time but need to hunt around
> for
> new mults etc. from time to time.  There's definitely an art to S&P
> efficiently.  I have in mind a QSY facility that works just like the
> 'tuneable IF' idea you already have, perhaps, or else a pair of QSY
> up/down
> buttons.  Then we can zero beat on people calling CQ and try to work them.
>
> My trusty old Morse Machine runs the Doctor DX program to simulate
> contests.
> It lets you change bands, and makes a reasonable attempt to change the
> callers to reflect the different propagation on each band ... This maybe
> just a bit sophisticated for free MR but it's maybe another idea to
> consider.
>
> With all those wish-list items off my mind, let me just say that I am not
> trying to overload the poor programmer and certainly don't expect to see
> these wishes met unless others agree.  Most of all, I would hate to
> compromise MR's beautifully realistic audio simulation that beats any
> other
> morse sim I have *ever* used hands-down.  And all this for free!  Alex,
> you're a star.
>
> 73
> Gary
> G4iFB  (also the weaker half of G3GRS/P and an insignificant element of
> M6T
> GW8GT G0FBB/P XT2DX  GJ2A etc. etc.)
>
>
> [Non-text portions of this message have been removed]
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>

Alex wrote: ...versions of Morse Runner, you can trade the reaction time for
stable audio,
> please see the readme file for details. Most people who run MR on Win98
> increased the buffer size as instructed, and fixed the problem completely.
>
Thanks Alex.
I did some tests.
Buffer value --- Effect

1 --- No audio at all.
2 --- no audio at all.
3 --- some noise it seems qrm, no audible cw when press f1.
4 --- qrm with little interruption, little unreadable cw noise when press
f1.
5. qrm almost perfect, unreadable cw when press f1 or stations answer.

Can MR accepts higher value than 5? Readme.txt says no... I tried with 7 and
8 but nothing change. Is there some trick to do that?

Thanks again.
Gabriel - Iz4Apu.

hi Alex does ionoprobe
have a com object so it data can be used by other programs thanks for any info
n9mfk

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

[Non-text portions of this message have been removed]

Alex,

I am new to contesting, just read about MR in QST. Downloaded fine,
works ok. How do I respond to other station's request for my NR? TNX
Rob

Hi Rob,

To send your exchange to the calling station, enter the callsign in the Call
field and press the ';' button, or hit Enter, or press F5 (send his call)
and F2 (send exchange).


73 Alex VE3NEA



> Alex,
>
> I am new to contesting, just read about MR in QST. Downloaded fine,
> works ok. How do I respond to other station's request for my NR? TNX
> Rob

Hi Alex,

try to use HamCap, also in cojunction with Win-Test.
HAMCAP refuse to start giving out an error,
cliaming VOACAP is not installed.
I installed VOACAP as per isntructions, and all seems OK.
VOACAP itself is working OK.

VOACAP installed in C:\itshfbc
and Voacapw.exe is present in the directory bin_win.

Nevertheless HamCap send out a Warning when start

VOACAP v.3.082 or higher is required for this program
to run. Open the VOACAP download page?  YES/NO.

Hit NO
then

an error window pops-up:

Acces violation at address 0043338F in module 'HamCap.exe'
Read of address 0000014C.

OK

And stops.

Any hint please?

Bob, I2WIJ

Hi Bob,

When Voacap installs itself, it stores the path to its home directory in the
Registry under the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ITS
HF Propagation

The value name is InstallLocation.

Make sure that this value exists and that it points to the right directory
(C:\itshfbc in your case).

73 Alex VE3NEA



> Hi Alex,
>
> try to use HamCap, also in cojunction with Win-Test.
> HAMCAP refuse to start giving out an error,
> cliaming VOACAP is not installed.
> I installed VOACAP as per isntructions, and all seems OK.
> VOACAP itself is working OK.
>
> VOACAP installed in C:\itshfbc
> and Voacapw.exe is present in the directory bin_win.
>
> Nevertheless HamCap send out a Warning when start
>
> VOACAP v.3.082 or higher is required for this program
> to run. Open the VOACAP download page?  YES/NO.
>
> Hit NO
> then
>
> an error window pops-up:
>
> Acces violation at address 0043338F in module 'HamCap.exe'
> Read of address 0000014C.
>
> OK
>
> And stops.
>
> Any hint please?
>
> Bob, I2WIJ

Hi Alex,

thank for replying.
I checked the registry as you suggested but
info are there and they are correct.
I even retyped the path but no changes.

Any other thing I can do to overcome this situation?
Thanks for your cooperation.

73
Bob, I2WIJ

============ you wrote ==============
Hi Bob,

When Voacap installs itself, it stores the path to its home
directory in the
Registry under the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstal
l\ITS
HF Propagation

The value name is InstallLocation.

Make sure that this value exists and that it points to the right
directory
(C:\itshfbc in your case).

73 Alex VE3NEA

Alex,
I have noticed several times now that after a competition run I am
congratulated on a new record. Yet if I go to the Web Site the posted score
is higher then the one on my screen. I.E.: Web post score = 13356, my new
verified score = 12584.

Is this normal? Are others seeing this too?

Also, what happens if I do submit a lower score - do I lose points?

73 Eric - VE3GSI



[Non-text portions of this message have been removed]

High Morse Runner Score Guys - You know who you are!

Would it be possible for you top end fellows to share some knowledge with us
who are wishing to climb up the score chart?

What speeds, activities, pitch and filter settings are you high score ops
using?  How many years have you been on CW. How much practice time? etc...

I have been running at 33 WPM - Activity 3 to get 13356. Is this good - bad
- average?

73 Eric - VE3GSI



[Non-text portions of this message have been removed]

Bob,

A lot of things can go wrong with the VOACAP installation, though none of
those usually happens if the program is installed in a normal way:

- you may not have a privilege to read the Registry,

- the UninstallString value, in addition to InstallLocation, in the Registry
may be missing or may contain a wrong path;

- the file that specifies the program version,
C:\itshfbc\database\Version.w32, may be missing or otherwise unavailable, or
it may contain a wrong version number (on my system, it is "Version
05.0119W");

- the C:\itshfbc\antennas folder may be missing or marked as read-only, or
you may not have sufficient privileges to write to it;

- the same is true for C:\itshfbc\AREADATA and C:\itshfbc\RUN;

- the executable may be corrupted, or you may not have a privilege to run
it.



73 Alex VE3NEA







> Hi Alex,
>
> thank for replying.
> I checked the registry as you suggested but
> info are there and they are correct.
> I even retyped the path but no changes.
>
> Any other thing I can do to overcome this situation?
> Thanks for your cooperation.
>
> 73
> Bob, I2WIJ

Hi Eric,

This is fixed in v.1.52.

If you submit a score lower than already listed for your call, the
submission will be rejected.

73 Alex VE3NEA






> Alex,
> I have noticed several times now that after a competition run I am
> congratulated on a new record. Yet if I go to the Web Site the posted
> score
> is higher then the one on my screen. I.E.: Web post score = 13356, my new
> verified score = 12584.
>
> Is this normal? Are others seeing this too?
>
> Also, what happens if I do submit a lower score - do I lose points?
>
> 73 Eric - VE3GSI
>
>
>
> [Non-text portions of this message have been removed]
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>

Hi Eric,



I don't consider myself part of that elite (?) group. I'm a bit below it.
But here are my settings anyway. If they end up helping you out, great! :-)



I use 45wpm, an activity level of 3, with the bandwidth usually left at
400hz. Oh, and the "sidetone" is at 500z. I realize that all of these
settings, especially the sidetone, are highly subjective.



Unless I'm terribly mistaken, the QRM/QRN/QSB, LIDS, etc. settings can NOT
be customized when in the competition mode.



All of the above has gotten me to just under 240000, which I believe
currently translates to 156 or so on the list.



These are excellent questions, btw. And to be honest, I've been wanting to
ask them myself for quite some time ;)



As for your other questions, I've been licensed since '75 and CW has always
been relatively easy for me. That is, until I start venturing outside of
contest exchanges, hi! I've not had a station of my own since about '82 (I
get my fixes by doing the guest op thing) so things like MR are pretty much
my only way of keeping my skills/speed up to par. I tend to go through
phases. I'll sometimes do 2 one-hour sessions in an evening. Maybe even 3 if
it's a weekend with nothing going on. (Note that they're never
"back-to-back". I always leave a few hours in between them). Then, for some
unknown reason, I might just walk away from it all for as long as a month!



Go figure ;)



GL es 73!



Ian, K5ZM



   _____

From: dxatlas_group@yahoogroups.com [mailto:dxatlas_group@yahoogroups.com]
On Behalf Of Eric - VE3GSI
Sent: Tuesday, 05 July, 2005 9:24 AM
To: dxatlas_group@yahoogroups.com
Subject: [dxatlas] High Morse Runner Score Guys



High Morse Runner Score Guys - You know who you are!

Would it be possible for you top end fellows to share some knowledge with us
who are wishing to climb up the score chart?

What speeds, activities, pitch and filter settings are you high score ops
using?  How many years have you been on CW. How much practice time? etc...

I have been running at 33 WPM - Activity 3 to get 13356. Is this good - bad
- average?

73 Eric - VE3GSI



[Non-text portions of this message have been removed]




   _____

YAHOO! GROUPS LINKS



*  Visit your group "dxatlas_group
<http://groups.yahoo.com/group/dxatlas_group> " on the web.

*  To unsubscribe from this group, send an email to:
  dxatlas_group-unsubscribe@yahoogroups.com
<mailto:dxatlas_group-unsubscribe@yahoogroups.com?subject=Unsubscribe>

*  Your use of Yahoo! Groups is subject to the Yahoo!
<http://docs.yahoo.com/info/terms/>  Terms of Service.



   _____



[Non-text portions of this message have been removed]

Many thanks Alex,

I hadn't realized a new version was available. Got it!

Thanks for all the work you put in to Morse Runner, it is a great programme.

73 Eric.




-----Original Message-----
From: Alex, VE3NEA
Subject: Re: [dxatlas] Score new Record?

This is fixed in v.1.52.

Hi ALex,

answers inside your e-mail text:

from: "Alex, VE3NEA" <alshovk@...>
Date: Tue Jul 5, 2005  6:31 pm
Subject: Re: [dxatlas] HAMCAP do not start

Bob,

A lot of things can go wrong with the VOACAP
installation, though none of
those usually happens if the program is installed in a
normal way:

- you may not have a privilege to read the Registry,

===>NO, I have that privilege (I have admin
privileges)

- the UninstallString value, in addition to
InstallLocation, in the Registry
may be missing or may contain a wrong path;

===>What does that string have to contain?
===>mine has   something /remove

- the file that specifies the program version,
C:\itshfbc\database\Version.w32, may be missing or
otherwise unavailable, or it may contain a wrong
version number (on my system, it is "Version
05.0119W");

===>Also mine has same content;


- the C:\itshfbc\antennas folder may be missing or
marked as read-only, or
you may not have sufficient privileges to write to it;

===> it was marked as read-only; changed to read/write
with no different results

- the same is true for C:\itshfbc\AREADATA and
C:\itshfbc\RUN;

===> did the same; changed to read/write
with no different results

- the executable may be corrupted, or you may not have
a privilege to run
it.

===> I have privilege to run; executable is not
corrupt
  since VOACAP is working ok on its own.

Please any other hints??


73
Bob, I2WIJ

Bob,

> - the UninstallString value, in addition to
> InstallLocation, in the Registry
> may be missing or may contain a wrong path;
>
> ===>What does that string have to contain?
> ===>mine has   something /remove

This path to the Voacap folder in this value must be correct:

C:\itshfbc\Setup.exe /remove


73 Alex VE3NEA

Hello Alex, and the group; In my trusty old Win '98 machine running
BandMaster as the 'control pregram' klicking on the band map
frequencies on the left side, it dclares an "Unexpected Failure" with
a OK button -
OK,(not)..pressing button.. now the cursor drags the whole freq
display up & down with no mouse buttons at all. Going from band map to
Spot list and back to band list, a single klik will restore normal
function......until you klik on the frequency column again. Have tried
uninstall & back, but it still happens. FWIW, running on a fast new XP
machine and a slow laptop 98 work just fine.
HaruuummPh (clearing throat)..and also...running HamCAP, the 'Map' tab
view only shows the map filiing from upper left corner, about 4/5ths
the width,
and about 4/5ths down from the same corner. Looking in the 'config'
file, nothing really reaches out and kicks me, but perhaps something
in there can be reset?
      I must say, when entering the shack/shop here the suite of
programs offers a VERY quick look at propagation.
73's
Steve   KE8PA

Hi Eric.

> What speeds, activities, pitch and filter settings are you high
score ops
> using?  How many years have you been on CW. How much practice
time? etc...
>

My settings are:
CW Speed: 60 WPM
CW Pitch: 400 Hz
RX Bandwidth: 350 Hz
Activity: 4

> I have been running at 33 WPM - Activity 3 to get 13356. Is this
good - bad
> - average?

Frankly speaking your current result is average.
To improve speed I can suggest you a helpful exercise:
(exercise is based only on my own experience)
Since your normal speed is 33 WPM, run MR at 33+20=53WPM
and try to recognize callsigns.
Work on that speed for for about 5 minutes.
Then set 33+10=43WPM and work also for about 5 minutes.
After 53 WPM you will notice that 43 WPM is not too fast and
more or less acceptable.
Then reduce the speed to your normal value and you will notice how
slow it is! :) Run competition mode on 35-38WPM and you will break
20K points.

Take a look at my MR log and MP3 file.
http://www.qsl.net/rw3gu/morserunner.htm

73!
Valery, RW3GU

Hi Steve,

> Hello Alex, and the group; In my trusty old Win '98 machine running
> BandMaster as the 'control pregram' klicking on the band map
> frequencies on the left side, it dclares an "Unexpected Failure" with
> a OK button

You seem to have invalid settings in the Rig Settings dialog. Please
double-check them.


> HaruuummPh (clearing throat)..and also...running HamCAP, the 'Map' tab
> view only shows the map filiing from upper left corner, about 4/5ths
> the width

This happens  because you have a non-standard system font selected in your
screen settings, or a non-standard DPI. You can correct these settings in
the Windows Display Settings dialog.


In the future, please send your bug reports to my direct email. Remember
that the messages posted to this group are sent to all subscribers of the
group, most of them are not interested in the details specific to your
system.


73 Alex VE3NEA

ALEX,

IT WAS THAT!!

now it is working great!
Thanks a lot for your cooperation.
73
Bob, I2WIJ

--- In dxatlas_group@yahoogroups.com, "Alex, VE3NEA" <alshovk@d...>
wrote:
> Bob,
>
> > - the UninstallString value, in addition to
> > InstallLocation, in the Registry
> > may be missing or may contain a wrong path;
> >
> > ===>What does that string have to contain?
> > ===>mine has   something /remove
>
> This path to the Voacap folder in this value must be correct:
>
> C:\itshfbc\Setup.exe /remove
>
>
> 73 Alex VE3NEA

Did anybody develop IC-725.ini file?

73! Sergey/UA6LGO

Hi
New MR record audio:
http://www.qsl.net/rw3gu/morserunner.htm

73!
RW3GU

--- In dxatlas_group@yahoogroups.com, "rw3gu" <stopsmoke1@y...> wrote:

> New MR record audio:
> http://www.qsl.net/rw3gu/morserunner.htm

WOW!  Incredible job Valery!  Thank you for posting both your log and
the audio.  You must have the best ears in the world to pick out so
many calls in the QSB and QRN at 60 WPM!  And also my congratulations
on your very low error rate for those QRQ exchanges.

You are my hero OM!

73,  Bill  W4ZV