https://www.os2museum.com/wp/unidentified-pc-dos-1-1-boot-sector-junk-identified/
Anyone trying to disassemble the PC DOS 1.1 boot sector soon notices that at offsets 1A3h through 1BEh there is a byte sequence that just does not belong. It appears to be a fragment of code, but it has no purpose in the boot sector and is never executed. So why is the sequence of junk bytes there, and where did it come from?
The immediate answer is "it came from FORMAT.COM". The junk is copied verbatim from FORMAT.COM to the boot sector. But those junk bytes are not part of FORMAT.COM, either. So the question merely shifts to "why are the junk bytes in FORMAT.COM, and where did they come from?"
It is not known if anyone answered the question in the past, but the answer has been found now, almost 40 years later—twice independently.
(Score: 2) by driverless on Sunday January 09 2022, @02:43AM (1 child)
That was a standard programming technique back then, you could bypass branches and/or individual instructions by prepending a byte that made the instruction that followed the operand of some no-op equivalent. Depending on whether you jumped to location n or n+1 you'd get a different effect.
(Score: 4, Informative) by Mojibake Tengu on Sunday January 09 2022, @03:28AM
This technique was common in assembly as imitation of procedures and subprograms with multiple entrypoints in certain high languages.
When naive functionalists defeated sanity, the whole concept of procedures as subprograms (together with multiple entrypoints idea) vanished from this reality.
Respect Authorities. Know your social status. Woke responsibly.