From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_07F6_01C75E49.781C69A0
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   The standard from the beginning of the PC is to use local time.  The =
better question is why do linux and the BSDs fail to follow the = standard?

Rich

  "mike"  wrote in message =
news:bb2mu29p0p4eutgmhtns3dcgsnno3pecr0{at}4ax.com...

  Linux and the BSDs want to use UTC for the hardware clock.

  In fact, there is a program that allows Linux and the BSDs to
  accommodate a Windows-based hardware clock that is set to local time.
  =
http://www.freebsd.org/cgi/man.cgi?query=3Dadjkerntz&apropos=3D0&sektion=3D=
0&manpath=3DFreeBSD+6.2-RELEASE&format=3Dhtml


  So the question remains, why does Windows insist on setting the =
hardware
  clock to local time?

  =20
   /m



------=_NextPart_000_07F6_01C75E49.781C69A0
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   The
standard from the =
beginning of the=20
PC is to use local time.  The better question is why do linux and
= the BSDs=20
fail to follow the standard?
 
Rich
 

  "mike" <mike{at}barkto.com>">mailto:mike{at}barkto.com">mike{at}barkto.com>
wrote=20
  in message news:bb2mu29p0p4=
eutgmhtns3dcgsnno3pecr0{at}4ax.com...Linux=20
  and the BSDs want to use UTC for the hardware clock.In fact, =
there is=20
  a program that allows Linux and the BSDs toaccommodate a =
Windows-based=20
  hardware clock that is set to local time.http://www.freebsd.org/cgi/man.cgi?query=3Dadjkerntz&apropos=3D=
0&sektion=3D0&manpath=3DFreeBSD+6.2-RELEASE&format=3Dhtml">ht=
tp://www.freebsd.org/cgi/man.cgi?query=3Dadjkerntz&apropos=3D0&se=
ktion=3D0&manpath=3DFreeBSD+6.2-RELEASE&format=3Dhtml=
So=20
  the question remains, why does Windows insist on setting the =
hardwareclock=20
  to local =
time?  /m

------=_NextPart_000_07F6_01C75E49.781C69A0--

--- BBBS/NT v4.01 Flag-5