Toshiba TV29C90 problem; Image fades to black...

[Mxsmanic]

Woody Brison writes:

The answer is that a clock on the computer is useful to record
creation/change time on files.

It doesn't really matter if the file was modified at 6:00.00 000000
or 6:00.00 000035

What matters is if one file was created before another. You're
compiling, but the source hasn't changed, or has; the params file
has been changed since X,Y, or Z... that kind of thing.

On a computer, Approximate Time is almost always all that's really
needed; a clock that ***always runs forward***, and keeps time within
a few minutes a day.

That is true if all activity is confined to a single computer. When
multiple computers are involved, however, they must be synchronized.
And if the computers interact with other computers outside local
control (as by communication over the Internet), then they must not
only be synchronized, but they must be synchronized to a universal
standard, such as UTC.

This is why clock accuracy is important.

In the old days when every PC was completely isolated, time hardly
mattered at all, and often people would use PCs without bothering to
ever set the correct date or time. Nowadays, almost all PCs have to
be at least approximately synchronized to the correct time of day, and
often very precise synchronization is required.

--
Transpose mxsmanic and gmail to reach me by e-mail.

 

[David Maynard]

Mxsmanic wrote:

Woody Brison writes:


The answer is that a clock on the computer is useful to record
creation/change time on files.

It doesn't really matter if the file was modified at 6:00.00 000000
or 6:00.00 000035

What matters is if one file was created before another. You're
compiling, but the source hasn't changed, or has; the params file
has been changed since X,Y, or Z... that kind of thing.

On a computer, Approximate Time is almost always all that's really
needed; a clock that ***always runs forward***, and keeps time within
a few minutes a day.


That is true if all activity is confined to a single computer. When
multiple computers are involved, however, they must be synchronized.
And if the computers interact with other computers outside local
control (as by communication over the Internet), then they must not
only be synchronized, but they must be synchronized to a universal
standard, such as UTC.

This is why clock accuracy is important.

In the old days when every PC was completely isolated, time hardly
mattered at all, and often people would use PCs without bothering to
ever set the correct date or time. Nowadays, almost all PCs have to
be at least approximately synchronized to the correct time of day, and
often very precise synchronization is required.

Except for spammers that routinely post years, even decades, into the past.

 

[tempus fugit]

Thanks again for the replies.

I solved the 120V on the chassis mystery - the new cord I installed wasn't
polarized after all. It has a white stripe on it (black cable) and one of
the tips appeared bigger than the other, but it would fit in the socket
either way. I installed an actual polarized cord and the chassis is AC free.

Hopefully I'll get to the caps soon. I'll keep you posted.

Thanks


<pfjw@aol.com> wrote in message
news:1131939646.310578.181400@z14g2000cwz.googlegroups.com...

When in doubt, use 33uF or so, @450V (22uF is OK for a start. If the
hum reduces but does not go away altogether, then go up). Otherwise,
200uF @20V or so for LV stuff.

Bridge: Voltage in X 1.4142 = voltage out.
Single diode: Voltage in .7071 = voltage out.

Keep that in mind.

Peter Wieck
Wyncote, PA

 

[Mxsmanic]

David Maynard writes:

Except for spammers that routinely post years, even decades, into the past.

What's the advantage of doing so? And why can't servers simply reject
anything that is obviously far in the past?

--
Transpose mxsmanic and gmail to reach me by e-mail.

 

[Woody Brison]

Mxsmanic wrote:

Woody Brison writes:
What matters is if one file was created before another. You're
compiling, but the source hasn't changed, or has; the params file
has been changed since X,Y, or Z... that kind of thing.

On a computer, Approximate Time is almost always all that's really
needed; a clock that ***always runs forward***, and keeps time within
a few minutes a day.

That is true if all activity is confined to a single computer. When
multiple computers are involved, however, they must be synchronized.
And if the computers interact with other computers outside local
control (as by communication over the Internet), then they must not
only be synchronized, but they must be synchronized to a universal
standard, such as UTC.

OK, thanks, but why is it so important? A message is received
on one computer at a certain time per that computer's clock. It
was sent from another computer at some time, recorded in the
message, per that computer's clock. Are we going to calculate
transit time or something? Check to make sure it didn't arrive
before it was sent?

 

[Mxsmanic]

Woody Brison writes:

OK, thanks, but why is it so important?

Sometimes you have to be able to correlate or synchronize events over
long distances with great accuracy (fractions of a second).

A message is received on one computer at a certain time per that
computer's clock. It was sent from another computer at some time,
recorded in the message, per that computer's clock. Are we going
to calculate transit time or something?

Yes.

Check to make sure it didn't arrive before it was sent?

Yes.

There are many applications for accurate time. In fact, the more
accurate time one can obtain, the more useful applications become
practical and available.

--
Transpose mxsmanic and gmail to reach me by e-mail.

 

[David Maynard]

Mxsmanic wrote:

David Maynard writes:


Except for spammers that routinely post years, even decades, into the past.


What's the advantage of doing so? And why can't servers simply reject
anything that is obviously far in the past?

Hell if I know but I just got one dated 1969.

 

[DevilsPGD]

In message <11nnmgeb2r2ks00@corp.supernews.com> David Maynard
<nospam@private.net> wrote:

Mxsmanic wrote:

David Maynard writes:


Except for spammers that routinely post years, even decades, into the past.


What's the advantage of doing so? And why can't servers simply reject
anything that is obviously far in the past?


Hell if I know but I just got one dated 1969.

That's usually because the date header was missing completely, and some
system along the way assigned a header of Jan 1 1970 -0000, then
corrected for timezone shift.

--
Light travels faster than sound. This is why some people appear
bright until you hear them speak...

 

[Isaac Wingfield]

In article <l1fln1trq5j600rvhrn8jlg5nerjeocadv@4ax.com>,
Mxsmanic <mxsmanic@gmail.com> wrote:

Woody Brison writes:

The answer is that a clock on the computer is useful to record
creation/change time on files.

It doesn't really matter if the file was modified at 6:00.00 000000
or 6:00.00 000035

What matters is if one file was created before another. You're
compiling, but the source hasn't changed, or has; the params file
has been changed since X,Y, or Z... that kind of thing.

On a computer, Approximate Time is almost always all that's really
needed; a clock that ***always runs forward***, and keeps time within
a few minutes a day.

That is true if all activity is confined to a single computer. When
multiple computers are involved, however, they must be synchronized.
And if the computers interact with other computers outside local
control (as by communication over the Internet), then they must not
only be synchronized, but they must be synchronized to a universal
standard, such as UTC.

This is why clock accuracy is important.

In the old days when every PC was completely isolated, time hardly
mattered at all, and often people would use PCs without bothering to
ever set the correct date or time. Nowadays, almost all PCs have to
be at least approximately synchronized to the correct time of day, and
often very precise synchronization is required.

In almost any instance where a high degree of precision and
synchronization is needed, the computer will be running a version of NTP
software which can provide precision time from even very poor CPU
timebases.

"Ordinary" computers don't need that degree of precision, and a
once-or-twice a day comparison to an NTP server somewhere on the 'net is
all that's required.

Isaac

 

[David Maynard]

DevilsPGD wrote:

In message <11nnmgeb2r2ks00@corp.supernews.com> David Maynard
nospam@private.net> wrote:


Mxsmanic wrote:


David Maynard writes:



Except for spammers that routinely post years, even decades, into the past.


What's the advantage of doing so? And why can't servers simply reject
anything that is obviously far in the past?


Hell if I know but I just got one dated 1969.


That's usually because the date header was missing completely, and some
system along the way assigned a header of Jan 1 1970 -0000, then
corrected for timezone shift.

Possible. But that doesn't explain the ones dated 2001.

 

[Tom Horsley]

That's usually because the date header was missing completely, and some
system along the way assigned a header of Jan 1 1970 -0000, then
corrected for timezone shift.

Possible. But that doesn't explain the ones dated 2001.

My theory: A lot of spam is sent by computers that have been taken
over by spam sending viruses. Computer owners who aren't bright
enough to set the time right are also not bright enough to install
anti-virus software or take other precautions to prevent their
computers from being turned into spam slaves, ergo lots of bad
times on spam .

P.S. http://home.att.net/~Tom.Horsley/ntptime.html is the web
page for my NTP client to keep your windows system time set if
anyone is interested.

 

[Mxsmanic]

Tom Horsley writes:

P.S. http://home.att.net/~Tom.Horsley/ntptime.html is the web
page for my NTP client to keep your windows system time set if
anyone is interested.

Recent versions of Windows already include an NTP client.

--
Transpose mxsmanic and gmail to reach me by e-mail.

 

[Rich the Newsgroup Wacko]

On Mon, 14 Nov 2005 07:41:37 +0100, Mxsmanic wrote:

David Maynard writes:

Well, that's a lot of Bull

The company has tried to make the best of its name in English ads,
often with slogans along the lines of what you give above, but it
hasn't been very successful. Bull doesn't mean anything in French, so
it's not a problem in France, but it's a problem in English-speaking
countries. It was just bad luck that one of the original founders had
a Norwegian name that by some weird coincidence happened to look just
like an English word (Bull doesn't look very Norwegian to me, but
maybe it is [?]).

But, if they'd said, "Honeywell Bowl," they'd think you were talking
about a football game.

Or Chinese food. ;-)

--
Cheers!
Rich
------
"Hear about... The fellow who chased his girlfriend up a tree and kissed
her between the limbs?"

 

[Rich Grise]

On Mon, 14 Nov 2005 07:44:54 -0600, David Maynard wrote:

Things that seem 'obvious' in one culture can be anything but to someone
not familiar with it. I learned that one in the middle east when I went
for a public toilet and found myself looking at two identically shaped
figures labeling which was for males and females. The only difference
was one was white and the other was black but to a westerner used to the
skirt/pants distinction it was a bit of a mystery, especially when not
thinking real clear due to the urgency

So, did you find out in time?

Thanks,
Rich

 

[Rich Grise]

On Thu, 17 Nov 2005 05:39:51 -0600, David Maynard wrote:

DevilsPGD wrote:
In message <11nnmgeb2r2ks00@corp.supernews.com> David Maynard
Mxsmanic wrote:
David Maynard writes:

Except for spammers that routinely post years, even decades, into the
past.

What's the advantage of doing so? And why can't servers simply reject
anything that is obviously far in the past?

Hell if I know but I just got one dated 1969.

That's usually because the date header was missing completely, and some
system along the way assigned a header of Jan 1 1970 -0000, then
corrected for timezone shift.

Possible. But that doesn't explain the ones dated 2001.

Well, Y2K, of course. ;-)

Cheers!
Rich

 

[David Maynard]

Rich Grise wrote:

On Mon, 14 Nov 2005 07:44:54 -0600, David Maynard wrote:


Things that seem 'obvious' in one culture can be anything but to someone
not familiar with it. I learned that one in the middle east when I went
for a public toilet and found myself looking at two identically shaped
figures labeling which was for males and females. The only difference
was one was white and the other was black but to a westerner used to the
skirt/pants distinction it was a bit of a mystery, especially when not
thinking real clear due to the urgency


So, did you find out in time?

Thanks,
Rich

Hehe. As a matter of fact, I did. I waited outside between the two till I
saw a local go in one.

It was one of those things that when you find out you feel doubly stupid.
Well, DUH, of course it's men-white.

 

[Thomas A. Horsley]

Recent versions of Windows already include an NTP client.

Yea, but as with almost all attempts Microsoft makes to interoperate
with networking standards, their client is badly broken (you can
probably find all the rants starting from www.ntp.org .
--

==>> The *Best* political site <URL:http://www.vote-smart.org/> >>==+
email: Tom.Horsley@worldnet.att.net icbm: Delray Beach, FL |

<URL:http://home.att.net/~Tom.Horsley> Free Software and Politics <<==+

 

[David Maynard]

Tom Horsley wrote:

That's usually because the date header was missing completely, and some
system along the way assigned a header of Jan 1 1970 -0000, then
corrected for timezone shift.

Possible. But that doesn't explain the ones dated 2001.


My theory: A lot of spam is sent by computers that have been taken
over by spam sending viruses. Computer owners who aren't bright
enough to set the time right are also not bright enough to install
anti-virus software or take other precautions to prevent their
computers from being turned into spam slaves, ergo lots of bad
times on spam .

Highly unlikely, especially after you trace it.

A more likely theory is there are plenty of stupid spammers.

P.S. http://home.att.net/~Tom.Horsley/ntptime.html is the web
page for my NTP client to keep your windows system time set if
anyone is interested.

 

[David Maynard]

Rich Grise wrote:

On Thu, 17 Nov 2005 05:39:51 -0600, David Maynard wrote:

DevilsPGD wrote:

In message <11nnmgeb2r2ks00@corp.supernews.com> David Maynard

Mxsmanic wrote:

David Maynard writes:


Except for spammers that routinely post years, even decades, into the
past.

What's the advantage of doing so? And why can't servers simply reject
anything that is obviously far in the past?


Hell if I know but I just got one dated 1969.

That's usually because the date header was missing completely, and some
system along the way assigned a header of Jan 1 1970 -0000, then
corrected for timezone shift.


Possible. But that doesn't explain the ones dated 2001.


Well, Y2K, of course. ;-)

Cheers!
Rich

Hehe. Sure.

I did go look at the 1969 header and it had a date of something like 20450,
which apparently wrapped and rolled into 1969 by the time Netscape finished
interpreting it.

The 2001 header was simply 2001.

 

[Mxsmanic]

Thomas A. Horsley writes:

Yea, but as with almost all attempts Microsoft makes to interoperate
with networking standards, their client is badly broken (you can
probably find all the rants starting from www.ntp.org .

It works perfectly on my system.

--
Transpose mxsmanic and gmail to reach me by e-mail.