Hi Sergey,
Thanks, that did the trick, didn't think of attacking it that.

>Hi Neil,
>
>NextFreeBlockOfsset = NextFreeBlockLocation * MemoBlockSize
>NextFreeBlockLocation: bytes 00 – 03
>MemoBlockSize: bytes 06 – 07
>
>Keep in mind that in SET BLOCKSIZE TO nBytes, the values from 1 to 32 are multiplied by 512 to get actual block size that is stored in MemoBlockSize.
>
>>Does anyone have code that will calculate the first block position in a new create memo file for varying blocksizes.
>>
>>From testing it doesn't seem to follow any pattern. i.e. blocksize 1 = 1, blocksize 33 = 16, blocksize 64 = 8 & 512 and above it drops back to 1.