+02Jan02=======================================================================
+1. updated the copyright dates
+2. modernised and extended the Windows instructions a bit.
31Dec01=======================================================================
1. Make a couple of changes to the Installation Manual and add a FAQ on msg
deletion. (g0vgs)
my @out;
push @out, "DX Spider Cluster version $main::version (build $main::build) on \u$^O";
-push @out, "Copyright (c) 1998-2001 Dirk Koopman G1TLH";
+push @out, "Copyright (c) 1998-2002 Dirk Koopman G1TLH";
return (1, @out);
<P>Get the current version of the DX Spider distribution. This needs
to be v1.47 or later. You've got two ways (currently) of getting
this; either get a CVS update from sourceforge (if you don't know
-what this is, then it isn't for you) or get my package from:-
+what this is, then it isn't for you) or get the latest "official"
+release from:-
<P>
-<A HREF="http://www.dcc.rsgb.org/WinSpider.zip">http://www.dcc.rsgb.org/WinSpider.zip</A><P>or if you want the lastest CVS version (which is produced every night)
+<A HREF="http://www.dxcluster.org/download/index.html">http://www.dxcluster.org/download/index.html</A><P>or if you want the lastest snapshot of CVS version (which is produced
+every night):-
<P>
-<A HREF="http://www.dxcluster.org/download/CVSlatest.tgz">http://www.dxcluster.org/download/CVSlatest.tgz</A><P>If you went down the CVS route, then everything will be nicely
-set out on your local disk. If you got the ZIP file, unpack it to
+<A HREF="http://www.dxcluster.org/download/CVSlatest.tgz">http://www.dxcluster.org/download/CVSlatest.tgz</A><P>This is generally the best one to go for as it is completely up to
+date. However, there is always the very slight chance that it might
+unstable. Generally, there will be a note on the website if this is
+the case.
+<P>
+<P>The only difference between "CVSlatest.tgz" and the latest
+"official" release version is that it is more up to date. Don't confuse
+this TGZ file with "Downloading from Sourceforge with CVS" - they are two
+quite different things.
+<P>
+<P>If you went down the CVS route (ie installed wincvs and downloaded from
+sourceforge), then everything will be nicely
+set out on your local disk. If you got the TGZ file, unpack it to
somewhere convenient. The following examples assume that you put
it on drive "C:\", for convenience.
-<P><B>NOTE:</B> This distribution method will go away as soon as the first
-v1.47 tarball is released. You can use WinZip to unpack that, and
-my life will be made easier by not needing to keep this .ZIP file
-updated.
+<P>
+<P>You will need
+<A HREF="http://www.winzip.com">winzip</A> to
+manipulate the TGZ files (they are bit like ZIP files) if you are not using CVS.
<P>
<HR>
<A HREF="installation-5.html">Next</A>
<HR>
<H2><A NAME="s5">5. Installing the software</A></H2>
-<P>Ensure that your CVS session or your unZIPped file have left you
-with a directory "C:\spider\local"; if not, go to "C:\spider\"
-and create one. If "C:\spider" is missing, go back and figure out
-why, because it shouldn't be.
+<P>Ensure that your CVS session or your WINunZIPped file have left you with
+a directory "C:\spider\local" and C:\spider\local_cmd"; if not, go to
+"C:\spider\" and create them. If "C:\spider" is missing, go back and
+figure out why, because it shouldn't be.
<P>Now create your own local copy of the DXVars.pm file by:-
<P>
<BLOCKQUOTE><CODE>
<LI> $mycall - Should hold the callsign of your DX Cluster</LI>
<LI> $myname - The SysOp's first name</LI>
<LI> $myalias - the SysOp's callsign. Cannot be the same as $mycall!</LI>
+<LI> $myqth - The station's geographical location (QTH).</LI>
+<LI> $mylatitude - The station latitude in degrees and decimal fractions</LI>
+<LI> $mylongitude - The station longitude in degrees and decimal fractions</LI>
+<LI> $mylocator - The Maidenhead (or QRA) locator of the station </LI>
</UL>
-<P>You really also ought to update the $mylatitude, $mylongitude,
-$myqth and $myemail variables. And unless you are absolutely
-certain you know what you're doing, you should change nothing
-else in this file.
+<P>You really also ought to update the $myqth and $myemail variables. And
+unless you are absolutely certain you know what you're doing, you
+should change nothing else in this file. Note that if you use an "@" or
+a "$" character in one of the above strings (typically in $myemail) you must
+write them as "\@" or "\$".
<P>
-<H2><A NAME="ss5.1">5.1 The AGW packet engine</A>
+<P>
+<H2><A NAME="ss5.1">5.1 Incoming telnets</A>
+</H2>
+
+<P>If you want to enable inbound "TELNET" connections (or you are running
+Windows NT, 2000 or XP), you've got a little more work to do. From a
+handy "DOS box" that's not doing anything else, do the following:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+copy \spider\perl\Listeners.pm \spider\local
+cd \spider\local
+notepad listeners.pm
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>The following lines need attention:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+["0.0.0.0", 7300],
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>On my machine, I've simply uncommented the "0.0.0.0" entry by
+removing the '#' from the front of the line.
+<P><B>You MUST carry out this step if you are
+running on a Windows NT, 2000 or XP based system</B>
+<P>If you don't have a static hostname for your machine, and you
+intend to allow folk to connect to your machine across the
+internet, then I'd suggest you pay a visit to www.dyndns.org and
+create one for yourself. While it's free, it will take a modest
+an amount of effort on your part to read, understand and
+implement what needs to be done to set this up.
+<P>
+<P>If your machine is connected to the internet <B>and</B> you don't
+want to allow your machine to be visible to the outside world you
+should change the "0.0.0.0" to "127.0.0.1" [which is
+"localhost"]. This will then only allow connections from inside your
+machine. As was said earlier: if you aren't running Win9x (or you want
+to use DXTelnet or somesuch), then you need to have the machine
+listening at least to "127.0.0.1" ("0.0.0.0" means <B>all</B> IP
+addresses).
+<P>
+<H2><A NAME="ss5.2">5.2 The AGW packet engine</A>
</H2>
<P>On the assumption that you'll be using the SV2AGW Packet Engine
<LI>$passwd - password that matches $login</LI>
</UL>
<P>
-<H2><A NAME="ss5.2">5.2 Setting up the initial user files</A>
+<H2><A NAME="ss5.3">5.3 Setting up the initial user files</A>
</H2>
<P>Next you need to create the initial user files, etc. A tool is
</CODE></BLOCKQUOTE>
<P>Now, if that's what you've got, you are very nearly home and dry
(in as far as these particular experiments are concerned, anyhow)
-<P>To access your new cluster (from the local machine) find yourself another
-"DOS box" and do the following:-
+<P>If you are running Windows 9x you can access your new cluster (from
+the local machine) by finding yourself another "DOS box" and doing the
+following:-
<P>
<BLOCKQUOTE><CODE>
<PRE>
perl winclient.pl
</PRE>
</CODE></BLOCKQUOTE>
-<P>If you are rewarded with a display which looks something like:-
+<P>If you are running Windows NT, 2000 or XP then winclient.pl does not
+work. We don't know why other than this seems to be some kind of
+incomaptibility in perl. You can achieve the same thing by telnetting
+to the port you defined in Listeners.pm (7300 as default), thus:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+Menu->Start->Run
+telnet localhost 7300
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>On getting the <B>login:</B> prompt, enter your sysop callsign (the one you
+put in DXVars.pm as $myalias).
+<P>
+<P>I would recommend <B>strongly</B> that you obtain a better telnet
+client than that which comes with windows (I use
+<A HREF="http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">PuTTY</A>).
+<P>
+<P>Anyway, if you are rewarded with a display which looks something like:-
<P>
<BLOCKQUOTE><CODE>
<PRE>
from the version of DXVars.pm that was on the machine when I
started the winclient.pl)
<P>
-<H2><A NAME="ss5.3">5.3 Incoming telnets</A>
-</H2>
-
-<P>If you want to enable inbound "TELNET" connections, you've got a
-little more work to do. From a handy "DOS box" that's not doing
-anything else, do the following:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-copy \spider\perl\listeners.pm \spider\local
-cd \spider\local
-notepad listeners.pm
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>The following lines need attention:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-["0.0.0.0", 7300],
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>On my machine, I've simply uncommented the "0.0.0.0" entry by
-removing the '#' from the front of the line.
-<P>If you don't have a static hostname for your machine, and you
-intend to allow folk to connect to your machine across the
-internet, then I'd suggest you pay a visit to www.dyndns.org and
-create one for yourself. While it's free, it will take a modest
-an amount of effort on your part to read, understand and
-implement what needs to be done to set this up.
+<P>The interface is very basic. It is a simple command line. There are
+better looking interfaces. Most of the "standard" logging and DX
+Cluster access programs that are capable of connecting via a TCP or
+telnet connection will work as a "Sysop Console" client. You connect
+to "localhost" on the port that you defined in Listeners.pm (usually
+7300). I recommend packages like
+<A HREF="http://www.qsl.net/wd4ngb/telnet.htm">DXTelnet</A>.
<P>
<H2><A NAME="ss5.4">5.4 Connecting to other clusters</A>
</H2>
-<P>If you want to connect this to another cluster, then you'll want
-to negotiate a link with someone. For experimental purposes, I'm
-happy to allow folk to connect to GB7DXA (spud.ath.cx), on the
-understanding that the system may or may not be there and may or
-may not be connected to anything particularly useful at any given
-moment. Contact me by Email if you want me to set up a connection
-for you.
+<P>If you want to connect this to another cluster, then you'll want to
+negotiate a link with someone. For experimental purposes, I'm happy to
+allow folk to connect to GB7DXA (spud.ath.cx), on the understanding
+that the system may or may not be there and may or may not be
+connected to anything particularly useful at any given moment. Contact
+me by
+<A HREF="mailto:g0rdi@blacksheep.org">Email</A> if you
+want me to set up a connection for you.
<P>
<HR>
<A HREF="installation-6.html">Next</A>
<H2><A NAME="toc5">5.</A> <A HREF="installation-5.html">Installing the software</A></H2>
<UL>
-<LI><A HREF="installation-5.html#ss5.1">5.1 The AGW packet engine</A>
-<LI><A HREF="installation-5.html#ss5.2">5.2 Setting up the initial user files</A>
-<LI><A HREF="installation-5.html#ss5.3">5.3 Incoming telnets</A>
+<LI><A HREF="installation-5.html#ss5.1">5.1 Incoming telnets</A>
+<LI><A HREF="installation-5.html#ss5.2">5.2 The AGW packet engine</A>
+<LI><A HREF="installation-5.html#ss5.3">5.3 Setting up the initial user files</A>
<LI><A HREF="installation-5.html#ss5.4">5.4 Connecting to other clusters</A>
</UL>
<P>
Log('cluster', "DXSpider V$version, build $build started");
# banner
-dbg("Copyright (c) 1998-2001 Dirk Koopman G1TLH");
+dbg("Copyright (c) 1998-2002 Dirk Koopman G1TLH");
dbg("DXSpider Version $version, build $build started");
# load Prefixes
Get the current version of the DX Spider distribution. This needs
to be v1.47 or later. You've got two ways (currently) of getting
this; either get a CVS update from sourceforge (if you don't know
-what this is, then it isn't for you) or get my package from:-
+what this is, then it isn't for you) or get the latest "official"
+release from:-
-<htmlurl url="http://www.dcc.rsgb.org/WinSpider.zip" name="http://www.dcc.rsgb.org/WinSpider.zip">
+<htmlurl url="http://www.dxcluster.org/download/index.html" name="http://www.dxcluster.org/download/index.html">
-or if you want the lastest CVS version (which is produced every night)
+or if you want the lastest snapshot of CVS version (which is produced
+every night):-
<htmlurl url="http://www.dxcluster.org/download/CVSlatest.tgz" name="http://www.dxcluster.org/download/CVSlatest.tgz">
-If you went down the CVS route, then everything will be nicely
-set out on your local disk. If you got the ZIP file, unpack it to
+This is generally the best one to go for as it is completely up to
+date. However, there is always the very slight chance that it might
+unstable. Generally, there will be a note on the website if this is
+the case.
+
+<p>The only difference between "CVSlatest.tgz" and the latest
+"official" release version is that it is more up to date. Don't confuse
+this TGZ file with "Downloading from Sourceforge with CVS" - they are two
+quite different things.
+
+<p>
+If you went down the CVS route (ie installed wincvs and downloaded from
+sourceforge), then everything will be nicely
+set out on your local disk. If you got the TGZ file, unpack it to
somewhere convenient. The following examples assume that you put
it on drive "C:\", for convenience.
-<bf>NOTE:</bf> This distribution method will go away as soon as the first
-v1.47 tarball is released. You can use WinZip to unpack that, and
-my life will be made easier by not needing to keep this .ZIP file
-updated.
+<p>You will need <htmlurl url="http://www.winzip.com" name="winzip"> to
+manipulate the TGZ files (they are bit like ZIP files) if you are not using CVS.
<sect>Installing the software
<P>
-Ensure that your CVS session or your unZIPped file have left you
-with a directory "C:\spider\local"; if not, go to "C:\spider\"
-and create one. If "C:\spider" is missing, go back and figure out
-why, because it shouldn't be.
+Ensure that your CVS session or your WINunZIPped file have left you with
+a directory "C:\spider\local" and C:\spider\local_cmd"; if not, go to
+"C:\spider\" and create them. If "C:\spider" is missing, go back and
+figure out why, because it shouldn't be.
Now create your own local copy of the DXVars.pm file by:-
<item> $mycall - Should hold the callsign of your DX Cluster
<item> $myname - The SysOp's first name
<item> $myalias - the SysOp's callsign. Cannot be the same as $mycall!
+<item> $myqth - The station's geographical location (QTH).
+<item> $mylatitude - The station latitude in degrees and decimal fractions
+<item> $mylongitude - The station longitude in degrees and decimal fractions
+<item> $mylocator - The Maidenhead (or QRA) locator of the station
</itemize>
-You really also ought to update the $mylatitude, $mylongitude,
-$myqth and $myemail variables. And unless you are absolutely
-certain you know what you're doing, you should change nothing
-else in this file.
+You really also ought to update the $myqth and $myemail variables. And
+unless you are absolutely certain you know what you're doing, you
+should change nothing else in this file. Note that if you use an "@" or
+a "$" character in one of the above strings (typically in $myemail) you must
+write them as "\@" or "\$".
+
+
+<sect1>Incoming telnets
+
+<P>
+If you want to enable inbound "TELNET" connections (or you are running
+Windows NT, 2000 or XP), you've got a little more work to do. From a
+handy "DOS box" that's not doing anything else, do the following:-
+
+<tscreen><verb>
+copy \spider\perl\Listeners.pm \spider\local
+cd \spider\local
+notepad listeners.pm
+</verb></tscreen>
+
+The following lines need attention:-
+
+<tscreen><verb>
+["0.0.0.0", 7300],
+</verb></tscreen>
+
+On my machine, I've simply uncommented the "0.0.0.0" entry by
+removing the '#' from the front of the line.
+
+<bf>You MUST carry out this step if you are
+running on a Windows NT, 2000 or XP based system</bf>
+
+If you don't have a static hostname for your machine, and you
+intend to allow folk to connect to your machine across the
+internet, then I'd suggest you pay a visit to www.dyndns.org and
+create one for yourself. While it's free, it will take a modest
+an amount of effort on your part to read, understand and
+implement what needs to be done to set this up.
+
+<p>If your machine is connected to the internet <bf>and</bf> you don't
+want to allow your machine to be visible to the outside world you
+should change the "0.0.0.0" to "127.0.0.1" [which is
+"localhost"]. This will then only allow connections from inside your
+machine. As was said earlier: if you aren't running Win9x (or you want
+to use DXTelnet or somesuch), then you need to have the machine
+listening at least to "127.0.0.1" ("0.0.0.0" means <bf>all</bf> IP
+addresses).
<sect1>The AGW packet engine
Now, if that's what you've got, you are very nearly home and dry
(in as far as these particular experiments are concerned, anyhow)
-To access your new cluster (from the local machine) find yourself another
-"DOS box" and do the following:-
+If you are running Windows 9x you can access your new cluster (from
+the local machine) by finding yourself another "DOS box" and doing the
+following:-
<tscreen><verb>
cd \spider\perl
perl winclient.pl
</verb></tscreen>
-If you are rewarded with a display which looks something like:-
+If you are running Windows NT, 2000 or XP then winclient.pl does not
+work. We don't know why other than this seems to be some kind of
+incomaptibility in perl. You can achieve the same thing by telnetting
+to the port you defined in Listeners.pm (7300 as default), thus:-
+
+<tscreen><verb>
+Menu->Start->Run
+telnet localhost 7300
+</verb></tscreen>
+
+On getting the <bf>login:</bf> prompt, enter your sysop callsign (the one you
+put in DXVars.pm as $myalias).
+
+<p>I would recommend <bf>strongly</bf> that you obtain a better telnet
+client than that which comes with windows (I use <htmlurl
+url="http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html"
+name="PuTTY">).
+
+<p>Anyway, if you are rewarded with a display which looks something like:-
<tscreen><verb>
Hello Iain, this is GB7SJP in Amersham, Bucks running DXSpider V1.47
from the version of DXVars.pm that was on the machine when I
started the winclient.pl)
-<sect1>Incoming telnets
-
-<P>
-If you want to enable inbound "TELNET" connections, you've got a
-little more work to do. From a handy "DOS box" that's not doing
-anything else, do the following:-
-
-<tscreen><verb>
-copy \spider\perl\listeners.pm \spider\local
-cd \spider\local
-notepad listeners.pm
-</verb></tscreen>
-
-The following lines need attention:-
-
-<tscreen><verb>
-["0.0.0.0", 7300],
-</verb></tscreen>
-
-On my machine, I've simply uncommented the "0.0.0.0" entry by
-removing the '#' from the front of the line.
-
-If you don't have a static hostname for your machine, and you
-intend to allow folk to connect to your machine across the
-internet, then I'd suggest you pay a visit to www.dyndns.org and
-create one for yourself. While it's free, it will take a modest
-an amount of effort on your part to read, understand and
-implement what needs to be done to set this up.
+<p>The interface is very basic. It is a simple command line. There are
+better looking interfaces. Most of the "standard" logging and DX
+Cluster access programs that are capable of connecting via a TCP or
+telnet connection will work as a "Sysop Console" client. You connect
+to "localhost" on the port that you defined in Listeners.pm (usually
+7300). I recommend packages like <htmlurl
+url="http://www.qsl.net/wd4ngb/telnet.htm" name="DXTelnet">.
<sect1>Connecting to other clusters
<P>
-If you want to connect this to another cluster, then you'll want
-to negotiate a link with someone. For experimental purposes, I'm
-happy to allow folk to connect to GB7DXA (spud.ath.cx), on the
-understanding that the system may or may not be there and may or
-may not be connected to anything particularly useful at any given
-moment. Contact me by Email if you want me to set up a connection
-for you.
+If you want to connect this to another cluster, then you'll want to
+negotiate a link with someone. For experimental purposes, I'm happy to
+allow folk to connect to GB7DXA (spud.ath.cx), on the understanding
+that the system may or may not be there and may or may not be
+connected to anything particularly useful at any given moment. Contact
+me by <htmlurl url="mailto:g0rdi@blacksheep.org" name="Email"> if you
+want me to set up a connection for you.
<sect>General Information
5. Installing the software
- 5.1 The AGW packet engine
- 5.2 Setting up the initial user files
- 5.3 Incoming telnets
+ 5.1 Incoming telnets
+ 5.2 The AGW packet engine
+ 5.3 Setting up the initial user files
5.4 Connecting to other clusters
6. General Information
Get the current version of the DX Spider distribution. This needs to
be v1.47 or later. You've got two ways (currently) of getting this;
either get a CVS update from sourceforge (if you don't know what this
- is, then it isn't for you) or get my package from:-
+ is, then it isn't for you) or get the latest "official" release from:-
- http://www.dcc.rsgb.org/WinSpider.zip
+ http://www.dxcluster.org/download/index.html
- or if you want the lastest CVS version (which is produced every night)
+ or if you want the lastest snapshot of CVS version (which is produced
+ every night):-
http://www.dxcluster.org/download/CVSlatest.tgz
- If you went down the CVS route, then everything will be nicely set out
- on your local disk. If you got the ZIP file, unpack it to somewhere
+ This is generally the best one to go for as it is completely up to
+ date. However, there is always the very slight chance that it might
+ unstable. Generally, there will be a note on the website if this is
+ the case.
+
+
+ The only difference between "CVSlatest.tgz" and the latest "official"
+ release version is that it is more up to date. Don't confuse this TGZ
+ file with "Downloading from Sourceforge with CVS" - they are two quite
+ different things.
+
+
+ If you went down the CVS route (ie installed wincvs and downloaded
+ from sourceforge), then everything will be nicely set out on your
+ local disk. If you got the TGZ file, unpack it to somewhere
convenient. The following examples assume that you put it on drive
"C:\", for convenience.
- NOTE: This distribution method will go away as soon as the first v1.47
- tarball is released. You can use WinZip to unpack that, and my life
- will be made easier by not needing to keep this .ZIP file updated.
+
+ You will need winzip to manipulate the TGZ files (they are bit like
+ ZIP files) if you are not using CVS.
5. Installing the software
- Ensure that your CVS session or your unZIPped file have left you with
- a directory "C:\spider\local"; if not, go to "C:\spider\" and create
- one. If "C:\spider" is missing, go back and figure out why, because it
- shouldn't be.
+ Ensure that your CVS session or your WINunZIPped file have left you
+ with a directory "C:\spider\local" and C:\spider\local_cmd"; if not,
+ go to "C:\spider\" and create them. If "C:\spider" is missing, go back
+ and figure out why, because it shouldn't be.
+
Now create your own local copy of the DXVars.pm file by:-
- cd \spider\local
+ cd \spider\local
o $myalias - the SysOp's callsign. Cannot be the same as $mycall!
- You really also ought to update the $mylatitude, $mylongitude, $myqth
- and $myemail variables. And unless you are absolutely certain you know
- what you're doing, you should change nothing else in this file.
+ o $myqth - The station's geographical location (QTH).
+
+ o $mylatitude - The station latitude in degrees and decimal fractions
+
+ o $mylongitude - The station longitude in degrees and decimal
+ fractions
+
+ o $mylocator - The Maidenhead (or QRA) locator of the station
+
+ You really also ought to update the $myqth and $myemail variables. And
+ unless you are absolutely certain you know what you're doing, you
+ should change nothing else in this file. Note that if you use an "@"
+ or a "$" character in one of the above strings (typically in $myemail)
+ you must write them as "\@" or "\$".
+
+
+
+ 5.1. Incoming telnets
+
+ If you want to enable inbound "TELNET" connections (or you are running
+ Windows NT, 2000 or XP), you've got a little more work to do. From a
+ handy "DOS box" that's not doing anything else, do the following:-
+
+
+
+
+
+ copy \spider\perl\Listeners.pm \spider\local
+ cd \spider\local
+ notepad listeners.pm
+
+
+
+
+ The following lines need attention:-
+
+
+
+ ["0.0.0.0", 7300],
+
+
- 5.1. The AGW packet engine
+ On my machine, I've simply uncommented the "0.0.0.0" entry by removing
+ the '#' from the front of the line.
+
+ You MUST carry out this step if you are running on a Windows NT, 2000
+ or XP based system
+
+ If you don't have a static hostname for your machine, and you intend
+ to allow folk to connect to your machine across the internet, then I'd
+ suggest you pay a visit to www.dyndns.org and create one for yourself.
+ While it's free, it will take a modest an amount of effort on your
+ part to read, understand and implement what needs to be done to set
+ this up.
+
+
+ If your machine is connected to the internet and you don't want to
+ allow your machine to be visible to the outside world you should
+ change the "0.0.0.0" to "127.0.0.1" [which is "localhost"]. This will
+ then only allow connections from inside your machine. As was said
+ earlier: if you aren't running Win9x (or you want to use DXTelnet or
+ somesuch), then you need to have the machine listening at least to
+ "127.0.0.1" ("0.0.0.0" means all IP addresses).
+
+
+ 5.2. The AGW packet engine
On the assumption that you'll be using the SV2AGW Packet Engine to
interface your radios to the cluster, you should now create your own
o $passwd - password that matches $login
-
-
- 5.2. Setting up the initial user files
+ 5.3. Setting up the initial user files
Next you need to create the initial user files, etc. A tool is
supplied which will do this for you. To run the tool:-
+
Now, if that's what you've got, you are very nearly home and dry (in
as far as these particular experiments are concerned, anyhow)
- To access your new cluster (from the local machine) find yourself
- another "DOS box" and do the following:-
-
-
-
-
- cd \spider\perl
- perl winclient.pl
-
+ If you are running Windows 9x you can access your new cluster (from
+ the local machine) by finding yourself another "DOS box" and doing the
+ following:-
- If you are rewarded with a display which looks something like:-
+ cd \spider\perl
+ perl winclient.pl
- Hello Iain, this is GB7SJP in Amersham, Bucks running DXSpider V1.47
- Cluster: 1 nodes, 1 local / 1 total users Max users 2 Uptime 0 00:00
- M0ADI de GB7SJP 4-Mar-2001 1511Z >
+ If you are running Windows NT, 2000 or XP then winclient.pl does not
+ work. We don't know why other than this seems to be some kind of
+ incomaptibility in perl. You can achieve the same thing by telnetting
+ to the port you defined in Listeners.pm (7300 as default), thus:-
- You've arrived. Try some commands, and see how they feel. (In case you
- were wondering, "Iain", "M0ADI" and "GB7SJP" all came from the version
- of DXVars.pm that was on the machine when I started the winclient.pl)
+ Menu->Start->Run
+ telnet localhost 7300
- 5.3. Incoming telnets
- If you want to enable inbound "TELNET" connections, you've got a
- little more work to do. From a handy "DOS box" that's not doing
- anything else, do the following:-
+ On getting the login: prompt, enter your sysop callsign (the one you
+ put in DXVars.pm as $myalias).
- copy \spider\perl\listeners.pm \spider\local
- cd \spider\local
- notepad listeners.pm
+ I would recommend strongly that you obtain a better telnet client than
+ that which comes with windows (I use PuTTY).
+ Anyway, if you are rewarded with a display which looks something
+ like:-
- The following lines need attention:-
-
+ Hello Iain, this is GB7SJP in Amersham, Bucks running DXSpider V1.47
+ Cluster: 1 nodes, 1 local / 1 total users Max users 2 Uptime 0 00:00
+ M0ADI de GB7SJP 4-Mar-2001 1511Z >
- ["0.0.0.0", 7300],
+ You've arrived. Try some commands, and see how they feel. (In case you
+ were wondering, "Iain", "M0ADI" and "GB7SJP" all came from the version
+ of DXVars.pm that was on the machine when I started the winclient.pl)
- On my machine, I've simply uncommented the "0.0.0.0" entry by removing
- the '#' from the front of the line.
- If you don't have a static hostname for your machine, and you intend
- to allow folk to connect to your machine across the internet, then I'd
- suggest you pay a visit to www.dyndns.org and create one for yourself.
- While it's free, it will take a modest an amount of effort on your
- part to read, understand and implement what needs to be done to set
- this up.
+ The interface is very basic. It is a simple command line. There are
+ better looking interfaces. Most of the "standard" logging and DX
+ Cluster access programs that are capable of connecting via a TCP or
+ telnet connection will work as a "Sysop Console" client. You connect
+ to "localhost" on the port that you defined in Listeners.pm (usually
+ 7300). I recommend packages like DXTelnet.
5.4. Connecting to other clusters
connected to anything particularly useful at any given moment. Contact
me by Email if you want me to set up a connection for you.
+
6. General Information
The following relates to all versions of DXSpider and is not platform
-
-
-
-
-
projects / spider.git / commitdiff