Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!umd5!purdue!i.cc.purdue.edu!j.cc.purdue.edu!pur-ee!uiucdcs!uiucdcsp!gillies
From: gillies@uiucdcsp.cs.uiuc.edu
Newsgroups: comp.arch
Subject: Re: How did this program burn out two m
Message-ID: <76700026@uiucdcsp>
Date: 28 May 88 02:36:00 GMT
References: <10244@agate.BERKELEY.EDU>
Lines: 12
Nf-ID: #R:agate.BERKELEY.EDU:10244:uiucdcsp:76700026:000:588
Nf-From: uiucdcsp.cs.uiuc.edu!gillies    May 27 21:36:00 1988


Perhaps it's not the board designer's fault, but the chip designer's
fault.  If a video chip is fully programmable, it might be pretty hard
to disable certain requests, like "set the horizontal scan to zero".
Some engineer somewhere is probably already using the chip with the
horizontal scan rate set to zero, for some wierd product.  I think
this might be tricky to prevent with a hardware fix, either in the
board, or in the monitor.

I don't really know this for sure, what do other people think?

Don Gillies {ihnp4!uiucdcs!gillies} U of Illinois
            {gillies@p.cs.uiuc.edu}