[WriteLog] Server busy message

[W. Wright, W5XD]

When running RTTY, WriteLog has two programs running, one for
the main log and the other for RTTY. Your description makes it
sound like the main log program (writel32.exe) has locked up.

I will understand if you don't believe me, but it is just 
about impossible for WriteLog to lock up by itself. Only
the Windows system and device drivers can do that.
Often such a problem comes from a COMM port driver for
an add-in COMM port board. The motherboard COMM ports on
just about all machines of the past 10 years or so are 
almost never a problem. Before you "chuck this program"
you might try running with no rig control for a while.

The lost QSOs you report should never happen. WL journals
all QSOs to disk as they are logged, and knows how to
recover them when restarted. It is possible, I suppose,
that the journalling fails under certain circumstances,
but, except for a few angry posts on this reflector
that I cannot verify, I have never seen any evidence
that WL loses QSOs on crashes.

Sorry I can't be of more help.

Wayne, W5XD


> -----Original Message-----
> From: owner-writelog@contesting.com
> [mailto:owner-writelog@contesting.com]On Behalf Of Jim Rhodes
> Sent: Sunday, February 11, 2001 01:52
> To: writelog@contesting.com
> Subject: Re: [WriteLog] Server busy message
> 
> 
> 
> A little more info. Using soundcard so only com port in use 
> was for rig 
> control (TS570DG). I had just entered a Q and was tuning up 
> the band when I 
> got the error message. Windows sounds all disabled, so should be no 
> conflict there. Running Win98SE.
> When this happened with 10.22 I got a message when I 
> restarted the program 
> that asked if I wanted to recover the Q's, this time I did 
> not get that 
> message. I really hate to lose Q's that way!!!
> Anybody have any ideas?
> At 19:07 02/10/2001 -0600, you wrote:
> 
> >OK, before I chuck this program out. What is going on when I 
> get an error 
> >message (right over the RTTY tune window) that says something about 
> >"unable to proceed, Server busy" and gives the name of the 
> active log 
> >file. I ended up having to 3 finger salute to get out of 
> Writelog and then 
> >lost a number of Q's when I rebooted. I had the same trouble 
> with 10.22 
> >and now again with 10.23. Never a problem with the older 
> versions that I 
> >can recall.
> >
> >Jim Rhodes K0XU
> >rhodes@evertek.net
> >
> >
> >--
> >WWW:                      http://www.writelog.com/
> >Submissions:              writelog@contesting.com
> >Administrative requests:  writelog-REQUEST@contesting.com
> >Problems:                 owner-writelog@contesting.com
> 
> Jim Rhodes K0XU
> rhodes@evertek.net
> 
> 
> --
> WWW:                      http://www.writelog.com/
> Submissions:              writelog@contesting.com
> Administrative requests:  writelog-REQUEST@contesting.com
> Problems:                 owner-writelog@contesting.com
> 
> 

--
WWW:                      http://www.writelog.com/
Submissions:              writelog@contesting.com
Administrative requests:  writelog-REQUEST@contesting.com
Problems:                 owner-writelog@contesting.com