X-Git-Url: http://www.dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;ds=sidebyside;f=html%2Fusermanual_en-11.html;h=99ef801e03405955ea93a544603d40366e1b091d;hb=3d66b51182cb1939154d96def02efb45784958c0;hp=310711a21389b8fec3fbbc6af68adf7f741ff7cc;hpb=bccf827cfc80f9871efc8a25f9bb69f99c771d77;p=spider.git diff --git a/html/usermanual_en-11.html b/html/usermanual_en-11.html index 310711a2..99ef801e 100644 --- a/html/usermanual_en-11.html +++ b/html/usermanual_en-11.html @@ -3,13 +3,12 @@
accept Set a filter to accept something
Create a filter to accept something
+There are 2 types of filter, accept and reject. See HELP FILTERING for more +info.
+accept/announce [0-9] <pattern> Set an 'accept' filter line for announce
Create an 'accept this announce' line for a filter.
+An accept filter line means that if the announce matches this filter it is +passed onto the user. See HELP FILTERING for more info. Please read this +to understand how filters work - it will save a lot of grief later on.
+You can use any of the following things in this line:-
++
+
+ info <string> eg: iota or qsl
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <prefixes or numbers> or: G,GM,GW
+ origin_zone <prefixes or numbers>
+ origin_state <states> eg: VA,NH,RI,NH
+ by_dxcc <prefixes or numbers>
+ by_itu <prefixes or numbers>
+ by_zone <prefixes or numbers>
+ by_state <states>
+ channel <prefixes>
+ wx 1 filter WX announces
+ dest <prefixes> eg: 6MUK,WDX (distros)
+
+
+
+some examples:-
++
+
+ acc/ann dest 6MUK
+ acc/ann 2 by_zone 14,15,16
+ (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
+
+
+
+or
+
+
+ acc/ann by G,M,2
+
+
+
+for american states
++
+
+ acc/ann by_state va,nh,ri,nh
+
+
+
+You can use the tag 'all' to accept everything eg:
++
+
+ acc/ann all
+
+
+
+but this probably for advanced users...
+accept/spots [0-9] <pattern> Set an 'accept' filter line for spots
Create an 'accept this spot' line for a filter.
+An accept filter line means that if the spot matches this filter it is +passed onto the user. See HELP FILTERING for more info. Please read this +to understand how filters work - it will save a lot of grief later on.
+You can use any of the following things in this line:-
++
+
+ freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
+ on <range> same as 'freq'
+ call <prefixes> eg: G,PA,HB9
+ info <string> eg: iota or qsl
+ by <prefixes>
+ call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
+ call_itu <prefixes or numbers> or: G,GM,GW
+ call_zone <prefixes or numbers>
+ call_state <states> eg: VA,NH,RI,ME
+ by_dxcc <prefixes or numbers>
+ by_itu <prefixes or numbers>
+ by_zone <prefixes or numbers>
+ by_state <states> eg: VA,NH,RI,ME
+ origin <prefixes>
+ channel <prefixes>
+
+
+
+'call' means the callsign that has spotted 'by' whoever.
+For frequencies, you can use any of the band names defined in +SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb - +thus: hf/ssb. You can also just have a simple range like: 0/30000 - +this is more efficient than saying simply: freq HF (but don't get +too hung up about that)
+some examples:-
++
+
+ acc/spot 1 on hf/cw
+ acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+
+
+
+You can use the tag 'all' to accept everything, eg:
++
+
+ acc/spot 3 all
+
+
+
+for US states
++
+
+ acc/spots by_state VA,NH,RI,MA,ME
+
+
+
+but this probably for advanced users...
+accept/wcy [0-9] <pattern> set an 'accept' WCY filter
It is unlikely that you will want to do this, but if you do then you can +filter on the following fields:-
++
+
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <prefixes or numbers> or: G,GM,GW
+ origin_zone <prefixes or numbers>
+ by_dxcc <prefixes or numbers>
+ by_itu <prefixes or numbers>
+ by_zone <prefixes or numbers>
+ channel <prefixes>
+
+
+
+There are no examples because WCY Broadcasts only come from one place and +you either want them or not (see UNSET/WCY if you don't want them).
+This command is really provided for future use.
+See HELP FILTER for information.
+accept/wwv [0-9] <pattern> set an 'accept' WWV filter
It is unlikely that you will want to do this, but if you do then you can +filter on the following fields:-
++
+
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <prefixes or numbers> or: G,GM,GW
+ origin_zone <prefixes or numbers>
+ by_dxcc <prefixes or numbers>
+ by_itu <prefixes or numbers>
+ by_zone <prefixes or numbers>
+ channel <prefixes>
+
+
+
+for example
++
+
+ accept/wwv by_zone 4
+
+
+
+is probably the only useful thing to do (which will only show WWV broadcasts +by stations in the US).
+See HELP FILTER for information.
+announce <text> Send an announcement to LOCAL users only
<text> is the text of the announcement you wish to broadcast
+announce full <text> Send an announcement cluster wide
This will send your announcement cluster wide
+apropos <string> Search help database for <string>
Search the help database for <string> (it isn't case sensitive), and print +the names of all the commands that may be relevant.
+blank [<string>] [<nn>] Print nn (default 1) blank lines (or strings)
In its basic form this command prints one or more blank lines. However if +you pass it a string it will replicate the string for the width of the +screen (default 80) and then print that one or more times, so:
++
+
+ blank 2
+
+
+
+prints two blank lines
++
+
+ blank -
+
+
+
+prints a row of - characters once.
++
+
+ blank abc
+
+
+
+prints 'abcabcabcabcabcabc....'
+This is really only of any use in a script file and you can print a maximum +of 9 lines.
+bye Exit from the cluster
This will disconnect you from the cluster
+chat <group> <text> Chat or Conference to a group
It is now possible to JOIN a group and have network wide conferencing to that +group. DXSpider does not (and probably will not) implement the AK1A +conference mode as this seems very limiting, is hardly used and doesn't seem +to work too well anyway.
+This system uses the existing ANN system and is compatible with both other +DXSpider nodes and AK1A clusters (they use ANN/<group>).
+You can be a member of as many "groups" as you want. To join a group type:-
++
+
+ JOIN FOC (where FOC is the group name)
+
+
+
+To leave a group type:-
++
+
+ LEAVE FOC
+
+
+
+You can see which groups you are in by typing:-
++
+
+ STAT/USER
+
+
+
+and you can see whether your mate is in the group, if he connects to the +same node as you, by typing:-
++
+
+ STAT/USER g1tlh
+
+
+
+To send a message to a group type:-
++
+
+ CHAT FOC hello everyone
+
+
+
+or
++
+
+ CH #9000 hello I am back
+
+
+
+See also JOIN, LEAVE, SHOW/CHAT
+clear/announce [1|all] Clear a announce filter line
This command allows you to clear (remove) a line in a annouce filter or to +remove the whole filter.
+see CLEAR/SPOTS for a more detailed explanation.
+clear/route [1|all] Clear a route filter line
This command allows you to clear (remove) a line in a route filter or to +remove the whole filter.
+see CLEAR/SPOTS for a more detailed explanation.
+clear/spots [0-9|all] Clear a spot filter line
This command allows you to clear (remove) a line in a spot filter or to +remove the whole filter.
+If you have a filter:-
++
+
+ acc/spot 1 on hf/cw
+ acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+
+
+
+and you say:-
++
+
+ clear/spot 1
+
+
+
+you will be left with:-
++
+
+ acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+
+
+
+If you do:
++
+
+ clear/spot all
+
+
+
+the filter will be completely removed.
+clear/wcy [1|all] Clear a WCY filter line
This command allows you to clear (remove) a line in a WCY filter or to +remove the whole filter.
+see CLEAR/SPOTS for a more detailed explanation.
+clear/wwv [1|all] Clear a WWV filter line
This command allows you to clear (remove) a line in a WWV filter or to +remove the whole filter.
+see CLEAR/SPOTS for a more detailed explanation.
+dbavail Show a list of all the Databases in the system
Title says it all really, this command lists all the databases defined +in the system. It is also aliased to SHOW/COMMAND.
+dbshow <dbname> <key> Display an entry, if it exists, in a database
This is the generic user interface to the database to the database system. +It is expected that the sysop will add an entry to the local Aliases file +so that users can use the more familiar AK1A style of enquiry such as:
++
+
+ SH/BUCK G1TLH
+
+
+
+but if he hasn't and the database really does exist (use DBAVAIL or +SHOW/COMMAND to find out) you can do the same thing with:
++
+
+ DBSHOW buck G1TLH
+
+
+
+
+directory List messages
directory <from>-<to> List messages <from> message <to> message
List the messages in the messages directory.
+If there is a 'p' one space after the message number then it is a +personal message. If there is a '-' between the message number and the +'p' then this indicates that the message has been read.
+You can use shell escape characters such as '*' and '?' in the <call> +fields.
+You can combine some of the various directory commands together eg:-
++
+
+ DIR TO G1TLH 5
+
+
+
+or
+
+
+ DIR SUBJECT IOTA 200-250
+
+
+
+You can abbreviate all the commands to one letter and use ak1a syntax:-
++
+
+ DIR/T G1* 10
+ DIR/S QSL 10-100 5
+
+
+
+
+directory <nn> List last <nn> messages
directory all List all messages
directory from <call> List all messages from <call>
directory new List all new messages
directory own List your own messages
directory subject <string> List all messages with <string> in subject
directory to <call> List all messages to <call>
dx [by <call>] <freq> <call> <remarks> Send a DX spot
This is how you send a DX Spot to other users. You can, in fact, now +enter the <freq> and the <call> either way round.
++
+
+ DX FR0G 144.600
+ DX 144.600 FR0G
+ DX 144600 FR0G
+
+
+
+will all give the same result. You can add some remarks to the end +of the command and they will be added to the spot.
++
+
+ DX FR0G 144600 this is a test
+
+
+
+You can credit someone else by saying:-
++
+
+ DX by G1TLH FR0G 144.600 he isn't on the cluster
+
+
+
+The <freq> is compared against the available bands set up in the +cluster. See SHOW/BANDS for more information.
+echo <line> Echo the line to the output
This command is useful in scripts and so forth for printing the +line that you give to the command to the output. You can use this +in user_default scripts and the SAVE command for titling and so forth
+The script will interpret certain standard "escape" sequences as follows:-
++
+
+ \t - becomes a TAB character (0x09 in ascii)
+ \a - becomes a BEEP character (0x07 in ascii)
+ \n - prints a new line
+
+
+
+So the following example:-
++
+
+ echo GB7DJK is a dxcluster
+
+
+
+produces:-
++
+
+ GB7DJK is a dxcluster
+
+
+
+on the output. You don't need a \n on the end of the line you want to send.
+A more complex example:-
++
+
+ echo GB7DJK\n\tg1tlh\tDirk\n\tg3xvf\tRichard
+
+
+
+produces:-
++
+
+ GB7DJK
+ g1tlh Dirk
+ g3xvf Richard
+
+
+
+on the output.
+ +filtering... Filtering things in DXSpider
There are a number of things you can filter in the DXSpider system. They +all use the same general mechanism.
+In general terms you can create a 'reject' or an 'accept' filter which +can have up to 10 lines in it. You do this using, for example:-
++
+
+ accept/spots .....
+ reject/spots .....
+
+
+
+where ..... are the specific commands for that type of filter. There +are filters for spots, wwv, announce, wcy and (for sysops) +connects. See each different accept or reject command reference for +more details.
+There is also a command to clear out one or more lines in a filter and +one to show you what you have set. They are:-
++
+
+ clear/spots 1
+ clear/spots all
+
+
+
+and
++
+
+ show/filter
+
+
+
+There is clear/xxxx command for each type of filter.
+For now we are going to use spots for the examples, but you can apply +the principles to all types of filter.
+There are two main types of filter 'accept' or 'reject'; which you use +depends entirely on how you look at the world and what is least +writing to achieve what you want. Each filter has 10 lines (of any +length) which are tried in order. If a line matches then the action +you have specified is taken (ie reject means ignore it and accept +means gimme it).
+The important thing to remember is that if you specify a 'reject' +filter (all the lines in it say 'reject/spots' (for instance)) then if +a spot comes in that doesn't match any of the lines then you will get +it BUT if you specify an 'accept' filter then any spots that don't +match are dumped. For example if I have a one line accept filter:-
++
+
+ accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+
+
+
+then automatically you will ONLY get VHF spots from or to CQ zones 14 +15 and 16. If you set a reject filter like:
++
+
+ reject/spots on hf/cw
+
+
+
+Then you will get everything EXCEPT HF CW spots, If you am interested in IOTA +and will work it even on CW then you could say:-
++
+
+ reject/spots on hf/cw and not info iota
+
+
+
+But in that case you might only be interested in iota and say:-
++
+
+ accept/spots not on hf/cw or info iota
+
+
+
+which is exactly the same. You should choose one or the other until +you are confortable with the way it works. Yes, you can mix them +(actually you can have an accept AND a reject on the same line) but +don't try this at home until you can analyse the results that you get +without ringing up the sysop for help.
+Another useful addition now is filtering by US state
++
+
+ accept/spots by_state VA,NH,RI,ME
+
+
+
+You can arrange your filter lines into logical units, either for your +own understanding or simply convenience. I have one set frequently:-
++
+
+ reject/spots 1 on hf/cw
+ reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
+
+
+
+What this does is to ignore all HF CW spots (being a class B I can't +read any CW and couldn't possibly be interested in HF :-) and also +rejects any spots on VHF which don't either originate or spot someone +in Europe.
+This is an exmaple where you would use the line number (1 and 2 in +this case), if you leave the digit out, the system assumes '1'. Digits +'0'-'9' are available.
+You can leave the word 'and' out if you want, it is implied. You can +use any number of brackets to make the 'expression' as you want +it. There are things called precedence rules working here which mean +that you will NEED brackets in a situation like line 2 because, +without it, will assume:-
++
+
+ (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
+
+
+
+annoying, but that is the way it is. If you use OR - use +brackets. Whilst we are here CASE is not important. 'And BY_Zone' is +just 'and by_zone'.
+If you want to alter your filter you can just redefine one or more +lines of it or clear out one line. For example:-
++
+
+ reject/spots 1 on hf/ssb
+
+
+
+or
++
+
+ clear/spots 1
+
+
+
+To remove the filter in its entirty:-
++
+
+ clear/spots all
+
+
+
+There are similar CLEAR commands for the other filters:-
++
+
+ clear/announce
+ clear/wcy
+ clear/wwv
+
+
+
+ADVANCED USERS:-
+Once you are happy with the results you get, you may like to experiment.
+my example that filters hf/cw spots and accepts vhf/uhf spots from EU +can be written with a mixed filter, eg:
++
+
+ rej/spot on hf/cw
+ acc/spot on 0/30000
+ acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
+
+
+
+each filter slot actually has a 'reject' slot and an 'accept' +slot. The reject slot is executed BEFORE the accept slot.
+It was mentioned earlier that after a reject test that doesn't match, +the default for following tests is 'accept', the reverse is true for +'accept'. In the example what happens is that the reject is executed +first, any non hf/cw spot is passed to the accept line, which lets +thru everything else on HF.
+The next filter line lets through just VHF/UHF spots from EU.
+help The HELP Command
HELP is available for a number of commands. The syntax is:-
++
+
+ HELP <cmd>
+
+
+
+Where <cmd> is the name of the command you want help on.
+All commands can be abbreviated, so SHOW/DX can be abbreviated +to SH/DX, ANNOUNCE can be shortened to AN and so on.
+Look at the APROPOS <string> command which will search the help database +for the <string> you specify and give you a list of likely commands +to look at with HELP.
+join <group> Join a chat or conference group
JOIN allows you to join a network wide conference group. To join a +group (called FOC in this case) type:-
++
+
+ JOIN FOC
+
+
+
+See also CHAT, LEAVE, SHOW/CHAT
+kill <from msgno>-<to msgno> Delete a range of messages
kill <msgno> [<msgno..] Delete a message from the local system
kill <msgno> [<msgno> ...] Remove or erase a message from the system
You can get rid of any message to or originating from your callsign using +this command. You can remove more than one message at a time.
+kill from <regex> Delete messages FROM a callsign or pattern
kill to <regex> Delete messages TO a callsign or pattern
leave <group> Leave a chat or conference group
LEAVE allows you to leave a network wide conference group. To leave a +group (called FOC in this case) type:-
++
+
+ LEAVE FOC
+
+
+
+See also CHAT, JOIN, SHOW/CHAT
+links Show which nodes is physically connected
This is a quick listing that shows which links are connected and +some information about them. See WHO for a list of all connections.
+read Read the next unread personal message addressed to you
read <msgno> Read the specified message
You can read any messages that are sent as 'non-personal' and also any +message either sent by or sent to your callsign.
+reject Set a filter to reject something
Create a filter to reject something
+There are 2 types of filter, accept and reject. See HELP FILTERING for more +info.
+reject/announce [0-9] <pattern> Set a 'reject' filter line for announce
Create an 'reject this announce' line for a filter.
+A reject filter line means that if the announce matches this filter it is +passed onto the user. See HELP FILTERING for more info. Please read this +to understand how filters work - it will save a lot of grief later on.
+You can use any of the following things in this line:-
++
+
+ info <string> eg: iota or qsl
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <prefixes or numbers> or: G,GM,GW
+ origin_zone <prefixes or numbers>
+ origin_state <states> eg: VA,NH,RI,ME
+ by_dxcc <prefixes or numbers>
+ by_itu <prefixes or numbers>
+ by_zone <prefixes or numbers>
+ by_state <states> eg: VA,NH,RI,ME
+ channel <prefixes>
+ wx 1 filter WX announces
+ dest <prefixes> eg: 6MUK,WDX (distros)
+
+
+
+some examples:-
++
+
+ rej/ann by_zone 14,15,16 and not by G,M,2
+
+
+
+You can use the tag 'all' to reject everything eg:
++
+
+ rej/ann all
+
+
+
+but this probably for advanced users...
+reject/spots [0-9] <pattern> Set a 'reject' filter line for spots
Create a 'reject this spot' line for a filter.
+A reject filter line means that if the spot matches this filter it is +dumped (not passed on). See HELP FILTERING for more info. Please read this +to understand how filters work - it will save a lot of grief later on.
+You can use any of the following things in this line:-
++
+
+ freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
+ on <range> same as 'freq'
+ call <prefixes> eg: G,PA,HB9
+ info <string> eg: iota or qsl
+ by <prefixes>
+ call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
+ call_itu <prefixes or numbers> or: G,GM,GW
+ call_zone <prefixes or numbers>
+ call_state <states> eg: VA,NH,RI,ME
+ by_dxcc <prefixes or numbers>
+ by_itu <prefixes or numbers>
+ by_zone <prefixes or numbers>
+ by_state <states> eg: VA,NH,RI,ME
+ origin <prefixes>
+ channel <prefixes>
+
+
+
+'call' means the callsign that has spotted 'by' whoever.
+For frequencies, you can use any of the band names defined in +SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb - +thus: hf/ssb. You can also just have a simple range like: 0/30000 - +this is more efficient than saying simply: on HF (but don't get +too hung up about that)
+some examples:-
++
+
+ rej/spot 1 on hf
+ rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
+
+
+
+You can use the tag 'all' to reject everything eg:
++
+
+ rej/spot 3 all
+
+
+
+but this probably for advanced users...
+reject/wcy [0-9] <pattern> set a 'reject' WCY filter
It is unlikely that you will want to do this, but if you do then you can +filter on the following fields:-
++
+
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <prefixes or numbers> or: G,GM,GW
+ origin_zone <prefixes or numbers>
+ by_dxcc <prefixes or numbers>
+ by_itu <prefixes or numbers>
+ by_zone <prefixes or numbers>
+ channel <prefixes>
+
+
+
+There are no examples because WCY Broadcasts only come from one place and +you either want them or not (see UNSET/WCY if you don't want them).
+This command is really provided for future use.
+See HELP FILTER for information.
+reject/wwv [0-9] <pattern> set a 'reject' WWV filter
It is unlikely that you will want to do this, but if you do then you can +filter on the following fields:-
++
+
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <prefixes or numbers> or: G,GM,GW
+ origin_zone <prefixes or numbers>
+ by_dxcc <prefixes or numbers>
+ by_itu <prefixes or numbers>
+ by_zone <prefixes or numbers>
+ channel <prefixes>
+
+
+
+for example
++
+
+ reject/wwv by_zone 14,15,16
+
+
+
+is probably the only useful thing to do (which will only show WWV broadcasts +by stations in the US).
+See HELP FILTER for information.
+reply Reply (privately) to the last message that you have read
reply <msgno> Reply (privately) to the specified message
reply b <msgno> Reply as a Bulletin to the specified message
reply noprivate <msgno> Reply as a Bulletin to the specified message
reply rr <msgno> Reply to the specified message with read receipt
You can reply to a message and the subject will automatically have +"Re:" inserted in front of it, if it isn't already present.
+You can also use all the extra qualifiers such as RR, PRIVATE, +NOPRIVATE, B that you can use with the SEND command (see SEND +for further details)
+send <call> [<call> ...] Send a message to one or more callsigns
send copy <msgno> <call> Send a copy of a message to someone
send noprivate <call> Send a message to all stations
All the SEND commands will create a message which will be sent either to +an individual callsign or to one of the 'bulletin' addresses.
+SEND <call> on its own acts as though you had typed SEND PRIVATE, that is +it will mark the message as personal and send it to the cluster node that +that callsign is connected to. If the <call> you have specified is in fact +a known bulletin category on your node (eg: ALL) then the message should +automatically become a bulletin.
+You can have more than one callsign in all of the SEND commands.
+You can have multiple qualifiers so that you can have for example:-
++
+
+ SEND RR COPY 123 PRIVATE G1TLH G0RDI
+
+
+
+which should send a copy of message 123 to G1TLH and G0RDI and you will +receive a read receipt when they have read the message.
+SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak) +SP is an alias for SEND PRIVATE
+The system will ask you for a subject. Conventionally this should be +no longer than 29 characters for compatibility. Most modern cluster +software should accept more.
+You will now be prompted to start entering your text.
+You finish the message by entering '/EX' on a new line. For instance:
++
+
+ ...
+ bye then Jim
+ 73 Dirk
+ /ex
+
+
+
+If you have started a message and you don't want to keep it then you +can abandon the message with '/ABORT' on a new line, like:-
++
+
+ line 1
+ line 2
+ oh I just can't be bothered with this
+ /abort
+
+
+
+If you abort the message it will NOT be sent.
+When you are entering the text of your message, most normal output (such +as DX announcements and so on are suppressed and stored for latter display +(upto 20 such lines are stored, as new ones come along, so the oldest +lines are dropped).
+Also, you can enter normal commands commands (and get the output +immediately) whilst in the middle of a message. You do this by typing +the command preceeded by a '/' character on a new line, so:-
++
+
+ /dx g1tlh 144010 strong signal
+
+
+
+Will issue a dx annoucement to the rest of the cluster.
+Also, you can add the output of a command to your message by preceeding +the command with '//', thus :-
++
+
+ //sh/vhftable
+
+
+
+This will show YOU the output from SH/VHFTABLE and also store it in the +message.
+You can carry on with the message until you are ready to send it.
+send private <call> Send a personal message
send rr <call> Send a message and ask for a read receipt
set/address <your address> Record your postal address
set/announce Allow announce messages to come out on your terminal
set/anntalk Allow talk like announce messages on your terminal
set/beep Add a beep to DX and other messages on your terminal
set/dx Allow DX messages to come out on your terminal
set/dxcq Show CQ Zones on the end of DX announcements
set/dxgrid Allow QRA Grid Squares on the end of DX announcements
set/dxitu Show ITU Zones on the end of DX announcements
set/echo Make the cluster echo your input
set/email <email> ... Set email address(es) and forward your personals
set/here Tell the system you are present at your terminal
set/homenode <node> Set your normal cluster callsign
Tell the cluster system where you normally connect to. Any Messages sent +to you will normally find their way there should you not be connected. +eg:- +
+
+ SET/HOMENODE gb7djk
+
+
+
+
+set/language <lang> Set the language you want to use
You can select the language that you want the cluster to use. Currently +the languages available are en (English), de (German), es (Spanish) +and nl (Dutch).
+set/location <lat & long> Set your latitude and longitude
set/logininfo Inform when a station logs in locally
set/name <your name> Set your name
Tell the system what your name is eg:- +
+
+ SET/NAME Dirk
+
+
+
+
+set/page <lines per page> Set the lines per page
Tell the system how many lines you wish on a page when the number of line +of output from a command is more than this. The default is 20. Setting it +explicitly to 0 will disable paging. +
+
+ SET/PAGE 30
+ SET/PAGE 0
+
+
+
+The setting is stored in your user profile.
+set/password Set your own password
This command only works for a 'telnet' user (currently). It will +only work if you have a password already set. This initial password +can only be set by the sysop.
+When you execute this command it will ask you for your old password, +then ask you to type in your new password twice (to make sure you +get it right). You may or may not see the data echoed on the screen +as you type, depending on the type of telnet client you have.
+set/prompt <string> Set your prompt to <string>
set/qra <locator> Set your QRA Grid locator
Tell the system what your QRA (or Maidenhead) locator is. If you have not +done a SET/LOCATION then your latitude and longitude will be set roughly +correctly (assuming your locator is correct ;-). For example:- +
+
+ SET/QRA JO02LQ
+
+
+
+
+set/qth <your qth> Set your QTH
Tell the system where you are. For example:- +
+
+ SET/QTH East Dereham, Norfolk
+
+
+
+
+set/talk Allow TALK messages to come out on your terminal
set/usstate Allow US State info on the end of DX announcements
set/wcy Allow WCY messages to come out on your terminal
set/wwv Allow WWV messages to come out on your terminal
set/wx Allow WX messages to come out on your terminal
show/chat [<group>] [<lines>] Show any chat or conferencing
This command allows you to see any chat or conferencing that has +occurred whilst you were away. SHOW/CHAT on its own will show data for +all groups. If you use a group name then it will show only chat for +that group.
+show/configuration [<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 is normally abbreviated to: sh/c
+Normally, the list returned will be just for the nodes from your +country (because the list otherwise will be very long).
++
+
+ SH/C ALL
+
+
+
+will produce a complete list of all nodes.
+BE WARNED: the list that is returned can be VERY long
+It is possible to supply a node or part of a prefix and you will get +a list of the users for that node or list of nodes starting with +that prefix.
++
+
+ SH/C GB7DJK
+
+
+
++
+
+ SH/C SK
+
+
+
+
+show/configuration/node Show all the nodes connected locally
Show all the nodes connected to this node.
+show/contest <year and month> Show all the contests for a month
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:-
++
+
+ SH/CONTEST sep2003
+ SH/CONTEST 03 march
+
+
+
+
+show/date [<prefix>|<callsign>] Show the local time
This is very nearly the same as SHOW/TIME, the only difference the format +of the date string if no arguments are given.
+If no prefixes or callsigns are given then this command returns the local +time and UTC as the computer has it right now. If you give some prefixes +then it will show UTC and UTC + the local offset (not including DST) at +the prefixes or callsigns that you specify.
+show/db0sdx <callsign> Show QSL infomation from DB0SDX database
This command queries the DB0SDX QSL server on the internet +and returns any information available for that callsign. This service +is provided for users of this software by http://www.qslinfo.de.
+See also SHOW/QRZ, SHOW/WM7D.
+show/dx Interrogate the spot database
If you just type SHOW/DX you will get the last so many spots +(sysop configurable, but usually 10).
+In addition you can add any number of these commands in very nearly +any order to the basic SHOW/DX command, they are:-
++
+
+ on <band> - eg 160m 20m 2m 23cm 6mm
+ on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
+ on <from>/<to> - eg 1000/4000 14000-30000 (in Khz)
+ <from>-<to>
+
+
+
++
+
+ <number> - the number of spots you want
+ <from>-<to> - <from> spot no <to> spot no in the selected list
+ <from>/<to>
+
+
+
++
+
+ <prefix> - for a spotted callsign beginning with <prefix>
+ *<suffix> - for a spotted callsign ending in <suffix>
+ *<string>* - for a spotted callsign containing <string>
+
+
+
++
+
+ day <number> - starting <number> days ago
+ day <from>-<to> - <from> days <to> days ago
+ <from>/<to>
+
+
+
++
+
+ info <text> - any spots containing <text> in the info or remarks
+
+
+
++
+
+ by <call> - any spots spotted by <call> (spotter <call> is the
+ same).
+
+
+
++
+
+ qsl - this automatically looks for any qsl info on the call
+ held in the spot database.
+
+
+
++
+
+ iota [<iota>] - If the iota island number is missing it will look for
+ the string iota and anything which looks like an iota
+ island number. If you specify then it will look for
+ that island.
+
+
+
++
+
+ qra [<locator>] - this will look for the specific locator if you specify
+ one or else anything that looks like a locator.
+
+
+
++
+
+ dxcc - treat the prefix as a 'country' and look for spots
+ from that country regardless of actual prefix.
+ eg dxcc oq2
+
+
+
++
+
+ You can also use this with the 'by' keyword so
+ eg by W dxcc
+
+
+
++
+
+ e.g.
+
+
+
++
+
+ SH/DX 9m0
+ SH/DX on 20m info iota
+ SH/DX 9a on vhf day 30
+ SH/DX rf1p qsl
+ SH/DX iota
+ SH/DX iota eu-064
+ SH/DX qra jn86
+ SH/DX dxcc oq2
+ SH/DX dxcc oq2 by w dxcc
+
+
+
+
+show/dxcc <prefix> Interrogate the spot database by country
This command takes the <prefix> (which can be a full or partial +callsign if desired), looks up which internal country number it is +and then displays all the spots as per SH/DX for that country.
+This is now an alias for 'SHOW/DX DXCC'
+The options for SHOW/DX also apply to this command. +e.g.
++
+
+ SH/DXCC G
+ 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
+
+
+
+
+show/dxqsl <callsign> Show any QSL info gathered from spots
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:-
++
+
+ sh/dxqsl 4k9w
+
+
+
+You can check the raw input spots yourself with:-
++
+
+ sh/dx 4k9w qsl
+
+
+
+This gives you more background information.
+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).
+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.
+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.
+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).
+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
+
+
+
+
+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.
+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.
+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
+show/newconfiguration/node Show all the nodes connected locally
Show all the nodes connected to this node in the new format.
+show/prefix <callsign> Interrogate the prefix database
This command takes the <callsign> (which can be a full or partial +callsign or a prefix), looks up which internal country number +it is and then displays all the relevant prefixes for that country +together with the internal country no, the CQ and ITU regions.
+See also SHOW/DXCC
+show/qra <lat> <long> Convert lat/long to a QRA Grid locator
This is a multipurpose command that allows you either to calculate the +distance and bearing between two locators or (if only one locator is +given on the command line) the distance and beraing from your station +to the locator. For example:-
++
+
+ SH/QRA IO92QL
+ SH/QRA JN06 IN73
+
+
+
+The first example will show the distance and bearing to the locator from +yourself, the second example will calculate the distance and bearing from +the first locator to the second. You can use 4 or 6 character locators.
+It is also possible to convert a latitude and longitude to a locator by +using this command with a latitude and longitude as an argument, for +example:-
++
+
+ SH/QRA 52 41 N 0 58 E
+
+
+
+
+show/qra <locator> [<locator>] Show distance between QRA Grid locators
show/qrz <callsign> Show any callbook details on a callsign
This command queries the QRZ callbook server on the internet +and returns any information available for that callsign. This service +is provided for users of this software by http://www.qrz.com
+See also SHOW/WM7D for an alternative.
+show/route <callsign> ... Show the route to the callsign
This command allows you to see to which node the callsigns specified are +connected. It is a sort of inverse sh/config.
++
+
+ sh/route n2tly
+
+
+
+
+show/satellite <name> [<hours> <interval>] Show tracking data
Show the tracking data from your location to the satellite of your choice +from now on for the next few hours.
+If you use this command without a satellite name it will display a list +of all the satellites known currently to the system.
+If you give a name then you can obtain tracking data of all the passes +that start and finish 5 degrees below the horizon. As default it will +give information for the next three hours for every five minute period.
+You can alter the number of hours and the step size, within certain +limits.
+Each pass in a period is separated with a row of '-----' characters
+So for example:-
++
+
+ SH/SAT AO-10
+ SH/SAT FENGYUN1 12 2
+
+
+
+
+show/station [<callsign> ..] Show information about a callsign
Show the information known about a callsign and whether (and where) +that callsign is connected to the cluster.
++
+
+ SH/ST G1TLH
+
+
+
+If no callsign is given then show the information for yourself.
+show/sun [ndays] [<prefix>|<callsign>] Show sun rise and set times
Show the sun 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.
+If all else fails it will show the sunrise and set times for the node +that you are connected to.
+For example:-
++
+
+ SH/SUN
+ SH/SUN G1TLH K9CW ZS
+
+
+
+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/SUN -1
+
+
+
+or in three days time:-
++
+
+ SH/SUN +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.
+show/time [<prefix>|<callsign>] Show the local time
If no prefixes or callsigns are given then this command returns the local +time and UTC as the computer has it right now. If you give some prefixes +then it will show UTC and UTC + the local offset (not including DST) at +the prefixes or callsigns that you specify.
+show/usdb [call ..] Show information held on the FCC Call database
Show the City and State of a Callsign held on the FCC database if +his is being run on this system, eg:-
++
+
+ sh/usdb k1xx
+
+
+
+
+show/vhfstats [days] [date] Show the VHF DX Statistics
Show the VHF DX spots breakdown by band for the last +<days> no of days (default is 31), starting from a date (default: today).
+show/vhftable [days] [date] [prefix ...] Show the VHF DX Spotter Table
Show the VHF 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/vhftable 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/vhftable 20 pa
+
+
+
+If you want to start at a different day, simply add the date in some +recognizable form:-
++
+
+ sh/vhftable 2 25nov02
+ sh/vhftable 2 25-nov-02
+ sh/vhftable 2 021125
+ sh/vhftable 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/vhftable all
+
+
+
+
+show/wcy Show last 10 WCY broadcasts
show/wcy <n> Show last <n> WCY broadcasts
Display the most recent WCY information that has been received by the system
+ +show/wm7d <callsign> Show callbook details on a US callsigns
This command queries the WM7D callbook server on the internet +and returns any information available for that US callsign. This service +is provided for users of this software by http://www.wm7d.net.
+See also SHOW/QRZ.
+show/wwv Show last 10 WWV broadcasts
show/wwv <n> Show last <n> WWV broadcasts
Display the most recent WWV information that has been received by the system
+sysop Regain your privileges if you login remotely
The system automatically reduces your privilege level to that of a +normal user if you login in remotely. This command allows you to +regain your normal privilege level. It uses the normal system: five +numbers are returned that are indexes into the character array that is +your assigned password (see SET/PASSWORD). The indexes start from +zero.
+You are expected to return a string which contains the characters +required in the correct order. You may intersperse those characters +with others to obscure your reply for any watchers. For example (and +these values are for explanation :-):
++
+
+ password = 012345678901234567890123456789
+ > sysop
+ 22 10 15 17 3
+
+
+
+you type:-
+
+
+ aa2bbbb0ccc5ddd7xxx3n
+ or 2 0 5 7 3
+ or 20573
+
+
+
+They will all match. If there is no password you will still be offered +numbers but nothing will happen when you input a string. Any match is +case sensitive.
+talk <call> > <node> [<text>] Send a text message to another station via a node
Send a short message to any other station that is visible on the cluster +system. You can send it to anyone you can see with a SHOW/CONFIGURATION +command, they don't have to be connected locally.
+The second form of TALK is used when other cluster nodes are connected +with restricted information. This usually means that they don't send +the user information usually associated with logging on and off the cluster.
+If you know that G3JNB is likely to be present on GB7TLH, but you can only +see GB7TLH in the SH/C list but with no users, then you would use the +second form of the talk message.
+If you want to have a ragchew with someone you can leave the text message +out and the system will go into 'Talk' mode. What this means is that a +short message is sent to the recipient telling them that you are in a +'Talking' frame of mind and then you just type - everything you send will +go to the station that you asked for.
+All the usual announcements, spots and so on will still come out on your +terminal.
+If you want to do something (such as send a spot) you preceed the normal +command with a '/' character, eg:-
++
+
+ /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
+ /HELP talk
+
+
+
+To leave talk mode type:
++
+
+ /EX
+
+
+
+If you are in 'Talk' mode, there is an extention to the '/' command which +allows you to send the output to all the people you are talking to. You do +with the '//' command. For example:-
++
+
+ //sh/hftable
+
+
+
+will send the hftable as you have it to all the people you are currently +talking to.
+talk <call> [<text>] Send a text message to another station
type <filearea>/<name> Look at the contents of a file in one of the fileareas
Type out the contents of a file in a filearea. So, for example, in +filearea 'bulletins' you want to look at file 'arld051' you would +enter:- +
+
+ TYPE bulletins/arld051
+
+
+
+See also SHOW/FILES to see what fileareas are available and a +list of content.
+unset/announce Stop announce messages coming out on your terminal
unset/anntalk Stop talk like announce messages on your terminal
The announce system on legacy cluster nodes is used as a talk +substitute because the network is so poorly connected. If you:
++
+
+ unset/anntalk
+
+
+
+you will suppress several of these announces, you may miss the odd +useful one as well, but you would probably miss them anyway in the +welter of useless ones.
++
+
+ set/anntalk
+
+
+
+allows you to see them again. This is the default.
+unset/beep Stop beeps for DX and other messages on your terminal
unset/dx Stop DX messages coming out on your terminal
unset/dxcq Stop CQ Zones on the end of DX announcements
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.
+unset/dxgrid Stop QRA Grid Squares on the end of DX announcements
A standard feature which is enabled in version 1.43 and above is +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.
+Conflicts with: SET/DXCQ, SET/DXITU
+Do a STAT/USER to see which flags you have set if you are confused.
+unset/dxitu Stop ITU Zones on the end of DX announcements
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.
+Conflicts with: SET/DXGRID, SET/DXCQ, SHOW/USSTATE
+Do a STAT/USER to see which flags you have set if you are confused.
+unset/echo Stop the cluster echoing your input
If you are connected via a telnet session, different implimentations +of telnet handle echo differently depending on whether you are +connected via port 23 or some other port. You can use this command +to change the setting appropriately.
+The setting is stored in your user profile.
+YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
+unset/email Stop personal msgs being forwarded by email
If any personal messages come in for your callsign then you can use +these commands to control whether they are forwarded onto your email +address. To enable the forwarding do something like:-
++
+
+ SET/EMAIL mike.tubby@somewhere.com
+
+
+
+You can have more than one email address (each one separated by a space). +Emails are forwarded to all the email addresses you specify.
+You can disable forwarding by:-
++
+
+ UNSET/EMAIL
+
+
+
+
+unset/here Tell the system you are absent from your terminal
unset/logininfo Inform when a station logs out locally
unset/privilege Remove any privilege for this session
You can use this command to 'protect' this session from unauthorised +use. If you want to get your normal privilege back you will need to +either logout and login again (if you are on a console) or use the +SYSOP command.
+unset/prompt Set your prompt back to default
This command will set your user prompt to exactly the string that you +say. The point of this command to enable a user to interface to programs +that are looking for a specific prompt (or else you just want a different +fixed prompt).
++
+
+ SET/PROMPT clx >
+
+
+
+UNSET/PROMPT will undo the SET/PROMPT command and set you prompt back to +normal.
+unset/talk Stop TALK messages coming out on your terminal
unset/usstate Stop US State info on the end of DX announcements
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.
+unset/wcy Stop WCY messages coming out on your terminal
unset/wwv Stop WWV messages coming out on your terminal
unset/wx Stop WX messages coming out on your terminal
who Show who is physically connected
This is a quick listing that shows which callsigns are connected and +what sort of connection they have
+wx <text> Send a weather message to local users
wx full <text> Send a weather message to all cluster users