I agree with Dave - no big deal. I could write a batch file (or script
in Linux) to run a clock nag, pause, then open Fldigi. QED
73,
-Joe-
David Kleber wrote:
Yes, these things are all apparent to most of us... just like you'd
think anyone out there should be able to find the program file
directories by breezing through the file structure with explorer. Yet,
folks will still have the wrong time or UTC correction made. It's
just a simple suggesting I was making... there are currently, and
always will be, folks that will miss this. Maybe they're complete
idiots not worthy of running emcomm ops, or maybe they just simply
never look at the time settings on their computer... who knows.
The prompt on startup of fldigi for an op at an emcomm station, maybe
on a computer that is not theirs, would catch the problem and just
seems to be no big deal, at least to me.
Its no problem that this never gets put into FLDIGI. It was only a
suggestion.
-Dave, KB3FXI
Mark Cudworth wrote:
w1hkj wrote:
Every OS that I run has the computer clock displayed somewhere on the
desktop. They also have some means for the user to adjust the
clock. Why is that not sufficient?
More to the point, if the computer's clock is wrong, won't it be wrong
for all of the other software that uses it? Why wait until someone runs
Fldigi to check the clock? Someone running a computer for Field Day or
for EmComm should have a nag program to check the clock when the
*computer* starts, not when Fldigi starts.
_______________________________________________
fldigi-alpha mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/fldigi-alpha
--
+---------------------------------------------------------------+
| Joseph A. Counsil [email protected] Phone:(573) 341-5186 |
| 1310 Woodlawn Drive, Rolla, MO 65401 Amateur Radio: - KØOG - |
+---------------------------------------------------------------+
_______________________________________________
fldigi-alpha mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/fldigi-alpha
