• Please review our updated Terms and Rules here

Any CPMTools experts out there?

DJ Sures

Member
Joined
Jan 10, 2023
Messages
17
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
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...
1674454605426.png
 

Koolstar42

Member
Joined
Sep 24, 2019
Messages
41
Location
Netherlands
did you first create an empty filesystem of the correct size?

dd if=/dev/zero of=TST.DSK bs=128 count=4000
mkfs.cpm -f nabutest TST.DSK
cpmcp -f nabutest TST.DSK file user:
 

DJ Sures

Member
Joined
Jan 10, 2023
Messages
17
ah yes brilliant - thank you for being a CPM Tools expert! So mkfs.cpm will fill the file if it already exists. That's really good to know - I will add the information to the cloud cp/m page so this can be shared with others
 
Top