From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_0107_01C762EE.79011100
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   Not true.  OSes follow the standard set by the BIOS and the hardware. =
 Look at the time reported in the BIOS screen when you boot to the BIOS. =
 You can have an OS that fails to follow this convention, like mike =
miller claims that linux/bsd want not to follow, but that doesn't make =
this violation the standard.

   It's not like this would be too difficult to change.  All we need is =
a flag to indicate whether the time is local or UTC or maybe the time =
zone of the time reported by the clock.  Maybe this has been done =
already.  Absent that, if there is time only the PC standard is that the =
time is local time.

Rich

  "Don Hills"  wrote in message =
news:6wn8FtgaXuiA092yn{at}attglobal.net...
  In article , "Geo."
 wrote:
  > ... What I'm saying is that for every OS that
  >runs on the PC, it has to deal with the PC standard.

  Think about it. There is no "PC Standard". There are several "OS =
conventions".
  It's the requirements of the OS that determines whether the PC clock =
is set
  to local time or GMT/UTC. There's nothing in the PC hardware that =
requires
  using one or the other.

  --=20
  Don Hills
------=_NextPart_000_0107_01C762EE.79011100
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   Not
true.  OSes =
follow the=20
standard set by the BIOS and the hardware.  Look at the time =
reported in=20
the BIOS screen when you boot to the BIOS.  You can have an OS
that = fails=20
to follow this convention, like mike miller claims that linux/bsd want = not to=20
follow, but that doesn't make this violation the standard.
 
   It's not
like this would =
be too=20
difficult to change.  All we need is a flag to indicate whether
the = time is=20
local or UTC or maybe the time zone of the time reported by the = clock. =20
Maybe this has been done already.  Absent that, if there is time =
only the=20
PC standard is that the time is local time.
 
Rich
 

  "Don Hills" <black.hole.4.spam{at}gmail.commailto:black.hole.4.spam{at}gmail.com">black.hole.4.spam{at}gmail.com
A>>=20
  wrote in message news:6wn8FtgaXuiA092yn{at}attg=
lobal.net...In=20
  article <45f0b8f1$1{at}w3.nls.net>,">mailto:45f0b8f1$1{at}w3.nls.net">45f0b8f1$1{at}w3.nls.net>,
=
"Geo."=20
  <georger{at}nls.net>">mailto:georger{at}nls.net">georger{at}nls.net>
=
wrote:>=20
  ... What I'm saying is that for every OS that>runs on the PC, =
it has to=20
  deal with the PC standard.Think about it. There is no
"PC =
Standard".=20
  There are several "OS conventions".It's the
requirements of the OS =
that=20
  determines whether the PC clock is setto local time or GMT/UTC. =
There's=20
  nothing in the PC hardware that requiresusing one or the =
other.--=20
  Don Hills

------=_NextPart_000_0107_01C762EE.79011100--

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