Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!pyrdc!netxcom!hadron!klr
From: klr@hadron.UUCP (Kurt L. Reisler)
Newsgroups: comp.sys.dec.micro
Subject: Re: Keeping my Rainbow healthy
Message-ID: <672@hadron.UUCP>
Date: Mon, 30-Nov-87 10:00:45 EST
Article-I.D.: hadron.672
Posted: Mon Nov 30 10:00:45 1987
Date-Received: Thu, 3-Dec-87 04:26:06 EST
References: <8711291625.AA06523@ucbvax.Berkeley.EDU>
Reply-To: klr@hadron.UUCP (Kurt L. Reisler)
Organization: Hadron, Inc., Fairfax, VA
Lines: 23

In article <8711291625.AA06523@ucbvax.Berkeley.EDU> GTHEALL@PENNDRLN.BITNET (George A. Theall) writes:
>Hello,
>
>  Can anyone tell me whether leaving a Rainbow on all the time is
>a bad idea? I've heard turning a machine on is the time when it's
>most susceptible to damage, so I've been leaving mine on. Is this
>likely to lead to problems later on? For instance, with the monitor
>or the fan, which runs continually? With HISTORY installed, I don't
>have to worry about images getting burned into my CRT, but is there
>a chance of it losing its brightness? What's the word?
>
>George

Well, I have 2 Rainbows that are running as FidoNet nodes (109/74 and
109/483).  Neither of these is EVER turned off, except for periodic
maintenance (vacume the dust out) or irregular power failures.  The
Bear's Den (109/74) has been running at home for almost 3.5 years
without a problem.  However, I just had to replace the RX-50 controller,
but I think this was more due to old-age (it was a used machine 3+ years
ago) than being on continuously.

A question.  Since the screen on a Rainbow auto-blanks after 30 minutes
of inactivity, why does HISTORY solve any screen burn problems?