Re: DST change and home auto...

["ohno" <emedley@xxxxxxxxxxxxxx>]

Actually,
those older operating systems are relatively safe.  Most virus
protection / internet security companies report that almost no
viruses, trojans, keyloggers, etc.. are being written that try to
access the known problems in Win98 or lesser.  It seems the hackers
out there have bigger fish in mind.  So, as long as you keep your
virus protection software current, you'll more-than-likely find
sailing to be smooth.  (Never mind the fact that they systems are so
antiquated that they can hardly do anything...)

On another note concerning the coming DST issues.  I find it rather
amusing that we in the programming community has been caught being
lazy again.  We thought Y2K would have taught us a lesson.

The N.I.S.T. time server (based upon the atomic clocks they run) has a
pretty good system that allows for the moving of Daylight Savings
time.

the following is an example of what you get when you hit their telnet
server

54157 07-02-26 13:12:30 00 0 0 493.4 UTC(NIST) *

The double zero you see in the middle is a count down.  When we get
close to the day of DST changing, it begins counting down from 99 each
day at 12:00am UTC.  When it hits 50, we're in standard time.
Likewise, in the fall, it beginns counting down from 50 until we hit
00 again.  Then it's DST.

Instead of putting in our computer clocks things like 3rd Sunday in
Oct. or whatnot, they should all just adopt this protocol.  Then the
powers-that-be can move the date around all they want.



On Feb 25, 8:06 pm, ken <omd-nos...@xxxxxxxxxxxxxx> wrote:
> Dave Houston wrote:
> > j...@xxxxxxxxxxxx wrote:
>
> >>There is a method to patch Windows 95, 98 and ME for DST.  It is not a
> >>...
> > But it's harder than my earlier suggestion of disabling Automatic DST and
> > using D4 to keep the clock synced with an NTP server - which has the added
> > advantage of keeping the clock accurate year round.
>
> and requiring a network connection.
>
> frankly, imho, anyone runnin WIN9x or WINme would be foolish to have it
> connected to external networks for many many security reasons.
>
> Win9x is a great dos-with-GUI for handling automation or other tasks,
> it should no longer be considered an internet platform.
>
> of course you could provide NTP services from WITHIN a private network.
> but that is overkill when patching once won't kill you.
>
>    -k