Limits on GET_STORAGE@?

Thanks John, above and beyond and all that!

K

K,

I am interested to find out what memory is available. I'd suggest that you call the free memory checking routine both early in the running of the program then near where the memory is not available. You might want to skip test 1. If I knew a way of releasing all the memory taken by the pointer array in test 2, then the routine could return for the program to continue. It could be that the use of a DLL, giving an apparent split memory address (based on the load maps you supplied) could be limiting the available memory. If so, is it possible to shift the DLL's start address? Again I have not made and linked my own DLL's to know about this.

John

Edit: I changed the memory mapping routine to releqase most of the memory, so that it can continue after being called. I did this with multiple pointer arrays to retain the first 15 addresses and then used DEALLOCATE. Appears to work. If you want to test this area, let me know.

Sorry, John,

a different panic has started (long term project finally got the go ahead!) so I don't have time to investigate this further at the moment. The /3GB switch seems to fix it so I'll carry on with that and get back to this as and when I get time!

thanks

K