Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!apple!lsr
From: lsr@Apple.COM (Larry Rosenstein)
Newsgroups: comp.sys.mac
Subject: Re: Risk on a Mac II
Message-ID: <528@internal.Apple.COM>
Date: 2 Feb 89 18:42:00 GMT
References: <6326@boulder.Colorado.EDU>
Organization: Advanced Technology Group, Apple Computer
Lines: 29

In article <6326@boulder.Colorado.EDU> bernard@boulder.Colorado.EDU (Bernie Bernstein) writes:
>who wanted to know the same info.  Here is an excerpt from the
>letter I received 
>
>    From: Jerry_Geronimo_Whitnell@cup.portal.com
>    
>    windows, it saves away the bit map.  The problem is, it is using
>    GetWMgrPort to get the port to figure out the size and Apple, in it's
>    great wisdom, change the definition of what GetWMgrPort returns (used
>    to be a GrafPort, now a CGrafPort).  So Risk calculates a random value

It's time again to defend the honor of the System Software engineers.  :-)

Everytime this question is asked, someone comes up with the same message,
which gives the proper patches for the wrong reasons.  The problem is that
RISK assumes that the product of the screen width and the row bytes will be
less than 32767.  (It sign extends the product.)  On a Mac II that's not
the case.  GetWMgrPort returns the same thing on a Mac II as on other Macs.

Also, it is not necessary to apply a different patch depending on your
screen depth.  RISK doesn't use color, so it only needs a 2-bit deep
offscreen buffer the size of the original Mac screen.  So you might as well
apply the 2 color patch to save heap space.

-- 
		 Larry Rosenstein,  Object Specialist
 Apple Computer, Inc.  20525 Mariani Ave, MS 46-B  Cupertino, CA 95014
	    AppleLink:Rosenstein1    domain:lsr@Apple.COM
		UUCP:{sun,voder,nsc,decwrl}!apple!lsr