Xref: utzoo comp.sys.mac.system:7407 comp.sys.mac.hardware:12117
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rosen
From: rosen@cs.utexas.edu (Eric Carl Rosen)
Newsgroups: comp.sys.mac.system,comp.sys.mac.hardware
Subject: Re: MaxAppleZoom
Message-ID: <1548@nada.cs.utexas.edu>
Date: 14 Jun 91 16:24:31 GMT
References: <1991Jun8.025731.7019@dhw68k.cts.com> <1991Jun11.234006.12996@nntp.hut.fi> <1991Jun14.142904.28785@eng.umd.edu>
Followup-To: comp.sys.mac.system
Organization: Dept of Computer Sciences, UTexas, Austin
Lines: 19

In article <1991Jun14.142904.28785@eng.umd.edu> russotto@eng.umd.edu (Matthew T. Russotto) writes:
>
>The bit about compressing the screen appears to be that MaxAppleZoom misses a
>few places where the 640*480 information is stored-- my guess is that it is
>the system 'scrn' resource, as the problem seems to fix itself after a few
>boots, but comes back if you move the video card.  
>
>(of course, it could also be parameter ram... do you know where the information
>for the main screen is stored in parameter ram?)
>
>

I tried changing the 'scrn' resource to account for the new 704x512 screen
size. Although the change stuck, even after rebooting, it did not seem to
make any difference to MAX's operation -- Macsbug still messes things up.
I did not zap the pram after I'd modified the 'scrn' resource as I don't
know how to do this under 7.0.

--Eric