I have a backup laptop (5yo panasonic toughbook) that only gets turned
on about 4 times a year and has no wireless, so it wouldn't pick up the
update from the internet time servers automatically. It would be VERY
easy for me to fire this up in a flooding situation on Monday (if we
were called out), after the time change, and not notice the time was off.
Also, several of the County EOC's I've dealt with, do not want the
RACES/ARES computers on their network, so the auto internet time updates
would be out there, too.
-Dave, KB3FXI
Joseph A. Counsil wrote:
Yep - you nailed it! Sometimes I use old junker PCs for Field Day, and they
often have dead CMOS batteries, so it would be nice to have a time check warning
on startup.
73,
-Joe-
Mike Haynes wrote:
I can only imagine this being a problem if the CMOS Battery is dead causing
one to have to manually set the
time or it is about to go dead and causing time to be incorrect.
I have never noticed a problem on any platform or OS I have used.
Perhaps I am missing something.
Yes NTP would do a very nice job if one is connected to the internet. In my
portable EmComm work I do
not have internet but have not had an issue.
73's
Mike
On Fri, Mar 12, 2010 at 8:45 AM, Stelios Bounanos <[email protected]
<mailto:[email protected]>> wrote:
>>>>> On Fri, 12 Mar 2010 06:22:57 -0500, David Kleber
<[email protected] <mailto:[email protected]>> said:
> A while back, I suggested that upon startup of FLDIGI, a window pop up
> showing the current time and date that the computer is set to. This
> could appear with a question, "Is your time and date correct" and a yes
> to continue... maybe clicking no would take you to where you can make
> the correction. Perhaps there could be somewhere in the program that
> this could be disabled for those who just can't stand the idea.
This is a pretty easy problem to solve without involving fldigi. If
your machince is connected to the internet, you can just set up an NTP
client and forget about the issue. It will keep your clock to within a
few milliseconds of the NTP server, accounting for drift and avoiding
large increments.
Here are some instructions for Windows:
http://www.boulder.nist.gov/timefreq/service/pdf/win2000xp.pdf
On Linux systems you would install the ntp package.
> I think for EmComm, this could become a very important issue, especially
> when logging incoming wrap files during an actual emergency deployment.
> Its pretty important to know that your messages are logged with the
> correct time and date.
Then you should make good timekeeping part of your SOP. NTP is the
simplest solution. It's much better for fldigi to assume that the time
is correct and let specialised software deal with setting it, because
that's usually a privileged operation that cannot be done in a system
independent manner.
--
73,
Stelios, M0GLD.
_______________________________________________
fldigi-alpha mailing list
[email protected] <mailto:[email protected]>
https://lists.berlios.de/mailman/listinfo/fldigi-alpha
--------------------------------------------------------------------------------
_______________________________________________
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
_______________________________________________
fldigi-alpha mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/fldigi-alpha
