[PaQSO] Software Problem Found

[Don Reamer]

Yes, Mark, the last 5 lines should be 001100, 011110, 101010, 01101, 110011, 
which represent comma, dash, period, forward slash, and question mark. 
There should be 41 lines total.  26 lines represent the letters of the 
alphabet, 10 lines represent the numbers 0 thru 9, and 5 lines represent the 
punctuation marks.  Sorry if I was unclear on that.

Don - KA3JWE


----- Original Message ----- 
From: <vze3v8dt at verizon.net>
To: "Don Reamer" <donster at enter.net>
Sent: Thursday, September 22, 2005 4:20 PM
Subject: Re: [PaQSO] Software Problem Found


> Hey Don,
>
> Thanks for the email with the corrections!  I was manually updating the 
> files and just have a question about the code.txt file which should read 
> 101010 on the last line.  I did use Notepad to make the change.  Just 
> wanted to clarify, because on my file it looked like the last three or so 
> lines were maybe messed up.  Now, my last three lines are:
>
> 001100
> 011110
> 101010
>
> Is this correct or am I missing a line or two?   When I just checked the 
> code.txt file from last year's program it had two more lines after the 
> "101010" which included 01101 and 110011.
>
> Funny thing about manually changing one of the files.  I made the changes 
> with Notepad, then hit ESC, then was about to hit :wq and then ENTER. 
> Somewhere in the middle of that sequence I reallized "Oops, I'm not using 
> 'vi', I'm using a dumb Windows program instead!"  Glad I didn't corrupt it 
> more with my "trained" keystrokes.
>
> 73,
>
> Mark, NK8Q
>
>>From: Don Reamer <donster at enter.net>
>>Date: Thu Sep 22 14:20:44 CDT 2005
>>To: PAQSO Reflector <paqso at mailman.qth.net>
>>Subject: [PaQSO] Software Problem Found
>
>>Recently I was made aware of a problem with the 2005 version of my logging
>>software.  For some reason three (3) text support files were corrupted
>>during the compiling or packaging process.  Could have been a power hit or
>>computer hiccup while the process was running, I don't know.  Anyway, I 
>>have
>>re-compiled the installation package and updated my web page with the new
>>files.
>>
>>If you've downloaded and installed the 2005 version already, you have 
>>three
>>options to fix things.
>>
>>1. If you feel adventurous, you can edit the text files manually and fix 
>>the
>>corruption.  The files are cnty.txt, sect.txt, and code.txt and they are
>>located in the program's directory.  The errors in the files should be 
>>easy
>>to identify.  There are non-ASCII characters inserted in the text.  The
>>cnty.txt file is corrupt at the MOE line.  The correct list should be MIF,
>>MOE, MGY, MTR.  The sect.txt file is corrupt at the SD line.  The correct
>>list should be SDG, SD, SFL, SF.  The code.txt file is corrupt on the last
>>line and should read 101010.  If you do decide to edit manually, use an
>>editor like NOTEPAD that doesn't add any formatting when you save the 
>>files
>>otherwise it will really mess things up.
>>
>>2. You can download new files from my webpage (support_files.zip), unzip,
>>and overwrite the three files.
>>
>>3. You can delete the entire installation, download the new installation
>>files and re-install the entire program.
>>
>>Thanks to Tom, KS3N, for catching the problem.
>>
>>See... it pays to practice and experiment before the contest!
>>
>>Sorry for the inconvenience.
>>
>>Don - KA3JWE
>>
>>_______________________________________________
>>PaQSO mailing list
>>PaQSO at mailman.qth.net
>>http://mailman.qth.net/mailman/listinfo/paqso
>
>