2 ms·

> you have all the overhead of understanding a filesystem. No need. Read & write cluster/sector or block/page directly; BIOS already does that.

• DougN7 3y ago
  Don’t you need to read a directory structure to know where the file’s sectors are, how many there are, etc, and thus need to understand the file system?
  • masklinn 3y ago
    You’d put the file contents at a static offset, or a location pointed to by the MBR or something.
  • EvanAnderson 3y ago
    You could do something really quick-and-dirty. Write the code into sequential sectors, put a sentinel value in the last sector to indicate the code ends. It wouldn't be at all good for in-place editing but it would be easy to load and parse the code.