From: Dirk Koopman <djk@tobit.co.uk>
Date: Wed, 27 Feb 2008 21:04:35 +0000 (+0000)
Subject: modify BPQ instructions
X-Git-Tag: 1.55~6
X-Git-Url: http://dxcluster.net/gitweb/gitweb.cgi?a=commitdiff_plain;h=2f2314177644005283f6750f40b38233303446b8;p=spider.git

modify BPQ instructions
---

diff --git a/perl/Version.pm b/perl/Version.pm
index 7e018f1d..c99aae34 100644
--- a/perl/Version.pm
+++ b/perl/Version.pm
@@ -11,6 +11,6 @@ use vars qw($version $subversion $build);
 
 $version = '1.54';
 $subversion = '0';
-$build = '213';
+$build = '214';
 
 1;
diff --git a/txt/spiderBPQ_en.txt b/txt/spiderBPQ_en.txt
index c142bc6a..35cbfc9a 100644
--- a/txt/spiderBPQ_en.txt
+++ b/txt/spiderBPQ_en.txt
@@ -8,21 +8,17 @@ You need to install package Win32::API. I downloaded it from:
 
 http://ppm.activestate.com/PPMPackages/zips/8xx-builds-only/Windows/Win32-API-0.41.zip
 
+Or, better yet, use ppm to install it for you:
 
-Copy \spider\perl\BPQConnect.pm to the \spider\local directory
-
-The following bit about bpqperl.dll is NOT neaded if you are using the
-Latest (409u) BPQ32.
+ppm install Win32-API
 
-copy bpqperl.dll to your windows directory. I had problems with
-WIN32::API calling the GetData routine of the BPQ API, so had to
-create this 'glue' routine. Hopefully I can solve the problem and get
-rid of this extra routine soon.
+Copy \spider\perl\BPQConnect.pm to the \spider\local directory
 
-Edit BPQConnect.pm as appropriate - you may need to change ApplMask and BPQStreams.
+Edit BPQConnect.pm as appropriate - you may need to change ApplMask
+and BPQStreams.
 
 Although running spider will dynamically load BPQ32 if it is not
-already running, it seems to function very slowly. I suggest you load
+already running, it does not function correctly. I suggest you load
 BPQ32 before starting spider. If you are already running any other bpq
 applications thats fine, otherwise run bpq32.exe, or better still
 bpqterminal, so you can monitor what is going on.
@@ -31,7 +27,18 @@ Outward connects to other clusters seems to work, although I've only
 been able to test it with a very old DOS based AK1A system. See sample
 connect script below:
 
-Use command set/debug bpq from a sysop session to enable extra debug output
+Use command "set/debug bpq" from a sysop session to enable extra debug
+output.
+
+Remember this is very much 'alpha' software!
+
+Any problems/suggestions, feel free to contact me.
+
+73
+John G8BPQ
+
+
+Sample connect script:
 
 timeout 120
 abort Downlink|Fail
@@ -39,12 +46,5 @@ abort Downlink|Fail
 connect bpq 1 switch
 'BPQ:GM8BPQ' 'c gb7bpq'
 'connected ''
-# you can leave this out if you call the script 'gb7bpq'
+# you can leave this next line out if you call the script 'gb7bpq'
 client gb7bpq bpq
-
-Remember this is very much 'alpha' software!
-
-Any problems/suggestions, feel free to contact me.
-
-73
-John G8BPQ