That's no memory allocation error, but a range-check error. The computed size (next would be 130 * 255 * 255 * 255) doesn't fit in a 32 bit signed integer anymore. If you want to allocate more than 2 GB in a single allocation (which was not your original request), you could try to use an unsigned type (Cardinal or perhaps better SizeType). However, I've never tested this, so there may be RTS or libc issues.
what does in this context mean "range check error"? Sometimes I get the same error when using dynamic arrays, usually when bounds are trespassed. Is there a way to know at which code line the error generates, and does the error have consequences on the results of the code?
Silvio
--
Email.it, the professional e-mail, gratis per te: http://www.email.it/f
Sponsor:
Solo 10 Euro per chiamare in tutto il mondo!! Scopri il vantaggio di Email Phone Card, clicca subito
Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=2685&d=26-7