public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: Warren Young <warren@etr-usa.com>
To: The Vulgar and Unprofessional Cygwin-Talk List <cygwin-talk@cygwin.com>
Subject: Re: the importance of the timer rollover bug in Win9x
Date: Thu, 11 Sep 2008 20:18:00 -0000	[thread overview]
Message-ID: <48C97CC9.5020602@etr-usa.com> (raw)
In-Reply-To: <gabi99$5qg$1@ger.gmane.org>

Matthew Woehlke wrote:
>>   http://support.microsoft.com/kb/216641
> 
> Oy, hadn't run across that before :-).

The fact that the problem wasn't fixed until 2000 or so made this more 
than just an embarrassment for Microsoft.  It was an inflection point.

What you had was a bug that was absolutely deterministic, which affected 
hundreds of millions of machines over many years.  Multiply it out and 
you come to something like 100 billion times the bug could have 
happened.  Sounds like a programmer's dream, right?  A bug you can count 
on to happen that reliably with such a huge installed base....yet it 
took ~5 years to diagnose and fix.

For such a bug to last so long, you're looking for probability of 
discovery down around 1 in 10 million.  It takes a lot of explaining to 
get from 1e11 to 1e-7.  I tried.  The "good reasons" got me down to 
about 1e2.  Maybe you can get down to 1e0.  You're still left with so 
many zeroes as to constitute objective evidence that Win9x boxes 
experience...erm, unscheduled restarts...*a lot*.

To this point, you had all kinds of anecdotal evidence of Win9x's 
instability.  The arguments raged on, as those based only on anecdotal 
evidence will.  This incident provided objective proof of the sort you 
don't see ignored outside of politics and religion.

  parent reply	other threads:[~2008-09-11 20:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <loom.20080904T183156-413@post.gmane.org>
     [not found] ` <48C0316C.F9E434A9@dessent.net>
     [not found]   ` <00fc01c90f39$f4006970$9601a8c0@CAM.ARTIMI.COM>
     [not found]     ` <loom.20080910T172329-77@post.gmane.org>
     [not found]       ` <007101c9136b$a62b3e10$9601a8c0@CAM.ARTIMI.COM>
     [not found]         ` <loom.20080910T174541-80@post.gmane.org>
     [not found]           ` <007c01c91372$1c48c3a0$9601a8c0@CAM.ARTIMI.COM>
     [not found]             ` <5E25AF06EFB9EA4A87C19BC98F5C8753016D87EE@core-email.int.ascribe.com>
2008-09-11 16:08               ` setup.exe --quiet-mode Matthew Woehlke
2008-09-11 16:39                 ` Dave Korn
2008-09-11 16:51                   ` Matthew Woehlke
2008-09-11 17:00                     ` Dave Korn
2008-09-11 20:18                     ` Warren Young [this message]
2008-09-11 23:25                       ` the importance of the timer rollover bug in Win9x Dave Korn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48C97CC9.5020602@etr-usa.com \
    --to=warren@etr-usa.com \
    --cc=cygwin-talk@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).