[WriteLog] smirk test
w8wej at citynet.net
Fri Jun 15 07:46:38 PDT 2012
thanks so much Gary,,, I am making hard copies for my "write log"
binder and punching this in for future reference for those tests that WL
may not cover.
being beyond computer chalanged, I really appreciate the see spot, see
spot run instructions.. perfect for me
again many thanks 73 john
On 6/15/2012 04:31, Gary AL9A wrote:
> Your mention of a generic contest type module triggered my tired old brain
> cells. There is a module called DXpedition Mode that should do it for you.
> It accepts any band from 160M through 6M. You will need to modify the Entry
> window fields slightly to suit your needs.
> Go to Contest/Exchange Format Setup... When the window pops up asking if
> you want to initialize ALL fields in the exchange answer No. In the Edit
> QSO Exchange Fields window that opens do the following:
> Click on the COUNTRY field and clear the Prompt box. Click on Save.
> Click on the C field and clear the Prompt box. Click on Save.
> Click on the Name filed and clear the Prompt box. Click on Save.
> This will prevent these unneeded fields from showing in the Entry window.
> They will still be in the log, just not in the
> Entry window.
> Now create two new fields for the SMIRK contest.
> Go to the end of the field name list and click on New. In the Caption box
> type GRID. In the list of options for this field click on Prompt, No Space
> allowed and Required. Click on Save.
> Click on New again. In the Caption box type SMIRK. The SMIRK field is 6
> characters wide so if you need more field width just add spaces to the field
> name. I am unfamiliar with SMIRK numbers, but if it is a number only click
> on the box for Number. If it is an alpha numeric number leave the Number
> box unchecked. Now click on Prompt, No Space and Required. Now click on
> Save and OK.
> The Entry window will now be clear of the unnecessary Country, C and Name
> fields and you will now see the GRID and SMIRK fields instead. This should
> work for your log entries, but the score will be meaningless. Good luck.
> Gary AL9A
> ----- Original Message -----
> From: "john"<w8wej at citynet.net>
> To: "Gary AL9A"<al9a at mtaonline.net>
> Cc: "WriteLog Reflector"<writelog at contesting.com>
> Sent: June 14, 2012 1:17 PM
> Subject: Re: [WriteLog] smirk test
>> thanks , Gary for you kindness in responding--think I can sort of use
>> logger 32 for the exchange, which is mostly what I care about,,score is no
>> concern as not interested in submitting any thing.. appreciate your input
>> I would like to see write log with a generic contest type to allow for
>> this type of test.
>> 73 john w8wej
>> On 6/14/2012 20:49, Gary AL9A wrote:
>>> Not too many contest modules use grid squares in the exchange. The only
>>> two I can think of are the Stew Perry, which is 160M only, and the
>>> Makrothen, which is a RTTY contest. The Makrothen module is for 80M -
>>> 10M so I'm not sure it will accept entries for 6 meters in CW or SSB. If
>>> the Makrothen module will let you enter 6 meter contacts you could modify
>>> the input layout to add an additional field to record the SMIRK number
>>> part of the exchanges.
>>> Gary AL9A
>>> ----- Original Message ----- From: "john"<w8wej at citynet.net>
>>> To: "WriteLog Reflector"<writelog at contesting.com>
>>> Sent: June 14, 2012 9:42 AM
>>> Subject: [WriteLog] smirk test
>>>> I want to bang around in this to pick up new states and grids,,,I could
>>>> not find smirk as such,, any other log availible--dont care about
>>>> score-- thanks john w8wej
>>>> WriteLog mailing list
>>>> WriteLog at contesting.com
>>>> WriteLog on the web: http://www.writelog.com/
>>> No virus found in this message.
>>> Checked by AVG - www.avg.com
>>> Version: 2012.0.2180 / Virus Database: 2433/5069 - Release Date: 06/14/12
> WriteLog mailing list
> WriteLog at contesting.com
> WriteLog on the web: http://www.writelog.com/
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2012.0.2180 / Virus Database: 2433/5071 - Release Date: 06/15/12
More information about the WriteLog