Newsgroups: comp.sys.amiga
Path: utzoo!utgpu!watserv1!maytag!watdragon!lion!tdesjardins
From: tdesjardins@lion.uwaterloo.ca (Tim Desjardins)
Subject: Re: flickerFixer Future
Message-ID: <1990Jun10.001539.25211@watdragon.waterloo.edu>
Sender: daemon@watdragon.waterloo.edu (Owner of Many System Processes)
Organization: University of Waterloo
References: <1990Jun7.133716.25812@portia.Stanford.EDU> <31141@ut-emx.UUCP> <1990Jun7.221030.4116@cbnewsm.att.com> <30649@cup.portal.com>
Distribution: na
Date: Sun, 10 Jun 90 00:15:39 GMT
Lines: 24

In article <30649@cup.portal.com> Rick_R_Kitts@cup.portal.com writes:
>
> I've been doing quite a bit of back and forth with MicroWay lately and
>can say quite confidently that there is _no_ reason to worry about them
>at all. In the first place, FlickerFixers are _not_ going to go away
[ stuff deleted ]
>flickerFixed system.

 So, are they going to release a new, flicker fixer that will de-interlace
the new modes that it can't de-interlace.
 Also, are they going to support more of the overscan screen than they do
now.

  I know, you probably you don't know, but, these are questions FF owners
should be asking. My only complaint with my FF is that I can't use all of
my overscan screen, this will probably be worse on the 3000 when you can't
de-interlace those extra 1280x400 modes and the like.
Judging, by the design of the FF, it is definately not upgradable.
Other than those gripes, I have no complaints.

--
Tim Desjardins.                       tdesjardins@lion.waterloo.{edu|CA}
"It's better to regret something you have done, then to regret something
you haven't done." Butthole Surfers
