Path: utzoo!attcan!uunet!jarthur!spectre.ccsf.caltech.edu!tybalt.caltech.edu!toddpw
From: toddpw@tybalt.caltech.edu (Todd P. Whitesel)
Newsgroups: comp.sys.apple
Subject: Re: //gs screen resolutions...
Message-ID: <1990Feb21.204027.14363@spectre.ccsf.caltech.edu>
Date: 21 Feb 90 20:40:27 GMT
References: <2483@ttardis.UUCP> <1990Feb21.075626.4416@spectre.ccsf.caltech.edu> <12200@smoke.BRL.MIL>
Sender: news@spectre.ccsf.caltech.edu
Organization: California Institute of Technology
Lines: 26

gwyn@smoke.BRL.MIL (Doug Gwyn) writes:

[ in response to this ]
>>(Oh yeah.. the 400 line interlaced graphics are done by a cheap hack too.
>>The super hires buffer in banks $E1 and $E0 -- really shadowed copies on
>>the VOC -- are displayed alternately with even and odd frames of the video.)

>That's exactly the way I would expect it to be done.
>Why do you denigrate it as a "cheap hack"?

Because it trashes the nice linear memory map they worked so hard to acheive.
It's nit picking, I know, and there was no other way to do it without it being
a _real_ pain.

I just don't want this to become an official standard (that is, as the only
interlaced mode in the next machine) because then we're just milking 128K
for all its worth again and we don't have to do that in these enlightened
days of cheap VRAMs.

IMHO, we should be moving towards a fully programmable video generator with 
enough settings to take us quite a few years ahead. Custom logic is much
cheaper to work with before it is cast in silicon. Read the Apple //f post
because it has a much better description of this.

Todd Whitesel
toddpw @ tybalt.caltech.edu