Don't copy the .ini or log files. You need to set them up on each
system manually. I have corrupted many an installation by doing just
that. You may also have to re-install WriteLog on all of the machines
to get it back to normal.
Mike, W1NR
-----Original Message-----
From: writelog-bounces@contesting.com
[mailto:writelog-bounces@contesting.com]On Behalf Of Gary Ferdinand W2CS
Sent: Wednesday, November 19, 2003 7:48 AM
To: writelog@contesting.com
Subject: [WriteLog] WL Failures
Perhaps someone can tell me what I'm screwing up here.
We've got a 5-position multi/multi we're trying to get going. Following
the
excellent suggestions at k9jy.com, we've assigned one position to be a
"server" (really a misnomer) position. It owns the connection to the
internet for spots. It is the position everyone else links to.
Once things appeared to be working just fine, we set up a new contest
matching the one we're about to work, logged nothing into it, and saved
it
as a base, or clean, copy. Since there's much similar among positions,
we
also did the same with writelog.ini so we could get the window layout
propagated.
We then propagated both the ini file and the clean log file to all the
other
positions, making ini edits to make certain the directories specified in
each ini accurately reflected the install of WL on each position.
Sometimes this seems to work fine. Other times, and I can't predict the
circumstances, what I get is some form of internally-corrupted band
segment
data. All spots are flagged as out of band, yet "show bands" tells me
that
the band segments are correctly covering all bands. However, when I use
the
standalone application called "edit sub-bands" found in the
start/programs
list, what I see for the trouble systems is no band segment info
whatsoever.
No extra, general, whatever with their subdirectory-like structure.
Totally
empty. Furthermore, edit sub-bands does not let me respecify them.
Can anyone with access to the source code look at this area and help me
figure out, given this symptom, why this is happening and what I can do
to
either fix it or prevent it?
Is there a gotcha somewhere in my habit of copying both the ini file
(then
edited) and the clean log file? Might using a rogue editor on the ini
file
have caused something like this to happen (ini *looks* ok to me). I
don't
recall the editor used...we've been clicking on the writelog.ini
filename in
windows explorer, so whatever editor that uses is what we've been
using...probably notepad, but I couldn't swear to it.
Thanks for all suggestions. WW is getting uncomfortably close ;-)
73
Gary W2CS
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
|