There might be an undocumented parameter that I'm unaware of - so maybe someone has the answer to this before I dive into the code and hopefully do not have to create my CPM image manager. But when I make a CPM disk image, the physical file is only as big as the data which I put on the file. If the diskdef defines the disk image as 512k, the physical file is not 512k. The file will only be as large as the data I put on the image using the cpmcp command.
If I create a disk image defined as 512k, I would expect the disk image file to be 512k - where the unused area is blank.
So, is there a parameter in CPM tools MKFS.CPM that I'm missing? Something that tells mkfs.cpm to create the file padded to the size of the diskdef definition?
For example, my disk definition is for an 8mb disk
But i end up with a 16kb disk image file...

If I create a disk image defined as 512k, I would expect the disk image file to be 512k - where the unused area is blank.
So, is there a parameter in CPM tools MKFS.CPM that I'm missing? Something that tells mkfs.cpm to create the file padded to the size of the diskdef definition?
For example, my disk definition is for an 8mb disk
diskdef naburn
seclen 128
tracks 16384
sectrk 4
blocksize 2048
maxdir 512
skew 1
boottrk 0
os 2.2
end
But i end up with a 16kb disk image file...
