initial commit

This commit is contained in:
Petr Hlozek 2013-03-15 21:13:08 +01:00
commit eff65a0d04
636 changed files with 745304 additions and 0 deletions

49
Makefile Normal file
View File

@ -0,0 +1,49 @@
CC=lazbuild
ST=strip
datadir = $(DESTDIR)/usr/share/cqrlog
bindir = $(DESTDIR)/usr/bin
sharedir = $(DESTDIR)/usr/share
cqrlog: src/cqrlog.lpi
$(CC) --ws=gtk2 src/cqrlog.lpi
$(ST) src/cqrlog
gzip tools/cqrlog.1 -c > tools/cqrlog.1.gz
clean:
rm -f -v src/*.o src/*.ppu src/*.bak src/lnet/lib/*.ppu src/lnet/lib/*.o src/lnet/lib/*.bak src/cqrlog src/cqrlog.compiled debian/cqrlog.* src/ipc/*.o src/ipc/*.ppu src/cqrlog.or
rm -rf debian/cqrlog
rm -f -v src/mysql/*.ppu src/mysq/*.bak src/mysql/*.o
rm -f -v tools/cqrlog.1.gz
install:
install -d -v $(bindir)
install -d -v $(datadir)
install -d -v $(datadir)/ctyfiles
install -d -v $(datadir)/help
install -d -v $(datadir)/help/img
install -d -v $(datadir)/members
install -d -v $(datadir)/xplanet
install -d -v $(datadir)/zipcodes
install -d -v $(datadir)/images
install -d -v $(sharedir)/pixmaps/cqrlog
install -d -v $(sharedir)/icons
install -d -v $(sharedir)/applications
install -d -v $(sharedir)/man/man1
install -v -m 0755 src/cqrlog $(bindir)
install -v -m 0755 tools/cqrlog-apparmor-fix $(datadir)/cqrlog-apparmor-fix
install -v -m 0644 ctyfiles/* $(datadir)/ctyfiles/
install -v -m 0644 help/img/* $(datadir)/help/img/
install -v -m 0644 help/*.* $(datadir)/help/
install -v -m 0644 members/* $(datadir)/members/
install -v -m 0644 xplanet/* $(datadir)/xplanet/
install -v -m 0644 zipcodes/* $(datadir)/zipcodes/
install -v -m 0644 images/* $(datadir)/images/
install -v -m 0644 tools/cqrlog.desktop $(sharedir)/applications/cqrlog.desktop
install -v -m 0644 images/cqrlog.png $(sharedir)/pixmaps/cqrlog/cqrlog.png
install -v -m 0644 images/cqrlog.png $(sharedir)/icons/cqrlog.png
install -v -m 0644 src/changelog.html $(datadir)/changelog.html
install -v -m 0644 tools/cqrlog.1.gz $(sharedir)/man/man1/cqrlog.1.gz
deb:
dpkg-buildpackage -rfakeroot -i -I
deb_src:
dpkg-buildpackage -rfakeroot -i -I -S

279
ctyfiles/Ambiguous.tbl Executable file
View File

@ -0,0 +1,279 @@
3D2
3Y1
3Y2
3Y3
3Y4
3Y5
3Y6
3Y7
3Y8
3Y9
3Y0
4D0
4E0
4F0
4G0
4H0
4I0
4N6
4O6
4U1
4U2
4U3
4U4
4U5
4U6
4U7
4U8
4U9
4U0
5J0
5K0
9M0
9M1
9M3
9M4
9M5
9M9
9W0
9W1
9W3
9W4
9W5
9W9
AH8
AX0
AX9
AY/Z
AZ/Z
BS7
BV9
BV0
CA9
CB9
CC9
CD9
CE9
CA0
CB0
CC0
CD0
CE0
CR0
DU0
DV0
DW0
DX0
DY0
DZ0
E50
E51
E52
E53
E54
E55
E56
E57
E58
E59
FO1
FO2
FO3
FO4
FO5
FO6
FO7
FO8
FO9
FO0
FT1
FT2
FT3
FT4
FT5
FT6
FT7
FT8
FT9
FT0
GB0
GB1
GB2
GB3
GB4
GB5
GB6
GB7
GB8
GB9
GB0
GE1
GE2
GE3
GE4
GE5
GE6
GE7
GE8
GE9
GE0
GG1
GG2
GG3
GG4
GG5
GG6
GG7
GG8
GG9
GG0
GO1
GO2
GO3
GO4
GO5
GO6
GO7
GO8
GO9
GO0
GQ1
GQ2
GQ3
GQ4
GQ5
GQ6
GQ7
GQ8
GQ9
GQ0
GR1
GR2
GR3
GR4
GR5
GR6
GR7
GR8
GR9
GR0
GV1
GV2
GV3
GV4
GV5
GV6
GV7
GV8
GV9
GV0
HJ0
HK0
II0
IO0
IQ0
IR0
IW0
J42004
JD1
KC4
KG4
KH8
L1/Z
L2/Z
L3/Z
L4/Z
L5/Z
L6/Z
L7/Z
L8/Z
L9/Z
L0/Z
LO/Z
LP/Z
LQ/Z
LR/Z
LS/Z
LT/Z
LU/Z
LV/Z
LW/Z
MB1
MB2
MB3
MB4
MB5
MB6
MB7
MB8
MB9
MB0
NH8
PP0
PQ0
PR0
PS0
PT0
PU0
PV0
PW0
PX0
PY0
R0
R1
R2
R3
R4
R5
R6
R7
R8
R9
TO1
TO2
TO3
TO4
TO5
TO6
TO7
TO8
TO9
TO0
TX1
TX2
TX3
TX4
TX5
TX6
TX7
TX8
TX9
TX0
VH9
VI9
VJ9
VK9
VL9
VM9
VN9
VH0
VI0
VJ0
VK0
VL0
VM0
VN0
VP6
VP8
VZ9
VZ0
WH8
YT6
YU6
YZ6
ZK1
ZV0
ZW0
ZX0
ZY0
ZZ0

5581
ctyfiles/AreaOK1RR.tbl Normal file

File diff suppressed because it is too large Load Diff

3890
ctyfiles/CallResolution.tbl Executable file

File diff suppressed because it is too large Load Diff

340
ctyfiles/Country.tab Executable file
View File

@ -0,0 +1,340 @@
1A|Sovereign Military Order of Malta|EU|-1|41.9055N|12.4808E|28|15|246||
1S|Spratly Islands|AS|-8|7.3734N|113.8223E|50|26|247||
3A|Monaco|EU|-1|43.75N|7.43E|27|14|260||
3B6|Agalega & Saint Brandon|AF|-4|10.3873S|56.6160E|53|39|4||
3B8|Mauritius|AF|-4|20.1649S|57.4968E|53|39|165||
3B9|Rodrigues Island|AF|-4|19.6824S|63.4176E|53|39|207||
3C|Equatorial Guinea|AF|-1|3.77N|8.79E|47|36|49||
3C0|Pagalu (Annobon) Island|AF|-1|1.4186S|5.6143E|52|36|195||
3D2|Fiji|OC|-12|18.1163S|178.4243E|56|32|176||
3D2(C)|Conway Reef (Ceva-I-Ra)|OC|-12|21.7389S|174.6397E|56|32|489||1989/01/01-
3D2(R)|Rotuma|OC|-12|12.4993S|177.0474E|56|32|460||1989/01/01-
3DA|Swaziland|AF|-2|26.32S|31.14E|57|38|468||
3V|Tunisia|AF|-1|36.85N|10.16E|37|33|474||
3W|Vietnam|AS|-7|21.04N|105.82E|49|26|293||
3X|Guinea|AF|0|9.54N|13.67W|46|35|107||
3Y(B)|Bouvet Island|AN|-1|54.4333S|3.4E|67|38|24||
3Y(P)|Peter I. Island|AN|4|68.812S|90.727W|72|12|199||
4J|Azerbaijan|AS|-4|40N|50E|29|21|18||
4L|Georgia|AS|-4|41.72N|44.79E|29|21|75||
4O|Montenegro|EU|-1|42.26N|19.2E|28|15|514||2006/06/28-
4S|Sri Lanka (Ceylon)|AS|-5.5|6.91N|79.91E|41|22|315||
4U(I)|ITU Geneva|EU|-1|46.2231N|6.1183E|28|14|117||
4U(U)|UN HQ ARC New York (USA)|NA|5|40.7506N|73.9683W|08|05|289||
4W|Timor Leste|OC|-9|8.5812S|125.5728E|54|28|511||2000/03/01-
4X|Israel|AS|-2|31.77N|35.19E|39|20|336||
5A|Libya|AF|-2|32.87N|13.18E|38|34|436||
5B|Cyprus|AS|-2|35.17N|33.38E|39|20|215||
5H|Tanzania|AF|-3|6.77S|39.25E|53|37|470||
5N|Nigeria|AF|-1|6.49N|3.37E|46|35|450||
5R|Madagascar (Malagasy Rep.)|AF|-3|18.92S|47.54E|53|39|438||
5T|Mauritania|AF|0|18.09N|15.89W|46|35|444||1960/06/20-
5U|Niger|AF|-1|13.52N|2.12E|46|35|187||1960/08/03-
5V|Togo|AF|0|6.18N|1.31E|46|35|483||
5W|Samoa|OC|-13|13.8326S|171.7507W|62|32|190||
5X|Uganda|AF|-3|0.32N|32.57E|48|37|286||
5Z|Kenya|AF|-3|1.28S|36.75E|48|37|430||
6W|Senegal|AF|0|14.69N|17.44W|46|35|456||1960/06/20-
6Y|Jamaica|NA|5|18.00N|76.81W|11|08|82||
7O|Yemen|AS|-3|15.36N|44.24E|39|21|492||1990/05/22-
7P|Lesotho|AF|-2|29.29S|27.48E|57|38|432||1981/01/01-
7Q|Malawi|AF|-2|13.99S|33.78E|53|37|440||
7X|Algeria|AF|-1|36.68N|3.15E|37|33|400||
8P|Barbados|NA|4|13.0919N|59.602411W|11|08|62||
8Q|Maldives|AS|-5|4.17N|73.50E|41|22|159||
8R|Guyana|SA|4|6.83N|58.16W|12|09|129||
9A|Croatia|EU|-1|45.80N|15.94E|28|15|497||1991/06/26-
9G|Ghana|AF|0|5.58N|0.20W|46|35|424||1957/03/05-
9H|Malta|EU|-1|35.90N|14.51E|28|15|257||
9J|Zambia|AF|-2|15.35S|28.32E|53|36|482||
9K|Kuwait|AS|-3|29.33N|47.97E|39|21|348||
9L|Sierra Leone|AF|0|8.50N|13.25W|46|35|458||
9M2|West Malaysia|AS|-8|3.53N|102.18E|54|28|299||1963/09/16-
9M6|East Malaysia|OC|-8|5.99N|116.03E|54|28|46||1963/09/16-
9N|Nepal|AS|-5.75|27.675N|85.342E|42|22|369||
9Q|Democratic Republic of the Congo|AF|-1|4.18S|15.21E|52|36|414||
9U|Burundi|AF|-2|3.31S|29.31E|52|36|404||1962/07/01-
9V|Singapore|AS|-8|1.30N|103.84E|54|28|381||1965/08/08-
9X|Rwanda|AF|-2|1.99S|30.09E|52|36|454||1962/07/01-
9Y|Trinidad & Tobago|SA|4|10.6672N|61.490707W|11|09|90||
A2|Botswana (Bechuanaland)|AF|-2|24.65S|25.92E|57|38|402||
A3|Tonga|OC|-13|21.1373S|175.216W|62|32|160||
A4|Oman|AS|-4|23.59N|58.55E|39|21|370||
A5|Bhutan|AS|-6|27.434N|89.676E|41|22|306||
A6|United Arab Emirates|AS|-4|24.47N|54.37E|39|21|391||
A7|Qatar|AS|-3|25.30N|51.50E|39|21|376||
A9|Bahrain|AS|-3|26.22N|50.58E|39|21|304||
AP|Pakistan|AS|-5|31.56N|74.35E|41|21|372||
BS7H|Scarborough (Huang Yan Dao) Reef|AS|-8|15.1833N|117.7667E|50|27|506||1995/01/01-
BV|Taiwan (Formosa)|AS|-8|25.04N|121.50E|44|24|386||
BV9P|Pratas (Tung Sha Dao) Island|AS|-8|20.7166N|116.7000E|44|24|505||1994/01/01-
BY|China|AS|-8|39.90N|116.43E|44|24|318||
C2|Nauru|OC|-12|0.55S|166.91E|65|31|157||
C3|Andorra|EU|-1|42.51N|1.52E|27|14|203||
C5|The Gambia|AF|0|13.46N|16.60W|46|35|422||
C6|Bahamas|NA|5|25.0088N|77.3087W|11|08|60||
C9|Mozambique|AF|-2|25.97S|32.58E|53|37|181||
CE|Chile|SA|4|33.46S|70.65W|14|12|112||
CE0(A)|Easter Islands (Rapa Nui)|SA|6|27.15S|109.43W|63|12|47||
CE0(X)|San Felix & San Ambrosio Islands|SA|4|26.27S|80.10W|14|12|217||
CE0(Z)|Juan Fernandez Islands|SA|4|33.61S|78.91W|14|12|125||
CE9|Antarctica|AN|0|80.3167S|81.25W|73|13|13||
CN|Morocco|AF|0|34.02N|6.84W|37|33|446||
CO|Cuba|NA|5|23.11N|82.41W|11|08|70||
CP|Bolivia|SA|4|16.49S|68.15W|12|10|104||
CT|Portugal|EU|0|38.707N|9.136W|37|14|272||
CT8|Azores Islands|EU|1|37.77N|25.67W|36|14|149||
CT9|Madeira Islands|AF|0|32.65N|16.91W|36|33|256||
CX|Uruguay|SA|3|34.88S|56.17W|14|13|144||
CY0|Sable Island|NA|4|43.9295N|59.9301W|09|05|211||
CY9|Saint Paul Island|NA|4|47.2103N|60.1616W|09|05|252||
D2|Angola|AF|-1|8.78S|13.24E|52|36|401||
D4|Cape Verde|AF|1|14.9357N|23.54659W|46|35|409||
D6|Comoros|AF|-3|11.71S|43.24E|53|39|411||1975/07/06-
DL|Federal Republic of Germany|EU|-1|52.52N|13.42E|28|14|230||1973/09/17-
DU|Philippines|OC|-8|14.63N|121.03E|50|27|375||
E3|Eritrea|AF|-3|15.34N|38.90E|48|37|51||-1962/11/14 1991/05/24-
E4|Palestine|AS|-2|31.30N|34.27E|39|20|510||1999/02/01-
E51(N)|North Cook Islands|OC|10|10.2476S|161.0237W|62|32|191||
E51(S)|South Cook Islands|OC|10|21.2251S|159.7856W|63|32|234||
E6|Niue|OC|11|19.0546S|169.923W|62|32|188||
E7|Bosnia-Herzegovina|EU|-1|43.86N|18.43E|28|15|501||1991/10/15-
EA|Spain|EU|-1|41.416N|3.70W|37|14|281||
EA6|Balearic Islands|EU|-1|39.59N|2.66E|37|14|21||
EA8|Canary Islands|AF|0|28.47N|16.26W|36|33|29||
EA9|Ceuta & Melilla|AF|-1|35.97N|5.47W|37|33|32||
EI|Ireland|EU|0|53.35N|6.10W|27|14|245||
EK|Armenia|AS|-4|40.18N|44.52E|29|21|14||
EL|Liberia|AF|0|6.30N|10.79W|46|35|434||
EP|Iran|AS|-3.5|35.71N|51.43E|40|21|330||
ER|Moldova|EU|-2|47.00N|28.50E|29|16|179||
ES|Estonia|EU|-2|59.44N|24.75E|29|15|52||
ET|Ethiopia|AF|-3|9.02N|38.75E|48|37|53||
EU|Belarus|EU|-2|53.89N|27.59E|29|16|27||
EX|Kyrgyzstan|AS|-6|42.90N|74.60E|31|17|135||
EY|Tadzhikistan|AS|-5|38.58N|68.76E|30|17|262||
EZ|Turkmenistan|AS|-5|38.00N|58.35E|30|17|280||
F|France|EU|-1|48.86N|2.36E|27|14|227||
FG|Guadeloupe Island|NA|4|15.9977N|61.718W|11|08|79||
FH|Mayotte|AF|-3|12.7792S|45.2135E|53|39|169||
FJ|Saint Barthelemy (Saint Bart's) Island|NA|4|17.8976N|62.8282W|11|08|516||2007/12/14-
FK|New Caledonia|OC|-11|22.3730S|166.4787E|56|32|162||
FK(C)|Chesterfield Islands|OC|-11|20.1749S|158.6848E|56|30|512||2000/03/23-
FM|Martinique|NA|4|14.6006N|61.00759W|11|08|84||
FO|French Polynesia|OC|10|17.54S|149.5681W|63|32|175||
FO(A)|Austral Islands|OC|10|22.27S|151.18W|63|32|508||1998/04/01-
FO(C)|Clipperton Island|NA|8|10.3104N|109.2264W|10|07|36||
FO(M)|Marquesas Islands|OC|9.5|8.56S|140.50W|63|31|509||1998/04/01-
FP|Saint Pierre & Miquelon|NA|3|46.7887N|56.1953W|09|05|277||
FR|Reunion|AF|-4|21.15S|55.56E|53|39|453||1960/06/25-
FS|Saint Martin Island|NA|4|18.0888N|63.0484W|11|08|213||
FT(G)|Glorioso Island (Isles Glorieuses)|AF|-4|11.5775S|47.2972E|53|39|99||
FT(J)|Juan de Nova, Europa|AF|-3|17.0564S|42.7388E|53|39|124||
FT(T)|Tromelin Island|AF|-4|15.8873S|54.5209E|53|39|276||
FT(W)|Crozet Island|AF|-5|46.4232S|51.7696E|68|39|41||
FT(X)|Kerguelen Islands|AF|-5|49.35S|70.2167E|68|39|131||
FT(Z)|Amsterdam & Saint Paul Islands|AF|-5|37.8441S|77.5564E|68|39|10||
FW|Wallis & Futuna Islands|OC|-12|13.315S|176.16W|62|32|298||
FY|French Guiana|SA|3|6.83N|58.16W|12|09|63||
G|England|EU|0|51.53N|0.12W|27|14|223||
GD|Isle of Man|EU|0|54.17N|4.50W|27|14|114||
GI|Northern Ireland|EU|0|54.61N|5.92W|27|14|265||
GJ|Jersey|EU|0|49.20N|2.11W|27|14|122||
GM|Scotland|EU|0|55.88N|4.23W|27|14|279||
GU|Guernsey|EU|0|49.47N|2.56W|27|14|106||
GW|Wales|EU|0|51.48N|3.18W|27|14|294||
H4|Solomon Islands|OC|-11|9.44S|159.96E|51|28|185||
H40|Temotu Province|OC|-11|10.71S|166.0E|51|32|507||1998/04/01-
HA|Hungary|EU|-1|47.52N|19.06E|28|15|239||
HB|Switzerland|EU|-1|46.20N|6.14E|28|14|287||
HB0|Liechtenstein|EU|-1|47.15N|9.53E|28|14|251||
HC|Ecuador|SA|6|0.19S|78.49W|12|10|120||
HC8|Galapagos Islands|SA|6|0.84S|91.05W|12|10|71||
HH|Haiti|NA|5|18.54N|72.32W|11|08|78||
HI|Dominican Rep.|NA|4|18.49N|69.91W|11|08|72||
HK|Colombia|SA|5|4.61N|74.08W|12|09|116||
HK0(A)|San Andres & Providencia|NA|5|12.59N|81.71W|11|07|216||
HK0(M)|Malpelo Island|SA|5|3.9752N|81.5993W|12|09|161||
HL|South Korea|AS|-9|37.58N|127.00E|44|25|137||
HP|Panama|NA|5|8.97N|79.55W|11|07|88||
HR|Honduras|NA|6|14.096N|87.20W|11|07|80||
HS|Thailand|AS|-7|13.75N|100.52E|49|26|387||
HV|Vatican|EU|-1|41.9023N|12.4533E|28|15|295||
HZ|Saudi Arabia|AS|-3|26.30N|50.00E|39|21|378||
I|Italy|EU|-1|41.90N|12.50E|28|15|248||
IS|Sardinia|EU|-1|40.000N|9.000E|28|15|225||
J2|Djibouti|AF|-3|11.60N|43.14E|48|37|382||
J3|Grenada|NA|4|12.0546N|61.7338W|11|08|77||
J5|Guinea Bissau|AF|0|11.90N|15.61W|46|35|109||
J6|Saint Lucia|NA|4|14.0078N|60.9835W|11|08|97||
J7|Dominica|NA|4|15.2847N|61.3858W|11|08|95||
J8|Saint Vincent & Grenadines|NA|4|13.2058N|61.2622W|11|08|98||
JA|Japan|AS|-9|35.70N|139.80E|45|25|339||
JD1(M)|Minami Torishima (Marcus Island)|OC|-10|24.29N|153.98E|90|27|177||
JD1(O)|Ogasawara (Bonin & Volcano Isl., Iwo Jima)|AS|-9|24.79N|141.34E|45|27|192||
JT|Mongolia|AS|-7|47.89N|106.98E|32-33|23|363||1993/01/01-
JW|Spitsbergen (Svalbard)|EU|-1|78.23N|15.57E|18|40|259||
JX|Jan Mayen Island|EU|1|70.98N|8.08W|18|40|118||
JY|Jordan|AS|-2|32.02N|35.98E|39|20|342||
KG4|Guantanamo Bay|NA|5|20.14N|75.20W|11|08|105||
KH0|Mariana Islands|OC|-10|15.179N|145.7546E|64|27|166||
KH1|Baker & Howland Islands|OC|12|0.8044N|176.616W|61|31|20||
KH2|Guam|OC|-10|13.467N|144.7476E|64|27|103||
KH3|Johnston Islands|OC|10|16.7388N|169.5183W|61|31|123||
KH4|Midway Island|OC|11|28.2337N|177.3693W|61|31|174||
KH5|Palmyra, Jarvis Islands|OC|11|5.8799N|162.0759W|61-62|31|197||
KH5(K)|Kingman Reef|OC|11|6.3711N|162.4110W|61|31|134||
KH6|Hawaii|OC|10|21.33N|157.84W|61|31|110||
KH7(K)|Kure Island|OC|10|28.4164N|178.3279W|61|31|138||
KH8|American Samoa|OC|11|14.2793S|170.7008W|62|32|9||
KH8(S)|Swain's Island|OC|11|11.0575S|171.0780W|62|32|515||2006/07/22-
KH9|Wake Island|OC|-12|19.298N|166.6307E|65|31|297||
KL|Alaska|NA|8|61.00N|149.00W|1|01|6||1960/08/16-
KP1|Navassa Island|NA|5|18.4012N|75.0098W|11|08|182||
KP2|Virgin Islands|NA|4|18.3445N|64.9318W|11|08|285||
KP4|Puerto Rico|NA|4|18.4195N|66.0353W|11|08|202||
KP5|Desecheo Island|NA|4|18.3846N|67.4806W|11|08|43||1979/03/01-
LA|Norway|EU|-1|59.94N|10.69E|18|14|266||
LU|Argentina|SA|3|34.61S|58.40W|14|13|100||
LX|Luxembourg|EU|-1|49.62N|6.13E|27|14|254||
LY|Lithuania|EU|-2|54.41N|25.19E|29|15|146||
LZ|Bulgaria|EU|-2|42.70N|23.31E|28|20|212||
OA|Peru|SA|5|12.04S|77.05W|12|10|136||
OD|Lebanon|AS|-2|33.91N|35.49E|39|20|354||
OE|Austria|EU|-1|48.20N|16.37E|28|15|206||
OH|Finland|EU|-2|60.17N|24.94E|18|15|224||
OH0|Aland Islands|EU|-2|60.14N|19.87E|18|15|5||
OJ0|Market Reef|EU|-2|60.3067N|19.1417E|18|15|167||
OK|Czech Republic|EU|-1|50.07N|14.42E|28|15|503||1993/01/01-
OM|Slovakia|EU|-1|48.16N|17.13E|28|15|504||1993/01/01-
ON|Belgium|EU|-1|50.86N|4.32E|27|14|209||
OX|Greenland (Kalaallit Nunaat)|NA|3|64.25N|51.71W|05|40|237||
OY|Faeroe Islands|EU|0|62.02N|6.77W|18|14|222||
OZ|Denmark|EU|-1|55.67N|12.57E|18|14|221||
P2|Papua New Guinea|OC|-10|9.47S|147.135E|51|28|163||1975/09/16-
P4|Aruba|SA|4|12.5246N|70.2675W|11|09|91||1986/01/01-
P5|North Korea|AS|-9|39.03N|125.74E|44|25|344||1995/05/14-
PA|Netherlands|EU|-1|52.38N|4.88E|27|14|263||
PJ2|Curacao|SA|4|12.1034N|68.9342W|11|09|517||2010/10/10-
PJ4|Bonaire|SA|4|12.2287N|68.3301W|11|09|520||2010/10/10-
PJ6|Saint Eustatius and Saba|NA|4|17.6372N|63.230661W|11|08|519||2010/10/10-
PJ7|Sint Maarten|NA|4|18.0255N|63.0461W|11|08|518||2010/10/10-
PY|Brazil|SA|3|23.33S|46.36W|15|11|108||
PY0(F)|Fernando de Noronha|SA|2|3.864S|32.3755W|13|11|56||
PY0(S)|Saint Peter & Saint Paul Rocks|SA|2|0.9512N|29.3695W|13|11|253||
PY0(T)|Trindade & Martim Vaz Islands|SA|2|20.5154S|29.3162W|15|11|273||
PZ|Suriname|SA|3|5.83N|55.16W|12|09|140||
R1(F)|Franz Josef Land, [Russian Territory] (FJ)|EU|-3|80.788N|50.4864E|75|40|61||
S0|Western Sahara|AF|0|27.16N|13.20W|37|33|302||
S2|Bangladesh (East Pakistan)|AS|-6|23.71N|90.407E|41|22|305||
S5|Slovenia|EU|-1|46.06N|14.50E|28|15|499||1991/06/26-
S7|Seychelles|AF|-4|4.63S|55.44E|53|39|379||
S9|Sao Tome & Principe|AF|0|0.307N|6.9318E|47|36|219||
SM|Sweden|EU|-1|59.33N|18.063E|18|14|284||
SP|Poland|EU|-1|52.24N|21.03E|28|15|269||
ST|Sudan|AF|-3|15.62N|32.52E|48|34|466||
SU|Egypt|AF|-2|30.0572N|31.227E|38|34|478||
SV|Greece|EU|-2|38.00N|23.75E|28|20|236||
SV(A)|Mount Athos|EU|-2|40.16N|24.33E|28|20|180||
SV5|Dodecanese|EU|-2|36.20N|28.00E|28|20|45||
SV9|Crete|EU|-2|35.30N|25.00E|28|20|40||
T2|Tuvalu|OC|-12|8.5234S|179.1822E|65|31|282||1976/01/01-
T30|West Kiribati|OC|-12|1.8804N|172.9856E|65|31|301||
T31|Central Kiribati|OC|-13|4.5291S|172.1838W|62|31|31||
T32|East Kiribati|OC|-14|1.9631N|157.3651W|61|31|48||1981/01/01-
T33|Banaba (Ocean) Island|OC|-12|0.88S|169.55E|65|31|490||
T5|Somalia|AF|-3|2.05N|45.28E|48|37|232||
T7|San Marino|EU|-1|43.94N|12.44E|28|15|278||
T8|Republic of Palau (Belau)|OC|-9|7.506N|134.62E|64|27|22||1994/01/01-
TA|Turkey|AS|-2|39.93N|32.84E|39|20|390||
TF|Iceland|EU|0|64.14N|21.92W|17|40|242||
TG|Guatemala|NA|6|14.64N|90.53W|11|07|76||
TI|Costa Rica|NA|6|9.93N|84.08W|11|07|308||
TI9|Cocos Island|NA|6|5.53N|87.06W|11|07|37||
TJ|Cameroon|AF|-1|3.88N|11.51E|47|36|406||
TK|Corsica|EU|-1|41.94N|8.73E|28|15|214||
TL|Central African Republic|AF|-1|4.42N|18.61E|47|36|408||1960/08/13-
TN|Congo|AF|-1|0.00S|15.63E|52|36|412||1960/08/15-
TR|Gabon|AF|-1|0.42N|9.40E|52|36|420||1960/08/17-
TT|Chad|AF|-1|12.16N|15.09E|47|36|410||1960/08/11-
TU|Ivory Coast|AF|0|5.33N|4.05W|46|35|428||1960/08/07-
TY|Benin (Dahomey)|AF|-1|6.49N|2.63E|46|35|416||1960/08/01-
TZ|Mali|AF|0|12.64N|7.99W|46|35|442||1960/06/20-
UA(AS)|Russia (Asiatic)|AS|-7|56.03N|93.05E|32|18|15||
UA(EU)|Russia (European)|EU|-4|56.00N|38.00E|29|16|54||
UA(K)|Kaliningrad (Koenigsberg)|EU|-2|54.427N|20.3058E|29|15|126||
UK|Uzbekistan|AS|-5|41.26N|69.22E|30|17|292||
UN|Kazakhstan|AS|-5|43N|77E|29-31|17|130||
UT|Ukraine|EU|-2|50.20N|30.33E|29|16|288||
V2|Antigua, Barbuda|NA|4|17.0974N|61.8298W|11|08|94||
V3|Belize|NA|6|17.30N|88.81W|11|07|66||
V4|Saint Kitts, Nevis|NA|4|17.2711N|62.7049W|11|08|249||1958/06/01-
V5|Namibia|AF|-1|22.56S|17.10E|57|38|464||
V6|Federated States of Micronesia|OC|-10|5.3495N|162.9756E|65|27|173||1981/01/01-
V7|Marshall Islands|OC|-12|16.68N|168.54E|65|31|168||
V8|Brunei Darussalam|OC|-8|4.95N|114.94E|54|28|345||
VE|Canada|NA|5|45.41N|75.65W|04|04|1||
VK|Australia|OC|-10|35.27S|149.13E|59|30|150||
VK0(H)|Heard Island|AN|-5|53.1176S|73.5500E|68|39|111||
VK0(M)|Macquarie Island|AN|-11|54.6167S|158.85E|60|30|153||1963/09/16-
VK9(C)|Cocos (Keeling) Islands|OC|-6.5|12.4000S|96.8352E|54|29|38||
VK9(L)|Lord Howe Island|OC|-10.5|31.53231S|159.03809E|60|30|147||
VK9(M)|Mellish Reef|OC|-10|17.4398S|155.8609E|56|30|171||
VK9(N)|Norfolk Island|OC|-11.5|29.0548S|167.9667E|60|32|189||
VK9(W)|Willis Island|OC|-10|16.1133S|150.0324E|55|30|303||
VK9(X)|Christmas Islands|OC|-7|10.4470S|105.6892E|54|29|35||
VP2E|Anguilla|NA|4|18.2254N|63.0633W|11|08|12||
VP2M|Montserrat|NA|4|16.6799N|62.2005W|11|08|96||
VP2V|British Virgin Islands|NA|4|18.4115N|64.6127W|11|08|65||
VP5|Turks & Caicos Islands|NA|5|21.47N|72.17W|11|08|89||
VP6|Pitcairn Island|OC|8|25.0672S|130.1019W|63|32|172||
VP6(D)|Ducie Atoll|OC|8|24.682S|124.7887W|63|32|513||2001/11/16-
VP8(F) VP8|Falkland Islands|SA|4|51.67S|57.89W|16|13|141||
VP8(G)|South Georgia (San Pedro) Islands|AN|2|54.2815S|36.508W|73|13|235||
VP8(H)|South Shetland Islands|AN|4|62.9833S|60.5667W|73|13|241||
VP8(O)|South Orkney Islands|AN|3|60.7167S|45.6W|73|13|238||
VP8(S)|South Sandwich Islands|AN|2|59.4212S|27.2304W|73|13|240||
VP9|Bermuda|NA|4|32.3032N|64.7980W|11|05|64||
VQ9|Chagos (Diego Garcia Isl.)|AF|-6|7.3220S|72.4226E|41|39|33||
VR|Hong Kong|AS|-8|22.31N|114.17E|44|24|321||
VU|India|AS|-5.5|28.63N|77.18E|41|22|324||
VU(A)|Andaman & Nicobar Islands|AS|-5.5|11.6672N|92.7629E|49|26|11||
VU(L)|Laccadive Islands (Lakshadweep)|AS|-5.5|10.9394N|72.2914E|41|22|142||
W|United States|NA|5|40.72N|74.06W|08|05|291||
XE |Mexico|NA|6|19.48N|99.13W|10|06|50||
XF4|Revilla Gigedo|NA|7|18.7928N|110.973W|10|06|204||
XT|Burkina Faso (Upper Volta)|AF|0|12.39N|1.54W|46|35|480||1960/08/16-
XU|Cambodia (Kampuchea)|AS|-7|11.52N|104.89E|49|26|312||
XW|Laos|AS|-7|18.00N|102.62E|49|26|143||
XX|Macao|AS|-8|22.20N|113.55E|44|24|152||
XZ|Myanmar (Burma)|AS|-6.5|16.81N|96.14E|49|26|309||
YA|Afghanistan|AS|-4.5|34.53N|69.16E|40|21|3||
YB|Indonesia|OC|-7|6.19S|106.84E|54|28|327||1963/05/01-
YI|Iraq|AS|-3|33.31N|44.37E|39|21|333||
YJ|Vanuatu (New Hebrides)|OC|-11|17.7107S|168.7330E|56|32|158||
YK|Syria|AS|-2|33.51N|36.28E|39|20|384||
YL|Latvia|EU|-2|56.57N|24.06E|29|15|145||
YN|Nicaragua|NA|6|12.15N|86.27W|11|07|86||
YO|Romania|EU|-2|44.43N|26.11E|28|20|275||
YS|El Salvador|NA|6|13.70N|89.22W|11|07|74||
YU|Serbia|EU|-1|44.80N|20.47E|28|15|296||
YV|Venezuela|SA|4.5|10.50N|66.93W|12|09|148||
YV0|Aves Island|NA|4|15.7243N|63.6547W|11|08|17||
Z2|Zimbabwe (Southern Rhodesia)|AF|-2|17.82S|31.04E|53|38|452||
Z3|Macedonia|EU|-1|42.00N|21.45E|28|15|502||1991/09/08-
Z8|Republic of South Sudan|AF|-3|4.85N|31.61E|48|34|521||2011/07/14-
ZA|Albania|EU|-1|41.33N|19.82E|28|15|7||
ZB|Gibraltar|EU|-1|36.14N|5.35W|37|14|233||1975/07/06-
ZC4|Cyprus UK Sovereign Base|AS|-2|34.67N|32.92E|39|20|283||1960/08/16-
ZD7|Saint Helena Island|AF|0|15.925S|5.7036W|66|36|250||
ZD8|Ascension Island|AF|0|7.948S|14.3623W|66|36|205||
ZD9|Tristan da Cunha & Gough Islands|AF|0|37.3038S|12.5099W|66|38|274||
ZF|Cayman Islands|NA|5|19.33N|81.21W|11|08|69||
ZK3|Tokelau Island|OC|-13|9.1819S|171.8207W|62|31|270||
ZL|New Zealand|OC|-12|36.83S|174.73E|60|32|170||
ZL7|Chatham Island|OC|-12.75|43.8500S|176.5533W|60|32|34||
ZL8|Kermadec Island|OC|-12|29.2459S|177.9268W|60|32|133||
ZL9|Auckland, Campbell Islands|OC|-12|50.5447S|166.2086E|60|32|16||
ZP|Paraguay|SA|4|25.28S|57.63W|14|11|132||
ZS|South Africa|AF|-2|25.74S|28.20E|57|38|462||
ZS(M)|Prince Edward & Marion Islands|AF|-3|46.9125S|37.7436E|57|38|201||

62
ctyfiles/CountryDel.tab Executable file
View File

@ -0,0 +1,62 @@
1B9|Blenheim Reef|AF|-5|5.21S|72.28E|41|39|23|D|-1975/07/01
1G5|Geyser Reef|AF|-3|12.33S|46.32E|53|39|93|D|-1978/03/01
1M4|Minerva Reef|OC|12|23.38S|179.55E|62|32|178|D|-1972/10/16
4W1 4W[02-9]|Yemen Arab Republic|AS|-3|15N|44E|39|21|154|D|-1990/05/21
7J1(O)|Okino Tori-shima (Parece Vela - Douglas Reef)|AS|-10|30N|140E|45|27|194|D|1976/05/30-1980/11/30
8Z4|Saudi Arabia/Iraq Neutral Zone|AS|-3|29.12N|46.52E|39|21|226|D|-1981/12/25
8Z5 9K3|Kuwait/Saudi Arabia Neutral Zone|AS|-3|29.5N|47E|39|21|68|D|-1969/12/14
9S4|Saar|EU|-1|49.25N|6.98E|28|14|210|D|-1957/03/31
9U5|Ruanda-Urundi|AF|-3|1.99S|30.09E|52|36|208|D|1960/07/01-1962/06/30
A1|Abu Ail, Jabal at Tair|AS|-2|14.0783N|42.8145E|39|21|2|D|-1991/03/30
AC3|Sikkim|AS|-5.5|27.5N|88.5E|41|22|231|D|-1975/04/30
AC4|Tibet|AS|-6|32.3N|86E|41|23|268|D|-1974/05/30
C9|Manchuria|AS|-8.5|32N|90E|33|24|164|D|-1949/12/31
CN2|Tangier|AF|0|35.79N|5.80W|37|33|264|D|-1960/06/30
CR8 CR10|Portuguese Timor|OC|-8|10S|128E|54|28|200|D|-1976/09/15
CR8(D)|Damao, Diu|AS|-5.5|20.71N|70.99E|41|22|42|D|-1961/06/30
CR8(G)|Goa|AS|-5.5|15.37N|74.04E|41|22|101|D|-1961/06/30
DL D[ACIJKM]|Germany|EU|-1|52N|7E|28|14|81|D|-1973/09/16
DM DT Y[2-9]|German Democratic Republic|EU|-1|52N|7E|28|14|229|D|1973/09/17-1990/10/02
EA9|Ifni (Rio de Oro)|AF|0|32S|11W|37|33|113|D|-1969/05/13
FF|French West Africa|AF|0|4S|15E|46|35|59|D|-1960/08/16
FH(C) FH FB8|Comoros|AF|-3|11.71S|43.24E|53|39|39|D|1960/06/01-1975/07/05
FI8|French Indo-China|AS|-7|10N|106.7E|49|26|58|D|-1950/12/20
FN8|French India|AS|-5.5|19N|72.8E|41|22|67|D|-1954/10/31
FQ8|French Equatorial Africa|AF|-1|12N|15W|47;52|36|57|D|-1960/08/16
HK0(B)|Bajo Nuevo|NA|5|15.8510N|79.2903W|11|08|19|D|-1981/08/17
HK0(S) KS4|Serrana Bank & Roncador Cay|NA|5|13.9814N|80.5787W|11|07|228|D|-1981/08/16
I1 MF2|Trieste|EU|-1|45.4N|13.4E|28|15|271|D|-1957/05/31
I5|Italian Somaliland|AF|-3|2N|46E|48|37|115|D|-1960/06/30
JZ0|Netherlands N. Guinea|OC|-10|9.4S|147.1E|51|28|184|D|-1963/04/30
KR(O)|Okinawa (Ryukyu Is)|OC|-8|26.23N|127.71E|45|25|193|D|-1972/05/14
J9|Okinawa (Ryukyu Is)|OC|-8|26.23N|127.71E|45|25|193|D|-1948/12/31
KS4(B) KS4 KP3|Swan Island|NA|6|17.2N|83.6W|11|7|261|D|-1972/08/31
KZ5 KZ0|Canal Zone|NA|5|8.99N|79.573W|11|7|28|D|-1979/09/30
OK O[L-M]|Czechoslovakia|EU|-1|49N|20E|28|15|218|D|-1992/12/31
P2 VK9|Papua Territory|OC|-10|9.4S|147.1E|51|28|198|D|-1975/09/15
P2 VK9|Territory of New Guinea|OC|-10|9.4S|147.1E|51|28|267|D|-1975/09/15
PJ2|Netherlands Antilles, Curacao|SA|4|12.1034N|68.9342W|11|09|85|D|-2010/10/09
PJ7|Sint Maarten|NA|4|18.0255N|63.0461W|11|08|255|D|-2010/10/09
PK1 PK[2-3]|Java|OC|-7.5|5.3S|159.5E|54|28|119|D|-1963/05/01
PK4|Sumatra|OC|-7|0.4N|100.2E|54|28|258|D|-1963/05/01
PK5|Dutch Borneo|OC|-8|0.4N|115E|54|28|183|D|-1963/05/01
PK6|Celebes & Molucca Islands|OC|-8|2N|120E|54|28|30|D|-1963/05/01
R1(M)|Malyj Vysotskij Island, [Russian Territory] (MV)|EU|-3|60.6361N|28.5635E|29|16|151|D|-2012/02/17
ST0 6[T-U]0 SS0|Southern Sudan|AF|-3|5N|32E|47-48|34|244|D|-1994/12/31
UN1|Karelo-Finnish Republic|EU|-4|61.44N|34.23E|19|16|128|D|-1960/06/30
VO|Newfoundland, Labrador|NA|3.5|47.57N|52.72W|9|02;05|186|D|-1949/03/31
VQ1 5H1|Zanzibar|AF|-3|6.16S|39.20E|53|37|307|D|-1974/05/31
VQ6 MD4 MS[460]|British Somaliland|AF|-3|2N|46E|48|37|26|D|-1960/06/30
VQ9(A)|Aldabra Isl.|AF|-4|9.4231S|46.3318E|53|39|8|D|-1976/06/28 1976/06/29-=379
VQ9(D)|Desroches Isl.|AF|-4|5.6833S|53.6833E|53|39|44|D|-1976/06/28 1976/06/29-=379
VQ9(F)|Farquhar Isl.|AF|-4|10.1917S|51.1069E|53|39|55|D|-1976/06/28 1976/06/29-=379
VS2 9M2|Malaya|AS|-7.5|3.53N|102.18E|54|28|155|D|-1963/09/15
VS4|Sarawak|AS|-8|2.1S|113E|54|28|220|D|-1963/09/15
VS9A VS9[PS]|Peoples Dem. Rep. of Yemen|AS|-3|13N|45.2E|39|21|243|D|-1990/05/21
VS9H|Kuria Muria Is.|AS|-4|17.52N|56.03E|39|21|139|D|-1967/11/29
VS9K|Kamaran Is.|AS|-3|15.45N|42.62E|39|20|127|D|-1982/03/10
ZC5|British North Borneo & Labuan|OC|-8|0.4N|115E|54|28|25|D|-1963/09/15
ZC6 ZC8 4X1|Palestine|AS|-2|31.30N|34.27E|39|20|196|D|-1968/06/30
ZD4|Gold Coast, Togoland|AF|0|5N|0W|46|35|102|D|-1957/03/05
ZS(P)|Penguin Island|AF|-2|27.00S|15.19E|57|38|493|D|-1994/02/28
ZS(W)|Walvis Bay|AF|-2|22.94S|14.51E|57|38|488|D|1977/09/01-1994/02/28

82
ctyfiles/Exceptions.tbl Normal file
View File

@ -0,0 +1,82 @@
1B
1C
1D
1E
1F
1G
1H
1I
1J
1K
1L
1M
1N
1O
1P
1Q
1R
1T
1U
1V
1W
1X
1Y
2K
AS
AT
AU
AV
BF
BL
BM
BS
DA
DB
DC
DD
DE
DF
DG
DH
DI
DJ
DK
DM
DN
DO
DP
DQ
DR
FF
FN
GC
JE
JP
JR
JS
LH
LP
LS
LT
LV
LW
MA
MG
MR
MT
MY
ND
RA
RD
RE
RI
RT
RU
RV
RW
RZ
SA
SJ
TC
TS
XA

BIN
ctyfiles/MASTER.DTA Normal file

Binary file not shown.

44228
ctyfiles/MASTER.SCP Normal file

File diff suppressed because it is too large Load Diff

99
ctyfiles/README Executable file
View File

@ -0,0 +1,99 @@
Country files README
====================
The country file set for CQRLOG is distributed in a tar.gz archive with an
unique name, ie. cqrlog-cty120812.tar.gz. The number (here 120812) denotes
version number which is the same as the release date.
Contents of the country file set (8 files):
AreaOK1RR.tbl (a file containing call areas, provinces, districts etc.)
CallResolution.tbl (a file containing call exceptions)
Country.tab (the main country list)
CountryDel.tab (a list of deleted countries)
iota.tbl (the IOTA list)
Exceptions.tbl (a list of two-character appendices which should be ignored,
ie. DL1ABC/LH is still Germany, not Norway)
Ambiguous.tbl (a list of ambiguous prefixes)
README (this file)
Since version 0.4.0 (2008-06-21) CQRLOG has an auto update option which provides
date/version country file check at the program startup. We recommend to enable
this option (Preferences -> Program). If your CQRLOG tends to perform repetitive
update on every startup, please check timestamp of this files in /ctyfiles
directory:
CallResolution.tbl
Country.tab
AreaOK1RR.tbl
Try to delete file cqrlog-cty.tar.gz from ctyfiles directory, run CQRLOG again
and confirm auto upgrade. It should help. You can also move all files from the
'ctyfiles' folder to another directory and run CQRLOG again. Allow to perform
the update cycle, CQRLOG should then run as usual.
The geographic coordinates using the WGS 84 (World Geodetic System). A Decimal
Notation is used, NOT (!!!) minutes/seconds!
NOTES:
=====
There are several operations which are not accepted for DXCC. Along with known
'ungood' ones there are stations permanently or very frequently operating aboard
a ship (ship museums, they using very usual call signs like K2AA or DF0MV).
Other known not accepted ones are operations from drifting ice, artic ski
expeditions and similar event stations. Its 'bad' DXCC status cannot be easily
verified, anyway such stations are not from rare countries so we expect (and
recommend) to use another station for an award application.
Manual country files update
===========================
1. Unpack and copy all files into the /home/~/.config/cqrlog/ctyfiles folder.
The purpose of this folder is to store the files only, it is not bound to the
CQRLOG and does not affect its function.
2. Start the CQRLOG and select the 'Show QSO list' from the 'File' item in the
main menu. You can go there also using shortcut Ctrl-O.
3. If you are already in the QSO list, go there to menu. Click the 'File' item,
then the 'Import' option. Choose the DXCC data option, located at lowest
position. A dialog appears, navigate to your /home/~/.config/cqrlog/ctyfiles
folder. Click the 'Open' button. All files are read and if the import completes,
a small window with the progress bar disappears. The update is finished.
Note:
=====
While opening your new country files [see 3.], you dont need to open a
particular files. The 'Open' button starts a procedure which reads ALL files in
the /ctyfiles folder.
Important:
==========
Don't attempt to create your own country files. This can result in program crash
or incorrect statistics. If you find an incorrectly resolved station (no matter
if current log or and old record), send a not directly to me: martin@ok1rr.com.
Replace ALWAYS all files in the /ctyfiles folder! If you leave an older file and
try only a single file from the new version, the resulting tables will became
out-of-sync which ends with incorrect statistics. Also, the logger may not work
properly.
NEW LOG FILE - you can create a new log file where you can import ADIF format
QSO data. If you do this, import the most fresh country files set BEFORE any
ADIF QSO data import!
The best way is to erase all files in the /ctyfiles folder and copy the 8 files
from your new archive.
*********************************************************************
* If you update your contry files or upgrade the CQRLOG version, *
* ALWAYS perform the 'Rebuild DXCC statistics' which is accessible *
* from the QSO list screen. *
*********************************************************************
BACKUP your data often! BACKUP your log file at the end of ANY session!
All what you need to backup and store in a safe place is the folder
/home/~/.config/cqrlog/database.
(~ means your user name)

66691
ctyfiles/eqsl.txt Normal file

File diff suppressed because it is too large Load Diff

1176
ctyfiles/iota.tbl Executable file

File diff suppressed because it is too large Load Diff

58093
ctyfiles/lotw1.txt Normal file

File diff suppressed because it is too large Load Diff

29292
ctyfiles/qslmgr.csv Normal file

File diff suppressed because it is too large Load Diff

252
debian/changelog vendored Normal file
View File

@ -0,0 +1,252 @@
cqrlog (1.5.4-1) unstable; urgency=low
* added MASTER.SCP file
-- Petr Hlozek <petr@ok2cqr.com> Sun, 24 FEB 2012 10:30:00 +0100
cqrlog (1.5.3-1) unstable; urgency=low
* added support for Super Check Partial
* added Tune function (for WinKeyerUSB and cwdaemon), hotkey
CTRL+T
* added Repair table function to database connection window
(Utils button)
* improved export for QSL labels printing (labels are sorted
by dxcc, you can choose what fields will be be printed)
* updated membership tables
* fiexd program crash when editing DX cluster information
* CW keys window doesn't show caption for F9 and F10 keys
* ADIF export ignored delimitter in TX_PWR (0.5 was exported
as 05)
* CQRLOG killed rigctld even when autostart was disabled
* double click to spots listed with SH/DX didn't work
* QSO list window showed filter is enabled after reopen
(filter was disabled)
* login to eQSL with password containing special character
didn't work
* when QSO passed over the midnight, the qso was saved with
wrong date
-- Petr Hlozek <petr@ok2cqr.com> Sun, 24 FEB 2012 10:30:00 +0100
cqrlog (1.5.2-1) unstable; urgency=low
* added CTRL+W hotkey to send spots to dxcluster
* DX cluster shows also country name next to the spot
(must be enabled in Prefereces)
* international characters in New QSO window should work again
* DX spots with freq eqauls to the start of the band (21.000,
14.000 etc., usually notes) are ignored
* HamQTH added to dx clusters list
* fixed reading A-index (was 1 even when actually was 10)
* /MM, /AM and stations with unknown DXCC country didn't appear
in bandmap
* database update hangs
* fixed xml request address of qrz.com
* DXCC CFM count function didn't uses eQSL cfm QSO
* fixed reading mode from FT-920 (returned MEMO as VFO)
* fixed bug in dxcluster caused program crashed randomly
* program didn't apply eQSL rcvd when the band was in lowercase
-- Petr Hlozek <petr@ok2cqr.com> Mon, 8 OCT 2012 19:01:00 +0100
cqrlog (1.5.1-1) unstable; urgency=low
* fixed program crash when scrolling down in QSO list window
* Clear new QSO window after significant freq change option
removed
-- Petr Hlozek <petr@ok2cqr.com> Sun, 5 AUG 2012 19:01:00 +0100
cqrlog (1.5.0-1) unstable; urgency=low
* brand new user friendly TRX control settings
* user can change freq in drop down list in new qso window
* clear RIT after saving QSO added
* clear New QSO window after significant freq change option
added
* remove dupes from the log function added
* native support of connection to MySQL server 5.5
* sh/dx cluster command fill the bandmap
* members database updated
* country tables updated
* program hangs when LoTW password was wrong or server
was down
* wrong freq caused program crash with unfriendly message
* dx cluster autologin didin't work when the prompt was
"Please enter your call:"
* after save QSO got endtime and start date not end date
* 5MHz band is not visible even if is checked in
Preferences -> Bands
* program crashed after editing QSO from QSO list window
(edit, close window, hit enter) - fixed
* station with /P, /M, KH6/ etc. get his original QTH and grid from
callbook - fixed
* Database update function fixed
-- Petr Hlozek <petr@ok2cqr.com> Sun, 29 JUL 2012 19:00:00 +0100
cqrlog (1.4.2-1) unstable; urgency=low
* removed ScrollWidth from lbPreferences
-- Petr Hlozek <petr@ok2cqr.com> Sun, 05 MAY 2012 19:00:00 +0100
cqrlog (1.4.1-1) unstable; urgency=low
* keys in CW Fx window also send CW messages
* error after click to "Station list" button in WAS
statistic - fixed
* wrong US state was marked like AL in WAS statistic - fixed
* fixed TRX control
* after change TRX name in Preference, the description in TRX
window wasn't changed - fixed
* number of cfm DXCC in mode table was the same like in total
DXCC cfm - fixed
* fixed problem with null comamnds in WKUSB communication
-- Petr Hlozek <petr@ok2cqr.com> Sat, 04 MAY 2012 20:30:00 +0100
cqrlog (1.4.0-1) unstable; urgency=low
* freq is displayed in 10Hz resolution instead of 100Hz
* Country name field into QSO list added
* added OR symbol into QSL_S combo box (Online Request)
* OK, Cancel and other buttons in filter window moved to the
right to reduce window height
* rig control rewrited to use rigctld
* LoTW/eQSL users has the same background color also in bandmap
* IOTA information inserted from HamQTH callbook
* eQSL import error log is now stored into user's home directory
* added CTRL+I hotkey for ADIF import function (in New QSO window)
* you can set different background color for eQSL and LoTW users
* power wasn't imported from ADIF file - fixed
* QSLR field was sometimes empty even if QSO was confirmed - fixed
-- Petr Hlozek <petr@ok2cqr.com> Sat, 27 APR 2012 20:30:00 +0100
cqrlog (1.3.1-2) unstable; urgency=low
* rebuild for Ubuntu 12.04
-- Petr Hlozek <petr@ok2cqr.com> Fri, 24 FEB 2012 22:30:00 +0100
cqrlog (1.3.1-1) unstable; urgency=low
* CQRLOG won't run on Ubuntu 12.04 - fixed
* previous qso for callsign with / didn't work when
"In previous QSO list show also QSO with call/p " option
enabled - fixed
-- Petr Hlozek <petr@ok2cqr.com> Tue, 21 FEB 2012 20:30:00 +0100
cqrlog (1.3.0-1) unstable; urgency=low
* full eQSL support added (filter, statistics, export, import ...)
* DXCC, WAS, WAC, ITU, WAZ and IOTA statistic improved
* export QSO to CSV file for SOTA website added
* option to show previous QSO with station that was /p, /m etc added
* program now takes UTC time from the computer time
* added new column "qslr" into QSO list where you can see symbols for
paper QSL confirmed, LoTW and eQSL together
* refresh button to propagation window added
* files with LoTW and eQSL users list are part of DXCC tables
* export in SQL console crashed when the field was NULL - fixed
* qrz.com button fixed
* database update didn't affect QTH field - fixed
* height and width was saved also for dialog (non-sizeable)
windows - fixed
* xplanet config file was always overwriten - fixed
* GF in propagation windows was empty - fixed
* QSL manager search in QSO list window didn't work - fixed
* MM and AM station didn't get to bandmap - fixed
-- Petr Hlozek <petr@ok2cqr.com> Sat, 21 JAN 2012 20:00:00 +0100
cqrlog (1.2.2-2) unstable; urgency=low
* debian/control: fixed alternative dependency order for lazarus, lcl
(Closes: #652176)
-- Kamal Mostafa <kamal@whence.com> Thu, 15 Dec 2011 15:00:53 -0800
cqrlog (1.2.2-1) unstable; urgency=low
* FREQ field added to ADIF export for LoTW
* ROS mode added
* new Ubuntu scrollbars disabled (a lot of problems solved)
* after chnge to another log, QTH profile remained the same - fixed
* QSO from ADIF with freq over 147MHz were refused - fixed
-- Petr Hlozek <petr@ok2cqr.com> Sun, 23 OCT 2011 11:00:00 +0100
cqrlog (1.2.1-1) unstable; urgency=low
* HamQTH.com integration improved
* qrz.com XML search fixed
-- Petr Hlozek <petr@ok2cqr.com> Sun, 31 Jul 2011 10:00:00 +0100
cqrlog (1.2.0-1) unstable; urgency=low
* HamQTH.com XML search added
* after View QSO New QSO window remained in readonly mode - fixed
* CTRL+F2 hotkey didn't work in New QSO window - fixed
* DELETE statement wasn't supported in SQL console - fixed
* in Remote mode when time pass the midnight hour date remain
the same - fixed
* program crashed after attempt to edit QSO when log was in
remote mode - fixed
* ADIF import crashed when QSO had wrong freq or band - fixed
* LoTW statistic always showed 0 confirmed countries - fixed
-- Petr Hlozek <petr@ok2cqr.com> Thu, 28 Jul 2011 16:00:00 +0100
cqrlog (1.1.0-1) unstable; urgency=low
* qrz.com XML search function added (Preferences -> Callbook)
* RST format is not changing when Automode is disabled
* big square statistic added
-- Petr Hlozek <petr@ok2cqr.com> Thu, 23 Jun 2011 19:30:00 +0100
cqrlog (1.0.2-1) unstable; urgency=low
* ADIF import fixed
-- Petr Hlozek <petr@ok2cqr.com> Sat, 11 Jun 2011 11:20:00 +0100
cqrlog (1.0.1-1) unstable; urgency=low
* backup into the same file option added
* ADIF export speed-up
* loading MySQL libraries on Debian unstable and Fedora 15 - fixed
* initial Debian release (Closes: #629587)
-- Petr Hlozek <petr@ok2cqr.com> Fri, 10 Jun 2011 19:30:00 +0100
cqrlog (1.0.0-1) unstable; urgency=low
* CQRLOG is now package ready (now deb packages for Ubuntu and Debian only)
* native 32bit and 64bit versions
* support multiple logs
* membership (> 70 clubs, 5 of them can be processed simultaneously) is tracked
by membership number (if a club doesn't have numbers, callsign is used)
* config file is stored directly to the main database. If a log is opened on
another computer, the settings will remain the same
* other windows (Grayline, Detail info, DX cluster etc.) auto-opened only if they
were previously opened in running CQRLOG which was properly (regularly) closed
* new faster ADIF import
* CQRLOG can be used on local computer with MySQL embedded or on a MySQL server,
CQRLOG can be run on another (remote) machine
* echo for telnet DX cluster added (the sent-out command is also displayed in DX
cluster window)
* clear log function added (in database connection window all log data can be
erased but the log file is not deleted)
* new About window added
* changelog in html format added
* membership databases updated
* manual page added
-- Petr Hlozek <petr@ok2cqr.com> Tue, 7 Jun 2011 20:05:00 +0100

1
debian/compat vendored Normal file
View File

@ -0,0 +1 @@
7

20
debian/control vendored Normal file
View File

@ -0,0 +1,20 @@
Source: cqrlog
Section: hamradio
Priority: extra
Maintainer: Debian Hamradio Maintainers <debian-hams@lists.debian.org>
Uploaders: Petr Hlozek <petr@ok2cqr.com>, Kamal Mostafa <kamal@whence.com>
Build-Depends: debhelper (>= 7), lazarus (>= 0.9.29) | lazarus-0.9.30, lcl (>= 0.9.30) | lcl-0.9.30, fp-utils, fp-units-misc, fp-units-gfx, fp-units-gtk, fp-units-db, libhamlib-dev (>= 1.2.10)
Standards-Version: 3.9.3
Homepage: http://www.cqrlog.com
Package: cqrlog
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, libssl-dev, mysql-server, mysql-client, libhamlib2 (>= 1.2.10), libhamlib-utils (>= 1.2.10)
Description: Advanced logging program for hamradio operators
CQRLOG is an advanced ham radio logger based on MySQL embedded database.
Provides radio control based on hamlib libraries (currently support of 140+
radio types and models), DX cluster connection, HamQTH/QRZ callbook (XML access),
a grayliner, internal QSL manager database support and a most accurate country
resolution algorithm based on country tables developed by OK1RR.
CQRLOG is intended for daily general logging of HF, CW & SSB contacts and
strongly focused on easy operation and maintenance.

174
debian/copyright vendored Normal file
View File

@ -0,0 +1,174 @@
This package was debianized by Petr Hlozek <petr@ok2cqr.com> on
Sat, 11 Jul 2011 19:50:00 +1.
Upstream Author: Petr Hlozek <petr@ok2cqr.com>
Copyright:
The main cqrlog source code is:
* Copyright (c) 2011 Petr Hlozek
* All rights reserved.
and is distributed under the GNU General Public License
(version 2 or later), which is available
in /usr/share/common-licenses/GPL-2
Copyright:
Source code of a part of Synapse (network communication, serial port classes) :
* Copyright (c)1999-2006, Lukas Gebauer
* All rights reserved.
Synapse is distributed under the following terms:
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
Neither the name of Lukas Gebauer nor the names of its contributors
may be used to endorse or promote products derived from this software
without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
“AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS
OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
It was downloaded from http://www.ararat.cz/synapse/doku.php/download
Copyright:
RegExp.pas file which contains classes for regular expression:
* Copyright (c) 1999-2004 Andrey V. Sorokin, St.Petersburg, Russia
* All rights reserved.
is distributed under the following terms:
You may use this software in any kind of development,
including comercial, redistribute, and modify it freely,
under the following restrictions :
1. This software is provided as it is, without any kind of
warranty given. Use it at Your own risk.The author is not
responsible for any consequences of use of this software.
2. The origin of this software may not be mispresented, You
must not claim that You wrote the original software. If
You use this software in any kind of product, it would be
appreciated that there in a information box, or in the
documentation would be an acknowledgement like
Partial Copyright (c) 2004 Andrey V. Sorokin
http://RegExpStudio.com
mailto:anso@mail.ru
3. You may not have any income from distributing this source
(or altered version of it) to other developers. When You
use this product in a comercial package, the source may
not be charged seperatly.
4. Altered versions must be plainly marked as such, and must
not be misrepresented as being the original software.
5. RegExp Studio application and all the visual components as
well as documentation is not part of the TRegExpr library
and is not free for usage.
It was downloaded from http://RegExpStudio.com
Copyright:
Source code of a part of lNet library (telnet communication routines):
* CopyRight (C) 2004-2008 Ales Katona
* All rights reserved.
Distributed under the GNU General Public License (version 2),
which is available in /usr/share/common-licenses/GPL-2
with this addon:
The source code of the Lightweight Network library are
distributed under the Library GNU General Public License
which is available in /usr/share/common-licenses/GPL-2
with the following modification:
- object files and libraries linked into an application may be
distributed without source code.
The unit tomwinsock.pas is EXLUDED from both the GPL and this addon license.
It is distributed under the terms of BSD license.
Copyright (c) The Regents of the University of California.
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
3. Neither the name of the University nor the names of its contributors
may be used to endorse or promote products derived from this software
without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.
It was downloaded from http://lnet.wordpress.com/download/
Copyright:
IPC communication routines:
* Copyright (c) 1999-2004 by the Free Pascal development team
* All rights reserved.
This is the file COPYING.FPC, it applies to the Free Pascal Run-Time Library
(RTL) and packages (packages) distributed by members of the Free Pascal
Development Team.
The source code of the Free Pascal Runtime Libraries and packages are
distributed under the Library GNU General Public License
(see the file COPYING) with the following modification:
As a special exception, the copyright holders of this library give you
permission to link this library with independent modules to produce an
executable, regardless of the license terms of these independent modules,
and to copy and distribute the resulting executable under terms of your choice,
provided that you also meet, for each linked independent module, the terms
and conditions of the license of that module. An independent module is a module
which is not derived from or based on this library. If you modify this
library, you may extend this exception to your version of the library, but you are
not obligated to do so. If you do not wish to do so, delete this exception
statement from your version.
If you didn't receive a copy of the file COPYING, contact:
Free Software Foundation, Inc.
51 Franklin St, Fifth Floor
Boston
MA 02110-1301, USA
it was downloaded from http://www.freepascal.org/download.var

0
debian/docs vendored Normal file
View File

1
debian/files vendored Normal file
View File

@ -0,0 +1 @@
cqrlog_1.2.0-1_amd64.deb hamradio extra

5
debian/postinst vendored Normal file
View File

@ -0,0 +1,5 @@
#!/bin/sh
set -e
/usr/share/cqrlog/cqrlog-apparmor-fix
#DEBHELPER#

30
debian/postrm vendored Normal file
View File

@ -0,0 +1,30 @@
#!/bin/bash
set -e
FILE=/etc/apparmor.d/usr.sbin.mysqld
FTMP=`mktemp /tmp/tmp.XXXXXX`
if [ -f $FILE ]
then
if `cat $FILE | grep -q -E '\@\{HOME\}\/\.config\/cqrlog\/database\/\*\*\ rwk\,'`
then
LINES=`cat $FILE | grep -n @{HOME}/.config/cqrlog/database/** | sed 's/\:.*//'`
LINES1=$((LINES-1))
LINES2=$((LINES+1))
head $FILE -n $LINES1 > $FTMP
tail $FILE -n +$LINES2 >> $FTMP
cat $FTMP > $FILE
echo ""
echo Changes removed from $FILE
echo ""
if which invoke-rc.d >/dev/null 2>&1; then
invoke-rc.d apparmor restart
else
/etc/init.d/apparmor restart
fi
else
echo ""
echo Changes from $FILE already removed
echo ""
fi
fi
rm $FTMP
#DEBHELPER#

13
debian/rules vendored Executable file
View File

@ -0,0 +1,13 @@
#!/usr/bin/make -f
# -*- makefile -*-
# Sample debian/rules that uses debhelper.
# This file was originally written by Joey Hess and Craig Small.
# As a special exception, when this file is copied by dh-make into a
# dh-make output file, you may use that output file without restriction.
# This special exception was added by Craig Small in version 0.37 of dh-make.
# Uncomment this to turn on verbose mode.
#export DH_VERBOSE=1
%:
dh $@

1
debian/source/format vendored Normal file
View File

@ -0,0 +1 @@
3.0 (quilt)

3
debian/watch vendored Normal file
View File

@ -0,0 +1,3 @@
version=3
http://www.cqrlog.com/deb_src/index.php cqrlog_(.+).tar.gz

75
help/cwd.html Normal file
View File

@ -0,0 +1,75 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html lang="en-us"><head>
<title>CQRLOG - Statistics</title></head>
<body><table border="0" cellpadding="5" cellspacing="2" width="100%"><tbody><tr><td valign="top"><img src="img/exc.png"></td><td align="justify" bgcolor="ffffcc" valign="top"><strong><font color="red">WARNING!</font></strong>
Backup your data often! BACKUP your log file at the end of ANY session!
All what you need to backup and store in a safe place is the main log
database cqrlog.fdb located in the /log_data folder.</td></tr></tbody></table>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td align="left" width="33%">&nbsp;&lt;<a href="h26.html"> Prev</a></td>
<td align="center" width="33%">[<a href="index.html#aa">Menu</a>]</td>
<td align="right" width="33%"><a href="h26.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
<div style="text-align: left;"><strong>CQRLOG for LINUX by OK2CQR &amp; OK1RR</strong></div>
<p align="center"><img src="img/line.png"></p>
<strong>cwdaemon setup</strong><br><br>
<div align="justify">The cwdaemon is very good software trick which does good job if you build your own kernel and you also don't need to fire it up separately with root privileges if you have an addition in your start-up scripts.<br><br>
<strong>Poor sounding CW </strong><br><br>
Sloppy CW from the cwdaemon it depends on kernel settings. I tested it thoroughly because I love CW at higher speeds. Latency of 1000 Hz helped a bit, I was able to run at usual contest speeds up to 36 wpm. Since kernel 2.6.23 the problem seems cured with tickless kernel. Here is an excerpt from my config:</div>
<pre>
# # Processor type and features #
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_SMP=y
CONFIG_X86_PC=y
....</pre>
<div align="justify">Now I can go up to 60 WPM and the resulting CW is excellent, however I'm using cwdaemon 0.9.4beta1. Versions below 0.8 are actually useless, the worst CW I ever heard was produced by cwdaemon 0.5 and an unmodified kernel.<br><br>
The newest cwdaemon 0.9.4 depends on the unixcw version 2.3 (or above) which won't compile on my Slackware (and I was not patient enough to track all the dependencies), therefore not tested. Let me believe that the new dependency was a bad step back... I hope that new versions of cwdaemon will continue the way set by the 0.9.4beta1 version (source download here). Anyway, with this version of cwdaemon and custom made kernel 2.6.23 (and higher) I am fully satisfied. I am convinced that any development of CW related software should be thoroughly consulted with high speed freaks, it is rather bad if a developer or tester means he did well if he is limited by 25 WPM... <br><br></div>
<strong>Start-up without root privileges </strong><br><br>
<div align="justify">There is no need to start the cwdaemon separately with root privileges. Put a little addition to your start-up script and cwdaemon will start without any keystroke. It is a good solution for a ham radio machine, however you may have some problems if you want to evaluate your parallel port for printing or other purposes. <br><br>
I added two simple blocks to the <font face=Courier,Courier New>/etc/rc.d/rc.local</font> which applies to Slackware GNU/Linux, however your preferred distribution may use another name and location.<br><br>
The first block is used to load parport and parport_pc modules whioch are essential to the cwdaemon. The second block actually loads the cwdaemon. First, it stops the module which can occupy your parallel port - here it was cups. cwdaemon also won't work if lp module is loaded, so unload it if necessary. Next, a device node is created and cwdaemon is loaded.</div>
<pre>#load parport, parport_pc
modprobe parport
modprobe parport_pc
# Load cwdaemon
echo "starting cwdaemon"
/etc/rc.d/rc.cups stop
# rmmod lp
cd /dev
mknod -m 0660 parport0 c 99 0
/usr/local/sbin/cwdaemon -x n </pre>
Remember the cwdaemon options:<br><br>
<img src="img/cwdaem.png"><br><br>
I find useful to start the cwdaemon without any sidetone, it seems much better to use the sidetone of your radio rather than the PC speaker.
<p align="center"><img src="img/line.png"></p>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td align="left" width="33%">&nbsp;&lt;<a href="h26.html"> Prev</a></td>
<td align="center" width="33%">[<a href="index.html#aa">Menu</a>]</td>
<td align="right" width="33%"><a href="h26.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
</body></html>

233
help/h1.html Normal file
View File

@ -0,0 +1,233 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
<title>CQRLOG - Preferences</title>
</head>
<body><table border="0" cellpadding="5" cellspacing="2" width="100%"><tbody><tr><td valign="top"><img src="img/exc.png"></td><td bgcolor=#ffffcc valign="top" align="justify"><strong><font color="red">WARNING!</font></strong> Backup your data often! BACKUP your log file at the end of ANY session! All what you need to backup and store in a safe place is the main log database cqrlog.fdb located in the /log_data folder.</td></tr></tbody></table>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="index.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h20.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
<div style="text-align: left;"><strong>CQRLOG for LINUX by OK2CQR &amp; OK1RR</strong></div>
<p align=center><img src=img/line.png></p>
<h2><strong>Preferences</strong></h2>
<div align=justify>The first step you need is to set up your log preferences. From logging window, choose the 'File' menu item and 'Options' (or Ctrl-P].<br><br>
<img src=img/h2.png border=0>
<br><br>
A multitab window appears, allowing setup of following parameters:<br>
<ul style="margin-left: 40px;">
<li><a href="h1.html#ah2">Program</a></li>
<li><a href="h1.html#ah3">Station</a></li>
<li><a href="h1.html#ah4">New QSO</a></li>
<li><a href="h1.html#ah5">Visible columns</a></li>
<li><a href="h1.html#ah6">Bands</a></li>
<li><a href="h1.html#ah7">TRX Control</a></li>
<li><a href="h1.html#ah8">Modes</a></li>
<li><a href="h1.html#ah9">QTH Profiles</a></li>
<li><a href="h1.html#ah10">Export</a></li>
<li><a href="h1.html#ah11">DX Cluster</a></li>
<li><a href="h1.html#ah12">Fonts</a></li>
<li><a href="h1.html#ah13">WAZ, ITU Zones</a></li>
<li><a href="h1.html#ah14">IOTA</a></li>
<li><a href="h1.html#ah15">Membership</a></li>
<li><a href="h1.html#bh1">Bandmap</a></li>
<li><a href="h1.html#bh2">xplanet support</a></li>
<li><a href="h1.html#bh3">Zip code tracking</a></li>
<li><a href="h1.html#bh4">LoTW support</a></li>
<li><a href="h1.html#ch1">CW interface</a></li>
<li><a href="h1.html#ch2">fldigi interface</a></li>
<li><a href="h1.html#ch3">Auto backup</a></li>
<li><a href="h1.html#ch4">External viewers</a></li>
</ul>
<h2><strong>Preferences</strong></h2>
The first tab of the 'Preferences' card is labelled 'Program'. Here is the setup of main program behaviour.<br><br>
<a name=ah2><h2><strong>Program</strong></h2></a>
<img src=img/h5.png border=0>
<br><br>
The <strong>Internet connection</strong> is important to those who is behind a proxy. The data to fill does not need further explanation, hopefully. Check the box above if you don't need an internet connection - CQRLOG attempts to connect if you try to connect to the DX Cluster (either via web or telnet) and/or if you hit F6 to access the QRZ.COM callbook data.
<br><br>
Other settings are:<br><br>
<strong>UTC offset</strong> - you need to set up your time difference to UTC. We needed this to enable CQRLOG to run properly with minimalistic desktop managers which may/may not set the time properly depending on your time zone and possibly the Daylight Save Time. KDE and Gnome providing this.
<br><br>
<strong>Grayline offset</strong> - you need to set up your time difference to UTC to provide correct display of gray line.
<br><br>
<strong>Sorting order of the QSO list</strong> - choose ascending to see first your first QSO but most common option is descending to see your latest records in your log book.
<br><br>
<strong>Show band map after program startup</strong> - if checked, you see the Band map at the program start.<br><br><img src=img/h64.png border=0><br><br>
<strong>Show DX cluster window after program startup</strong> - if checked, you see the DX cluster window at the program start.<br><br><img src=img/h4.png border=0><br><br>
<strong>Show grayline after program startup</strong> - if checked, you see the grayline window at the program start.<br><br>
<img src=img/h24.png border=0><br><br>
<strong>Show TRX control window after program startup</strong> - if checked, you see the radio control window at the program startup.<br><br>
<img src=img/h21.png border=0>
<br><br>
<strong>Show propagation window after program startup</strong> - if checked, a small window with propagation indices appears at the program startup.<br><br>
<img src=img/h110.png border=0>
<br><br>
<strong>Check for newer version of DXCC tables after program startup</strong></a> - if checked, CQRLOG will check if any update of country files available. If new version is found, an update will be performed, however you are asked if you want this update.<br><br>
<strong>Check for newer version of qsl managers database after program startup</strong> - if checked, CQRLOG will check if any update of QSL Managers database is available. If new version is found, an update will be performed, however you are asked if you want this update.<br><br>
<img src=img/h67.png border=0><br><br>
<strong>Show deleted countries in statistics</strong></a> - adds formerly valid countries to statistics and overall DXCC counts.<br><br>
<strong>Show sunrise/sunset in UTC</strong> - if checked, sunrise and sunset times are shown in UTC, otherwise in local time. Set up the proper time difference for both grayline and sun rise/set.<br><br>
<strong>Show all QSOs - Show QSO since</strong></a> - affects the QSO list window (Ctrl-O). 'Show all QSOs' means that all records in the log are displayed. It may speed up the operation if you are using a huge log (> 70 000 QSO). Actually, it limits the number of processed records to contacts since a year (the box contains a year in 4 digit form), entered into the box right from <em>Show QSO since</em>. sets the limit of number of records displayed but the rendering of QSO list is much faster. Remember, that the option <strong><em>'Show QSO since'</em> affects also the export!</strong><br><br>
<strong>Show statistics in</strong> metres (m) or Megahertz (MHz). Checking of one of the radio buttons affects the statistics appearing at the bottom of logging screen:<br><br>
<img src=img/h27.png border=0><br><br>
and also headers of the main statistics (DXCC, WAZ and ITU).
<br><br>
The bottom line with two options - 'Show all QSOs' and 'Show QSO since' affects the QSO list window . but the rendering is rather slow, the other option - if you want to export records earlier than the year set in the fill box, choose 'Show all QSOs'!
</div>
<p align=center><img src=img/line.png></p>
<a name=ah3><h2><strong>Station</strong></h2></a>
<img src=img/h6.png border=0><br><br>
<div align=justify>
Enter your call, name, QTH and WW Locator here. Remember, that the entered call is used also as login for the DX Cluster and is displayed in all stats exported to html. The WW locator is of high importance because it determines your accurate position (ie. you don't need to enter your exact coordinates). The WW Locator is used in beam and distance computation as well as the start point of the simplified path to the other station which appears in the grayline map.
</div>
<p align=center><img src=img/line.png></p>
<a name=ah4><h2><strong>New QSO</strong></h2></a>
<img src=img/h7.png border=0><br><br>
<div align=justify>
Here are the default values for the new QSO. Remember, if the radio control is active, the default frequency does not appear on the logging screen. The preset RST values will apppear in their corresponding boxes.
<br><br>
The <em>'Use spacebar to move between fields'</em> is very interesting and probably the most natural way but it works only if you are moving forwards. To move between fields, there are two other generic possibilities (TAB key and up/down arrow keys) which would remain unaffected even if you check the spacebar option. The <em>'Refresh data after save QSO'</em> affects the data displayed in the QSO List (Ctrl-O). If checked, each QSO appears in this list immediately after logging, however the refresh procedure is quite slow. To save time, keep this box unchecked. The <em>'Skip over mode and frequency when radio is connected'</em> is very important if the radio control is active. The <em>'Show detail window'</em> option enables an extra window to appear at program start. The <em>'Enable auto search on QRZ.COM'</em> switches on the automated search for QRZ callbook data for any worked station. This option does the same as F6 in logging screen, however it can be rather slow depending on the QRZ.COM server availability. Finally, the <em>'Show recent QSO records for last ** days'</em> limits the record number listed in the logging screen. Do not set the number of days too high, a high number can cause the log speed issues! The default value of 5 days is appropriate for most cases.</div><br>
<img src=img/h25.png border=0><br><br>
<div align=justify>
This window dispays details about new/confirmed zones, IOTA details etc.</div>
<p align=center><img src=img/line.png></p>
<a name=ah5><h2><strong>Visible columns</strong></h2></a>
<img src=img/h8.png border=0><br><br>
<div align=justify>
Checked columns are visible in the previous QSO list appearing at the top of the logging screen.</div>
<p align=center><img src=img/line.png></p>
<a name=ah6><h2><strong>Bands</strong></h2></a>
<img src=img/h9.png border=0><br><br>
<div align=justify>
Checked bands are visible in both statistics appearing at the bottom of logging screen (bands/modes of the actual logged station) and main DXCC, WAZ and ITU zones statistics. It affects also the Challenge points at the bottom of the DXCC statistics.</div>
<p align=center><img src=img/line.png></p>
<a name=ah7><h2><strong>TRX Control</strong></h2></a>
<img src=img/h10.png border=0><br><br>
<div align=justify>
The TRX Control displays actual frequency. You can change band and mode. No further explanation needed. The number behind the RIG: indicates the radio type ID which correspond to the IDs used by hamlib. The full list is <a href=h6.html><strong>here</strong></a>.<br><br>
The default frequencies where the radio tunes if you click onto a band button in the 'TRX control' panel can be changed to your preferences. The mode is switched in accordance to the band plan, there is actually a separate set of default frequencies for each CW, SSB, RTTY, AM and FM modes. Click onto 'Change default frequencies' button and set up frequencies of your choice.</div><br>
<img src=img/h100.png border=0><br>
<p align=center><img src=img/line.png></p>
<a name=ah8><h2><strong>Modes</strong></h2></a>
<img src=img/h11.png border=0><br><br>
Here you can set up the default bandwidth for any of supported modes (CW - SSB - RTTY - AM - FM). If your radio is tuned to the corresponding band segment or if you switch the mode on the radio control panel, CQRLOG will change the bandwidth to the desired value. The bandwidth can be changed at any time, however a program restart will be probably needed to take the changes into effect.<br><br><strong>User definable digital modes</strong> can be set up in a separate box. Use comma as a separator, ie.BPSK31,QPSK64,OLIVIA,CONTESTIA etc.
<p align=center><img src=img/line.png></p>
<a name=ah9><h2><strong>QTH Profiles</strong></h2></a>
<img src=img/h12.png border=0><br><br>
CQRLOG uses QTH Profiles. Your QTH and equipment details can be entered here. If you are logging a new QSO, choose the appropriate profile. Later, you can watch which rig and antenna was used but the main purpose is usage in filters. You can create a filter with QTH Profile as one of the criteria, a later filtering of QSOs made on your portable operation or QRP activity is possible. This method seems more effective as an usual portable log, even if you are using MM0XXX/P as your call it will probably contain a mixture of all portable activities together. With QTH Profile, there is always possible to make a separate 'log' for each operation.
<p align=center><img src=img/line.png></p>
<a name=ah10><h2><strong>Export</strong></h2></a>
<img src=img/h13.png border=0><br><br>
<table width="100%" border="0" cellpadding="5" cellspacing="2"><tbody><tr><td valign="top"><img src="img/bulb.png"></td><td bgcolor="#ccffff" valign="top"><strong><font color="blue">Our tip:</font></strong> Check all fields if you backup your whole log. Nothing will be lost and the data amount is not so high, compared to very reduced export.</td></tr></tbody></table><br><br>
This option allows an easy setup of the log fields to be exported into ADIF or HTML format. Exported are, of course, only checked fields. The 'Width' option denotes the column size in the HTML export.<br><br>
<a name=ah11><h2><strong>DX cluster</strong></h2></a>
<img src=img/h14.png border=0><br><br>
This card allows an easy setup of the DX cluster spot filtering. Check the bands you want to display. If you want to supress (ie. filter out) spots of some DX countries, put its prefixes to the box below. Use a semicolon as a separator.
<p align=center><img src=img/line.png></p>
<a name=ah12><h2><strong>Fonts</strong></h2></a>
<img src=img/h15.png border=0><br><br>
This card is self explaining, hopefully it does not need any comments. Choose the appropriate font size to prevent any screen garbage and a nice look of the buttons.
<p align=center><img src=img/line.png></p>
<a name=ah13><h2><strong>WAZ, ITU zones</strong></h2></a>
<img src=img/h16.png border=0><br><br>
This is the color coding setup for the 'Details' window. New ones can be displayed in different color and QSL status is indicated verbosely in the 'Details' window. The 'Show info' boxes must be checked to display the relevant info.
<p align=center><img src=img/line.png></p>
<a name=ah14><h2><strong>IOTA</strong></h2></a>
<img src=img/h17.png border=0><br><br>
New IOTA color coding and QSL status can be set up here. The 'Show info' boxes must be checked to display the relevant info.
<p align=center><img src=img/line.png></p>
<a name=ah15><h2><strong>Membership</strong></h2></a>
<img src=img/h31.png border=0><br><br>
The primary aim of the 'Membership' info is tracking of members of a club or stations valid for an award. The info is derived from the call sign entered into 'Call' box in the logging screen. CQRLOG can track member's calls from up to 5 databases simultaneously. To set up the tracking, do following steps:<br><br>
<strong>1. Choose a Club to be tracked.</strong> Click the first long button in the 'First club' box. A long list of Clubs appears.<br><br><img src=img/h37.png border=0><br><br>
<strong>2. Click the 'Load' button.</strong> The membership data are loaded from the text database in the 'members' subfolder of your CQRLOG directory. A box with the number of converted records appears.<br><br><img src=img/h38.png border=0><br><br>
<table border="0" cellpadding="5" cellspacing="2" width="100%"><tbody><tr><td valign="top"><img src="img/note.png"></td><td bgcolor=#eaeaea valign="top" align="justify"><strong><font color="blue">Note:</font></strong> All files in the <em>'membership'</em> subfolder are displayed. If you create your own database, put it into this subfolder!
</td></tr></tbody></table><br><br>
<strong>3. Click the 'Settings' button.</strong> A new dialog appears:<br><br>
<img src=img/h32.png border=0><br><br>
The color coding scheme for new members, new band, new mode, need of a QSL card and an already confirmed contact can be set up in the left half of the window. You can see here also my preferred color settings.<br><br>This dialog allows also to set up the messages appearing in the 'Details' window if you work a member of a club which is tracked. There can be anything, my preferred messages are:<br>
<pre>New %s member! (%c #%n)
New band %s member! (%c #%n)
New mode %s member! (%c #%n)
QSL needed for %s member! (%c #%n)
Already confirmed %s member! (%c #%n)</pre><br>
Note also the regular expressions used in the messages. The complete list is here:<br>
<pre>%l - long club name
%s - short club name
%n - club number
%c - callsign</pre><br>
The right half of this screen contains the join rules.
<table border="0" cellpadding="5" cellspacing="2"><tbody><tr><td valign="top"><img src="img/h35.png"></td><td valign="top"><img src="img/h36.png">
</td></tr></tbody></table>
Here you can set up what from the QSO entry should be bound with the appropriate column in the membership database. Because most relevant is the call sign in the QSO and the membership database contains also mostly the call sign, use the defaults - the 'clubcall' in the 'join ... field in club database' and the 'call' in the 'with ... field in main database'.<br><br>The lower part contains a dialog allowing to set up where the resulting info will be stored.
<br><br>
<img src=img/h34.png border=0><br><br>While logging, you will see the info in the corresponding field. The most preferred field is 'Award'. Since this field is used for check purposes only, all info (more meberships) are displayed in a single line which can be longer than the corresponding field on the logging screen. You can navigate here with the cursor but the well formated and color coded results in verbose form are displayed in the 'Details' window.<br><br>
<img src=img/h33.png border=0>
<br><br>
<a name=bh1><h2><strong>Bandmap</strong></h2></a>
<img src=img/h61.png border=0><br><br>The Band map is a well known feature of many contesting programs, however it is great also in a general logging program. It contains a mix of filtered DX Cluster spots and your own entries where you can store call and frequency of a station which you can't work just now but you want to return to it later.<br><br> A very useful option of the Band Map is the <em>'entries aging'</em>. Depending on the time left since entry 'birth', the color changes to lighter tone until the entry disappears. There are two levels between appearance and disappearance of the entry. The times of these two levels and the time of disappearance can be set up. If you change the aging times, restart CQRLOG. Remember that a program restart will be needed to take the changes into effect!<br><br>The spots can be color coded to highlight new countries, new band countries etc., in the same way as in the DX Cluster window - check the <em>'Use the same color as the spot'</em> option. If this option remains unchecked, all entries are shown in black color (with aging to dark grey and light grey) and your own entries, <strong>made with Ctrl-A</strong> or the <strong>Big Plus key</strong> on the numerical keyboard, are shown in blue. Also, another set of <em>Watched</em> and <em>Ignored</em> entries can be defined.<br><br>The content of the Band map can be stored if leaving the log. Check the <em>'Save band map after close'</em> option.<br><br>The <em>'Show only active mode'</em> and <em>'Show only active band'</em> options providing an additional level of cluster spot filtering. When checked, the Band Map will show only spots for the mode or band where the radio is on. The spot are sorted by frequency, so you will see what is on the band - at a glance. No doubt you will prefer this over the DX Cluster window which contains a garbage of rolling spots, often hard to 'catch out'. Finally, if the <em>'Delete station from band map after QSO'</em> option is checked, the entry with a worked station disappers from the Band Map. If such station is spotted again, it appears again in the Band Map.
<a name=bh2><h2><strong>xplanet support</strong></h2></a>
<img src=img/h66.png border=0><br><br>
To ensure correct rendering of the azimuthal map with DX Cluster spots, the external program xplanet must be installed and several parameters must be set up. First, install xplanet (version 1.2 if possible). Many distributions have this program either on the installation media (CD, DVD) or xplanet exists in the form of a corresponding package (rpm, deb, tgz, ebuild etc.). If not, download source codes from:<br>
<a href="http://xplanet.sourceforge.net/download.php"><strong>http://xplanet.sourceforge.net/download.php</strong></a><br><br>Follow the usual installation instructions:<br>
<pre>./configure
make
make install</pre>
There are no known dependencies issues.<br><br>
<div align=justify>
First thing to be set up is the path to the xplanet binary. The default <pre>/usr/local/bin/xplanet</pre> is OK in most cases for installation from sources, the usual path for installation from precompiled packages is <pre>/usr/bin/xplanet</pre>Adjust the <strong>window size</strong> (remember to set up a square, ie. 400x400, 300x300 etc. to avoid strange efects). Also, the <strong>window position</strong> must be set up to create nice looking screen. Use the <strong>Test it!</strong> button to see how your settings affected the resulting screen.<br><br>
Xplanet can refresh its display in a preset interval. This is very useful because it can read the spot (entry) list and update the displayed data. To avoid 'flooded', unreadable window, the number of displayed spots/entries must be limited. It seems that 20 is the maximum to keep the display garbage away. Actually, the number of spots (entries) is not limited by the program but by the readability. If you change the number of spots to be displayed or if the spots should (should not) go to xplanet, restart the program. Remember that a program restart will be needed to take the changes into effect!<br><br>
Set up the source (DX Cluster, Band map) by checking the appropriate radio button in the '<strong>Show stations from</strong>' section. The '<strong>Projection</strong>' has 3 options:<br>
<ul><li><strong>3D</strong> - shows the globe as viewed from the space. This rendering type without any projection is very nice, however the very distant points will be not visible, also spots or band map entries of distant DX locations will disappear. Angles should be true because the globe is 'centered' to your domestic location. Distance are <em>not true</em> because of lack of projection. This eye candy is therefore good for those who does not work DX stations.</li>
<li><strong>Azimuthal</strong> - is the usual directional map which you find useful for any rotator indication. Both angles and distances are true, however the continents patterns may look a bit strange to those who is not very accustomed with this projection. The azimuthal projection is the best for a DXer.</li>
<li><strong>Azimuthal without background</strong> - is the same as above but the background which contains the angle (polar) scale is not rendered. It is an 'emergency' solution which is useful if you have not space enough to set up the main xplanet window as a square.</li></ul>
The xplanet window has currently no other function than to display spots or band map entries in the azimuthal projection or 3D-like picture.
<br><br>
<a name=bh3><h2><strong>Zip code tracking</strong></h2></a>
<img src=img/h69.png border=0><br><br>
Zip code tracking allows to determine states, counties, provinces and other geographical details if the postal zip code structure allows such operations. The zip code itself is retrieved from the callbook address. The database is located in the /zipcodes folder. If set up properly, the F6 key is used to determine US state, US county and italian province.<br><br>
<strong>Setup: </strong>The database must be loaded before use and the target (field) must be specified. Also, the position of the zip code (line begin or end) must be set up.<br><br>
<a name=bh4><h2><strong>LoTW support</strong></h2></a>
<img src="img/h76.png"><br><br>
Provide your user name for LoTW and the password (this is <strong>not</strong> the password sent to US amateurs via postcard!). Choose if you want to include LoTW confirmation in the statistics and <em>New country</em> and <em>New band country</em> info messages.<br><br>
<a name=ch1><h2><strong>CW interface</strong></h2></a>
<img src="img/h95.png"><br><br>
Choose your preferred CW interface. There are 3 options: None, WinKeyer USB and cwdaemon. We strongly recommend the Winkey USB by Steve Elliot, K1EL, which provides 'all in one', including one of most advanced paddle keyers available. The cwdaemon should be seen as provisional option with many limitations, which may need a custom made linux kernel to avoid sloppy CW at speeds above 25 WPM. If cwdaemon used, only keyoard keying is possible.<br><br>
Detailed setup of both CW devices is here:<ul>
<li><a href=cwd.html><strong>cwdaemon</strong></a>
<li><a href=wkusb.html><strong>Winkey USB</strong></a></li></ul>
The further steps (CW messages edit, keyboard keyer operation) - click <a href=h26.html><strong>here</strong></a>.
<br><br>
<a name=ch2><h2><strong>fldigi interface</strong></h2></a>
First, <em>fldigi</em> must be installed and functional.
Preferences must be set up to operate with fldigi. Set up the path to fldigi of you want to start it when CQRLOG switches to remote mode. Other parameters including the way how should the CQRLOG - fldigi combo handle the frequency, mode and RST. CQRLOG also loads the fldigi contents to keep the data, so the 'polling' period should be set up. The 2 seconds interval is very acceptable default.<br><br>
<img src="img/h101.png"><br><br>
The way how the CQRLOG - fldigi combo handles the frequency, mode and RST is rather important. Keep in your mind that CQRLOG operates in remote mode which means that the logger is offline and therefore does not display the actual frequency and mode on the logging screen. If you set up properly the <em>fldigi</em> mode and frequency control, both are correctly displayed in the <em>fldigi</em> window. <strong>Choose the fldigi</strong> option in <em>Frequency from</em>, <em>Mode from</em> and <em>RST from</em> boxes and you don't need to watch the logger, except the QSO list in the upper portion of the logging screen. When logging/saving a contact, frequency, mode and RST should appear correctly in this QSO list. If you choose the CQRLOG option, you must set the mode in CQRLOG which seems less comfortable.
<a name=ch3><h2><strong>Auto backup</strong></h2></a>
To increase the safety of your log data, CQRLOG is equipped with <em>Auto backup</em> option which allows to export (ADIF) and store the log data in another safe location. The ADIF format was choosen because of its text format. The output file can be compressed in tar.gz format.<br><br>
<img src="img/h102.png"><br><br>
Of course, the export and compression takes some time, depending on the log size (QSO count). If you are not in a hurry, allow the program 2-3 minutes to perform this safety measure. We reccomend to backup your log to your hard drive from here it should be copied to another media (your server, USB flash, a memory card etc.).
<a name=ch4><h2><strong>External viewers</strong></h2></a>
Set up the viewers used for browsing the notes related to a particular callsign.<br><br>
<img src="img/h111.png"><br><br>
The notes in the call_data subfolder can contain text, html, pdf and image files. To enable reading of all file types, corresponding viewers must be set up properly, ie. must be in the system path.
</div>
<p align=center><img src=img/line.png></p>
<br>
<table width="100%" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="index.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h20.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
</body></html>

245
help/h20.html Normal file
View File

@ -0,0 +1,245 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
<title>CQRLOG - Keys and Shortcuts</title>
</head>
<body>
<table border="0" cellpadding="5" cellspacing="2" width="100%"><tbody><tr><td valign="top"><img src="img/exc.png"></td><td bgcolor=ffffcc valign="top"><strong><font color="red">WARNING!</font></strong> Backup your data often! BACKUP your log file at the end of ANY session! All what you need to backup and store in a safe place is the main log database cqrlog.fdb located in the /log_data folder.</td></tr></tbody></table>
<table width="100%" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h1.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h21.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
<div align="left"><strong>CQRLOG for LINUX by OK2CQR &amp; OK1RR</strong></div>
<p align=center><img src=img/line.png></p>
<a name="ah16"><h2><strong>Keys and shortcuts</strong></h2></a>
<strong>Logging screen</strong><br><br>
<table width="99%" border="0" cellpadding="4" cellspacing="0">
<tbody>
<tr>
<td width="35%">PgUp</td>
<td width="65%">CW Speed +2 WPM (QRQ)</td>
</tr>
<tr>
<td width="35%">PgDn</td>
<td width="65%">CW Speed -2 WPM (QRS)</td>
</tr>
<tr>
<td width="35%">~ (tilde)</td>
<td width="65%">Send a spot to the DX Cluster</td>
</tr>
<tr>
<td width="35%">+ (plus on numerical keyboard) - see also Ctrl-A</td>
<td width="65%">Add the logged call sign and the actual frequency to the bandmap</td>
</tr>
<tr>
<td width="35%">F11</td>
<td width="65%">QRZ Callbook (call in the field)</td>
</tr>
<tr>
<td width="35%">Ctrl-A (same as the + (plus) key - see also +</td>
<td width="65%">Add the logged call sign and the actual frequency to the bandmap</td>
</tr>
<tr>
<td width="35%">Ctrl-D </td>
<td width="65%">DXCC statistics - Confirmed only</td>
</tr>
<tr>
<td width="35%">Ctrl-I </td>
<td width="65%">Detailed info</td>
</tr>
<tr>
<td width="35%">Ctrl-L </td>
<td width="65%">Change your WW locator</td>
</tr>
<tr>
<td width="35%">Ctrl-M</td>
<td width="65%">Remote mode for fldigi</td>
</tr>
<tr>
<td width="35%">Ctrl-N </td>
<td width="65%">Show/edit long note</td>
</tr>
<tr>
<td width="35%">Ctrl-O </td>
<td width="65%"><strong><font color="red">QSO list</font></strong> (see below)</td>
</tr>
<tr>
<td width="35%">Ctrl-P </td>
<td width="65%">Preferences</td>
</tr>
<tr>
<td width="35%">Ctrl-Q </td>
<td width="65%">Quit (Close)</td>
</tr>
<tr>
<td width="35%">Ctrl-R </td>
<td width="65%">Change ref. call</td>
</tr>
</tbody>
</table>
<br>
<p align=center><img src=img/line.png></p>
<strong>QSO list</strong><br><br>
<table><tr><td valign="top"><img src="img/bulb.png"></td><td bgcolor=ccffff width="100%"><strong><font color="blue">The QSO list is the main screen for the maintenance!</font></strong> </td></tr></table>
<br><br>
<table width="100%" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="35%">F1</td>
<td width="65%">Help (this file)</td>
</tr>
<tr>
<td width="35%">F2</td>
<td width="65%">New QSO</td>
</tr>
<tr>
<td width="35%">F3</td>
<td width="65%">View QSO</td>
</tr>
<tr>
<td width="35%">F4</td>
<td width="65%">Edit QSO <font color="red"><strong>*</strong></font></td>
</tr>
<tr>
<td width="35%">F6</td>
<td width="65%">QRZ Callbook search</td>
</tr>
<tr>
<td width="35%">F7</td>
<td width="65%">Sort (setup sort order)</td>
</tr>
<tr>
<td width="35%">F8</td>
<td width="65%">Delete QSO <font color="red"><strong>*</strong></font></td>
</tr>
<tr>
<td width="35%">F10</td>
<td width="65%">Go to menu</td>
</tr>
<tr>
<td width="35%">F12</td>
<td width="65%">Create filter</td>
</tr>
<tr>
<td width="35%">Ctrl-D </td>
<td width="65%">DXCC statistics <font color="blue"><strong>**</strong></font></td>
</tr>
<tr>
<td width="35%">Ctrl-F</td>
<td width="65%">Search</td>
</tr>
<tr>
<td width="35%">Ctrl-P </td>
<td width="65%">Preferences</td>
</tr>
<tr>
<td width="35%">Ctrl-Q </td>
<td width="65%">Close the QSO list window</td>
</tr>
<tr>
<td width="35%">Ctrl-R</td>
<td width="65%">QSL received</td>
</tr>
</tbody>
</table><br>
<table border="0" cellpadding="5" cellspacing="2" width="100%"><tbody><tr><td valign="top"><img src="img/exc.png"></td><td bgcolor=ffffcc valign="top"><strong><font color="red">WARNING!</font></strong> Use the <strong>Edit (F4)</strong> and <strong>Delete (F8)</strong> (marked with a red star) options only if you are sure, what you doing! There is NO UNDO, so the operation cannot be undone!</td></tr></tbody></table><br>
<table border="0" cellpadding="5" cellspacing="2" width="100%"><tbody><tr><td valign="top"><img src="img/bulb.png"></td><td bgcolor=ccffff valign="top" width="100%"><strong><font color="blue">Your DXCC statistics can be rebuild only from the QSO list!</font></strong> </td></tr></tbody></table>
<p align=center><img src=img/line.png></p>
<a name="ah17"><h2><strong>New QSO (online logging)</strong></h2></a>
<div align="justify">
While logging online (during your QSO), date, start and end time are
set automatically. Type the call into the dedicated box and move from
this field with <strong>Arrow-Down</strong> key or <strong>spacebar</strong> (only if you enable it in the <a href="h1.html#ah4"><strong>Preferences</strong></a>). The 'Frequency' and 'Mode' fields are skipped if you properly set up the <a href="h1.html#ah7"><strong>TRX Control</strong></a>.
If you omit to set up the TRX Control option or if your radio does not
allow the Computer Aided Control (CAT), the Frequency and Mode fields
are not skipped and must be filled manually, however you can use the
pull-down menu to choose corresponding default frequency in any band
and the mode. <br><br>
If the cursor leaves the 'Call' field, you will see your previous
contacts with logged station (if any). The number above 'Call' box marked 'QSO nr.' denotes number of contacts you already have with the worked station (here, 130 QSO worked already with G3LIK, the 131th being just logged). The already confirmed contacts are highlighted in red. If the station has a QSL
manager, his call appears in the 'QSL VIA' field and an information
'QSL manager found' is displayed. If the station wants QSL direct only,
the 'QSL VIA' field remains empty but the red 'QSL manager found'
warning is still displayed. Click the button at the right side of the
'QSL VIA' fiels and a separate window with QSL managers appears, the
correct address is highlighted.<br><br>
<img src="img/h29.png" border="0"><br><br>
Note, please, that if you move the cursor from the 'Call' field to 'His
RST' field, the S in the RST is highlighted, making possibly to simply
overwrite the corresponding number (S). The same applies to 'My RST'
field.<br><br>
This trick can speed up the QSO entering procedure. You can also move
between fields with TAB key but there is whole RST highlighted, so
reports where more than a single character needs to be overwritten (ie.
449) can be entered easier than with 'tricky' RST. The default report
is predefined in the <a href="h1.html#ah4"><strong>Preferences</strong></a>). Anyway, the RST changes to its correct form (RS or RST) with mode.<br><br>
The 'Start time' begins to run if you move the cursor to 'My RST'
field. This means that you can set your RST without any hurry. Also,
the QSO duration counter starts to run. Find it just behind the time
fields on the logging screen.<br><br>
If the cursor leaves the 'Call' field, a lot of another details is
displayed. If the location is exactly on an island with IOTA reference
number, it is displayed in the IOTA field. If the call represents more
IOTA refs., the IOTA designator above its field became red. Click the
button on roght side and a pull-down menu with all possible IORA
references is displayed.<br><br>
<img src="img/h26.png" border="0"><br><br>
CQRLOG displays also the usual data like exact QTH description
(including province, regions, call districts etc.), WAZ and ITU zones,
continent, DXCC reference, geographical coordinates (in decimal form),
distance, azimuth (direction), date and local time of the target point
and the salutation corresponding to the local time (GM, GE etc.). <br><br>
You can add a general long note to your log with Ctrl-N key (from the logging screen or from the 'File' menu option).<br><br>
<img src="img/h2.png" border="0"><br><br>
Ctrl-N opens a new dialog window where you can add or edit your note. This note is <b>not</b> related to any record, it is just a notepad allowing operations with your notes which are stored in your log database.<br><br>
<img src="img/h68.png" border="0"><br><br>
If a call sign is entered, the grayline map displays a line from your QTH to the target point.<br><br>
</div><img src="img/h24.png" border="0"><br><br>
<table border="0" cellpadding="5" cellspacing="2" width="100%"><tbody><tr><td valign="top"><img src="img/note.png"></td><td bgcolor="#eaeaea"><strong><font color="blue">Note: </font></strong>
The yellow line on the grayline map has nothing to do with actual beam
heading nor the actual path! The purpose of this line is to indicate if
the path goes from/to day or night areas.</td></tr></tbody></table><br>
<div align="justify"><strong><h3>Status line</h3></strong>
<img src="img/h44.png" border="0"><br><br>
Here is displayed your own WW locator which can be changed using Ctrl-L (important mostly for VHF freaks who forget to change the WW locator in the QTH profile). In the other column is the reference call sign (the core of a slashed call, ie. KH6/OK2CQR). You can change it using Ctrl-R. The purpose is to provide a possibility to change the reference call if a correction of membership needed. The number in the right corner denotes the version.
<p align=center><img src=img/line.png></p>
<a name="ah17"><h2><strong>New QSO (offline logging, ie. from paper log etc.)</strong></h2></a>
To switch to the offline mode, check the 'Offline' box above the date.
To indicate that you are offline, the box with the 'Offline'
description became red framed.<br><br>
<img src="img/h30.png" border="0"><br><br>
Basically, the offline logging is the same as online logging, however
there are some differences. The 'Frequency' and 'Mode' fields are not
skipped. You can enter the exact frequency or choose a default (for
each band) from the pull-down menu. The same applies to the mode.<br><br>
You need also to enter the 'Date' and at least the 'Start time'. The
date format is YYYYMMDD and you can enter it without dashes, ex. 26.
May 1994 can be entered just as 19940526. The dashes are added
automatically. The same applies to the time which can be entered
without the colon.<br><br>
The CAT (radio computer control) is now off. Other fields and log
actions are the same. If you uncheck the 'Offline' box, CQRLOG returns
to the online mode.<br><br></div>
<a name="ah33"><h2><strong>Digital modes (including RTTY)</strong></h2></a>
CQRLOG employs <em>fldigi</em> by Dave Freese, W1HKJ. We believe that this is the best digimode software available. To use <em>fldigi</em>, CQRLOG must be switched to Remote mode using Ctrl+M (or from the menu File -> Remote mode for fldigi).<br><br>
<img src="img/h104.png"><br><br>
The logging screen changes to indicate that CQRLOG works now in remote mode and can be controlled either from <em>fldigi</em> or can "dictate" the mode and frequency and <em>fldigi</em> now serves as the remote input device.<br><br>
<img src="img/h103.png"><br><br>
Now, use <em>fldigi</em> in its normal way and your contacts will go directly to CQRLOG. The most important thing is a <a href="h1.html#ch2">proper setup</a> of the remote mode (frequency and mode). See fldigi help and the Beginners Guide on the W1HKJ site <a href=http://www.w1hkj.com/beginners.html><strong>http://www.w1hkj.com/beginners.html</strong></a>.
<p align=center><img src=img/line.png></p>
<table width="100%" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h1.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h21.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
</div></body></html>

96
help/h21.html Normal file
View File

@ -0,0 +1,96 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
<title>CQRLOG - DX Cluster Operation</title>
</head>
<body><table border="0" cellpadding="5" cellspacing="2" width="100%"><tbody><tr><td valign="top"><img src="img/exc.png"></td><td bgcolor=ffffcc valign="top" align="justify"><strong><font color="red">WARNING!</font></strong> Backup your data often! BACKUP your log file at the end of ANY session! All what you need to backup and store in a safe place is the main log database cqrlog.fdb located in the /log_data folder.</td></tr></tbody></table>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h20.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h22.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
<div style="text-align: left;"><strong>CQRLOG for LINUX by OK2CQR &amp; OK1RR</strong></div>
<p align=center><img src=img/line.png></p>
<a name="ah19"><h2><strong>DX Cluster Operation</strong></h2></a>
<img src="img/h4.png" border="0"><br><br>
There are two basic options - web cluster and usual DX cluster with
telnet options. The web cluster is good for monitoring. There is no
internal node setup, also you can't spot. CQRLOG downloads the spots in
regular periods, there is a fixed interval only which cannot be
changed.
<br><br>Telnet cluster is fully featured. You can also set up your
preferences on the node. The Command line box is used for all commands,
settings etc. with one exception - the Tilde key (~, next left key to 1
key) is used for spotting. The color coding and spot filtering is set
up in the <a href="h1.html#ah11"><b>Preferences menu</b></a>. <strong>Connect</strong> to the cluster node by simple clicking the 'Connect' button. You should see the cluster node messages indicating the progress. Of course, you can enter any sommand into the 'Command' field (ie. SH/DX to display last spots, SH/U to see the users connected to the node etc.).
<br><br>
<table border="0" cellpadding="5" cellspacing="2"><tbody><tr><td valign="top"><img src="img/bulb.png"></td><td bgcolor="#ccffff" width="100%"><strong><font color="blue">Our tip:</font></strong> For nice looking cluster window, choose a fixed-width font. We prefer
Monospace Regular or Onuava but also Courier works nicely. Apple's
Monaco font is also very nice and has a slashed zero.</td></tr></tbody></table>
<br>
<table border="0" cellpadding="5" cellspacing="2" width="99%"><tbody><tr><td valign="top"><div align="justify">CQRLOG
has some predefined cluster nodes, however you will probably need to
set up a node of your preference. Click the 'Select' button and a list
of cluster node appears (see below). Click there 'New' option. Another dialog appears (right). <br><br><img border="0" src="img/h18.png"></div></td><td valign="top"><img src="img/h19.png" border="0" align="top"><br><div style="text-align: justify;">Enter
the description (mostly the callsign). The 'Address' can be either IP
or the name (see examples in the list). The 'Port' is given by number.
Both address and port number you can get from the lists of DX cluster
nodes which are widely available over the internet.<br><br><font color="red"><strong>Remember</strong></font> to put your callsign into 'User name' field. This will enable the <strong>autologin</strong>. The 'Password' column should remain empty in most cases because only few nodes are password protected.
<br><br>A detailed list of DX Cluster nodes is <a href="http://www.dxcluster.info/telnet/index.php"><strong>here</strong></a> (page created by Jim, AD1C).
</div></td></tr></tbody></table><br><br>
<p align=center><img src=img/line.png></p>
<table border="0" cellpadding="5" cellspacing="2" width="99%"><tbody>
<tr><td valign="top">
<a name="bh19"><h2><strong>Bandmap Operation</strong></h2></a>
<img src="img/h64.png" border="0"></td><td valign="top"><div align="justify"><br><br>The main purpose of a bandmap is to gather most interesting info from two sources - DX Cluster and your personal notes. The bandmap combines a DX Cluster window with scratch pad memories available on many radios, however a band map is more comfortable by far - you don't need to manipulate with subtle buttons on the radio panel, also the transceiver does not indicate what is in the scratch pad memory. The band map is operated from the keyboard and shows all at a glance.
<br><br>A valuable addition is the 'entries aging' option. If the bandmap entry is 'too' old, it changes the color and after another period it disappears. This is different from usual DX Cluster windows which displays details of stations you already worked, they are QRT or are not very interesting for you from another reason. A band map provides frequency-sorted and highly filtered details which doesn't roll away (like DX Cluster window does). There are two levels of filtering:</div>
<ul>
<li>Spot filtering set up for the DX Cluster window</li>
<li>Additional band map filtering capable to filter out spots from momentarily unwanted mode, contries, zones or continents. CQRLOG has another filter allowing to watch spots of special interests, ie. you are waiting for an expedition etc. You can set up another filter showing spots only on the actual band (the band where the radio is on) and the actual mode (the mode the radio is on).</li>
</ul>
<div align="justify">You can add your own information by writing the call into logging screen in usual way (like logging). Then press <strong>Ctrl-A</strong> or the <strong>+ (plus) key</strong> on the numerical keyboard and the entry will be added to the band map. Your own entries are marked with an asterisk (here MD0CCE). You can return to the frequency anytime, the call will jump into its box in the same way like if clicked from the DX Cluster window. Click on any entry, you are on, prepared for QSO logging.<br><br>
If the entry became older than the adjusted time, it is displayed in lighter color. Very old ones will disappear, also if you log the station, the corresponding entry disappears from the band map. The entries are always sorted by the frequency.
</div>
</td></tr>
</tbody>
</table><br><br>
<p align=center><img src=img/line.png></p>
<table border="0" cellpadding="5" cellspacing="2" width="99%"><tbody>
<tr><td valign="top">
<a name="ch19"><h2><strong>Xplanet support</strong></h2></a>
<img src="img/h65.png" border="0"></td><td valign="top"><div align="justify"><br><br>There is currently no other function than DX Cluster spot displaying in true azimuthal projection with correct angles (azimuth) and distances. Alternatively, a map without projection, ie. the globe as seen from the space can be selected.</div>
</td></tr>
</tbody>
</table><br><br>
<p align=center><img src=img/line.png></p>
<table border="0" cellpadding="5" cellspacing="2" width="99%"><tbody>
<tr><td valign="top">
<a name="ch20"><h2><strong>Propagation indicator</strong></h2></a>
<img src="img/h110.png" border="0"></td><td valign="top"><div align="justify"><br><br>There is a simple window providing propagation indices as provided by the NOAA Space Weather Center. CQRLOG does not include any propagation forecast module but keen users can estimate many parameters just from the supplied data.</div>
</td></tr>
</tbody>
</table><br><br>
<p align=center><img src=img/line.png></p>
<table border="0" cellpadding="5" cellspacing="2" width="99%"><tbody>
<td><td valign="top">
<a name="ch21"><h2><strong>Additional notes to a callsign</strong></h2></a>
<img src="img/h112.png" border="0"><div align="justify"><br><br>CQRLOG provides a virtually unlimited support of additional notes which can be attached to a particular callsign (ie. an electronic QSL, a map showing the position, text files with antenna details etc). Assumed that external viewers for the text, PDF, image (jpg, png, gif) and HTML files are <a href="h1.html#ch4">set up properly</a>, all these files can be displayed.<br><br>The main program tree contains the <strong>call_data</strong> subfolder where any callsign can have its own subfolder containing the files related to the call sign. The subfolder for a call sign must be created manually. If this subfolder exists, a special icon "Call has an attachment" appears at the bottom right corner of the <em>Comment to callsign</em> field in the main logging screen. Click this icon and another window <strong>Call attachment</strong> appears, showing the contents of the call sign subfolder. Highlight the file you want to view and either double click or use the View button to display the file. The number of call sign related subfolders in <strong>call_data</strong> is unlimited, also the call sign related subfolder might contain any number of files.</div>
</td><td valign="middle"><img src="img/h113.png" border="0"><br><br><div align="justify">If the folder contains a file named "qsl_call_front.png" or "qsl_call_front.jpg" (must be .png or .jpg), another icon "Call has a QSL image" (ie. the ok2cqr subfolder contains qsl_ok2cqr_front.jpg). Click this icon and a QSL browser appears showing the front side of the QSL card. The "qsl_call_front.png" or "qsl_call_front.jpg" <strong>is a mandatory</strong> but there can be also reverse side of QSL card with the name "qsl_call_back.png" or "qsl_call_back.jpg". If this file is available, you can use the"Front" and "Back" tabs to display both sides of the QSL card.<br><br><img src="img/h116.png" border="0"></div></td></tr>
</tbody>
</table><br><br>
<p align=center><img src=img/line.png></p>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h20.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h22.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
</div></body></html>

103
help/h22.html Normal file
View File

@ -0,0 +1,103 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
<title>CQRLOG - QSL Records</title>
</head>
<body><table border="0" cellpadding="5" cellspacing="2" width="100%"><tbody><tr><td valign="top"><img src="img/exc.png"></td><td bgcolor=ffffcc valign="top" align="justify"><strong><font color="red">WARNING!</font></strong> Backup your data often! BACKUP your log file at the end of ANY session! All what you need to backup and store in a safe place is the main log database cqrlog.fdb located in the /log_data folder.</td></tr></tbody></table>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h21.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h23.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
<div style="text-align: left;"><strong>CQRLOG for LINUX by OK2CQR &amp; OK1RR</strong></div>
<p align=center><img src=img/line.png></p>
<a name="ah21"><h2><strong>QSL records</strong></h2></a>
All QSL operation must be done from the QSO list (Ctrl-O from the logging screen). The QSO list has a dedicated QSL menu item in the upper menu bar.
<ul>
<li><strong>Send QSL</strong> - the already sent QSL card has following options:<br><br>
<img src="img/h71.png" border="0"><br><br>
<ul>
<li>Buro (B) (a 'B' appears in the log, column 'QSL sent')</li>
<li>Direct (D)</li>
<li>eQSL(E)</li>
<li>Manager (M)</li>
<li>Do not send (N)</li>
<li>Manager direct (MD)</li>
<li>Manager buro (MB)</li>
<li>Confirmad by email (CE)</li>
</ul></ul>
If you want to send a QSL card, it is better to mark the QSO record with similar mark which begins with <strong>'S'</strong> (Send). This can be done with Ctrl-W shortcut. The QSO record will be marked with default option <strong>'SB'</strong> (Send via the Buro). For other options, go to the menu QSL->QSL send->Will send-> and choose an appropriate option. Once a QSL is filled (made ready to go), press Ctrl-S. The 'S' letter disappears making clearly visible that the QSL is filled and sent.
<ul>
<li><strong>Receive QSL</strong> - navigate to the record for the QSL is received. Press Ctrl-R and in the 'QSL_R' (QSL Received) field appears an 'X'.</li></ul>
<strong>QSL manager search</strong><br><br>
<img src="img/h53.png" border="0"><br><br>
Choose this option. A QSL manager window appears, in the lower left corner is a box with <em>Find</em> button.<br><br>
For LoTW operations look <a href=h7.html><strong>here</strong></a>.
<p align=center><img src=img/line.png></p>
<a name="bh4"><h2><strong>QSL labels printing</strong></h2></a>
<div align="justify">QSL label printing is accomplished with the gLabels software which is very powerful, comfortable and allows to print QSL labels of any size, any number, also a whole QSL card can be designed and printed in professional quality (printer depending). The gLabels software can be downloaded from http://glabels.sourceforge.net/. It contains numerous predefined templates of label sheets from many manufacturers. Most Linux distrubutions have gLabels in their repositories, the Slackware package can be downloaded from the OK1RR personal repository at <a href=http://www.ok1rr.com/download.php?list.10><strong>www.ok1rr.com</strong></a>.</div><br>
<strong>gLabels installation</strong><br><br>
gLabels is designed for Gnome and can be installed directly into distributions using Gnome desktop manager. For KDE and other desktop managers, you need to install:
<pre>GTK+-2.10.x
LIBGNOME[UI]-2.16.x
LIBXML-2.6.x
LIBGLADE-2.6.x</pre>
to be more specific, gLabels needs following Gnome components which should be additionally installed into KDE:<br>
<pre>avahi-0.6.23-i486-1as.tgz
gail-1.20.2-i486-1_rlw.tgz
gconf-2.20.1-i686-7as.tgz
gnome-keyring-2.20.3-i686-1dl.tgz
gnome-vfs-2.20.1-i686-1dl.tgz
libbonoboui-2.20.0-i686-1dl.tgz
libbonobo-2.20.3-i686-1dl.tgz
libgnomecanvas-2.20.1.1-i686-1dl.tgz
libgnomeui-2.20.1.1-i686-1dl.tgz
libgnome-2.20.1.1-i686-2dl.tgz
orbit2-2.14.12-i686-1dl.tgz</pre>
<div align="justify">The main task of CQRLOG is data preparation in a format (CSV) which can be processed by gLabels. More bands/modes on a single label is a mandatory and gLabels provides all what we need. </div><br>
<strong>QSL label template</strong><br>
<IMG src="img/h72.png"><br><br>
<div align="justify">A template with data to be printed, its order, typeface, position etc. is needed to print your QSL labels. gLabels uses its own format for label design. The result is a binary file. The syntax can be derived from the label designer picture, you own label design can be derived from the example qsl.glabels included in the CQRLOG installation.</div><br>
<strong>Printing of individual QSL labels (default)</strong><br><br>
<IMG src="img/h71.png"><br><br>
<div align="justify">The QSO records should be properly marked. Exported are records previously marked SB (Send Bureau), SM (Send Manager), SMB (Send Manager - Bureau), SD (Send Direct) or SMD (Send Manager- Direct) in any combination.</div><br>
<IMG src="img/h70.png"><br><br>
<strong>Batch QSL label printing</strong>
<div align="justify">This method can be used if no QSO records are previously marked. A filter can be set up, labels are printed for the filtered output and all such records are marked as 'QSL sent'. To make this option effective, check the box 'Export all QSOs' and 'Mark QSLs sent after export'. If you omit to check the 'Export all QSOs' box, no output will be generated unless there are previously marked QSO record (see above). If the 'Mark QSLs sent after export' remains unchecked, no QSO records will be marked as 'QSL sent'.</div><br>
<div align="justify">In both methods, the filtering potential can be evaluated. For example, you can filter out all QSO with DJ3 stations and print QSL labels for them. You will get such output:</div><br>
<IMG src="img/h73.png"><br>
<div align="justify">There is no need to print QSL labels online on your printer. Very good and proven trick is to print the labels into a PDF file, check for the correctness and proper alignment against real label sheet and then print out.</div>
<br>
<p align=center><img src=img/line.png></p>
<a name="bh5"><h2><strong>Auto mark QSL</strong></h2></a>
<IMG src="img/h74.png"><br><br>
<div align="justify">This useful option allows to mark QSL for first QSO with a particular station on a band, mode, band/mode and for first band, mode, band/mode contact with a particular DXCC country regardless of the station.<br> <br>
<IMG src="img/h75.png"><br><br>
It works with cooperation with the filters, however the fact of the 'first QSO' is taken from the whole log. You can limit your selection to the 2008 but if you worked this station in 1998 for first time, it will be NOT marked. This prevents you from sending multiple QSL for an already confirmed contact on that band, mode or band+mode.</div>
<p align=center><img src=img/line.png></p>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h21.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h23.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
</div></body></html>

40
help/h23.html Normal file
View File

@ -0,0 +1,40 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
<title>CQRLOG - Filtering</title>
</head>
<body><table border="0" cellpadding="5" cellspacing="2" width="100%"><tbody><tr><td valign="top"><img src="img/exc.png"></td><td bgcolor=ffffcc valign="top" align="justify"><strong><font color="red">WARNING!</font></strong> Backup your data often! BACKUP your log file at the end of ANY session! All what you need to backup and store in a safe place is the main log database cqrlog.fdb located in the /log_data folder.</td></tr></tbody></table>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h22.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h24.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
<div style="text-align: left;"><strong>CQRLOG for LINUX by OK2CQR &amp; OK1RR</strong></div>
<p align=center><img src=img/line.png></p>
<a name="ah21"><h2><strong>Filtering</strong></h2></a>
CQRLOG offers a wide variety of filtering options allowing to select and export records (for awards etc.) into ADIF or HTML formats. Take a closer look onto a picture and find the options self-explanatory.<br><br>
<img src="img/h49.png"><br><br>
Most of fields have an option to select records based on the exact match or a substring contained in the selected field, ie. if you want to select all WA3 station, put the WA3 into the 'Callsign' box and click the 'Include' radio button. Note, please, that if you select contacts with members of a particular club or from your own database, you should choose the time span (date from-to) to make the 'Membership' option active.<br><br>
The sorting order can be selected from following options:<br><br>
<img src="img/h50.png"><br><br>
Selected records can be grouped by following criteria:<br><br>
<img src="img/h51.png"><br><br>
Once your filter is set up, go to upper menu (item 'File' in QSO list) and choose 'Export'.<br><br>
<img src="img/h45.png"><br><br>
Choose 'ADIF' or 'HTML'. An usual dialog appears (depending on the desktop used). Choose a location and file name.<br><br>
<p align=center><img src=img/line.png></p>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h22.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h24.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
</div></body></html>

64
help/h24.html Normal file
View File

@ -0,0 +1,64 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
<title>CQRLOG - Statistics</title>
</head>
<body><table border="0" cellpadding="5" cellspacing="2" width="100%"><tbody><tr><td valign="top"><img src="img/exc.png"></td><td bgcolor=ffffcc valign="top" align="justify"><strong><font color="red">WARNING!</font></strong> Backup your data often! BACKUP your log file at the end of ANY session! All what you need to backup and store in a safe place is the main log database cqrlog.fdb located in the /log_data folder.</td></tr></tbody></table>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h23.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h27.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
<div style="text-align: left;"><strong>CQRLOG for LINUX by OK2CQR &amp; OK1RR</strong></div>
<p align=center><img src=img/line.png></p>
<a name="ah23"><h2><strong>Statistics</strong></h2></a>
There are 4 basic types of online statistics:<ul>
<li>DXCC statistic</li>
<li>WAZ zones</li>
<li>ITU zones</li>
<li>IOTA statistic</li></ul>
<p align=center><img src=img/line.png></p>
<strong>DXCC</strong><br><br>
The statistics can be watched from both loggin screen and QSO list, however the menu is slightly different. While the logging screen allows only watching statistics, from the QSO list can be the DXCC statistic rebuilt.
<table cellspacing="2" border="0" cellpadding="5">
<tbody>
<tr><td><strong>Logging screen</strong></td><td><strong>QSO List</strong></td></tr>
<tr><td valign="top"><img src="img/h20.png" border="0"><td valign="top"><img src="img/h46.png"></td></td></tr></tbody>
</table>
The main difference is that the 'Details' window can be activated (if not activated at program startup, <a href="h1.html#ah4"><strong>see 'Preferences'</strong></a>) only from the logging screen. Statistics <a href="h3.html#ah30"><strong>rebuilding</strong></a> is possible only from the QSO list.<br><br>
The only statistics which should be maintained is the DXCC. With the exception of the footer of DXCC detailed presentation, all DXCC scores are based on actual valid contries on the current DXCC list, ie. <strong>NO</strong> deleted countries. Other stats are computed while logging.<br><br>
There are several presentations of DXCC statistics. A summary is displayed in the QSO List, just above the table.<br>
<img src="img/h56.png" border="0"><br><br>
The detailed statistics is diplayed from the logging screen by clicking on the 'Statistics' item of the upper menu bar.<br>
<img src="img/h57.png" border="0"><br>
The 'X' denotes a worked country, the 'Q' a confirmed country. The order is <strong>PHONE - CW - DIGI</strong>. The example above shows, that Rodrigues, 3B9, been worked on 30 metres CW only, on 20 and 17 metres CW and SSB and on 15 metres CW, SSB and digital modes.<br><br>
<img src="img/h58.png" border="0"><br>
The summary footer shows your actual score band by band on all modes, worked and confirmed separately. The 'Totals' column shows your band point score per DXCC Challenge rules. The framed counts showing <strong>ALL TIME DXCC scores</strong> with deleted countries. It is the only instance showing this.<br><br>
The 'Export to HTML' button allows exporting of your whole statistics into nicely formatted HTML page. This is an exact copy of the detailed DXCC stats presentation, including the footer with all-time scores.
<p align=center><img src=img/line.png></p>
<strong>WAZ and ITU Zones</strong><br><br>
Both statistics are similar and very simple.<br><br>
<img src="img/h59.png" border="0"><br><br>
Again, the 'X' denotes a worked country, the 'Q' a confirmed zone. The footer contains totals of worked and confirmed zones, band by band.
<p align=center><img src=img/line.png></p>
<strong>IOTA</strong><br><br>
<img src="img/h60.png" border="0">
<br><br>
The IOTA statistics presentation is slightly different. An IOTA reference number and the station worked (confirmed) is displayed. This statistics is derived from the IOTA records of each logged contact. If a QSO record does not contain an IOTA information but the station <strong>is</strong> valid for IOTA, the statistics does not reflect this fact. So update regularly!<br><br>
The small check box in left lower corner toggles the worked/confirmed scores. The 'Save' button exports the whole statistics into a ASCII text file.
<p align=center><img src=img/line.png></p>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h23.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h27.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
</div></body></html>

54
help/h25.html Normal file
View File

@ -0,0 +1,54 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
<title>CQRLOG - QSL Records</title>
</head>
<body><table border="0" cellpadding="5" cellspacing="2" width="100%"><tbody><tr><td valign="top"><img src="img/exc.png"></td><td bgcolor=ffffcc valign="top" align="justify"><strong><font color="red">WARNING!</font></strong> Backup your data often! BACKUP your log file at the end of ANY session! All what you need to backup and store in a safe place is the main log database cqrlog.fdb located in the /log_data folder.</td></tr></tbody></table>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h24.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h26.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
<div style="text-align: left;"><strong>CQRLOG for LINUX by OK2CQR &amp; OK1RR</strong></div>
<p align=center><img src=img/line.png></p>
<h2><strong>QSO record edit</strong></h2>
<div align="justify">Most editing operations can be done from the QSO list window which appears if pressing Ctrl-O or clicking corresponding menu item from the logging screen.<br></div>
<p><img src=img/h2.png></p>
<div align="justify">The QSO list displays either all QSO records or a limited QSO number (QSO since ... year), depending on the <a href="h1.html#ah2">Preferences -> Program</a> settings.<br></div>
<p><img src=img/h89.png></p>
<div align="justify">This window has a quite complex icon system which is explained here:<br></div>
<p><img src=img/h77.png></p>
<div align="justify">A single record can be edited (viewed, deleted) if you highlight it using mouse or up/down keys and click the corresponding button (it will be EA8FC here, of course). You will be returned to the QSO logging window which is now changed to Edit window. This status is clearly marked with the red message <font color=#ff0000>(edit mode)</font> just behind the <em>Call</em> header which is also displayed with red letters. Of course, all fields can be edited. If you finish editing, you should save the chages using ENTER key or clicking the <em>Save QSO [enter]</em> button, just in the same way as you do if you want to log in a new contact.<br></div>
<p><img src=img/h93.png></p>
<div align="justify">A QSO record can be now edited also directly from the logging screen. The QSOs made in last few days <a href="h1.html#ah4">(see Preferences -> New QSO)</a> are displayed in the logging screen. Right click on the particular record which appears in the logging screen, edit mode, exactly as described above (here 5R8IC will be edited).<br></div>
<p><img src=img/h94.png></p>
<div align="justify">Of course, you can also view the record (no edit) and search in the QRZ database or look for the QSL manager in the IK3QAR QSL manager database.
<p align=center><img src=img/line.png></p>
<a name="grp"><h2><strong>Group edit</strong></h2></a>
<div align="justify">A record can be tagged clicking the corresponding icon or with mouse - hold the Ctrl key on the keyboard and left click on the QSO record to be tagged.<br></div>
<p><img src=img/h90.png></p>
<div align="justify">Click the <em>Edit QSO</em> button and a group edit menu appears:<br></div>
<p><img src=img/h91.png></p>
<div align="justify">Choose the field to be edited from the pulldown menu:<br></div>
<p><img src=img/h92.png></p>
<div align="justify">The field name changes. Enter the value (word, string) which will appear in <strong>ALL</strong> tagged QSO records. Click the <em>Apply</em> button and the value in all tagged records will be changed to the value entered into <em>Value:</em> box. All values entered within a session are temporarily stored so you can list it with the "arrow down" button in the group edit menu.</div>
<table border="0" cellpadding="5" cellspacing="2" width="100%"><tbody><tr><td valign="top"><img src="img/exc.png"></td><td bgcolor=ffffcc valign="top" align="justify"><strong><font color="red">WARNING!</font> There is no UNDO option!</strong> If you click the <em>Apply</em> button, there is no way to return to previous values! Make a backup before any group edit operation!</td></tr></tbody></table>
<p align=center><img src=img/line.png></p>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h24.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h26.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
</div></body></html>

56
help/h26.html Normal file
View File

@ -0,0 +1,56 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
<title>CQRLOG - Preferences</title>
</head>
<body><table border="0" cellpadding="5" cellspacing="2" width="100%"><tbody><tr><td valign="top"><img src="img/exc.png"></td><td bgcolor=#ffffcc valign="top" align="justify"><strong><font color="red">WARNING!</font></strong> Backup your data often! BACKUP your log file at the end of ANY session! All what you need to backup and store in a safe place is the main log database cqrlog.fdb located in the /log_data folder.</td></tr></tbody></table>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h25.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="index.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
<div style="text-align: left;"><strong>CQRLOG for LINUX by OK2CQR &amp; OK1RR</strong></div>
<p align=center><img src=img/line.png></p>
<h2><strong>CW interface</strong></h2>
<li align=justify>Assumed that your CW interface is properly set up and working, you can add and/or edit your CW messages.<br><br>
First, set up your CW messages. In the upper menu bar on the logging screen, click on the 'CW' item.<br><br>
<img src=img/h96.png><br><br>
Choose the 'Messages' option. In the resulting window, edit your CW messages which should be played if you press the corresponding F key (in the logging screen). You can set up to 10 predefined messages:<br><br>
<img src=img/h97.png><br><br>
There are some predefined macros which you can use in your messages:<br><br>
<table border="0" cellpadding="5" cellspacing="2" width="50%"><tbody><tr><td bgcolor=#ffffcc valign="top">
%mc - my callsign<br>
%mn - my name<br>
%mq - my qth<br>
%r - rst to be sent out<br>
%n - his name<br>
%c - his callsign<br>
| - half space<br>
</td></tr></tbody></table><br>
Another option 'CW type' is a powerful keyboard keyer with 3 operation modes:<br><br>
<img src=img/h98.png><br><br><ul>
<li><strong>letter mode</strong> - the character of the corresponding keyboard key is sent out immediately after key pressing
<li><strong>word mode</strong> - a whole word is typed, sending starts after pressing of spacebar
<li><strong>word mode, first word in letter mode</strong> - a combination of above. The keyer begins in letter mode to avoid unneccessary delays, if you type fast enough it turns to the word mode</li></ul>
These modes are usual on professional keyboard keyers.<br><br>
The <strong>keying speed</strong> can be changed with PgUp (QRQ) and PgDn (QRS) keys in 2 WPM steps. In the 'CW type' window, it can be also changed with the small arrow buttons right from the speed indicator. The actual speed is also always displayed in the status line of the logging screen.<br><br>
<img src=img/h99.png><br><br>
The setup howtos for both <a href=cwd.html><strong>cwdaemon</strong></a> and <a href=wkusb.html><strong>Winkey USB</strong></a> - click on the name.<br><br>
</div>
<p align=center><img src=img/line.png></p>
<br>
<table width="100%" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h25.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="index.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
</body></html>

111
help/h27.html Normal file
View File

@ -0,0 +1,111 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
<title>CQRLOG - Advanced operations</title>
</head>
<body><table border="0" cellpadding="5" cellspacing="2" width="100%"><tbody><tr><td valign="top"><img src="img/exc.png"></td><td bgcolor=ffffcc valign="top" align="justify"><strong><font color="red">WARNING!</font></strong> Backup your data often! BACKUP your log file at the end of ANY session! All what you need to backup and store in a safe place is the main log database cqrlog.fdb located in the /log_data folder.</td></tr></tbody></table>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h24.html#ah23"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h3.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
<div style="text-align: left;"><strong>CQRLOG for LINUX by OK2CQR &amp; OK1RR</strong></div>
<p align=center><img src=img/line.png></p>
<h2><strong>SQL Console</strong></h2>
<div style="text-align: justify;">To enter the SQL Console, go to QSO list (Ctrl+O) and in the upper menu bar go to <em>Filter -> SQL console.</em>
<div align="left"><table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="50%" align="left"><img src=img/h114.png border="0"></td></tr>
<tr><td width="50%" align="left"><img src=img/h115.png border="0"></td>
</tr>
</tbody>
</table><br>
The icons in the upper menu allowing following actions:<br><br>
<strong>1st icon</strong>
&nbsp; &nbsp;&nbsp;Execute SQL statement<br>
<strong>2nd icon</strong>
&nbsp;&nbsp;&nbsp;Previous SQL command<br>
<strong>3rd icon</strong>
&nbsp;&nbsp;&nbsp;Next SQL command<br>
<strong>4th icon</strong>
&nbsp;&nbsp;&nbsp;Load SQL command saved into a file<br>
<strong>5th icon</strong>
&nbsp;&nbsp;&nbsp;Save SQL command into a file aktualniho SQL dotazu do souboru<br>
<strong>6th icon</strong>
&nbsp;&nbsp;&nbsp;Export data into a csv or html file<br>
<strong>7th icon</strong>
&nbsp;&nbsp;&nbsp;Get SQL command currently used to the main database. For example, if a filter is set, clicking this icon allows to edit SQL command created by the filter.<br><br>
<strong>Tables:</strong><br><br>
<strong>cqrlog_main</strong><br>
&nbsp;&nbsp;&nbsp;the main table with all QSO records<br><br>
<strong>remarks</strong><br>
&nbsp;&nbsp;&nbsp;table containing the call sign related notes<br><br>
<strong>bandcn</strong><br>
&nbsp;&nbsp;&nbsp;info if the country is worked and confirmed by a paper QSL or via LoTW<br><br>
<strong>ref_dxcc</strong><br>
&nbsp;&nbsp;&nbsp;the current DXCC reference table<br><br>
<strong>exceptions</strong><br>
&nbsp;&nbsp;&nbsp;list of strings to be ignores if such string appears in the call sign after a slash<br><br>
<strong>bands</strong><br>
&nbsp;&nbsp;&nbsp;band limits (lower/upper end)<br><br>
<strong>profiles</strong><br>
&nbsp;&nbsp;&nbsp;list of QTH profiles<br><br>
<strong>version</strong><br>
&nbsp;&nbsp;&nbsp;program version<br><br>
<strong>dxclusters</strong><br>
&nbsp;&nbsp;&nbsp;list of DX cluster nodes<br><br>
<strong>ambiguos</strong><br>
&nbsp;&nbsp;&nbsp;list of ambiguos prefixes<br><br>
<strong>iota_list</strong><br>
&nbsp;&nbsp;&nbsp;IOTA reference list<br><br>
<strong>award1 ... award5</strong><br>
&nbsp;&nbsp;&nbsp;external tables used for memberships<br><br>
<strong>zipcode1 ... zipcode3</strong><br>
&nbsp;&nbsp;&nbsp;external tables used for zip codes<br><br>
<strong>long_note</strong><br>
&nbsp;&nbsp;&nbsp;a long note valid for whole log<br><br>
</div>
<strong>Example:</strong><br><br>
<div align="justify">Select from the database date, call sign, frequency and mode, where the QSO date is from timespan between Jan. 1. 2009 and Dec. 31. 2009 and the WAZ zone is 15.<br><br>
<strong>SQL command:</strong><br>
<pre>
SELECT qsodate, call, freq, mode FROM cqrlog_main WHERE qsodate >= '2009-01-01' and qsodate <= '2009-31-12' and waz = 15
</pre><br>
The databases structures are listed <a href=sql_console.html><strong>here</strong>.</a></div>
</div>
<p align=center><img src=img/line.png></p><br>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h24.html#ah23"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h3.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
</body></html>

157
help/h3.html Normal file
View File

@ -0,0 +1,157 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
<title>CQRLOG - Maintenance</title>
</head>
<body><table border="0" cellpadding="5" cellspacing="2" width="100%"><tbody><tr><td valign="top"><img src="img/exc.png"></td><td bgcolor=ffffcc valign="top" align="justify"><strong><font color="red">WARNING!</font></strong> Backup your data often! BACKUP your log file at the end of ANY session! All what you need to backup and store in a safe place is the main log database cqrlog.fdb located in the /log_data folder.</td></tr></tbody></table>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h24.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h4.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
<div style="text-align: left;"><strong>CQRLOG for LINUX by OK2CQR &amp; OK1RR</strong></div>
<p align=center><img src=img/line.png></p>
<h2><strong>Maintenance</strong></h2>
<div style="text-align: justify;">
<a name=ah24><strong>ADIF import</strong></a><br><br>
The main purpose is to add QSO records from other logging and/or contesting programs. You may need it if you migrate from another logger and if you adding your contacts made in a contest (any modern contesting program has the ADIF export facility, some older programs may need a third party conversion utility).
<br><br>
Go to QSO list (Ctrl+O on the main logging screen or File -> Show QSO list Ctrl+O from the menu).<br><br>
<img src="img/h39.png" border="0"><br><br>
From the menu <strong>here</strong> choose File -> Import -> ADIF.<br><br>
Click on 'ADIF' and a 'Open file' dialog appears.<br><br>
<img src="img/h40.png" border="0"><br><br>Navigate to the file you want to import and click 'Open'. You will see a new dialog, click the 'Import' button here. You can add also a QTH profile and a note ('Remarks:') which will appear at any imported QSO record. Using this options, a portable, mobile or QRP operation can be clearly marked.<br><br>
<img src="img/h41.png" border="0"><br><br>
If you import a huge file, you will see a progress bar, however import of a small file is so fast that you never note any progress indicator.<br><br>
<img src="img/h42.png" border="0"><br><br>
The previous window now indicates the import completion, number of imported records and number of errors. If the ADIF file contains incorrect entries, they will be stored separately in the file <strong>errors.adi</strong> located in the 'log_data' subfolder. You can fix the errors manually and import again. <br><br>
<img src="img/h43.png" border="0"><br><br>
Duplicate entries (contacts already in the log) are indicated with a separate dialog allowing to exclude or include these records.
<p align=center><img src=img/line.png></p>
<a name=ah25><strong>ADIF export</strong></a><br><br>
Go to QSO list using Ctrl-O or choose the QSO list from upper menu - item 'File'.<br><br>
<img src=img/h39.png><br><br>
From the QSO list, choose 'Export' in the menu - item 'File'.<br><br>
<img src=img/h45.png><br><br>
Choose 'ADIF'. An usual dialog appears (depending on the desktop used). Choose a location and file name.<br><br>
<p align=center><img src=img/line.png></p>
<a name=ah26><strong>HTML export</strong></a><br><br>
The same as above, only difference is to choose the 'HTML' option.<br><br>
<p align=center><img src=img/line.png></p>
<a name=ah27><strong>Program version update</strong></a><br><br>
<table width="100%" border="0" cellpadding="5" cellspacing="2"><tbody><tr><td valign="top"><img src="img/exc.png"></td><td style="width: 100%; text-align: justify; background-color: rgb(255, 255, 204);"><strong><font color="red">WARNING!</font></strong> A BACKUP of your log file before program update <strong><font color="red">is a MUST!</font></strong></td></tr></tbody></table>
Download the new version from <a href=http://www.cqrlog.com><strong>CQRLOG web site</strong></a> or <a href=http://www.ok1rr.com/download.php?list.9><strong>OK1RR site</strong></a> (other mirrors may appear later). Unpack the tarball into a temporary location and run the installer <pre>cqrlog_install.sh</pre>
<img src="img/h48.png"><br><br>
and choose 'Upgrade from previous version'.
Run the program and perform the DXCC Statistics Rebuild. That's all.<br><br>
The upgrade process will <strong>NOT overwrite</strong> your log file or your configuration.<br><br>
<table width="100%" border="0" cellpadding="5" cellspacing="2"><tbody><tr><td valign="top"><img src="img/exc.png"></td><td style="width: 100%; text-align: justify; background-color: rgb(255, 255, 204);"><strong><font color="red">WARNING!</font></strong> If you choose 'Complete new install', your log and configuration <strong><font color="red">will be overwritten!</font></strong></td></tr></tbody></table>
<p align=center><img src=img/line.png></p>
<a name=ah28><strong>Country files update</strong></a><br><br>
CQRLOG checks at startup the country file version and the update can be <strong>automated</strong> if you choose this option in <a href="h1.html#ch3">Preferences.</a> The automated update needs only to click 'Yes' in the update dialog.<br><br><img src=img/h67.png><br><br>
<strong>Manual update</strong><br><br>
The country file set for CQRLOG is distributed in a tar.gz archive with an unique name, ie. cqrlog-cty080227.tar.gz. The number (here 080227) denotes version number which is the same as the release date.<br><br>
Contents of the country file set (8 files):
<ul>
<li>AreaOK1RR.tbl</li>
<li>CallResolution.tbl</li>
<li>Country.tab</li>
<li>CountryDel.tab</li>
<li>iota.tbl</li>
<li>Exceptions.tbl</li>
<li>Ambiguous.tbl</li>
<li>README</li></ul>
<strong>How to update Country files:</strong><br>
<ol>
<li>Unpack and copy all files into the /ctyfiles folder in your CQRLOG main folder. The purpose of this folder is to store the files only, it is not bound to the CQRLOG and does not affect its function.</li>
<li>Start the CQRLOG and select the 'Show QSO list' from the 'File' item in the main menu. You can go there also using shortcut Ctrl-O.</li>
<li>If you are already in the QSO list, go there to menu. Click the 'File' item, then the 'Import' option. Choose the DXCC data option, located at lowest position. A dialog appears, navigate to your /ctyfiles folder. Click the 'Open' button. All files are read and if the import completes, a small window with the message 'Import complete. Please restart program' appears. Click the OK button and quit CQRLOG.</li>
<li>Restart CQRLOG. The update is finished.</li></ol>
<table width="100%" border="0" cellpadding="5" cellspacing="2"><tbody><tr><td valign="top"><img src="img/note.png"></td><td style="width: 100%; text-align: justify; background-color: rgb(204, 255, 255);"><strong><font color="blue">Note:</font></strong> While opening your new country files [see 3.], you dont need to open a particular files. The 'Open' button starts a procedure which reads ALL files in the /ctyfiles folder.</td></tr></tbody></table>
<br>
<table width="100%" border="0" cellpadding="5" cellspacing="2"><tbody><tr><td valign="top"><img src="img/exc.png"></td><td style="width: 100%; text-align: justify; background-color: rgb(255, 255, 204);"><strong><font color="red">WARNING!</font></strong> Don't attempt to create your own country files. This can result in program crash or incorrect statistics. If you find an incorrectly resolved station (no matter if current log or an old record), send a note directly to me: martin@ok1rr.com. Replace <strong><font color="red">ALWAYS</font></strong> all files in the /ctyfiles folder! If you leave an older file and try only a single file from the new version, the resulting tables will became out-of-sync which ends with incorrect statistics. Also, the logger may not work properly.</td></tr></tbody></table>
<br>
NEW LOG FILE - you can create a new log file (crqlog.fdb) where you can import ADIF format QSO data. A new log file is created by CQRLOG automatically if the program does not find a cqrlog.fdb file in the /log_data folder. If you create a new log file, import the most fresh country files set BEFORE any ADIF QSO data import! The best way is to erase all files in the /ctyfiles folder and copy the 8 files from your new archive.<br><br>
<table width="100%" border="0" cellpadding="5" cellspacing="2"><tbody><tr><td valign="top"><img src="img/exc.png"></td><td style="width: 100%; text-align: justify; background-color: rgb(255, 255, 204);"><strong><font color="red">WARNING!</font></strong> If you update your contry files or upgrade the CQRLOG version, <strong>always</strong> perform the 'Rebuild DXCC statistics' which is accessible from the QSO list screen.</td></tr></tbody></table><br>
Some users reported that their DXCC statistics became 'out of sync' and the actual DXCC scoring does not match the results reported by CQRLOG.<br><br>
Remember that a regular rebuild of your DXCC statistics is a matter of importance. Rebuild if you upgrade country files, rebuild also if you upgrade the program version!
<p align=center><img src=img/line.png></p>
<a name=ah29><strong>QSL Manager Database update</strong></a><br><br>
Since version 0.8.0 CQRLOG uses its own QSL Manager database in very simple, plain text format (CSV, semicolon separated). The update is very simple. The automated update checks the availability of a new version, downloads and unpacks the tar.gz file if available. The new version must be imported - go to QSO list (Ctrl+O or from menu <em>File -> Show QSO list</em>) and choose the <em>File -> Import -> Import qsl managers database</em>.<br><br>
A manual update is also possible if you download the recent version from the CQRLOG site <a href=http://www.cqrlog.com><strong>http://www.cqrlog.com</strong></a>.<br><br>
<img src=img/h107.png><br><br>
The QSL Manager database format is as follows:<br>
<pre>
call;qsl_manager;publishing_date
Example:
3D2BV;JA1PBV;2008-01
</pre>
You can maintain your own records but we carefully maintain this database with verified records from reliable sources (DX Bulletins). The database is monthly updated and the covered timespan of QSL Managers is limited to 10 years after publishing date. After this time, the expired records will be removed and stored in another file (archive) which will be available on the CQRLOG site <a href=http://www.cqrlog.com><strong>http://www.cqrlog.com</strong></a>.<br><br>
<table width="100%" border="0" cellpadding="5" cellspacing="2"><tbody><tr><td valign="top"><img src="img/note.png"></td><td style="width: 100%; text-align: justify; background-color: rgb(204, 255, 255);"><strong><font color="blue">Note:</font></strong> Because the QRZ.COM entries very often contain details useful for direct lookup but not suitable to print on QSL labels, choose the option <em>'Ignore QRZ.COM qsl info'</em> on the <em>Preferences -> New QSO</em> card. </td></tr></tbody></table>
<br>
If a station has more than a single QSL Manager, click the small button left from the QSL VIA field.<br><br>
<img src=img/h106.png><br><br>
A popup window with selection option appears:<br><br>
<img src=img/h105.png><br><br>
Navigate to the appropriate QSL manager, use the publishing date column or verify the QSL manager from another source. This ensures that the QSL label will contain the proper QSL manager.
<p align=center><img src=img/line.png></p>
<a name=ah30><strong>Statistics rebuilding</strong></a><br><br>
<img src=img/h46.png><br><br>
The only possibility to rebuild your statistics is <strong>from the QSO list</strong>. The 'Statistics' menu item here has the 'Rebuild DXCC statistics' option (the similar option on the logging screen does NOT have any 'Rebuild' option).<br><br>
<table width="100%" border="0" cellpadding="5" cellspacing="2"><tbody><tr><td valign="top"><img src="img/exc.png"></td><td style="width: 100%; text-align: justify; background-color: rgb(255, 255, 204);"><strong><font color="red">WARNING!</font></strong> The statistics rebuilding takes a long time if your log contains some tens of thousands records!</td></tr></tbody></table><br>
<img src=img/h46.png><br><br>
A warning appears before rebuilding process. If you answer 'Yes', be prepared for a long procedure.<br><br>
<img src=img/h47.png>
<p align=center><img src=img/line.png></p>
<a name=ah31><strong>Membership databases</strong></a><br><br>
CQRLOG supports online tracking of up to 5 memberships simultaneously. The membership databases can be used also for filter creation, along with a date span (from-to). The tracking and filtering feature is not limited to membership only, you can create your own databases using lists of your particular interests (short-terw awards, local groups etc.). The databases have a pure text format with data columns separated by a semicolon ';'.<br><br>
The default installation contains data of some 57 clubs: AFM, AGCW, ARKTIKA, A1-CLUB, A1-OP, CAV, CCT, CFO, CFT, CONVENIAT, CTC, CWJF, CWSP, DIG, DTC, EHSC, EPC, FFR, FIRAC, FISTS, FMC, FOC, GACW, GQRPC, HACWG, HHC, HH, HSC, HTC, JAIG, MARCONISTA, MCL, MFCA, MF, OKDXC, OKDXF, OTC-SARA, PRC, PRL, QCWA, RAFARS, RIA, RNARS, RRDXA, RTC, SHSC, SKCC, SPAR, SPDXC, TEN-TEN, TFC, UDXC, UFT, VHSC, VRK, WAP, 070-CLUB, 9ACWG. You can go to<br>
<pre>/home/~/cqrlog/members</pre>
(the tilde ~ represents a name of your personal subdirectory within the 'home' folder).<br><br>
Any membership contains also a header consisting of two lines:
<pre>HSC
High Speed Club</pre>
where the first line represents the <strong>short</strong> name of the club and the second line means the long <strong>club</strong> name. Both names must be in the header on separated lines. The first line must be the same as the filename without suffix, ie. the HSC membership list <strong>must</strong> be <pre>hsc.txt</pre> The mandatory suffix is <strong>.txt</strong> and the filename must be in <strong>lowercase</strong>.<br><br>
You can examine the syntax which will be more descriptive than this short example, however there are basically 3 types of membership list files:<br><br>
<strong>1. Simple list of call signs.</strong> It does not contain any membership number or date limits. Syntax:<br><br>
&nbsp;&nbsp;W5LGY<br>
&nbsp;&nbsp;W5LJT<br>
&nbsp;&nbsp;W5LKL<br>
&nbsp;&nbsp;W5LP<br><br>
ie. a <strong>single</strong> call per line.<br><br>
<strong>2. List of call signs with membership numbers.</strong> Syntax:<br><br>
&nbsp;&nbsp;DL5JAN;4603<br>
&nbsp;&nbsp;DL5JBM;4746<br>
&nbsp;&nbsp;DL5JBN;4642<br>
&nbsp;&nbsp;DL5JBW;5740<br><br>
ie. a <strong>single</strong> call and membership number per line. The call and the membership number are separated by a semicolon ';'.<br><br>
<strong>3. List of call signs with membership numbers and date limits.</strong>Used for short term awards or time span limited memberships. Syntax:<br><br>
&nbsp;&nbsp;6O2NG;533;1957-04;2005-03<br>
&nbsp;&nbsp;6Y5SR;868;1966-03;1982-07<br>
&nbsp;&nbsp;6Y5XG;331;1951-05;-<br>
&nbsp;&nbsp;7J1AEF;1297;1976-06;-<br><br>
ie. a <strong>single</strong> call, membership number and datelimits from-to, separated by a semicolon ';', per line. See above the two optins: 6O2NG with membership number 533 was a member of the club from April, 1957 to March, 2005. 6Y5XG with number 331 started his membership May, 1951 and is still a member. The dash instead date (separated from the begin date by a semicolon) denotes that the membership is still actual. A dash can be used <strong>only</strong> at the position of 'to'.<br><br>
<table width="100%" border="0" cellpadding="5" cellspacing="2"><tbody><tr><td valign="top"><img src="img/exc.png"></td><td style="width: 100%; text-align: justify; background-color: rgb(255, 255, 204);"><strong><font color="red">WARNING!</font></strong> You must keep lists of your particalr interest by yourself! It is impossible to keep all these tables up-to-date by log authors, however if you update a list and would like to share it with others, you are welcome!</td></tr></tbody></table><br>
<p align=center><img src=img/line.png></p>
<a name=ah32><strong>Log backup</strong></a><br><br>
Your log is in the file<br>
<pre>/home/~/cqrlog/log_data/cqrlog.fdb</pre>
(the tilde ~ represents a name of your personal subdirectory within the 'home' folder).<br><br>
Backup this file, however it is big. If you want to save space, export your log into ADIF file which is about a half size of the .fdb file. ADIF is also version independent. Zipped or tared ADIF file has a reasonable size also if your log contain several 100 000 records.
<p align=center><img src=img/line.png></p>
</div>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h24.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h4.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
</body></html>

43
help/h4.html Normal file
View File

@ -0,0 +1,43 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
<title>CQRLOG - I want to...</title>
</head>
<body><table border="0" cellpadding="5" cellspacing="2" width="100%"><tbody><tr><td valign="top"><img src="img/exc.png"></td><td bgcolor=ffffcc valign="top" align="justify"><strong><font color="red">WARNING!</font></strong> Backup your data often! BACKUP your log file at the end of ANY session! All what you need to backup and store in a safe place is the main log database cqrlog.fdb located in the /log_data folder.</td></tr></tbody></table>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h3.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h5.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
<div style="text-align: left;"><strong>CQRLOG for LINUX by OK2CQR &amp; OK1RR</strong></div>
<p align=center><img src=img/line.png></p>
<h2><strong>I want to...</strong></h2>
<div style="text-align: justify;"><ul>
<a name="ah33"><li><strong>Prepare LoTW or eQSL log/update</strong></li>
<strong>eQSL.cc</strong> - Create a filter for the time span you want to QSL or choose another criteria and export to ADIF which can be directly uploaded to the eQSL.cc server.<br><br>
<strong>LoTW</strong> must be signed and converted to the .tq8 format required by the ARRL. Full description is <a href=h7.html><strong>here</strong></a>. <strong>Trusted QSL</strong> is needed for LoTW operations. You need the updated version, download <a href="http://www.ok2cqr.com/?q=lotw-and-linux"><strong>here</strong></a> (sources, SuSE and Fedora packages). Ubuntu and Debian have this package in their repositories. Slackware packages download <a href="http://www.ok1rr.com/request.php?196"><strong>here</strong></a>.
<br><br>
<li><strong>Suggest a new feature</strong></li>
Probably the best way is to make a suggestion on the <a href=http://www.cqrlog.com/?q=forum/4><strong>CQRLOG we site</strong></a>.<br><br>
Other lists and forums:<ul>
<div align="left"><li><a href="http://tech.groups.yahoo.com/group/cqrlog/"><strong>Yahoo Groups</strong> (http://tech.groups.yahoo.com/group/cqrlog/)</a> (you must be a member of Yahoo Groups)</li>
<li><a href="http://nagano.cz/cgi-bin/mailman/listinfo/cqrlog"><strong>Mailing list at Nagano Server</strong> (http://nagano.cz/cgi-bin/mailman/listinfo/cqrlog)</a></ul><br>
You can get also in touch with the authors, emails see the title page.</li></ul></div>
</div>
<p align=center><img src=img/line.png></p><br>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h3.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h5.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
</body></html>

76
help/h5.html Normal file
View File

@ -0,0 +1,76 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
<title>CQRLOG - Troubleshooting</title>
</head>
<body><table border="0" cellpadding="5" cellspacing="2" width="100%"><tbody><tr><td valign="top"><img src="img/exc.png"></td><td bgcolor=ffffcc valign="top" align="justify"><strong><font color="red">WARNING!</font></strong> Backup your data often! BACKUP your log file at the end of ANY session! All what you need to backup and store in a safe place is the main log database cqrlog.fdb located in the /log_data folder.</td></tr></tbody></table>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h4.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h6.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
<div style="text-align: left;"><strong>CQRLOG for LINUX by OK2CQR &amp; OK1RR</strong></div>
<p align=center><img src=img/line.png></p>
<h2><strong>Troubleshooting</strong></h2>
<div style="text-align: justify;">
<a name="ah37"><em><strong>My radio control (CAT) does not work</strong></em><ul>
<li><strong>Check your ports.</strong> You must be a member of the user group, which has permission to use ttyS* or ttyUSB* devices.</li>
<li><strong>Check if your radio is properly set up </strong><a href="h1.html#ah7"><em>(see here)</em></a>. Check if the radio type is properly set up <a href="h6.html"><em>(see here)</em></a>. Click the 'Settings' button and check port settings - ttyS* or ttyUSB* number and <strong>all</strong> communication parameters.</li>
<li><strong>Isn't the poll rate set too fast?</strong> Try lower settings (higher number).</li>
</ul><br>
<p align=center><img src=img/line.png></p>
<em><strong>When I click on a spot in the DX cluster window it populates the log but it does not move the rig to the new operating frequency.</strong> I am using an Icom 756 (original nonPro model).</strong></em><ul>
<li>Set IF filters bandwidth to 0 (Preferences -> Modes tab).</li>
</ul><br>
<p align=center><img src=img/line.png></p>
<a name="ah38"><em><strong>I'm unable to autologin to the Cluster</strong></em><ul>
Open DX cluster window and click the 'Select' button. In the <a href="h21.html#ah19"><strong>DX Cluster List</strong></a> choose the 'Edit' option. A dialog appears:<br><br>
<img src="img/h55.png" border="0"></ul>
<br>
The 'User name:' field must be filled with your call sign.<br>
<p align=center><img src=img/line.png></p>
<a name="ah39"><em><strong>I get this error message when trying to load:</strong></em><ul>
<pre>"Can't load library: /home/ham/cqrlog/libfbembed.so.2.1.1
Press OK to ignore and risk data corruption.
Press Cancel to kill the program. </pre></ul>
<p>The library <pre>libstdc++5</pre> is not installed.</p>
<table border="0" cellpadding="5" cellspacing="2" width="100%"><tbody><tr><td valign="top"><img src="img/note.png"></td><td bgcolor=#eaeaea valign="top" align="justify"><strong><font color="blue">Note:</font> Since version 0.8.5 the libstdc++5</strong> does not need to be installed, it <strong>is already part of the installation</strong> and can be found in the /lib folder (file name libstdc++.so.5.0.7., size 737 192 B). If you get the above mentioned error message, check the /lib folder for presence of libstdc++.so.5.0.7.
</td></tr></tbody></table>
</div>
<p align=center><img src=img/line.png></p>
<a name="ah40"><em><strong>I have troubles with LoTW login getting following error message:</strong></em><ul>
<pre>PROGRESS shows:
NOT logged
Error: 0
Error: ssl_none</pre>
<p>Solution: libssl-dev must be installed</p></ul>
<p align=center><img src=img/line.png></p>
<a name="ah41"><em><strong>CQRLOG is very slow or does not run at all</strong></em><ul>
<p align="justify">The accompanying problem is the abonormally high CPU load. The problem is instant polling of non-existent (not responding) radio. Your radio setup is probably incorrect, possible a mess in the cqrlog.cfg. Try to downoad a default cqrlog.cfg from the CQRLOG web site (www.cqrlog.com) and copy it into your /cqrlog/log_data folder. Backup before your old cqrlog.cfg if you want. The default cqrlog.cfg redirects all polling to the hamlib dummy radio (model=1] and the high CPU load should return to its normal values.<br><br>Then you should set up your radio again. Don't use a too low poll rate, a value of 300 is sufficient.</p></ul></div>
<p align=center><img src=img/line.png></p>
<a name="ah42"><em><strong>64 bit - CQRLOG won't install (won't run)</strong></em><ul>
<p align="justify">32 bit libraries must be installed! If not, please install bug-buddy.i386 and all the libstdc.i386 packages. Also hamlib 32bit version has to be installed.</p></ul></div>
<p align=center><img src=img/line.png></p>
<a name="ah43"><em><strong>Disappearing fonts in the Radio Control Window</strong></em><ul>
<p>If your Radio Control Window looks like this</p>
<p><img src=img/h108.png></p>
<p>go to Preferences -> Fonts and uncheck the 'Use default settings' option</p>
<p><img src=img/h109.png></p>
<div align="justify"><p>and set fonts manually. Choose any font of your preference which is present in your system (you will see it in the font choice pulldown dialog 'Select font'). This fixes this problem.</p></ul></div>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h4.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h6.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
</body></html>

209
help/h6.html Normal file
View File

@ -0,0 +1,209 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
<title>CQRLOG - Supported Radio Types</title>
</head>
<body><table border="0" cellpadding="5" cellspacing="2" width="100%"><tbody><tr><td valign="top"><img src="img/exc.png"></td><td bgcolor=ffffcc valign="top" align="justify"><strong><font color="red">WARNING!</font></strong> Backup your data often! BACKUP your log file at the end of ANY session! All what you need to backup and store in a safe place is the main log database cqrlog.fdb located in the /log_data folder.</td></tr></tbody></table>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h5.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h7.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
<div style="text-align: left;"><strong>CQRLOG for LINUX by OK2CQR &amp; OK1RR</strong></div>
<p align=center><img src=img/line.png></p>
<strong><h2>Supported radio types</h2></strong>
<br>
<div style="text-align: justify;">
The actual list of supported radios depends on the hamlib version.
You can obtain the actual list using the command:
<pre>
./rigctl --list > riglist.txt
</pre>
However, you must navigate to the folder containing <i>rigctl</i> executable (mostly /usr/local/bin).
The actual snapshot version 1.2.7. supports following radio types:
<pre>
Rig# Mfg Model Vers. Status
===================================================================
1701 Alinco DX-77 0.7 Beta
2506 AmQRP DDS-60 0.1 Alpha
508 AOR AR2700 0.5 Untested
506 AOR AR3000A 0.5 Beta
505 AOR AR3030 0.4 Untested
504 AOR AR5000 0.5 Beta
514 AOR AR5000A 0.5 Alpha
503 AOR AR7030 0.4 Beta
502 AOR AR8000 0.5 Untested
501 AOR AR8200 0.5 Alpha
513 AOR AR8600 0.5 Beta
2503 Coding Technologies Digital World Travel0.1 Untested
902 Drake R-8A 0.5 Beta
903 Drake R-8B 0.5 Untested
2303 DTTS Microwave SocieDttSP 0.1 Alpha
221 Elecraft K2 0.6 Beta
229 Elecraft K3 0.6 Beta
2501 Elektor Elektor 3/04 0.4 Stable
2507 Elektor Elektor SDR-USB 0.1 Beta
2301 Flex-radio SDR-1000 0.2 Untested
1 Hamlib Dummy 0.4 Beta
2 Hamlib NET rigctl 0.2 Beta
1901 Hamlib RPC rig 0.3 Beta
354 Icom IC ID-1 0.4 Untested
303 Icom IC-271 0.4 Untested
304 Icom IC-275 0.4.1 Beta
306 Icom IC-471 0.4 Untested
307 Icom IC-475 0.4.1 Beta
360 Icom IC-7000 0.4 Untested
355 Icom IC-703 0.4 Untested
309 Icom IC-706 0.4 Untested
310 Icom IC-706MkII 0.4 Untested
311 Icom IC-706MkIIG 0.4 Stable
312 Icom IC-707 0.4 Untested
313 Icom IC-718 0.4 Alpha
314 Icom IC-725 0.4.1 Beta
315 Icom IC-726 0.4 Stable
316 Icom IC-728 0.4 Untested
319 Icom IC-735 0.4.1 Beta
320 Icom IC-736 0.4 Untested
321 Icom IC-737 0.4 Untested
323 Icom IC-746 0.4 Untested
346 Icom IC-746PRO 0.4 Untested
324 Icom IC-751 0.4.1 Beta
326 Icom IC-756 0.4 Alpha
327 Icom IC-756PRO 0.4 Untested
347 Icom IC-756PROII 0.4 Alpha
357 Icom IC-756PROIII 0.4 Untested
328 Icom IC-761 0.4.1 Stable
329 Icom IC-765 0.4 Stable
330 Icom IC-775 0.4.1 Untested
345 Icom IC-78 0.4 Untested
356 Icom IC-7800 0.4 Untested
331 Icom IC-781 0.4.1 Untested
332 Icom IC-820H 0.4 Alpha
334 Icom IC-821H 0.4 Alpha
344 Icom IC-910 0.4 Beta
335 Icom IC-970 0.4 Untested
402 Icom IC-PCR100 0.5 Beta
401 Icom IC-PCR1000 0.5 Alpha
336 Icom IC-R10 0.4 Untested
358 Icom IC-R20 0.4 Untested
340 Icom IC-R7000 0.4.0 Alpha
337 Icom IC-R71 0.4 Untested
341 Icom IC-R7100 0.4.0 Untested
338 Icom IC-R72 0.4 Untested
339 Icom IC-R75 0.4 Beta
343 Icom IC-R9000 0.4 Untested
342 Icom ICR-8500 0.4.1 Beta
605 JRC NRD-525 0.1 Alpha
606 JRC NRD-535D 0.6 Stable
607 JRC NRD-545 DSP 0.6 Beta
1801 Kachina 505DSP 0.3 Alpha
215 Kenwood R-5000 0.6 Alpha
217 Kenwood TH-D7A 0.3 Alpha
220 Kenwood TH-F7E 0.3 Beta
223 Kenwood TH-G71 0.3 Beta
226 Kenwood TM-D700 0.3 Untested
227 Kenwood TM-V7 0.3 Beta
230 Kenwood TRC-80 0.6 Alpha
225 Kenwood TS-140S 0.6.1 Beta
214 Kenwood TS-2000 0.6.3 Beta
202 Kenwood TS-440 0.6.0.6 Alpha
203 Kenwood TS-450S 0.6 Beta
228 Kenwood TS-480 0.6.1 Untested
201 Kenwood TS-50S 0.6 Untested
204 Kenwood TS-570D 0.6.1 Stable
216 Kenwood TS-570S 0.6.1 Stable
224 Kenwood TS-680S 0.6.1 Beta
205 Kenwood TS-690S 0.6 Alpha
206 Kenwood TS-711 0.6.0.6 Untested
207 Kenwood TS-790 0.6.1 Alpha
208 Kenwood TS-811 0.6.0.6 Untested
209 Kenwood TS-850 0.6.0 Beta
210 Kenwood TS-870S 0.6.0 Beta
222 Kenwood TS-930 0.6 Untested
211 Kenwood TS-940S 0.6.0.6 Alpha
213 Kenwood TS-950SDX 0.6 Beta
1004 Lowe HF-235 0.3 Alpha
2508 mRS miniVNA 0.1 Alpha
353 Optoelectronics OptoScan456 0.3 Beta
352 Optoelectronics OptoScan535 0.3 Beta
1103 Racal RA6790/GM 0.1 Untested
804 Radio Shack PRO-2052 0.3 Untested
2401 RFT EKD-500 0.4 Alpha
2502 SAT-Schneider DRT1 0.2 Beta
1402 Skanti TRP8000 0.2 Untested
2201 TAPR DSP-10 0.2 Alpha
351 Ten-Tec Omni VI Plus 0.2 Beta
1603 Ten-Tec RX-320 0.5 Beta
1604 Ten-Tec RX-340 0.1 Untested
1605 Ten-Tec RX-350 0.1 Untested
1607 Ten-Tec TT-516 Argonaut V 0.2 Stable
1602 Ten-Tec TT-538 Jupiter 0.3 Alpha
1601 Ten-Tec TT-550 0.2 Beta
1608 Ten-Tec TT-565 Orion 0.4 Beta
1611 Ten-Tec TT-588 Omni VII 0.3 Alpha
802 Uniden BC245xlt 0.3 Untested
806 Uniden BC250D 0.3 Untested
801 Uniden BC780xlt 0.3 Untested
803 Uniden BC895xlt 0.3 Untested
810 Uniden BCD-396T 0.3 Alpha
811 Uniden BCD-996T 0.3 Alpha
2601 Video4Linux SW/FM radio 0.1 Untested
1204 Watkins-Johnson WJ-8888 0.2 Untested
1501 Winradio WR-1000 0.6 Untested
1502 Winradio WR-1500 0.6 Untested
1503 Winradio WR-1550 0.6 Untested
1504 Winradio WR-3100 0.6 Untested
1505 Winradio WR-3150 0.6 Untested
1506 Winradio WR-3500 0.6 Untested
1507 Winradio WR-3700 0.6 Untested
117 Yaesu FRG-100 0.4 Beta
119 Yaesu FRG-8800 0.2 Untested
118 Yaesu FRG-9600 0.2 Untested
121 Yaesu FT-100 0.4 Beta
103 Yaesu FT-1000D 0.0.6 Alpha
124 Yaesu FT-1000MP 0.1 Alpha
129 Yaesu FT-2000 0.21 Untested
127 Yaesu FT-450 0.21.1 Beta
110 Yaesu FT-736R 0.2 Untested
105 Yaesu FT-747GX 0.3 Alpha
106 Yaesu FT-757GX 0.4 Beta
107 Yaesu FT-757GXII 0.4 Stable
109 Yaesu FT-767GX 0.1 Alpha
120 Yaesu FT-817 0.5 Beta
111 Yaesu FT-840 0.1 Untested
101 Yaesu FT-847 0.4 Beta
122 Yaesu FT-857 0.3 Beta
115 Yaesu FT-890 0.1 Stable
123 Yaesu FT-897 0.3.2 Beta
113 Yaesu FT-900 0.1 Untested
114 Yaesu FT-920 0.3.4 Stable
128 Yaesu FT-950 0.21.1 Alpha
116 Yaesu FT-990 0.1 Alpha
130 Yaesu FTDX-9000 0.21 Untested
125 Yaesu MARK-V Field FT-10000.0.5 Alpha
104 Yaesu MARK-V FT-1000MP 0.0.5 Alpha
126 Yaesu VR-5000 0.2 Alpha
------------------------------------------------------------------
</pre>
There's no standardized protocol to remotely control one's rig, be it a Ham radio transceiver, a SWL receiver, any kind of scanner and other mobiles. However, some manufacturer may have designed their own proprietary protocol, implemented in some of their product family. Therefore, each rig family will require a Hamlib backend to set the VFO frequency, change mode and passband width, get current signal strength, etc.<br><br>
<table width="100%" border="0" cellpadding="5" cellspacing="2"><tbody><tr><td valign="top"><img src="img/note.png"></td><td style="width: 100%; text-align: justify; background-color: rgb(234, 234, 234);"><strong><font color="blue">Note:</font></strong> If your radio is not on the list, it does not mean that it is not supported at all. The Elecraft K3 radio works as K2 (Rig# 221), you can also try one of the Kenwood radios. Ten-Tec Omni-VI is using Icom IC-735 backend.</td></tr></tbody></table><br>
Anyway, new backends for Yaesu FTDX-9000, FT-2000, FT-950 and FT-450 to be expected very soon. You can try the Kenwood radio instead or FT-1000MP.
<br>
</div>
<p align=center><img src=img/line.png></p>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h5.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h7.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
</body></html>

77
help/h7.html Normal file
View File

@ -0,0 +1,77 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html lang="en-us"><head>
<title>CQRLOG - LoTW support</title></head>
<body><table border="0" cellpadding="5" cellspacing="2" width="100%"><tbody><tr><td valign="top"><img src="img/exc.png"></td><td align="justify" bgcolor="#ffffcc" valign="top"><strong><font color="red">WARNING!</font></strong>
Backup your data often! BACKUP your log file at the end of ANY session!
All what you need to backup and store in a safe place is the main log
database cqrlog.fdb located in the /log_data folder.</td></tr></tbody></table>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td align="left" width="33%">&nbsp;&lt;<a href="h6.html"> Prev</a></td>
<td align="center" width="33%">[<a href="index.html#aa">Menu</a>]</td>
<td align="right" width="33%"><a href="h8.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
<div align=left><strong>CQRLOG for LINUX by OK2CQR &amp; OK1RR</strong></div>
<p align="center"><img src="img/line.png"></p><a name="bh4"></a><br><b><h2>LoTW support</h2></b>
<p><strong>Preparation</strong></p>
<div align=justify>Assume that you have a working LoTW Account. If you are new to LoTW, read carefully the instructions provided by ARRL and set up properly your account.<br><br>Very important is the certificate. ARRL issues certificates (.tq8) which are bound to a particular machine and cannot be transferred to another place. If you receive a .tq8 certificate, it is <b>absolutely essential to convert it to more usual .p12</b> format which <strong>can</strong> be transferred. Do this immediately!<br><br> Download and install the LoTW utilities (<em>tqsl</em> and <em>tqslcert</em>). The original Linux utilities are obsolete and won't compile and run with any recent version of wxwidgets. They have been reworked by Petr, OK2CQR to compile with wxwidgets-2.8.x series. The updated version of <strong>Trusted QSL</strong> download <a href="http://www.ok2cqr.com/?q=lotw-and-linux"><strong>here</strong></a> (sources, SuSE and Fedora packages). Ubuntu and Debian have this package in their repositories. Slackware packages download <a href="http://www.ok1rr.com/request.php?196"><strong>here</strong></a>.</div>
<p><strong>Setup</strong></p>
<img src="img/h76.png"><br><br>
<div align=justify>If you didn't it already in the 'Preferences' setup procedure, provide your user name for LoTW and the password (this is <strong>not</strong> the password sent to US amateurs via postcard!).<br><br>
Now you need to select a certificate corresponding to the QTH you used while making the QSOs you want to confirm. Check the certificates available by opening tqslcert which displays all certificates.</div><br>
<img src="img/h78.png"><br><br>
<div align=justify>Now select the proper certificate <strong><em>in tqsl</em></strong>. If you have single certificate only, you don't need to make any selection, however note the name of the QTH which must be entered into CQRLOG.</div><br>
<img src="img/h79.png"><br><br>
<img src="img/h80.png"><br><br>
<div align=justify>The QTH profile name here is 'Praha'. The callsign is added by default however only the name (here 'Praha') should be entered into <em>tqsl command line arguments:</em> column of the <em>QSL->LoTW->Export->Upload to LoTW</em> window.</div><br>
<img src="img/h81.png"><br><br>
<div align=justify>Once entered, the QTH name stays in the predefined command line.</div>
<p><strong>LoTW file export and upload</strong></p>
<div align=justify><strong>1. Select the QSO records</strong> you want to confirm. Good choice is a filter for date, QSL received etc.<br><br>Now, there are two possibilities:
<blockquote>
<strong>I. Export the selected records</strong> to a local ADIF file. This is useful if you don't want (or it is impossible) to upload your log to LoTW. Go to <em>QSL->LoTW->Export->Export QSOs to LoTW adif file</em><br><br>
<img src="img/h82.png"><br><br>
<div align=justify>Provide a file name and put it to <em>Export to:</em> field.</div><br>
<img src="img/h83.png"><br><br>
<div align=justify>If you want to mark the exported QSO records, do it now. Click the <em>Export</em> button and go to <em>Upload to LoTW menu</em> item. The ADIF file can be signed and uploaded later.<br><br>Another option is export, signing and upload your log to LoTW at a glance.<br><br>
<strong>II. export, signing and upload your log to LoTW from CQRLOG</strong><br><br>
Go to Upload to LoTW card and choose QSO records which should be exported:</div><br>
<img src="img/h84.png"><br><br>
<div align=justify>Click the <em>Export & sign</em> button. You should see:<br>
<pre>Signing adif file ...
Signed ...
If you did not see any errors, you can send signed file to LoTW
website by pressing Upload button</pre><br>
Now click the <em>Upload</em> button. A message<br>
<pre>Uploading file ...
Size: xxxxx
Uploading was succesful<br></pre>
</blockquote>
This procedure can be checked in following way: in the /cqrlog/lotw folder should appear two new files - an ADIF file named date_time.adi (where date and time corresponding to the date and time of creation) and the signed file with the same file name but .tq8 extension which is then uploaded to the LoTW site. Finally, you can check the <a href=https://p1k.arrl.org/lotwuser/default><strong>LoTW site</strong></a>. Log in and go to <em>Your Account -> Your Activity</em> and you should see your last upload with the date, time and file name.
<br><br></div>
<p><strong>LoTW files download and processing</strong></p>
<div align=justify>The main purpose of the LoTW files processing (also download) is to mark existing QSO records as confirmed via LoTW. Files can be downloaded directly into CQRLOG or an already downloaded ADIF files can be processed.</div><br>
<img src="img/h85.png"><br><br>
<div align=justify>Both options shown here. If the <em>Import local LoTW ADIF file</em> (already downloaded from the LoTW site) is processed, a simple progress indicator is shown.</div><br>
<img src="img/h86.png"><br><br>
If you choose <em>Download and process data from LoTW website</em> a progress indicator is displayed.</div><br><br>
<img src="img/h87.png"><br><br>
<div align=justify>The Size changes while downloading, if finished it indicates the total file size. When download finishes, a summary appears and the import begins, showing the same progress indicator as above.</div><br>
<img src="img/h88.png"><br><br>
If the file is not accessible (due to server overload etc.), an error message is shown. Also if the file contains a record which is not in your log, a warning message appears.
<p align="center"><img src="img/line.png"></p>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td align="left" width="33%">&nbsp;&lt;<a href="h6.html"> Prev</a></td>
<td align="center" width="33%">[<a href="index.html#aa">Menu</a>]</td>
<td align="right" width="33%"><a href="h8.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
</body></html>

125
help/h8.html Normal file
View File

@ -0,0 +1,125 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
<title>CQRLOG - GNU GENERAL PUBLIC LICENSE</title>
</head>
<body>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h7.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="index.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
<div style="text-align: left;"><strong>CQRLOG for LINUX by OK2CQR &amp; OK1RR</strong></div>
<p align=center><img src=img/line.png></p>
<div style="text-align: justify;">
<h3>GNU GENERAL PUBLIC LICENSE</h3>
<p> Version 2, June 1991 </p>
<pre>Copyright (C) 1989, 1991 Free Software Foundation, Inc. <br>51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA<br><br>Everyone is permitted to copy and distribute verbatim copies<br>of this license document, but changing it is not allowed.<br></pre>
<h3>Preamble</h3>
<p> The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Lesser General Public License instead.) You can apply it to your programs, too. </p>
<p> When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things. </p>
<p> To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it. </p>
<p> For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. </p>
<p> We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software. </p>
<p> Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations. </p>
<p> Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all. </p>
<p> The precise terms and conditions for copying, distribution and modification follow. </p>
<h3>TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION</h3>
<p> <strong>0.</strong> This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you". </p>
<p> Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does. </p>
<p> <strong>1.</strong> You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program. </p>
<p> You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee. </p>
<p> <strong>2.</strong> You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: </p>
<dl>
<dt></dt>
<dd> <strong>a)</strong> You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change. </dd>
<dt></dt>
<dd> <strong>b)</strong> You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License. </dd>
<dt></dt>
<dd> <strong>c)</strong> If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.) </dd>
</dl>
<p> These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. </p>
<p> Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program. </p>
<p> In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License. </p>
<p> <strong>3.</strong> You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following: </p>
<dl>
<dt></dt>
<dd> <strong>a)</strong> Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, </dd>
<dt></dt>
<dd> <strong>b)</strong> Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, </dd>
<dt></dt>
<dd> <strong>c)</strong> Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.) </dd>
</dl>
<p> The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable. </p>
<p> If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code. </p>
<p> <strong>4.</strong> You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance. </p>
<p> <strong>5.</strong> You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it. </p>
<p> <strong>6.</strong> Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License. </p>
<p> <strong>7.</strong> If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program. </p>
<p> If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances. </p>
<p> It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. </p>
<p> This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License. </p>
<p> <strong>8.</strong> If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License. </p>
<p> <strong>9.</strong> The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. </p>
<p> Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation. </p>
<p> <strong>10.</strong> If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. </p>
<p><strong>NO WARRANTY</strong></p>
<p> <strong>11.</strong> BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. </p>
<p> <strong>12.</strong> IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. </p>
<h3>END OF TERMS AND CONDITIONS</h3>
<h3>How to Apply These Terms to Your New Programs</h3>
<p> If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. </p>
<p> To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. </p>
<table><tbody><tr><td style="background-color: rgb(238, 238, 238);">
<pre><var>one line to give the program's name and an idea of what it does.</var>
Copyright (C) <var>yyyy</var> <var>name of author</var>
This program is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License
as published by the Free Software Foundation; either version 2
of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
</pre></td></tr></tbody></table>
<p>Also add information on how to contact you by electronic and paper mail.</p>
<p>If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:</p>
<table><tbody><tr><td style="background-color: rgb(238, 238, 238);">
<pre>Gnomovision version 69, Copyright (C) <var>year</var> <var>name of author</var>
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details
type `show w'. This is free software, and you are welcome
to redistribute it under certain conditions; type `show c'
for details.</pre></td></tr></tbody></table>
<p> The hypothetical commands <samp>`show w'</samp> and <samp>`show c'</samp> should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than <samp>`show w'</samp> and <samp>`show c'</samp>; they could even be mouse-clicks or menu items--whatever suits your program. </p>
<p> You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the names: </p>
<table><tbody><tr><td style="background-color: rgb(238, 238, 238);"> <pre>Yoyodyne, Inc., hereby disclaims all copyright<br>interest in the program `Gnomovision'<br>(which makes passes at compilers) written <br>by James Hacker.<br><br><var>signature of Ty Coon</var>, 1 April 1989<br>Ty Coon, President of Vice<br></pre> </td></tr></tbody></table>
<p> This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the </strong>GNU Lesser General Public License</strong> instead of this License. </p>
</div>
<br>
<p align=center><img src=img/line.png></p>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h7.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="index.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
</body></html>

BIN
help/img/bulb.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 652 B

BIN
help/img/c03.jpg Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 34 KiB

BIN
help/img/cwdaem.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 21 KiB

BIN
help/img/exc.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.9 KiB

BIN
help/img/h1.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 17 KiB

BIN
help/img/h10.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 13 KiB

BIN
help/img/h100.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 8.1 KiB

BIN
help/img/h101.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 14 KiB

BIN
help/img/h102.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 11 KiB

BIN
help/img/h103.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 17 KiB

BIN
help/img/h104.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 6.2 KiB

BIN
help/img/h105.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 7.5 KiB

BIN
help/img/h106.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 4.0 KiB

BIN
help/img/h107.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 7.6 KiB

BIN
help/img/h108.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 3.6 KiB

BIN
help/img/h109.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 8.5 KiB

BIN
help/img/h11.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 48 KiB

BIN
help/img/h110.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 2.7 KiB

BIN
help/img/h111.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 54 KiB

BIN
help/img/h112.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 26 KiB

BIN
help/img/h113.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 3.4 KiB

BIN
help/img/h114.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 30 KiB

BIN
help/img/h115.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 10 KiB

BIN
help/img/h116.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 71 KiB

BIN
help/img/h12.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 12 KiB

BIN
help/img/h13.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 15 KiB

BIN
help/img/h14.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 14 KiB

BIN
help/img/h15.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 13 KiB

BIN
help/img/h16.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 12 KiB

BIN
help/img/h17.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 11 KiB

BIN
help/img/h18.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 4.8 KiB

BIN
help/img/h19.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 2.5 KiB

BIN
help/img/h2.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.8 KiB

BIN
help/img/h20.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 2.6 KiB

BIN
help/img/h21.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 4.7 KiB

BIN
help/img/h22.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 2.1 KiB

BIN
help/img/h23.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 16 KiB

BIN
help/img/h24.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 13 KiB

BIN
help/img/h25.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 3.9 KiB

BIN
help/img/h26.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 6.4 KiB

BIN
help/img/h27.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 7.7 KiB

BIN
help/img/h28.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 11 KiB

BIN
help/img/h29.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 19 KiB

BIN
help/img/h3.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 17 KiB

BIN
help/img/h30.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 3.4 KiB

BIN
help/img/h31.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 15 KiB

BIN
help/img/h32.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 11 KiB

BIN
help/img/h33.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 7.4 KiB

BIN
help/img/h34.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 5.7 KiB

BIN
help/img/h35.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 4.3 KiB

BIN
help/img/h36.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 7.4 KiB

BIN
help/img/h37.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 12 KiB

BIN
help/img/h38.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 5.7 KiB

BIN
help/img/h39.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 10 KiB

BIN
help/img/h4.html Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 22 KiB

BIN
help/img/h4.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 7.7 KiB

BIN
help/img/h40.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 16 KiB

BIN
help/img/h41.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 9.3 KiB

BIN
help/img/h42.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 6.1 KiB

Some files were not shown because too many files have changed in this diff Show More