In my experience, the error occurs when any one of the windows is tied up
doing a dialog box such as a file selection or whatever. I normally get a
message that allows a retry. So I ignore it until I complete the dialog,
then specify retry and everything continues.
As for the rebooting PTC when it refuses to read the read buffers, actually
it does read them, just incredibly slow. Only solution is to restart
everything. The PTC also completely crashed once -- that is probably a PTC
problem.
I also was privileged to experience the continuing problems with the DXP38
interface. Basically, if you try to "stack" message keys (hit F11 for CQ
twice quickly), it fails to properly send and locks up in transmit. Also,
do not ever interrupt a DXP38 transmission -- it can have the similar
effect.
I also experienced the sequence numbering problems, but found an acceptable
workaround.
Version 10.22 D, didn't know that there was a .23x or would have used that.
Overall Writelog did a fantastic job and was a lot of fun doing SO2R.
73,
Mike WA0SXV
----- Original Message -----
From: "Don Hill" <aa5au@msn.com>
To: <writelog@contesting.com>
Sent: Monday, January 08, 2001 09:27
Subject: Re: [WriteLog] "Server not available" error?
>
> I think Randy hit close to the problem. I didn't have this problem and
normally
> don't. The only time it has happened is when I tried to open a 3rd RTTY
window
> while doing some testing before the contest. The problem was that the COM
> port assigned to that window was already in use and thus I got the error.
>
--
WWW: http://www.writelog.com/
Submissions: writelog@contesting.com
Administrative requests: writelog-REQUEST@contesting.com
Problems: owner-writelog@contesting.com
|