I have a disk with the program supercop by erbosoft. I tried to make a .dsk but it failed (pc tells me bad sector at the beginning). Then I tried to make a .dmk file with the read-dmk.com tool, but that one also failed. Does anyone know another method I can try ?
I checked the READ-DMK source code ... that "sector buffer overflow" error is given when the buffer space reserved to store all sector data is too small. The size of that buffer is currently 7680 bytes.
In your screenshot I see that the total size of this track is only 6302 bytes, so less than the sector-buffer size. However some copy-protections have sectors that overlap with each other. In such a case it can be possible that the sum of the sector sizes is larger than the total size of the track. READ-DMK does support overlapping sectors, but apparently not to this degree.
@TheKid: as Manuel already asked. Could you share the generated debug file? That might contain more details about the track layout, and it may allow me to estimate how large the sector buffer should be. If it's only a little too small then I can probably tweak READ-DMK. If it's much too small then it needs a different buffering strategy.
Ah, and it's normal that reading sectors with READ-DMK is A LOT slower than 'regular' sector reads. The reason for this is to handle duplicate sectors within a track (multiple sectors that share the same sector number). A regular sector read returns the data from an 'arbitrary' instance of these sectors (depending on how the disk is currently rotated). But in READ-DMK we want to ensure that we read the 'correct' instance. This is done via some timing tricks.
TheKid: a DMK file is always larger than 720kB, so you can't write it to drive B if drive B is a simple floppy drive. I suppose DMK Creator is supposed to be used with mass storage to save the DMK file to.
With read-dmk, the DMK file is written per track, so when the drive B disk is full, you can put in a next disk to save the remaining tracks to. Afterwards, the tracks are combined into a single DMK file with a PC tool (combine-dmk).
Anyway, thanks for the debug file. I hope Wouter can find out what's going wrong using that.
