Thats it!? That dang DLL, easy to find and install.
?
Myself I do large devices and I don't do from container files in
Fat file systems.
?
My approach is format the uSD or CF as fat.? Then use parted(linux) or
other tool discover where the device Block replacement table
that is used internally.
?
The system treats any foreign format as meaningless.? ?The BIOS I've
done treat CF or uSD as a contiguous collection of 512 byte blocks
addressed as LBA.? Usually starting at 1000h and for every 16384
(0x4000)blocks are a? 8mb disk.? The parameter block in the bios
has a parameter called offset by making sequential logical drives
easy to do on large devices.? ?No need to partition the device.
?
One trick I've started to use is make the first block in a non file space
a format table so I can move the device to another system
(mostly IDE/CF).? It describes size and organization.? A single
block is easy to read and understand than a partition table.
?
Using FAT16 to do this works but adds another layer of?file system?
to find the desired container files and its starting address or
extended address.? Adds overhead and makes the device
readable by PC save for the file contents still needs a tool
to understand the CP/M directory structure.? A similar tool
could easily read the device directly without using FAT.
?
Actually I have tools for CP/M that can write RX01 (RT11 format)
and DOS fat12 or fat16 floppies and write them as well.
I found that more convenient when floppies were a thing.
?
Allison
?
