It's a siple text file, so just run FC on the two INI files. ----- Original Message ----- From: "Mike" <nasfred@1bigred.com> To: <writelog@contesting.com> Sent: July 04, 2001 15:31 Subject: [WriteLog] Server Busy Alert Problem >> Hello, >> This is what was done to eliminate the Server Busy alert problem. >> Reloaded the program (full) and swaped the old writelog.ini for the new > one. Still had the same Server Busy problem. >> Used the new writelog.ini and no problem with WL! >> Gotta be in the old writelog.ini. Would like to find the problem in the > old writelog.ini, but not enthused about doing it. Seems like spending > more time fixing software and computer H/W than ant., radio, etc. Need to > relook at the priorities! >> Thanks to all for helping get WL working at K4GMH. >> 73, > Mike, K4GMH >>>> -- > 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