Hi Mark,

I can't see this being a problem, but would echo what others said about killing the .hdr/.img duple support. I'm also one for keeping the changes simple at this point (not changing other parts of the header while you are at it), the reason being is that the NifTi header is always going to be restrictive in what you can put in there. Extra bits should be added as NifTi comments or as you mention done as part of a NifTi successor.

At least if niftilib is going to support this without any hassle to me that's more than a good reason for us here in MINC-land to use it instead of our own home-grown nifti reading/writing libraries. So thumbs up from MINC.

Still I am curious, just how much RAM do you lot have to have exhausted 32767*32767*x?


a