Home Messages Index
[Date Prev][Date Next][Thread Prev][Thread Next]
Author IndexDate IndexThread Index

Re: Windows-based Voting Machines Had "Screen-freeze" Problems for Years

  • Subject: Re: Windows-based Voting Machines Had "Screen-freeze" Problems for Years
  • From: "Larry Qualig" <lqualig@xxxxxxxxx>
  • Date: 5 Nov 2006 05:57:17 -0800
  • Complaints-to: groups-abuse@google.com
  • In-reply-to: <pan.2006.10.30.21.11.04.89564@ncoldns.com>
  • Injection-info: m7g2000cwm.googlegroups.com; posting-host=12.170.48.219; posting-account=I0FyeA0AAABAUAjJ9vi7laKRssUBoQA3
  • Newsgroups: comp.os.linux.advocacy
  • Organization: http://groups.google.com
  • References: <2171689.y4osqRCZnF@schestowitz.com> <1161959765.066449.189800@i42g2000cwa.googlegroups.com> <pan.2006.10.27.23.07.45.296873@ncoldns.com> <1162001913.479192.275220@i42g2000cwa.googlegroups.com> <reply_in_group-495830.20203227102006@news.supernews.com> <1726621.QYBZDup5ya@schestowitz.com> <reply_in_group-6647DC.22542127102006@news.supernews.com> <pan.2006.10.28.08.35.43.220955@ncoldns.com> <1162039795.216107.193570@k70g2000cwa.googlegroups.com> <b4ca0$45437afc$544a537b$9079@news.hispeed.ch> <1162050925.904050.161900@e64g2000cwd.googlegroups.com> <pan.2006.10.30.21.11.04.89564@ncoldns.com>
  • User-agent: G2/1.0
  • Xref: news.mcc.ac.uk comp.os.linux.advocacy:1177652
Kelsey Bjarnason wrote:
> [snips]
>
> On Sat, 28 Oct 2006 08:55:25 -0700, Larry Qualig wrote:
>
> > (Note that none of the articles that I read mentions anything about
> > chipsets not being supported by Windows. But they do mention replacing
> > faulty motherboards.)
>
> No, they mention replacing motherboards, period.  If the combination of
> Windows + drivers + motherboards fails, and Windows is *known* not to like
> some motherboards, and some drivers are *known* to be crap and some mobos
> are *known* to be faulty... why assume only one of the three possible
> causes is involved?
>
> Replacing the mobos would, likely, fix the problem.  So would, likely,
> changing the OS.  That they're changing the mobos suggests that it's
> cheaper to do this than migrate their software to a different OS, not that
> the mobos are, of necessity, the culprit.
>
> > But if it was a chipset issue, why replace the motherboards? Why not
> > simply install a new driver that properly handles the chipset being
> > used?
>
> Because that doesn't always work.  Fact is, Windows just _does not
> like_ some mobos, regardless of driver set.  Buggy drivers?  Perhaps.
> Issues with Windows and, say, DMA handling?

> Could be.  Point is we don't know why it occurs,
> at least not in every case... we just know it does -
> and that updated drivers don't always help.

I'm glad that hear that you also agree that Roy's comment of - "Sounds
like Windows' handling of motherboard interrupts." is total bullshit
that he fabricated on the spot.






> > Ah... I should have read this first before attempting to explain chipset
> > drivers. So you obviously understand that the problem could be fixed
> > with correct chipset drivers.
>
> Correct; we understand that it *could be* fixed by such an update...
> "could", not "would".  Even with updated drivers, it still doesn't always
> fix the problem.
>
> Hell, I've got an old 366Mhz mobo at home... rock solid under Linux, *used
> to be* rock solid under Win2K... but Win2K+SP4, it spontaneously reboots
> every 24 hours give or take.  Regardless of whether I'm using the
> originally-shipped drivers or the latest.
>
> Windows simply *does not like that motherboard*.  Something between SP3
> and SP4 changed in Windows which caused it to stop operating reliably on
> that hardware.  It never ran reliably again on that mobo... but the mobo
> runs Linux fine.


[Date Prev][Date Next][Thread Prev][Thread Next]
Author IndexDate IndexThread Index