+ SH/DXCC W on 20m iota
+
+This can be done with the SHOW/DX command like this:-
+
+ SH/DX dxcc g
+ SH/DX dxcc w on 20m iota
+
+This is an alias for: SH/DX dxcc
+
+=== 0^SHOW/FDX^Show the DX data in realtime format.
+Normally SHOW/DX outputs spot data in a different format to the
+realtime data. This is a deliberate policy (so you can tell the
+difference between the two). Some logging programs cannot handle
+this so SHOW/FDX outputs historical data in real time format.
+
+This is an alias for: SHOW/DX real
+
+=== 0^SHOW/DXSTATS [days] [date]^Show the DX Statistics
+Show the total DX spots for the last <days> no of days (default is 31),
+starting from a <date> (default: today).
+
+=== 0^SHOW/FILES [<filearea> [<string>]]^List the contents of a filearea
+SHOW/FILES on its own will show you a list of the various fileareas
+available on the system. To see the contents of a particular file
+area type:-
+ SH/FILES <filearea>
+where <filearea> is the name of the filearea you want to see the
+contents of.
+
+You can also use shell globbing characters like '*' and '?' in a
+string to see a selection of files in a filearea eg:-
+ SH/FILES bulletins arld*
+
+See also TYPE - to see the contents of a file.
+
+=== 0^SHOW/FILTER^Show the contents of all the filters you have set
+Show the contents of all the filters that are set. This command displays
+all the filters set - for all the various categories.
+
+=== 0^SHOW/GRAYLINE [ndays] [<prefix>|<callsign>]^Show Civil dawn/dusk times
+This command is very similar to SHOW/SUN except that it shows the
+start and end of "Official" or "Civil" Dawn and Dusk. This is defined
+as when the Sun is 6 degrees below the horizon.
+
+If you don't specify any prefixes or callsigns, it will show the
+times for your QTH (assuming you have set it with either SET/LOCATION
+or SET/QRA), together with the current azimuth and elevation.
+
+If all else fails it will show the civil dawn and dusk times for
+the node that you are connected to.
+
+For example:-
+
+ SH/GRAYLINE
+ SH/GRAYLINE G1TLH W5UN
+
+You can also use this command to see into the past or the future, so
+if you want to see yesterday's times then do:-
+
+ SH/GRAYLINE -1
+
+or in three days time:-
+
+ SH/GRAYLINE +3 W9
+
+Upto 366 days can be checked both in the past and in the future.
+
+Please note that the times are given as the UT times of the requested
+UT day.
+
+=== 0^SHOW/HFSTATS [days] [date]^Show the HF DX Statistics
+Show the HF DX spots breakdown by band for the last <days> no of days
+(default is 31), starting from a <date> (default: today).
+
+=== 0^SHOW/HFTABLE [days] [date] [prefix ...]^Show the HF DX Spotter Table
+Show the HF DX Spotter table for the list of prefixes for the last
+<days> no of days (default is 31), starting from a <date> (default: today).
+
+If there are no prefixes then it will show the table for your country.
+
+Remember that some countries have more than one "DXCC country" in them
+(eg G :-), to show them (assuming you are not in G already which is
+specially treated in the code) you must list all the relevant prefixes
+
+ sh/hftable g gm gd gi gj gw gu
+
+Note that the prefixes are converted into country codes so you don't have
+to list all possible prefixes for each country.
+
+If you want more or less days than the default simply include the
+number you require:-
+
+ sh/hftable 20 pa
+
+If you want to start at a different day, simply add the date in some
+recognizable form:-
+
+ sh/hftable 2 25nov02
+ sh/hftable 2 25-nov-02
+ sh/hftable 2 021125
+ sh/hftable 2 25/11/02
+
+This will show the stats for your DXCC for that CQWW contest weekend.
+
+You can specify either prefixes or full callsigns (so you can see how you
+did against all your mates). You can also say 'all' which will then print
+the worldwide statistics.
+
+ sh/hftable all
+
+=== 8^SHOW/HOPS <call> [ann|spots|route|wcy|wwv]^Show the hop counts for a node
+This command shows the hop counts set up for a node. You can specify
+which category you want to see. If you leave the category out then
+all the categories will be listed.
+
+=== 1^SHOW/ISOLATE^Show list of ISOLATED nodes
+
+=== 9^SHOW/LOCKOUT <prefix>|ALL^Show the list of locked out or excluded callsigns
+
+=== 8^SHOW/LOG [<callsign>]^Show excerpts from the system log
+This command outputs a short section of the system log. On its own
+it will output a general logfile. With the optional callsign it will
+show output from the log associated with that callsign.
+
+=== 0^SHOW/MOON [ndays] [<prefix>|<callsign>]^Show Moon rise and set times
+Show the Moon rise and set times for a (list of) prefixes or callsigns,
+together with the azimuth and elevation of the sun currently at those
+locations.
+
+If you don't specify any prefixes or callsigns, it will show the times for
+your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
+together with the current azimuth and elevation.
+
+In addition, it will show the illuminated fraction of the moons disk.
+
+If all else fails it will show the Moonrise and set times for the node
+that you are connected to.
+
+For example:-
+
+ SH/MOON
+ SH/MOON G1TLH W5UN
+
+You can also use this command to see into the past or the future, so
+if you want to see yesterday's times then do:-
+
+ SH/MOON -1
+
+or in three days time:-
+
+ SH/MOON +3 W9
+
+Upto 366 days can be checked both in the past and in the future.
+
+Please note that the rise and set times are given as the UT times of rise and
+set on the requested UT day.
+
+=== 0^SHOW/MUF <prefix> [<hours>][long]^Show the likely propagation to a prefix
+This command allow you to estimate the likelihood of you contacting
+a station with the prefix you have specified. The output assumes a modest
+power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)
+
+The result predicts the most likely operating frequencies and signal
+levels for high frequency (shortwave) radio propagation paths on
+specified days of the year and hours of the day. It is most useful for
+paths between 250 km and 6000 km, but can be used with reduced accuracy
+for paths shorter or longer than this.
+
+The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
+used to predict the MUF given the predicted flux, day of the year,
+hour of the day and geographic coordinates of the transmitter and
+receiver. This routine is reasonably accurate for the purposes here,
+with a claimed RMS error of 3.8 MHz, but much smaller and less complex
+than the programs used by major shortwave broadcasting organizations,
+such as the Voice of America.
+
+The command will display some header information detailing its
+assumptions, together with the locations, latitude and longitudes and
+bearings. It will then show UTC (UT), local time at the other end
+(LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
+(Zen) and the likely signal strengths. Then for each frequency for which
+the system thinks there is a likelihood of a circuit it prints a value.
+
+The value is currently a likely S meter reading based on the conventional
+6dB / S point scale. If the value has a '+' appended it means that it is
+1/2 an S point stronger. If the value is preceeded by an 'm' it means that
+there is likely to be much fading and by an 's' that the signal is likely
+to be noisy.
+
+By default SHOW/MUF will show the next two hours worth of data. You
+can specify anything up to 24 hours worth of data by appending the no of
+hours required after the prefix. For example:-
+
+ SH/MUF W
+
+produces:
+
+ RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
+ Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
+ Location Lat / Long Azim
+ East Dereham, Norfolk 52 41 N 0 57 E 47
+ United-States-W 43 0 N 87 54 W 299
+ UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
+ 18 23 11.5 -35 mS0+ mS2 S3
+ 19 0 11.2 -41 mS0+ mS2 S3
+
+indicating that you will have weak, fading circuits on top band and
+80m but usable signals on 40m (about S3).
+
+inputing:-
+
+ SH/MUF W 24
+
+will get you the above display, but with the next 24 hours worth of
+propagation data.
+
+ SH/MUF W L 24
+ SH/MUF W 24 Long
+
+Gives you an estimate of the long path propagation characterics. It
+should be noted that the figures will probably not be very useful, nor
+terrible accurate, but it is included for completeness.
+
+=== 0^SHOW/MYDX^Show the DX data filtered with your spot filter.
+SHOW/DX potentially shows all the spots available in the system. Using
+SHOW/MYDX will, instead, filter the availble spots using any spot filter
+that you have set, first.
+
+This command, together with ACCEPT/SPOT or REJECT/SPOT, will allow
+you to customise the spots that you receive.
+
+So if you have said: ACC/SPOT on hf
+
+Doing a SHOW/MYDX will now only, ever, show HF spots. All the other
+options on SH/DX can still be used.
+
+=== 0^SHOW/NEWCONFIGURATION [<node>]^Show all the nodes and users visible
+This command allows you to see all the users that can be seen
+and the nodes to which they are connected.
+
+This command produces essentially the same information as
+SHOW/CONFIGURATION except that it shows all the duplication of
+any routes that might be present It also uses a different format
+which may not take up quite as much space if you don't have any
+loops.
+
+BE WARNED: the list that is returned can be VERY long
+
+=== 0^SHOW/NEWCONFIGURATION/NODE^Show all the nodes connected locally
+Show all the nodes connected to this node in the new format.
+
+=== 1^SHOW/NODE [<callsign> ...]^Show the type and version number of nodes
+Show the type and version (if connected) of the nodes specified on the
+command line. If no callsigns are specified then a sorted list of all
+the non-user callsigns known to the system will be displayed.