[comp.arch] How did this program burn out two m

gillies@uiucdcsp.cs.uiuc.edu (05/28/88)

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}

rick@datacube.UUCP (06/02/88)

>Maybe the files got corrupted.  When I ran the .exe file, my monitor
>made a high-pitched whine, then the power light went off, and a 
>crackling noise came out of the back until I pulled the power cord.
>Curious about whether this was a coincidence, I took the program
>to work and tried it on an extra monitor I had there.........


	Actually, another famous mode of 'Monitor Meltdown' can occur.
	Since the yoke looks like a nice big inductor in the circuit,
	you can create an 'inductor oven' by feeding it synch's at
	100 Khz or higher. This will heat the yoke up to above the
	melting point of glass, and the monitor implodes, (pretty
	spectacular). I suspect the whine may have been this mode of
	failure and the crackling noise you heard was melting
	insulation and glass.


				Rick Cooley
-----------------------------------------------------------------------------
  ------      Datacube Inc.
 /    /|      4 Dearborn Rd.
------ |      Peabody, Ma 01960
||  \| |      ihnp4!datacube!rick
||  /|/       Human:(617)535-6644
------        Fax:  (617)535-5643
-----------------------------------------------------------------------------