| Title: | AMIGA NOTES |
| Notice: | Join us in the *NEW* conference - HYDRA::AMIGA_V2 |
| Moderator: | HYDRA::MOORE |
| Created: | Sat Apr 26 1986 |
| Last Modified: | Wed Feb 05 1992 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 5378 |
| Total number of notes: | 38326 |
In another note it seemed pretty clear that I can't convert some of my
IFF files to postscript with ADpro because I don't have enough
contiguous memory. It was calculated that I needed almost 2MB of
contigous and since my machine only has a total of 2MB of fast and 2MB
of chip, finding 2MB of contiguous anything seemed doubtful.
I have the Micron 2MB board (old) which maxes out at 2MB. Now I would
like to add an 8up or similar type board with 2 more megs. My question
is, will I now have 4MB of contiguous fast ram or will the fact that
the memory is spread across two boards introduce the possibility that
all the fast ram may no be contiguous? If the boards are physically
located next to each other, will they be contiguous, and which one
should go in first? Or am I just naive and worrying about nothing?
Terry
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4805.1 | I don't think there's a problem | HPSCAD::GATULIS | Frank Gatulis 297-6770 | Mon Jun 10 1991 16:02 | 10 |
Re -1
Terry,
I think contiguous memory will be no problem. I have one of those 2meg
micron memory boards and an old C= 2meg memory board and a MERGMEM
in the startup-sequence makes them appear as a 4meg contiguous chunk.
Frank
| |||||
| 4805.2 | MERGEMEM | TLE::RMEYERS | Randy Meyers | Mon Jun 10 1991 17:10 | 10 |
Re: .0 .1 is right on the money. Normally, memory from different autoconfig boards does not show up as contiguous memory even though the two memory regions have contiguous addresses. The problem is that the Exec's code to merge memory deallocations into contiguous chunks doesn't work during autoconfig. However, the MERGMEM program that is part of the Workbench distribution, will fix this problem by merging the memory in the Exec memory list. | |||||