Xref: utzoo comp.sys.amiga:69952 comp.sys.amiga.tech:15393
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!unsvax!arrakis.nevada.edu
From: niobium@arrakis.nevada.edu (Christopher W. Carlson)
Newsgroups: comp.sys.amiga,comp.sys.amiga.tech
Subject: AntiFlicker Woes
Message-ID: <2193@unsvax.NEVADA.EDU>
Date: 24 Oct 90 08:38:43 GMT
Sender: news@unsvax.NEVADA.EDU
Followup-To: comp.sys.amiga
Distribution: na
Organization: University of Nevada, System Computing Services
Lines: 29


What a wonderful program this Antiflicker is!  If you're stuck with no
FlickerFixer and have utility for it (I use it with DNet to make a _really_
slick setup), be sure to check this out!

"Huh?" you ask yourself.  "Subject line says `woes'!"  Well, yeah.  I 
followed the tips in the last few lines of the file AntiFlicker.English
which is in the AntiFlicker.lzh file on abcfd20 and modified my system-
configuration to make me an Overscan screen.  Cool!  Unfortunately, I
believe that I've also just given myself a PAL-mode screen, which simply
won't do, as I'm in the US and have a NTSC Amiga!

So!  Can anybody give me hints as to what I should change bytes D8 and D9
in devs:system-configuration to to give myself a normal overscan screen?
I wouldn't complain except that programs like MuchMore, etc., utilize
every scan line they can find and I just can't read that far down the screen,
where the monitor face is covered!

Hmm.  Perhaps what I'm asking just isn't possible, hmm?  Let me know.

Thanks.

-=* Christopher W. Carlson
    niobium@arrakis.nevada.edu
--
 __   _          _  _____  _    ___       __  |  Christopher W. Carlson |   //
/ __ / \  |     / \   |   / \  |__  /  \ (__  |    niobium@nevada.edu   | \X/
\__// /_\ |___ / /_\  |  / /_\ |___ \__/ ___) |--------------------------------
      Galataeus, ex-Bard of Arrakis           |  I never said these words...