#: 20975 S12/OS9/68000 (OSK)
    31-May-95  12:47:48
Sb: #20971-buffers
Fm: LARRY OLSON 72227,3467
To: Kevin Darling 76703,4227 (X)


 > Unfortunately, there isn't a way to allocate memory for a group of
 > buffers ahead of time.  The internal system has to know where each
 > "object" will begin so it can make better decisions about storing it.
 >
 > If you run out of buffers, some people use P_ID+128, although that may not
 > be safe on everyone's system.

   Kevin,
       Thanks, I'll keep that P_id + 128 in mind. What brought the question
up was as usual, another dumb mistake of mine. I kept getting the error
message - can't allocate memory -, when I was trying to run this program and
I thought the problem was in allocating memory for the GET/PUT buffers. I had
forgotten that I had changed another part of the program, that was loading a
sound file. Well now the sound file wasn't where the program thought it was
and that was where the program kicked out the -can't allocate memory- error.
  Ok, I'll get back to playing with these GET/PUT buffers again, I havn't
got it figured out completely yet but the GET appears to be sensitive about
where the object is on the screen, because some objects when they are later
put to the screen, the rightmost pixels of the object are missing. I thought
I had it figured out by drawing the objects so that they fall on the 8 bit
boundries, and for some of the objects this worked, but not for all.

   Thanks again Kevin
   larry