Path: utzoo!utgpu!attcan!uunet!husc6!bloom-beacon!gatech!ncar!ames!pasteur!ucbvax!agate!saturn!ucscb.UCSC.EDU!koreth
From: koreth@ucscb.UCSC.EDU (Socking the Sockets)
Newsgroups: comp.sys.atari.st
Subject: Re: Questions about ST Video Ram
Message-ID: <4376@saturn.ucsc.edu>
Date: 3 Aug 88 03:18:30 GMT
References: <535@skywest.UUCP>
Sender: usenet@saturn.ucsc.edu
Reply-To: koreth@ucscb.UCSC.EDU (Socking the Sockets)
Organization: American Redundancy Society of America
Lines: 14

In article <535@skywest.UUCP> brenes@skywest.UUCP (Erasmo Brenes) writes:
>If the Shifter expects the video ram to start at 32K boundaries,
>then how do I get MWC, or any C program to allocate a 32Kb buffer starting in
>a 32Kb boundary in an efficient manner?

Well, the boundary turns out to be a lot less than 32K: screen RAM must
start on a page boundary, which is to say screenram%256 == 0.
Thus you only have to allocate 32256 bytes, which you can most likely
afford.  (Screen memory is 32000 bytes, not a full 32K.)

---
These are my opinions, and in no way reflect those of UCSC, which are wrong.
Steven Grimm		Moderator, comp.{sources,binaries}.atari.st
koreth@ssyx.ucsc.edu	...!ucbvax!ucscc!ssyx!koreth