Retro System Interface to Modern Peripherals:
Retro System Interface to Modern Peripherals:
...These HDDs will not last forever...will some day crash...same will happen with the old floppies...What then?
PC HDD ANSWER:
For early PCs, the system needs a retro interface to SATA drives. SATA can be used in a default IDE protocol which really simplifies things. Just a matter of designing an IDE board for early PCs with an intelligent controller to make peace between the two sides. You won't get all the speed advantages of SATA because an intelligent controller will have to buffer and spoon-feed the early PC. Note you likely won't be able to access the complete modern SATA drive's capacity, but you could expand the amount used with a logical drive mapping such as C:,D:... Z:. While we might not be able to use that much data storage, its offensive not to be able to access everything you've bought. Solution, SATA logical banking to reuse some of the C:-Z: drive names.
CP/M HDD ANSWER:
HDD for non-PC systems: An interface to SATA drives can be designed for the CP/M era but you won't be able to access Terabytes of storage through a 64K page; it might take you a week to key in all the multiples of remapped drive names. You won't get all the speed advantages of SATA because an intelligent controller will have to buffer and spoon-feed the CP/M system.
My thinking is to make such a SATA drive a shared external so that can improve the use of the drive by allowing your other non-PC systems access it via an external shared comm link like cheaper RS-422/485; not RS422 direct... hiddon on the other side of the fake-floppy drive (concept similar to a storage drive on ethernet). The advantage here is if you have three systems, you don't have to buy 3 SATA drives (no one is that dedicated to CP/M). As these CP/M systems are all so unique, my solution is to go for the common high-speed interface, the floppy cable. A floppy emulator (I prefer the less pretentious term "Fake Floppy" drive) is really the ideal way to tap into non PC, CP/M era computers. But forget that floppy counter interface (that's poorly thought out). Technically you can hang anything on the other side of a fake-floppy (including universal Floppy reading drives). SCSI interfacers won't like that but the floppy interface serves the greater community... maybe SCSI and more unique solutions could be a later variant.
CP/M FLOPPY ANSWER:
This typically requires something (1) to read old floppies, recovering everything possible (instead of PASS/FAIL), (2) to store images on modern computers for storage on HDD/DVD/CD/USB/CF, (3) to recreate a new floppy in any format to use or store, (4) to read useful transportable media like CF/USB.Mem/uSD/ as if it were your boot floppy, (5) maintain a RomDrive on your floppy cable to access you entire collection of floppy disks (why wear-out your floppies). Note that a cost effective NAND Flash rom, 1GBYTE (bytewide) single chip is ~$6 in production but it takes an intelligent controller to better access it, hence a fake floppy solution.
Thats more easy than it sounds: That means you can store all the information from your old floppies in one small solid state card.
To read floppies universally, I hear there are several groups addressing this various ways. I decided to do my own as a fake floppy that emulates a floppy drive upstream to the system, but has its own downstream floppy controller interface (using no FDC chip). Initially that lets you read and clone all the magnetic data from the floppy and store or copy it. It can also be used to reverse the process to make a new perfect clone of the floppy from storage. Note that this technique doesn't need to know anything about the format or organization of data/sectors/skew/interleave/density etc. Technically this would be able to clone any drive, even if its not FM/MFM (Apple and Commodore used some data packing formats on floppies that this could clone to an new floppy without knowing the format involved, conceptionally even variable track speeds could be copied).
I don't yet know about hard-sector cloning, that technically is more complex to this sort of design but as hard sectored is a small family, it should just be a software module that responds to the characteristic number of index pulses (index+sector) and runs accordingly. As hard sector is a small piece of the pie, I'll look at it last.
An interesting thing I'm looking at in the early stage is a fake floppy design that allows you to read any physical floppy in a different side/density/sector format behind the fake-floppy and have the fake floppy reformat that data into the floppy format that the system (CP/M computer) reads; i.e. you don't have to change you CP/M floppy definitions. If all you read and write is 40 track SSSD floppies, the fake floppy will read a 8in DSDD downstream and LIE to your CP/M and give you files in SSSD or whatever you use. But as floppies are a dying media, this is more WAY COOL than useful.