I recently hooked up smartportsd device to apple 2c that has ZRAM Utra 3 board installed. After patching the firmware to report images of size 800K as "DISK 3.5" floppy I was able to run CPAM60UF.com to make the image bootable to CPAM 5.1 on the board.
Now I wanted to have a bigger sized hard drive image not necessarily bootable, just for more storage. According to Users manual the only hard drive that was supported at the time was Sider drive, no mention of smart port hard drives.
I tried to use a 32MB image with copy of bootable floppy image at the start of the image. The filesystem is recognized with stat reporting different geometry from floppy:
So the image is treated as 2MB drive, which is not as good as full capacity, but better than 800k. With that data I created the following disk definition for cpmtools:
With this format I created a 2MB image using mkfs.cpm and put some files using cpmcp. The files were recognized on target machine but contents are curiously incorrect. By typing a long text files I found that the first 128 bytes are repeated 8 times, then 128 bytes at position 1024 are repeated 8 times and so on.
So I am trying to solve this puzzle of what is at fault here and for what the reason, and invite all enthusiasts of puzzles of the sort to participate with troubleshooting advice.
One strange fact in reported geometry is absent value for "records/ physical extent" on hard drive, whatever that means. Where would that come from? How in general cp/m would deduce all these parameters for hard drive?
Now I wanted to have a bigger sized hard drive image not necessarily bootable, just for more storage. According to Users manual the only hard drive that was supported at the time was Sider drive, no mention of smart port hard drives.
I tried to use a 32MB image with copy of bootable floppy image at the start of the image. The filesystem is recognized with stat reporting different geometry from floppy:
Code:
A: Drive characteristics (800k 3.5 drive)
62272; 128-byte record capacity
784: kilobyte drive capacity
256: 32-byte directory entries
64: checked directory sectors
128: records/ physical extent
16: records/ reservation block
64: 128-byle sector/track
2: reserved tracks
Code:
B: Drive characteristics (32MB image)
16368; 128-byte record capacity
2046: kilobyte drive capacity
512: 32-byte directory entries
0: checked directory sectors
: records/ physical extent
16: records/ reservation block
64: 128-byle sector/track
2: reserved tracks
So the image is treated as 2MB drive, which is not as good as full capacity, but better than 800k. With that data I created the following disk definition for cpmtools:
Code:
diskdef cpam-hd
seclen 128
tracks 256
sectrk 64
blocksize 2048
maxdir 512
boottrk 2
os 2.2
end
With this format I created a 2MB image using mkfs.cpm and put some files using cpmcp. The files were recognized on target machine but contents are curiously incorrect. By typing a long text files I found that the first 128 bytes are repeated 8 times, then 128 bytes at position 1024 are repeated 8 times and so on.
So I am trying to solve this puzzle of what is at fault here and for what the reason, and invite all enthusiasts of puzzles of the sort to participate with troubleshooting advice.
One strange fact in reported geometry is absent value for "records/ physical extent" on hard drive, whatever that means. Where would that come from? How in general cp/m would deduce all these parameters for hard drive?
Last edited: