David Taylor wrote: >Does Lazarus (or any similar project) plan to support Win64? I really >don't want to have to recode all my stuff in C# or C++, but I do want to >handle very large image data...
which was exactly the reason behind my enquiry. At the moment, using the memory mapped file feature for bitmaps available in the Imageen library, I'm able to load and to some extent manipulate digital map images with 15478x15478 side lengths on a dual-processor machine with WinXP SP2 and 2 GB physical memory and hyper-threading enabled (which looks like four processors in the Task Manager Performance windows). Although a typical Landsat 7 false colour 24 bit satellite image Tiff tile with 20101 x 17141 pixels (1.03GB) can be displayed, trying to do anything with it gives an "out of resources" error from the OS. This happens even though there is more than enough free memory as shown by an API call to GetSystemMemory. As I understand it, Paged Pool memory, apparently needed for constructing the internal bitmap, is limited to 492 MB under XP/2000 Pro, 650 MB under XP2003 Server but 120 GB under WinXP64 according to Russinovich & Solomon, Windows Internals, 4th ed. p. 401, Table 7-5, but these figures are smaller than the image sizes mentioned above. Is there a known relationship between available Paged Pool and the maximum size of available resources for the construction of a bitmap under 32 bit Windows? Does GetProcessMemoryInfo return anything useful for determining this? Irwin Scollar _______________________________________________ Delphi mailing list -> [email protected] http://www.elists.org/mailman/listinfo/delphi
