Hello,
The root cause of the Server Busy alert problem has been found when using
WriteLog and RITTY. It was having RITTY's comm port the same as WL's.
Changed the RITTY comm port to "none" and the WL/RITTY works as it should.
What I've done is create a special RITTY initiation file for use in WL.
The new initiation file is called WL_RITTY.ini and has all the RITTY
contest setting with the comm port selection in RITTY set to "none". The
WL_RITTY.pif file's command line has WL_RITTY.ini after the "W". The
regular RITTY initiation file, RITTY.ini, was not changed and is used when
RITTY is operated as a stand alone RTTY program.
All the other "fixes" can be tracked back to making a change in the comm
ports for WL and RITTY and not having both directed to the same port. The
problem has been duplicated by changing the comm port in RITTY to the same
comm port used by WL.
Hope the above helps others avoid what I went through. (Got so bad, that
cat herding as a hobby started looking good.)
73,
Mike, K4GMH
--
WWW: http://www.writelog.com/
Submissions: writelog@contesting.com
Administrative requests: writelog-REQUEST@contesting.com
Problems: owner-writelog@contesting.com
|