X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=sgml%2Fusermanual.sgml;h=8c0b89ce9fda7217330d611605878be2632db976;hb=5b621c40fa6165a9f0eaf592d24a63a174e4b902;hp=b74258a0e8ece4c2fef5431a9d9cf085e89a5c5c;hpb=4f3bdfa16cf0d5adf08ef13fc06384e39db485c6;p=spider.git

diff --git a/sgml/usermanual.sgml b/sgml/usermanual.sgml
index b74258a0..8c0b89ce 100644
--- a/sgml/usermanual.sgml
+++ b/sgml/usermanual.sgml
@@ -4,9 +4,10 @@
 
 <!-- Title information -->
 
-<title>The DXSpider User Manual 
-<author>Ian Maude, G0VGS, (ianmaude@btinternet.com)
-<date>Version 1.0 (Revision 3), March 2001
+<title>The DXSpider User Manual v1.50</title> 
+<author>Ian Maude, G0VGS, (g0vgs@gb7mbc.net)</author>
+<date>September 2002 revision 0.1</date>
+
 <abstract>
 A complete reference for users of the DXSpider DXCluster program.
 </abstract>
@@ -45,9 +46,9 @@ relatively old DOS software today.
 
 There are several new compatible cluster programs around now, 
 including DXSpider.  DXSpider is a clone of PacketCluster software that runs 
-under the Linux operating system.  Linux is fast becoming the choice 
-for amateur radio stations because of it's flexibility, reliability 
-and the lack of the memory limitations of DOS.  Linux supports 
+under several operating systems including Linux and Windows.  Linux is fast 
+becoming the choice for amateur radio stations because of it's flexibility, 
+reliability and the lack of the memory limitations of DOS.  Linux supports 
 multitasking and is also multiuser. It has support for AX25, ROSE, 
 NetROM and TCPIP built in, making it the ideal choice for amateur
 radio.  It is also totally free!
@@ -56,7 +57,7 @@ DXSpider was conceived and begun in 1998 by Dirk Koopman, G1TLH as an
 exercise in perl programming.  It has developed rapidly and today is a
 very powerful cluster program.  It was designed to be totally compatible
 with the AK1A program, although several commands have been extended to
-try and improve functionality.
+improve functionality.
 
 This manual is designed to help you become familiar with the commands
 that DXSpider supports and to help you get the best from the program so 
@@ -114,10 +115,8 @@ connect MBCDX
 <sect1>Telnet logins.
 
 <p>
-Because DXSpider runs under the Linux operating system, it is possible to
-make a direct telnet connection into the cluster.  With telnet 
-connections, the source callsign is not seen by DXSpider, so you will be 
-asked to login with your callsign.  
+With telnet connections, the source callsign is not seen by DXSpider, so 
+you will be asked to login with your callsign.  
 To telnet to DXSpider, you would connect to a specific port.  There is no 
 standard at the moment for a cluster telnet port but ask the sysop if 
 you are unsure.
@@ -143,11 +142,11 @@ You could also send a disconnect if you are using AX25, or a <bf>CLOSE</bf>
 command if you are connected via telnet.
 If you do not log out gracefully using one of the above commands, 
 you may find you are unable to get a full connect next time.  This
-may also happen if a NETRom connection drops.  You may get connected, 
+may also happen if a netrom connection drops.  You may get connected, 
 but nothing else will happen because the program thinks you are still 
 connected and will not let you connect twice under the same call.  
 However you could reconnect by adding a number to the end of your call,
-for example G0YLM2.  
+for example G0YLM-2.  
 This can be done by either altering your MYCALL setting in the TNC or 
 by altering your program configuration.  
 
@@ -1074,7 +1073,7 @@ but this probably for advanced users...
 
 <P>
 <tt>
-<bf>accept/announce &lsqb;0-9&rsqb; &lt;pattern&gt;</bf> Set an accept filter 
+<bf>accept/spots &lsqb;0-9&rsqb; &lt;pattern&gt;</bf> Set an accept filter 
 line for spots
 </tt>
 
@@ -1897,6 +1896,33 @@ WWV messages with the <em>unset/wwv</em> command.
 Allow WX information to be seen at your console.  You can switch off
 WX messages with the <em>unset/wx</em> command.
 
+<sect1>show/configuration
+
+<P>
+<tt>
+<bf>show/configuration &lsqb;&lt;node&gt;&rsqb;</bf> Show all visible nodes and their users
+</tt>
+
+<P>
+This command allows you to see all the users that can be seen
+and the nodes to which they are connected.  With the optional <em>node</em>,
+you can specify a particular node to look at.
+
+This command is normally abbreviated to: sh/c
+
+BE WARNED: the list that is returned can be VERY long
+
+<sect1>show/configuration/node
+
+<P>
+<tt>
+<bf>show/configuration/node</bf> Show all the nodes connected
+</tt>
+
+<P>
+Show all the nodes connected locally and the nodes they have connected.
+
+
 <sect1>show/date 
 
 <P>