Thanks John. Also may I repeat a feature request: that there be a sysop/configuration option to order the node table alphabetically by callsign. Having itMessage 1 of 3 , Nov 21, 2008View Source
Also may I repeat a feature request: that there be a sysop/configuration option to order the node table alphabetically by callsign. Having it alpha alias as now is the more user unfriendly of the two methods because nodes are not grouped by country/geo-location making it difficult to find a required destination.
Ok, Eric. I'm away for a few days, but will look into it when I get back.
From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of Eric Carling
Sent: 21 November 2008 12:37
Subject: [BPQ32] Problems with new version
The latest version gives me two issues: the first is the pre-existing failure of agwtobpq.exe to run for very long in MS Vista before it locks up. I’d prefer to use it over the dll method (in AR-Cluster) but I can and have been managing to use dll so this is not critical to me.
A new issue has arisen from installing the new version: I have DXSpider (now my preferred cluster software over ARC) and I have BPQ enabled within it so that Spider launches BPQ automatically. After the update, BPQ32 launches but is locked up. In the Console window I see “Initialising Port 02 AXIP unable to read bpqaxip.cfg file”
If I manually start BPQ32 then the error does not occur and I can then start Spider and all is well. However I have lost the ability to have Spider start BPQ sucessfully. If I re-install the previous version of BPQ, Spider will start BPQ as before. Something about the update has screwed this up in my case. This, as I said above, is in MS Vista.