#ImageMaster problem
6 messages in this thread
We have a problem with a customer using ImageMaster (v9.16 & 9.21) on an
unaccelerated Amiga 2000… when loading some IFF24 pictures (scanned with
a ES300C and ADpro)… the machine gurus when the message "decompressing
picture" appears… and yes we are using the 68000 version when there is
no accelerators in the machine. At first we thought that it could be the
installation so we reinstalled both the workbench and IM, with no better
results. We the tried the controler & memory card in another A2000 CPU
with the same results. We then took a Hardcard and an accelerator from a
machines that was able to load these pictures and it did work in the
customer's machine so the conclusion is that when there is no 68040 or
68030 in the machine, some of our pictures do not load! Strange… any
idea?
Pat, How much RAM is in that 2000?24 bit images tend to be HUGE soooooo.
I can't use 1600*2000 REZ images on my 14 meg 3000,tho I'm going to
attempt to use Gigamem with IM's Virtual Memory.
The A2000 has 6MB ram (2MB chip/4MBfast).
The IFF file is 325k big (169×659 pixels)
Yes, I tested the software with different ram board in case of a bad
chip… still the same result! 🙁
Actually, if the undo buffer is on (it usually is) then that file is 780k,
not 325k. Still well within the machine's limits, but I thought I'd point
it out to you. You can find memory requirements by looking at page 18 in
the Imagemaster manual.
–Ben
…via AutoPilot
Very Strange.You shouldn't have a problem IMHO for a pic that small with 6
megs in the machine.Good Luck.Hope you find the problem
Not offhand; I would consider AdPro as a high-quailyt image file source,
and so would assume that the problem is somehow related to the 68000
version of the software.
I would suggest that you get the latest upgrade; the reason why is that we
are now compiling it with a brand-new version of the C compiler, which
seems to make far more reliable code. I know of at two specific situations
where the code generation of the 5.x compiler was broken for 68000's and
we had to work around that with some assembly code; it's possible that
there is another similar situation in the loader code we've not caught. If
so, the new version will almost certainly fix it, as it did fix both of
the other problems. These are guesses, but informed ones at least. :^)
One thing you can do is send us one of the images; you can upload it to
our library here, if you like. It won't be made public. We have some
extensive IFF image file diagnostic software that we can use to see what's
in the file, and we can also throw it at the program here to see if we can
spook the loader. I would certainly appreciate it if you would do so,
although I realize it would take considerable time. Another option would
be to send us the file on diskette, marked attention Mike French. Mike
handles most of the file I/O stuff for us now, with about 10% being done
by Pete.
Thanks for the report, anyway.
–Ben
…via AutoPilot