I'm pretty new to WriteLog ...
but will try to provide some answers.
1. WriteLog server
Does not exist. There's some good documentation
in the help files and/or the PDF file on this.
Basically the process is:
- create the log for the contest you're interested in
- put it on a computer that has a file share on it
- on remote computers, open that shared file
- and immediately save it to the local disk
>From my understanding, WriteLog will not share a
log file on a file server with multiple clients
accessing it. (I have not tried this; that statement
is in the documentation.)
WriteLog does keep *all* log files on networked computers
in sync. If one computer was to go off-line, when its
back on-line (system crash, network problem, etc.)
WriteLog will sync all the log files - so that they
all have in essence the same copy of the log.
2. Recovery after restart
Kinda covered above. Stand alone is a no-brainer,
networked contest will sync log files.
3. Recover of WriteLog server
Doesn't exist / not applicable.
WriteLog is even designed that you can have a temp
loss of network connectivity - still logging contacts
on a system on a broken network connection, and then
just rejoin later. WriteLog will sync.
As for sticking your nose in the doc ... hee hee ...
There IS a PDF file, almost 400 pages. Its been generated
from the help files. I printed it out - it was helpful.
(I wish there was a true manual though.)
6. Operating M/M or M/2 using WriteLog to ... ???
I participate in the NC1I September VHF contest effort,
where we've been using CT in its network mode.
It works - but supporting the (MS-DOS) based network
is a real pain. Working on trying to get the group
to migrate to WriteLog. Since WriteLog is just a
Windows based application, you get to use all your
favourite networking tools, on whatever version of
Windows you like.
7. Ethernet and RFI ...
Ethernet is pretty tolerable. I've worked with it at
a number of mountain top transmitter sites, with a lot
of RF (television, paging, high power FM, cell, etc.)
Have used coax based 10base2 as well as 10 and 100 mbps
twisted pair implementations. Worst problem ever encountered
was lightning induced failure of a transistor junction on
the coax port of JetDirect cards.
Just be careful of coax Ethernet network in environments
where you're using multiple (different) power sources ...
you don't want ground (or voltage) potential on the coax
shield. (Insulate terminators and T-connectors.)
Bob McCormick W1QA
|