Early mid September work on lDebug, EDR-DOS, and lDOS instsect

2024-09-15

• Add structure for Extension for lDebug (ELD) trailer header
• Support ELD trailer header in debugger's ELD loader
• Support ELD trailer header in list.eld
• Add eldapend tool to create a file with ELD trailer header pointing at an ELD
• In eldapend require destination file to exist
• In eldapend check that destination file doesn't have an ELD trailer header yet
• Document ELD trailer header in eldexe section of the manual
• List ELD trailer header support in news-r9 section of manual
• Update a different reference in manual for ELD trailer header
• Disable _DX option by default (needed to be able to build lCDebugX with _ELDTRAILER=1)
• Update eld-dx to refer to _DX=0 default (another reference to the dx.eld still has to be updated)
• Add _SREVERSE option to allow disabling support for S command REVERSE keyword
• Use an equate for length of SRO array
• Fix s.eld overflow of SRO array in _PM=0 debugger build
• Optimise SRO array indexing

During the review I noticed that the AXO variable exists, which is supposed to be for the next address of the _DX command. However, it has several problems:

• It isn't conditional on the _DX define
• The dx.eld doesn't install a variable structure for it
• It actually points at the offset for the AAO variable (a_addr), not the intended variable (x_addr). So it never was functional as intended.

Edited to add:

• Fix AXO variable in debugger
• Prepare dx.eld for ELD variable use by moving install code to behind data section
• Add AXO variable as an ELD variable to dx.eld

• Fix issue #111 of the SvarDOS repo, allowing to select C: as the boot drive if it is a partition on hdb and there are none on hda (SvarDOS pick)
• Work on issue #109:
  • Display cs:ip and code hex dump in int 0 handler
  • Fix to display int 0 dump to stderr
  • Display four GPRs in int 0 handler too
  • Likely fix the issue by not calculating CHS values for units accessed with LBA (SvarDOS pick)
• Fix version.mac writing long version if nasm option -t (TASM compatibility) is used, affecting the "Starting" message in init.nas

Add a type heuristic, allowing instsect to inspect the boot sector loader for which load protocol it appears to implement. This as yet only uses far jumps, either those presumably transferring control to the next stage (kernel / initial loader) or those early in the FreeDOS loaders to transfer to the relocated sector loader. The latter happens to be immediately before the loadseg variable which controls where the next stage is loaded and what address it is entered at.

The recognised load protocols so far are:

• lDOS (new), jmp 200h:400h
• lDOS (old), jmp 70h:400h
• MS-DOS v7, jmp 70h:200h
• MS-DOS v6 / IBM-DOS / lDOS (EDR-DOS), jmp 70h:0
• FreeDOS (FreeDOS), jmp 1FE0h:XXXXh followed by dw 0, 60h
• FreeDOS (Enhanced DR-DOS), jmp 1FE0h:XXXXh followed by dw 0, 70h
• FreeDOS (other), jmp 1FE0h:XXXXh followed by dw 0
• lDOS (FreeDOS), jmp 60h:0

(The parameters marked by XXXXh are wildcards in the search patterns.)