</H2>
<P>
-From version 1.47 there is a new (more efficient) way of doing this
+>From version 1.47 there is a new (more efficient) way of doing this
(see next section) but, if you prefer, the method of doing it described
here will continue to work just fine.
<P>
<H2><A NAME="ss4.3">4.3 Setting up telnet connects (from 1.47 onwards)</A>
</H2>
-<P>From version 1.47 you can choose to allow the perl cluster.pl program to
+<P>>From version 1.47 you can choose to allow the perl cluster.pl program to
allow connections directly (i.e. not via the <CODE>/spider/src/client</CODE>
interface program). If you are using Windows then this is the only method
available of allowing incoming telnet connections.
</CODE></BLOCKQUOTE>
<P>
<P>This line works fine for RedHat distributions. It is also fine for SuSE up to
-7.0. From Suse 7.1 you need to add runlevels 2 and 5 like this ...
+7.0. From SuSE 7.1 you need to add runlevels 2 and 5 like this ...
<P>
<BLOCKQUOTE><CODE>
<PRE>
<P>This will automatically start DXSpider on tty7 (ALT-F7) on bootup and restart
it should it crash for any reason.
<P>
+<P>NB: It should be noted that /dev/tty7 is only an example. Some SuSE systems will
+only accept upto tty6. It really does not matter which tty you run it on.
+<P>
<P>As root type the command <EM>telinit q</EM>. DXSpider should start up
immediately. You will see the output on tty7 and if you login as <EM>sysop</EM>
you should find everything running nicely.