[comp.sys.ibm.pc] Screen blanker for Hercules GC

johnm@ncr-sd.SanDiego.NCR.COM (John McDaid) (01/13/88)

The title says it all: Does anyone have a PD screen blanker for a Hercules
Graphics Card.  Please e-mail me directly with any responses.  Thanks in
advance to anyone that can help me out.

John McDaid
John.McDaid@SanDiego.NCR.COM

pjh@mccc.UUCP (Peter J. Holsberg) (01/14/88)

Not PD, but shareware is BURNOUT by Chris Dunford.  If that's not
available to you, let me know and if it's small enough, I'll mail it.
Otw, you can send me a formatted disk in a reusuable mailer (with
address and return postage) and I'll copy it for you.

-- 
Peter Holsberg                  UUCP: {rutgers!}princeton!mccc!pjh
Technology Division             CompuServe: 70240,334
Mercer College                  GEnie: PJHOLSBERG
Trenton, NJ 08690               Voice: 1-609-586-4800

guest@vu-vlsi.UUCP (visitors) (01/15/88)

In article <1976@ncr-sd.SanDiego.NCR.COM> johnm@ncr-sd.SanDiego.NCR.COM (John McDaid) writes:
>The title says it all: Does anyone have a PD screen blanker for a Hercules
>Graphics Card.  Please e-mail me directly with any responses.  Thanks in
>advance to anyone that can help me out.
>
>John McDaid
>John.McDaid@SanDiego.NCR.COM

I am also greatly interested in such a program.  If anyone knows of such a 
program, please let me know.

Many thanks.
 
==============================================================================
| Mark Schaffer        | BITNET: 164485913@vuvaxcom                          |
| Villanova University | UUCP:   ...{ihnp4!psuvax1,burdvax,cbmvax,pyrnj,bpa} |
| (Go Wildcats!)       |           !vu-vlsi!excalibur!164485913              |
==============================================================================
 
  please respond/reply to the above addresses and not to guest@vu-vlsi.UUCP

guest@vu-vlsi.UUCP (visitors) (01/16/88)

In article <129@mccc.UUCP> pjh@mccc.UUCP (Peter J. Holsberg) writes:
>Not PD, but shareware is BURNOUT by Chris Dunford.  If that's not

If I recall correctly, in the doc file for BURNOUT it is recommended that
the program is _NOT_ used with a Hercules card.

 
==============================================================================
| Mark Schaffer        | BITNET: 164485913@vuvaxcom                          |
| Villanova University | UUCP:   ...{ihnp4!psuvax1,burdvax,cbmvax,pyrnj,bpa} |
| (Go Wildcats!)       |           !vu-vlsi!excalibur!164485913              |
==============================================================================
 
  please respond/reply to the above addresses and not to guest@vu-vlsi.UUCP

david@infopro.UUCP (David Fiedler) (01/17/88)

In article <1297@vu-vlsi.UUCP>, guest@vu-vlsi.UUCP (visitors) writes:
> In article <129@mccc.UUCP> pjh@mccc.UUCP (Peter J. Holsberg) writes:
> >Not PD, but shareware is BURNOUT by Chris Dunford.  If that's not
> 
> If I recall correctly, in the doc file for BURNOUT it is recommended that
> the program is _NOT_ used with a Hercules card.

A week or two ago, I ran another PD program "SCRNSAVE" 
on my machine (with a Hercules clone card), and after a short amount of
time (15 or 20 minutes) smelled some hot components. I shut down real fast
and never ran it again after I figured out what had happened.
-- 
David Fiedler         {ames,attmail,hplabs,ihnp4,pyramid,ucdavis}!infopro!david
USMail: InfoPro Systems, PO Box 220, Rescue CA 95672      Phone: (916) 677-5870

"Trust me. I know what I'm doing."

dmkdmk@ecsvax.UUCP (David M. Kurtiak) (01/17/88)

Just for the sake of curiousity - I have a Hercules card clone -
all of this talk about not running various screen blanking programs
has me wondering:  What causes a card to fry?  I was always under
the impression that hardware (for PCs) was 'protected' against
such a mishap as the result of any software.  In other words,
how does this screen blanking program go out and sizzle the
components?  I can see if I applied a kludge to the card by ways
of adding jumpers, etc., but with *software*?  Could someone
_please_ explain this phenomenon?
  
---
David M. Kurtiak
UNC - Greensboro
UUCP:   dmkdmk@ecsvax.UUCP  {rutgers,gatech}!mcnc!ecsvax!dmkdmk
Bitnet: DMKDMK@ECSVAX.BITNET (Mail ONLY)

dean@violet.berkeley.edu (Dean Pentcheff;4059 LSB;;39048;KG97) (01/19/88)

In article <1297@vu-vlsi.UUCP>, guest@vu-vlsi.UUCP (visitors) writes:
> In article <129@mccc.UUCP> pjh@mccc.UUCP (Peter J. Holsberg) writes:
> >Not PD, but shareware is BURNOUT by Chris Dunford.  If that's not
> 
> If I recall correctly, in the doc file for BURNOUT it is recommended that
> the program is _NOT_ used with a Hercules card.

In fact, BURNOUT has two modes of action (switch selectable): it can
blank a screen by twiddling with the controller hardware (this lunches
Hercules cards), or it can blank a screen by simply writing blanks to
the video memory (restoring what was there originally after a
keypress).  The second mode is safe and effective.  Of course, it would
be nice if it automatically detected the herc board and used the
appropriate mode, but...

Anyway, BURNOUT is available from simtel20.arpa.

-Dean
-----------------
Dean Pentcheff	(dean@violet.berkeley.edu)
-----------------
"A university is a place where people pay high prices for goods which
they then proceed to leave on the counter when they go out of the store."

tj@gpu.utcs.toronto.edu (Terry Jones) (01/20/88)

In article <4436@ecsvax.UUCP> dmkdmk@ecsvax.UUCP (David M. Kurtiak) writes:
>such a mishap as the result of any software.  In other words,
>how does this screen blanking program go out and sizzle the
>components?  I can see if I applied a kludge to the card by ways

The card itself usually isn't harmed. Usually it is the monitor.
On a composite monitor the thing scans on its own, then if you
cive it a signal it locks onto that and scans at the signals frequency.

On a TTL monochrome monitor you get the scanning from the signals from the
PC and the monitor usually doesn't scan on its own. The currents that
flow through the monitor circuitry are quite different in a "dynamic"
state (when scanning) then they are when the monitor stops scanning. Often
transistors are on steady instead of for 10 or 20% of the time like they
are when the monitor is scanning. The overheat when on too long. (in an
on or conducting state). IBM made the mono monitor plug into the PC
for a real good reason. When the PC is off there are no scan signals
for the monitor so they want the monitor off. There are three ways to
fratz a ttl mono monitor. 1) unplug the video cable to it while on. 2) plug it
in somewhere else and forget to turn it off when you turn off the PC 3)
via software turn off the video signals. 

Now there are going to be a trillion of you out there that say well I have
a frimfram monitor and I leave it on for weeks and it doesn't do what
you say... or I have use this screen blanker and it works fine with my 
setup. Sure. Some monitors can take it. The IBM TTL mono can't. This is
has been statistically shown. Your mileage may vary as they say. Do it
any way YOU want.