Hi Chris,
On 03/26/2013 04:30 PM, Chris Albertson wrote:
I would think that the best cure for persistent server abuse (abuse
that continues even after a KoD is sent) would be to send back a bogus
time with a huge random error of many thousands of hours. A normal
NTP client will notice the
The appearent conflict here is in the definition of real time.
For the video capture application we only need to keep up with the
average data rate and if the system stops reading data for a few tens
of milliseconds and lets it buffer in the capture hardware then it is
OK because nothing is lost.
: Chris Albertson albertson.ch...@gmail.com
Sender: time-nuts-boun...@febo.com
Date: Wed, 27 Mar 2013 08:38:32
To: Discussion of precise time and frequency measurementtime-nuts@febo.com
Reply-To: Discussion of precise time and frequency measurement
time-nuts@febo.com
Subject: Re: [time-nuts] Win
albertson.ch...@gmail.com said:
For the video capture application we only need to keep up with the average
data rate and if the system stops reading data for a few tens of
milliseconds and lets it buffer in the capture hardware then it is OK
because nothing is lost. The only criteria for
Good explanation. I guessed, since the list is time nuts I assumed
real time in reference to an OS would be understood. :) My bad.
Because windows is not a real time operating system (RTOS), I lack
seeing the purpose in getting the windows clock synchronized to within
microseconds or
time-nuts@febo.com
Subject: Re: [time-nuts] Win XP and NIST time
Good explanation. I guessed, since the list is time nuts I assumed
real time in reference to an OS would be understood. :) My bad.
Because windows is not a real time operating system (RTOS), I lack
seeing the purpose in getting
On Wed, Mar 27, 2013 at 9:46 AM, Dan Kemppainen d...@irtelemetrics.comwrote:
As for timing things on windows, check out how to read the performance
counters in windows. I believe these are QueryPerformanceCounter and
QueryPerformanceFrequency in kernel32. In most modern systems these should
orin.e...@gmail.com said:
Then all bets are off if you have a CPU that runs at variable speed if you
want the result to be actual time.
I think that got fixed on newer CPU chips. I don't know when.
Another interesting problem in that area is that the temperature changes with
the CPU load.
On 3/27/2013 2:54 PM, time-nuts-requ...@febo.com wrote:
Then all bets are off if you have a CPU that runs at variable speed if you
want the result to be actual time.
I think that got fixed on newer CPU chips. I don't know when.
Another interesting problem in that area is that the temperature
Orin writes:
If you use those, you have to lock the thread you are timing to one
CPU/Core as the performance counters are per CPU/Core and can get
out of step. Or you can force your thread onto one CPU for the
QueryPerformanceCounter call. This seems to be a bad idea to me as
it would add an
Chris writes:
For most users I think that is reasonable. It's just not what one
expects to read on a Time Nuts list. Here we expect to see posting
from true nut-cases who want microsecond just because they can do it.
But how can you verify microsecond accuracy on Windows? Even the OS
only
On Mon, Mar 25, 2013 at 9:46 PM, Hal Murray hmur...@megapathdsl.net wrote:
albertson.ch...@gmail.com said:
I think you can get Windows to run at the few milliseconds of error range
with the standard NTP distribution.
I don't think I've seen anything that bad, but it's easy to be off by 100s
On Mon, Mar 25, 2013 at 10:56 PM, Anthony G. Atkielski
anth...@atkielski.com wrote:
Chris writes:
For most users I think that is reasonable. It's just not what one
expects to read on a Time Nuts list. Here we expect to see posting
from true nut-cases who want microsecond just because they
From: Anthony G. Atkielski
[]
I've been using the standard NTP client in Windows XP for ages, and it
works just fine. I tried third-party stuff. It was just more work for
no apparent gain. The XP desktop is synchronized with my NTP server
perfectly within the limits of my perception, so there is
From: Anthony G. Atkielski
[]
But how can you verify microsecond accuracy on Windows? Even the OS only has
10 ms resolution for the system clock.
[]
Anthony
===
Anthony,
I appreciate that your needs don't include accurate PC time, but for the
record
On Tue, 26 Mar 2013 05:05:26 +0100, Anthony G. Atkielski
anth...@atkielski.com wrote:
Dan (I think) writes:
Because, up until today, windows time did what I needed it to do. It may
still, if the fault turns out to be network related.
In reality, it's more software to learn to administer, and
davidwh...@gmail.com said:
I have had trouble with the built in XP NTP client where it fails silently
so I usually install Tardis which keeps an easy to read log which includes
performance data.
One of the problems with timekeeping is the load on the servers.
The standard ntpd package tries
On Tue, Mar 26, 2013 at 12:41 AM, Hal Murray hmur...@megapathdsl.net wrote:
davidwh...@gmail.com said:
I have had trouble with the built in XP NTP client where it fails silently
so I usually install Tardis which keeps an easy to read log which includes
performance data.
One of the problems
I think using satellite Dave's plot routines is the way to tweak NTP. If you
update too often, you can see the disturbance. This isn't a scientific
solution, but a practical one.
___
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
On 3/26/2013 2:43 AM, time-nuts-requ...@febo.com wrote:
albertson.ch...@gmail.com said:
I think you can get Windows to run at the few milliseconds of error range
with the standard NTP distribution.
I don't think I've seen anything that bad, but it's easy to be off by 100s of
ms if I download
On 3/26/2013 7:21 PM, Dan Kemppainen wrote:
Keep in mind, we are after all, taking about windows. An operating
system that IS NOT real time operating system. (You think it is, try
move a continuous stream of a few 6+ MBytes/Sec data to it!)
Well, the Perseus SDR, when set to its maximum
within network latency of around a second or so
A second is a long time/distance for a packet.
The measured round trip time from California to Maine is under 100 ms.
Sanity check: The US is 3000 miles east-west. A mile is 5000 feet. The
speed of light is 1 ft/ns in vacuum. So that's
On Tue, Mar 26, 2013 at 07:39:51PM +0100, Alberto di Bene wrote:
On 3/26/2013 7:21 PM, Dan Kemppainen wrote:
Keep in mind, we are after all, taking about windows. An operating
system that IS NOT real time operating system. (You think it is, try
move a continuous stream of a few 6+ MBytes/Sec
Because, up until today, windows time did what I needed it to do. It may
still, if the fault turns out to be network related.
In reality, it's more software to learn to administer, and setup and run
on bunch of PC's. As a time nut, I know exactly how much time I need for
all of my other
Because, up until today, windows time did what I needed it to do. It may
still, if the fault turns out to be network related.
In reality, it's more software to learn to administer, and setup and run
on bunch of PC's. As a time nut, I know exactly how much time I need for
all of my other hobbies,
Dan (I think) writes:
Because, up until today, windows time did what I needed it to do. It may
still, if the fault turns out to be network related.
In reality, it's more software to learn to administer, and setup and run
on bunch of PC's. As a time nut, I know exactly how much time I need
albertson.ch...@gmail.com said:
I think you can get Windows to run at the few milliseconds of error range
with the standard NTP distribution.
I assume you are talking about getting time from the net rather than a local
GPS/GPSDO or such.
The accuracy depends upon your network connection
On Mon, Mar 25, 2013 at 9:05 PM, Anthony G. Atkielski
anth...@atkielski.com wrote:
I've been using the standard NTP client in Windows XP for ages, and it
works just fine. I tried third-party stuff. It was just more work for
no apparent gain. The XP desktop is synchronized with my NTP server
From: Anthony G. Atkielski
[]
I've been running XP for years using its built-in simple NTP client to
query the NTP server on my server, which in turn synchronizes with a
variety of NTP sources on the Net.
[]
Anthony
==
Folks,
I'm surprised by how many
Being an old-timer, I've been running Jag-Air's Nixie Clock
on Windows machines. See:
http://www.clockvault.com/clocks%5Cnixiehowto.htm
I've also used GPSCon with an HP Z3801 receiver as a source
for SNTP. The Jag-Air solution is much simpler.
Of course, NTP is more challenging, if that's what
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24/03/2013 06:27, David J Taylor wrote:
I'm surprised by how many time-nuts are not using the reference
NTP port for Windows, considering the many advantages it has over
the simple (non conformant and non-manageable) client built into
: James Harrison ja...@talkunafraid.co.uk
Sender: time-nuts-boun...@febo.com
Date: Sun, 24 Mar 2013 10:39:09
To: Discussion of precise time and frequency measurementtime-nuts@febo.com
Reply-To: Discussion of precise time and frequency measurement
time-nuts@febo.com
Subject: Re: [time-nuts] Win XP
From: li...@lazygranch.com
[]
Win7 is missing a few features of older MS operation systems. The search
feature is gone, but you can run a free program called everything. It is
so fast, you can turn off indexing. Also gone is hyperterminal, but you can
run terraterm, also free.
[]
On Sat, Mar 23, 2013 at 11:27 PM, David J Taylor
david-tay...@blueyonder.co.uk wrote:
I'm surprised by how many time-nuts are not using the reference NTP port
for Windows, considering the many advantages it has over the simple (non
conformant and non-manageable) client built into Windows).
I
Recently, my 'puter clock has been resetting back an hour every so often.
The auto-sync to time.NIST.gov is the timeserver it uses.
Does that site change to Daylight time?
Does the Windows time site change to aylight time?
Tjanks,
-John
==
Recently, my 'puter clock has been resetting back an hour every so often.
The auto-sync to time.NIST.gov is the timeserver it uses.
Does that site change to Daylight time?
Does the Windows time site change to aylight time?
Tjanks,
-John
===
John,
Internally, Windows
I think the date for the DST time change were altered some years ago,
hence the Win SW messes up. I keep the 'puter clock on local time for
convenience, and switch because eBay does. I am only concerned with
roughly accurate local time.
Best,
-John
===
Recently, my 'puter clock
I think the date for the DST time change were altered some years ago,
hence the Win SW messes up. I keep the 'puter clock on local time for
convenience, and switch because eBay does. I am only concerned with
roughly accurate local time.
Best,
-John
John,
I
On 3/23/13 7:27 AM, J. Forster wrote:
I think the date for the DST time change were altered some years ago,
hence the Win SW messes up. I keep the 'puter clock on local time for
convenience, and switch because eBay does. I am only concerned with
roughly accurate local time.
For the last few
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23/03/2013 14:50, Jim Lux wrote:
It wouldn't surprise me that XP doesn't have an accurate table of
this, since that would be one of the casualties of being past
support EOL although the KB entries I link below indicate that
they ARE still
Thank you.
My question is really does NIST time change to DST. I'm completely happy
with manually changing the time twice a year by hand. I'm trying to see if
disabling the auto-update fixes the problem. Resetting a clock is not
exactly a major task.
I have no interest in going to Vista or
For some reason, I always had trouble with the XP time service so I
disabled it and added a different NTP demon. I never had another problem.
As I understand it, NTP never does DST changes. That's up to your OS to
handle. I live in an area that doesn't do DST changes so I've never had
to
Thank you,
-John
==
For some reason, I always had trouble with the XP time service so I
disabled it and added a different NTP demon. I never had another problem.
As I understand it, NTP never does DST changes. That's up to your OS to
handle. I live in an area that doesn't
On Sat, Mar 23, 2013 at 10:02 AM, J. Forster j...@quikus.com wrote:
Thank you.
My question is really does NIST time change to DST. I'm completely happy
with manually changing the time twice a year by hand. I'm trying to see if
disabling the auto-update fixes the problem. Resetting a clock is
Hi all,
I am a new member, in St Pete, Florida. I noticed that last week, my XP
laptop had not updated at the arrival of summer time and I had to do it
manually.
Cheers.
Jay
___
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
If you double left click on the clock; click on the Time Zone tab, there
is a check box for DST update on/off. Since the dates of DST have changed,
it does not work right.
Best,
-John
=
Hi all,
I am a new member, in St Pete, Florida. I noticed that last week, my XP
laptop had
I'm running Microsoft Windows XP Professional -- Version 5.1.2600
Service Pack 3 Build 2600.
I still get occasional notifications and update my OS with latest
changes. (Don't know how much longer that will continue.) The time on my
system updated OK and is currently correct. I haven't noticed
When I was having trouble with my XP system, I could set the time off by
a few minutes and then ask it to do a time sync. It would report
success, but the time was still a few minutes off. At that point I
disabled the time service and installed an NTP program.
Ed
On 3/23/2013 8:30 PM, Rex
Jay Cox writes:
I am a new member, in St Pete, Florida. I noticed that last week, my XP
laptop had not updated at the arrival of summer time and I had to do it
manually.
The DST changeover times are contained in the registry. Each time they
change, Microsoft issues an update that corrects the
...@yahoogroups.com
- Original Message -
From: Rex r...@sonic.net
To: Discussion of precise time and frequency measurement
time-nuts@febo.com
Sent: Saturday, March 23, 2013 9:30 PM
Subject: Re: [time-nuts] Win XP and NIST time
I'm running Microsoft Windows XP Professional -- Version
50 matches
Mail list logo
