You could choose to do something similar with cassette. It's common for tape drives to verify the data that was written. Rewinding is one way, but it's slow. A

You could choose to do something similar with cassette. It's common for tape drives to verify the data that was written. Rewinding is one way, but it's slow. A faster way is with two separate heads: as the tape moves, it passes over a write head first and then a read head. You could maintain a buffer in RAM of data that has been written but not yet verified (as readable without errors). If you can verify it, you discard it from the buffer. If you can't, then you queue it up to be rewritten. This wouldn't even require a special cassette deck. There were plenty of three-head audio cassette decks that allowed you to listen to the read head while making a recording. That made it much easier to set the right recording level. (Basically, there were two common types of cassette deck: two-head and three-head. A two-head cassette deck has an erase head and a dual-purpose read/write head. A three-head deck has erase, read, and write heads. At least, that's the basic idea. Things get more complicated with auto-reverse cassette decks.)