X-Git-Url: http://scm.dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;ds=inline;f=sgml%2Fadminmanual_en.sgml;h=dddb3102b8e2471433c86d3d1f47a2dec201c788;hb=97ed91562320bf23d3ca62194a732fb9d89bb8ba;hp=23bbd0b5b18b7e0d3b3d859a916a4110dca9b573;hpb=7c3d8bfac8fa88490ef5473116ef73656934c4bf;p=spider.git
diff --git a/sgml/adminmanual_en.sgml b/sgml/adminmanual_en.sgml
index 23bbd0b5..dddb3102 100644
--- a/sgml/adminmanual_en.sgml
+++ b/sgml/adminmanual_en.sgml
@@ -3655,6 +3655,14 @@ You can carry on with the message until you are ready to send it.
+
+
+
-
-
-
-
@@ -3888,6 +3896,14 @@ fed new style DX Protocol rather normal user commands.
+
+
+
This command shows information on all the active connections known to
the node. This command gives slightly more information than WHO.
+
+
+
+Show all known contests which are maintained at http://www.sk3bg.se/contest/
+for a particular month or year. The format is reasonably flexible.
+For example:-
+
+
@@ -4157,6 +4190,35 @@ This can be done with the SHOW/DX command like this:-
SH/DX dxcc w on 20m iota
+
+
+
+The node collects information from the comment fields in spots (things
+like 'VIA EA7WA' or 'QSL-G1TLH') and stores these in a database.
+
+This command allows you to interrogate that database and if the callsign
+is found will display the manager(s) that people have spotted. This
+information is NOT reliable, but it is normally reasonably accurate if
+it is spotted enough times.
+
+For example:-
+
+
@@ -5177,6 +5239,22 @@ will allow text with this word again.
+
+
+
+Display both the Spotter's and the Spotted's CQ Zone on the end
+of a DX announcement (there is just enough room). Some user programs
+cannot cope with this. The Spotter's CQ is on the RHS of the
+time, the Spotted's CQ is on the LHS.
+
+Conflicts with: SET/DXGRID, SET/DXITU, SHOW/USSTATE
+
+Do a STAT/USER to see which flags you have set if you are confused.
@@ -5190,24 +5268,26 @@ that if the spotter's grid square is known it is output on the end
of a DX announcement (there is just enough room). Some user programs
cannot cope with this. You can use this command to reset (or set)
this feature.
-
-
-If the spotter's or spotted's US State is known it is output on the
-end of a DX announcement (there is just enough room).
+Display both the Spotter's and the Spotted's ITU Zone on the end
+of a DX announcement (there is just enough room). Some user programs
+cannot cope with this. The Spotter's ITU is on the RHS of the
+time, the Spotted's ITU is on the LHS.
-A spotter's state will appear on the RHS of the time (like
-SET/DXGRID) and the spotted's State will appear on the LHS of the
-time field. Any information found will override any locator
-information from SET/DXGRID.
+Conflicts with: SET/DXGRID, SET/DXCQ, SHOW/USSTATE
-Some user programs cannot cope with this. You can use this command
-to reset (or set) this feature.
+Do a STAT/USER to see which flags you have set if you are confused.
@@ -5333,6 +5413,28 @@ normal.
+
+
+
+If the spotter's or spotted's US State is known it is output on the
+end of a DX announcement (there is just enough room).
+
+A spotter's state will appear on the RHS of the time (like
+SET/DXGRID) and the spotted's State will appear on the LHS of the
+time field. Any information found will override any locator
+information from SET/DXGRID.
+
+Some user programs cannot cope with this. You can use this command
+to reset (or set) this feature.
+
+Conflicts with: SET/DXCQ, SET/DXITU
+
+Do a STAT/USER to see which flags you have set if you are confused.