From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_09CA_01C76025.2400FF10
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   I believe you but according to mike miller they do not or prefer not =
too.  I don't know why he would make such a claim if not true.

Rich
  "Geo."  wrote in message =
news:45ee2946$1{at}w3.nls.net...
  Linux (I've not run BSD) follows the standard, it doesn't reset my =
clock=20
  when I dual boot with Windows and it does display the correct time.

  Geo.

  "Rich"  wrote in message news:45ed93ef$1{at}w3.nls.net...
     The standard is what it is.  mike miller questioned why linux and =
the=20
  BSDs fail to follow it.  I guess you can feel better if you redefine =
what=20
  they do as the new standard and ignore that some software do follow =
the=20
  existing standard.

  Rich

    "Don Hills"  wrote in message=20
  news:zhV7FtgaXWnf092yn{at}attglobal.net...
    In article , "Rich"  wrote:
    >   The early IBM PCs worked without an OS so you are fishing to =
switch
    >the standard from the PC.

    The only fishy part is you doing your standard red herring drag.

    >The history is irrelevant as the standard is
    >what it is and according to mike miller, linux and the BSDs fail to
    >follow it.

    "History is irrelevant"? "The standard is what it
(happens to be at =
the
    moment)"?   No wonder we're in the mess we're discussing.

    --=20
    Don Hills=20

------=_NextPart_000_09CA_01C76025.2400FF10
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   I believe you but =
according to mike=20
miller they do not or prefer not too.  I don't know why he would =
make such=20
a claim if not true.
 
Rich

  "Geo." <georger{at}nls.net>">mailto:georger{at}nls.net">georger{at}nls.net>
wrote=20
  in message news:45ee2946$1{at}w3.nls.net...Linux=20
  (I've not run BSD) follows the standard, it doesn't reset my clock =
when I=20
  dual boot with Windows and it does display the correct=20
  time.Geo."Rich"
<{at}> wrote in message news:45ed93ef$1{at}w3.nls.net...=
  =20
  The standard is what it is.  mike miller questioned why linux and =
the=20
  BSDs fail to follow it.  I guess you can feel better if you =
redefine=20
  what they do as the new standard and ignore that some software do =
follow=20
  the existing
standard.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:zhV7FtgaXWnf092yn{at}attg=
lobal.net... =20
  In article <45ec4a2f$1{at}w3.nls.net>,">mailto:45ec4a2f$1{at}w3.nls.net">45ec4a2f$1{at}w3.nls.net>,
=
"Rich"=20
  <{at}> wrote:  >  
The early IBM PCs worked =
without=20
  an OS so you are fishing to switch  >the
standard from the =

  PC.  The only fishy part is you doing your
standard red =
herring=20
  drag.  >The history is irrelevant as
the standard =
is =20
  >what it is and according to mike miller, linux and the BSDs fail=20
  to  >follow it. 
"History is irrelevant"? =
"The=20
  standard is what it (happens to be at the  =
moment)"?   No=20
  wonder we're in the mess we're discussing. 
--   =
Don=20
  Hills 

------=_NextPart_000_09CA_01C76025.2400FF10--

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