LoadImage causes a MAV when trying to load very large images (I haven't done tests to figure out exactly how many MB is too many on my PC).
It's obviously because it wants to load the entire image into RAM (and of course store it as an uncompressed bitmap).
FreeImage, while being able to load slightly larger files for some reason, does hit the same brick wall.
I'm actually building a mesh at runtime, and then painting surfaces with 256x256 textures.
I'm only displaying a small number at any one time, so that won't present any RAM problems.
I am indeed using banks to bring the data in from the files produced from the image pieces.
My requirement to use ImageMagick stems from wanting to grab arbitrary 256x256 pieces of an image, regardless of that image's size.
ImageMagick has a stream command that lets you do this.
Incidentally, I've just had a go at running ImageMagick directly using ExecFile() with the following command:
ExecFile("stream -extract 256x256+0+0 -map rgb -quiet "+Chr$(34)+"test.png"+Chr$(34)+" "+Chr$(34)+"test.tmp"+Chr$(34))But I still get the dos box appearing for a second...
:o(
The whole image-streaming technique I'm using seems to be working nicely - it's just the dos box thing that's driving me nuts.