> > That's right, for disks detected as RX01 (which are of course fully FM, 128
> > bytes per sector).__ Sector data that is actually 0xDEADBEEF will
> > show up in the .dmk as 0xDDEEAADDBBFF.
>
> I've wondered why .dmk did that.
Redunredundancydancy?
--
On 2/11/21 10:00 AM, David Schmidt via cctech wrote:
That's right, for disks detected as RX01 (which are of course fully FM, 128 bytes per sector). Sector data that is actually 0xDEADBEEF will
show up in the .dmk as 0xDDEEAADDBBFF.
I've wondered why .dmk did that.
On 2/11/21 8:56 AM, Mattis Lind wrote:
After sending my message I did some hard drive archeology and found the
dmklib I downloaded five years ago. There were some adaptations to
handle RX02 format and it worked quite well. At least when the disk has
been read error free.
However the version
Den mån 8 feb. 2021 kl 20:39 skrev David Schmidt via cctech <
cct...@classiccmp.org>:
> On 2/8/21 1:00 PM, Mattis Lind wrote:
>
> I wrote my own, not knowing where another one lived. I happen to think
> in Java, so that's what it's implemented in.
>
> Description is here:
>
>
On 2/8/21 1:00 PM, Mattis Lind wrote:
This is highly annoying. Back in 2015 I did exactly this and now I have
forgotten how.
I dumped a set of RX02 disks with catweasel into .DMK and now I want a raw
sector image to be able to test them with SimH.
What is a good tool to use? I have some faint
This is highly annoying. Back in 2015 I did exactly this and now I have
forgotten how.
I dumped a set of RX02 disks with catweasel into .DMK and now I want a raw
sector image to be able to test them with SimH.
What is a good tool to use? I have some faint memory of glancing through
hexdumps of
