🚀 go-pugleaf

jfinete@cats.ucsc.edu (Joe Finete) writes:

>mystery was solved.  It turns out that the famous After-Dark fish
>"screen-saver" had burned the ocean floor into the phosphor of our
>monitor.  Granted our secretary probably kept the monitor on for months
>with the fish scene "saving" the monitor every night, but when does a
>"screen-saver" turn malicious?  Any other persistent ocean floors out
>there?
JF>  The ocean floor is an option that can be turned off. In fact, 
JF> I believe the manual warns you that leaving this option on 
JF> can result in screen burn-in. The buyer should beware his/her 
JF> own mistakes.

I noticed the sea bottom deal right away when After Dark came out, and knew
without looking in the manual that problems like this could (and would) easily
occur.  Given that this is a screen saver, though, I think it was idiotic for
such a "feature" to be included in _any_ module.

Saying "the buyer should beware his/her own mistakes" in this case is like
saying, "Yeah, Excel's SUM function just flat doesn't work, but the user
should notice this in the results right away.  Besides, the program gives a
checkbox in a dialog box to have the SUM function work properly, and Microsoft
does mention this in the manual."  How absolutely lunatic.

After Dark's fish w/sea floor is a screen saver that burns an image into the
screen when used as directed.  Might as well turn cmd-S into a macro that
selects all, then hits the backspace key.

My sympathy to the guy who got the damaged Radius monitor,
--Adam--
former Pyro! user who finally decided to use that little knob underneath his
Plus screen instead
 
--  
Adam Frix via cmhGate - Net 226 fido<=>uucp gateway Col, OH
UUCP: ...!osu-cis!n8emr!cmhgate!20.18!Adam.Frix
INET: Adam.Frix@p18.f20.n226.z1.FIDONET.ORG