#ADPro Memory Help
15 messages in this thread
I recently purchased ADPro 2.3. I attempted to load a large IFF file
and got an error message saying there was insufficient memory to load
it. I have 12 Mb of RAM, composed of 4 megs of 16 bit memory in a
hard card, and 8 megs of 32 bit memory in a Progressive 040 accelerator.
The ADPro "ABOUT" function says I only have a bit over 4 megs for the
buffer, and the image required something like 4.1 megs. The only thing
I can find in the book is some reference to "contiguous" memory, and
I'm wondering if for some reason ADPro is not recognizing my 8 megs
of 32 bit memory. Is there some way to get it to recognize the entire
12 megs. Thanks.
Consult the manual section describing the MAXMEM tool type. By default the
MAXMEM tooltype is set fairly low.
Thanks for the response on my memory problem. I tried upping the MAXMEM
limit, and even removed the limit altogether. However, it didn't change
anything. It seems everything else recognizes my 12Mb except ADPro. Any
ideas ? Thanks.
Could you please redescribe your hardware layout? IE: what memory is located
where.
My memory configuration is 1Mb of chip ram, 4Mb of 16 bit ram on a IVS Grand
Slam hard card, and 8 Mb of 32 bit ram on a Progressive 040 accelerator card.
I'll try your suggestion of starting ADPro from the CLI tonight. Thanks.
With the memory organization you specified, I think that 8MB will be
the most that ADPro can grab. There's no way to put 4 MB of 16 bit
memory next to 32 bit memory in the Amiga's hardware map, if memory
serves.
Thanks. I tried running ADPro from the CLI as you suggested, and I still
couldn't get more than 4Mb for the buffer. Now when you say that 8Mb will
be the most that ADPro can grab with my configuration, how would I get
the additional 4Mb ?
I don't know, at this point, you are not getting the 8 meg section. Do you
have a program which lists memory chunks – one such program is called
frags. From what you've told me so far, you should be getting at least
close to an 8MB slice. Are you running any utilities or hacks at start up?
I run 8 meg 16-bit on Supra Ram board, and 8 meg 32-bit on PPS 040 and
I've never able to access more than an 8 meg chunk with ADPro.
Gigamem works just fine with ADPro for large file conversions.
….John
Thanks, John. BTW, what is Gigamem ?
Jim,
Gigamem is a commercial package that adds virtual memory capabilities
to programs that are "Gigamem aware". AdPro is one such program. There
are others out there, but since I rarely do serious image work, I haven't
bothered to track it down. I'm also not sure if there are specific
hardware requirements for using Gigamem.
If you aren't familiar with the term, virtual memory refers to the
capability of using space on your harddrive as additional memory. To
make it work, when a memory block is not in memory, a "fault" occurs
and the required memory block is swapped in from the harddrive. It's
a slower than real memory, but on a fast machine with a harddrive, it
may not be noticeable. As with any system sleight-of-hand, it's a
tradeoff. More memory for a hit in speed.
Jim,
look for a program called MergeMem. You'll probably find it on older
versions of the AmigaDOS system. Funny, but it shouldn't be a problem
with the current version of AmigaDOS (2.1) as it seems to merge all
existing memory automagically.
Brian
bjbart@watnxt01.ucr.edu
Thanks Brian. I tried a version of MergeMem called JoinMM (I couldn't find
MergeMem on my 1.3 disks), but it said I've already got 12Mb, and it
couldn't do any merging. I think you were right that AmigaDOS 2.1 already
merges it; however, ADPro doesn't recognize it for some reason, although
everything else does. Any ideas ?
From a freshly booted system, please try running ADPro from the CLI and
then hit the HELP key on the keyboard. The primary image buffer size should
be given in the resulting panel. Running from the CLI (as in simply:
ADPro:ADPro
will cause ADPro to consume as much memory as it can. See if this gets you
a primary image buffer larger than you've had before.
nope. If it's not a problem with the maxmem and it's contiguous,
then it _should_ work.
Brian
bjbart@watserv.ucr.edu