HP3000-L Archives

June 1999, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Joe Geiser <[log in to unmask]>
Reply To:
Joe Geiser <[log in to unmask]>
Date:
Thu, 10 Jun 1999 13:48:58 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (28 lines)
Gavin writes,

> If your organization uses Windows based file servers, get up right now and
> go look at their consoles.  If you find any animated screen saver running
> on any of them, either disable it or change it to the simple "blank
screen"
> saver.  Instant cpu upgrade.

Yes, screen savers can be a CPU bottleneck, and yes, the "blank screen"
screen saver will work - but any screensaver - will have some effect.

The best screensaver we have found is the little control on the monitor
called "brightness" - and a switch called "On/Off" or "0/1".  Just turn the
monitor off.  Windows still continues to run, and no screensaver code is
needed at all!  If you  absolutely must keep the monitor on - turn down the
brightness.  This will give you Gavin's upgrade, and more :)

Lastly, everyone seems to think that phosphor burn-in will occur with
Windows.  I won't absolutely say that it happens, but I can say
categorically, that I have yet to see any burn-in from any Windows-based
computer.  I've seen a lot of MS-DOS based systems with burn-in, but because
of the color schemes (most use the grey or blue background, and colors are
on in most of the pixels) - burn-in is usually not a problem.  The problem
is power saving - again, just turn it off.

Cheers,
Joe

ATOM RSS1 RSS2