On Wed, Mar 1, 2023, 6:43 AM Brian K. White <b.kenyo...@gmail.com> wrote:
> COM: does not see any filename, it only sees the content bytes. > This is totally unrelated to storing a file in the ram filesystem. > It's the tpdd client that creates an inloaded file in the RAM filesystem, including deciding which section to put it in. The ROM has low level helper code to make gaps, fix up pointers and such but them logic is mostly in the tpdd client you use. Except for the cassette subsystem. It handles inloading based on file type encoded in the file header. But in a way cassette are all binary files since they have a binary header. And they're only ever created by the ROM so it doesn't allow such an accident. It's a closed system. Until/unless someone creates a cassette based PC interface with a bug in it... I suppose someone could craft a evil cassette text file with a BA header and wreak havoc. But they or at least their file would quickly become unpopular. -- John. >
