> I hope you will use mt_alloc instead. If pool_alloc is "fixed" in this > way then I will have to hack access to 128 different locks - and even I'm afraid to ask but... Why is one writing any code, anywhere that knows the number of library internal locks? Regards, Loren