We ran networked computers with the main Writelog server being hardwired
to the router and the rest wireless. No issues to report other than one
of the stations had the infamous "no data entry window" bug (reported
earlier) which required a full de-install, registry and .ini file cleanup,
and a reinstall to fix. A time consuming pain in the ass but at least
solvable.
I networked Writelog this way for dupe reasons and to maintain a central
backup of the logs on my laptop should one or more of the computers fail.
It also makes it easy to plunk in a new PC and re-replicate the data over
the network should one fail, or have one replicating all the time ready to
plunk in should the need arise. I took out all the bells and whistles and
just had duping and the mult list visible as the old timers easily get
their knickers in a twist and refuse to use anything that smacks of change
or complexity.
I would recommend to anyone doing this that they put the master Writelog
server on a laptop with any of the power save features disabled, or on a
PC with a large generator capable UPS for at least thirty minutes uptime.
Ditto for the wireless router so neither go down when the generators run
out of gas. This would solve a number of potential problems. Also, in
wireless workstations. Some of them tend to roam to their favourite
default hot spot name, ie. Linksys, default, etc. Change the advanced
settings so that only your 802.11 network name is visible and at the top
of the priority list.
And setup an account on each PC that comes up as default on boot but is
devoid of any Power User or Administrative functions - and password
protect the administrator account. Blocking the flying fingers of field
day fate is always a wise move.
I suspect that issues discussed of late were related to RFI. Writelog
does some funny things when random and sometimes lengthy network
disconnects happen. I've noticed no RFI issues with 802.11 routers as
long as the router itself is not in a strong RF field area and there are
no long network cables plugged into it (6' and shorter seem to be fine).
Shielding the router and providing RF blocking from the power supply leads
will help as well. Ping your workstations continually during field day
(or a contest) to see if you have issues. If you do, fix them right away.
Dale VE7GL
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
|