jsivier@ux1.cso.uiuc.edu (Jonathon Sivier ) (12/05/90)
I have run into a problem with Deluxe Paint III. I have an Amiga 2000 with 1 Meg of chip ram, 4 megs of fast ram, a CSA 68020 accelerator card with a 68881 math co-processor. I was working with two pictures 640 * 400 * 4 (16 colors). I cut a very large brush (aprox. 400 * 350) out of the back buffer, and tried to blend it onto the front buffer. I got the message that there was not enough memory for the operation. So I deleted the back buffer and tried again. Same error message. Then I went out to the CLI and did AVAIL, it showed me as having over 500 KBytes of chip ram free with the largest block being about 330 Kbytes, and almost 4 Mbytes of fast ram free. So what is the deal here? There is no way that I didn't have enough memory for the operation, no matter what the operation was. Does DPaint not pay attention the actual amount of free space, or what? I wasn't running the Workbench so couldn't free any memory that way. I could remove the resident commands I have and so free up a little more chip ram, but if 500 K plus isn't enough then I don't think that will help. I like Dpaint in general, but this is a very annoying sort of problem, and so meaningless. If anyone has any insights into this I would be glad to here them. Thanks, Jonathan -- ------------------------------------------------------------------- | Jonathan Sivier | Ballo ergo sum. | | jsivier@ux1.cso.uiuc.edu | (I dance therefore I am.) | | Flight Simulation Lab | - des Cartwright |
drtiller@uokmax.ecn.uoknor.edu (Donald Richard Tillery Jr) (12/06/90)
In a message from: jsivier@ux1.cso.uiuc.edu (Jonathon Sivier ) > I have run into a problem with Deluxe Paint III. I have an Amiga 2000 with >1 Meg of chip ram, 4 megs of fast ram, a CSA 68020 accelerator card with a >68881 math co-processor. I was working with two pictures 640 * 400 * 4 (16 [stuff about running out of memory in DPaint III deleted] >...Does DPaint not pay attention the actual >amount of free space, or what?... >...I could remove the resident commands I have and so >free up a little more chip ram, but if 500 K plus isn't enough then I don't >think that will help. AND, the newest Amiga World says that DPaint is limited by available RAM. Why doesn't fast RAM count? I too have 5 megs (1 chip, 4 fast) and keep running out during operations when I have plenty of chip, but even more surprisingly, lots of fast RAM. At any rate, I think Amiga World guilded the lily a bit (to say the least). Rick Tillery (drtiller@uokmax.ecn.uoknor.edu)
d0micke@dtek.chalmers.se (Mikael Andersson) (12/07/90)
In article <1990Dec4.174815.24734@ux1.cso.uiuc.edu>, jsivier@ux1.cso.uiuc.edu (Jonathon Sivier ) writes: |> |> I have run into a problem with Deluxe Paint III. I have an Amiga 2000 with |> 1 Meg of chip ram, 4 megs of fast ram, a CSA 68020 accelerator card with a |> 68881 math co-processor. I was working with two pictures 640 * 400 * 4 (16 |> colors). I cut a very large brush (aprox. 400 * 350) out of the back buffer, |> and tried to blend it onto the front buffer. I got the message that there was |> not enough memory for the operation. So I deleted the back buffer and tried |> again. Same error message. Then I went out to the CLI and did AVAIL, it |> showed me as having over 500 KBytes of chip ram free with the largest block |> being about 330 Kbytes, and almost 4 Mbytes of fast ram free. So what is the |> deal here? There is no way that I didn't have enough memory for the operation, |> no matter what the operation was. Does DPaint not pay attention the actual |> amount of free space, or what? I wasn't running the Workbench so couldn't |> free any memory that way. I could remove the resident commands I have and so |> free up a little more chip ram, but if 500 K plus isn't enough then I don't |> think that will help. I like Dpaint in general, but this is a very annoying |> sort of problem, and so meaningless. If anyone has any insights into this |> I would be glad to here them. |> |> Thanks, |> Jonathan |> |> |> -- To mee it sounds like you had some nice memory fragmentation problem and not a large enough free block to hold your image. Try some of the really nice defragmentation programs that are published in the Fish PD disks. It's smart to make a memory defragmentation run - well let's say every 15 minutes or so to keep the memory tidy and neat.... :) /Micke
Classic_-_Concepts@cup.portal.com (12/08/90)
One of your strategies to free up some memory (by nuking the swap
screen), was a step in the right direction, but I have found it doesn't
always give you back everything you need (especially if you have also
been using large fonts, which are held in memory). You can further free
some memory by going to the menu item for changing the screen format.
You don't have to (or want to) make any changes, but clicking the OK
gadget on the screen format screen will blast away some of the stuff
being cached in memory only after it has been selected by the user during
that session. So you can squeeze a little more of it out that way.
If that doesn't provide you with enough, then run one of the defrag.
programs suggested by the other posters. Good luck.
J. Petersen (LadyHawke)