MS-DOS "exit" exits the command.com interpreter, not just the current script #12

New Issue

2018-07-28T22:33:39+01:00

SuzanneSoy commented

2018-07-28 22:33:39 +01:00

(Migrated from github.com)

We should instead let the execution reach the end of the file. This can be done via comments (\r\n::), with lines of at most 8192 bytes (excluding the \r\n), or using GOTO, which apparently in some cases need the target to be at most one block (which could be 512 bytes) away from the GOTO.

I'm not sure whether the \r\n:: can be placed in arbitrary data within the FAT12 portion of the OS, but it's probably not possible without wasting a whole sector. If that's accurate, we should interleave sectors of data for which we know that string can be injected in various places and sectors of data for which that string needs not be present.

We should instead let the execution reach the end of the file. This can be done via comments (`\r\n::`), with lines of at most 8192 bytes (excluding the \r\n), or using `GOTO`, which apparently in some cases need the target to be at most one block (which could be 512 bytes) away from the GOTO. I'm not sure whether the `\r\n::` can be placed in arbitrary data within the FAT12 portion of the OS, but it's probably not possible without wasting a whole sector. If that's accurate, we should interleave sectors of data for which we know that string can be injected in various places and sectors of data for which that string needs not be present.

Sign in to join this conversation.