Problems with multi-segment OMF

[fadden]

This is all w.r.t Merlin 32 v1.0. Version 1.1.1 fails with an error on the first blank line. v1.1.9 from lroathe's fork seems to have similar behavior to v1.0.

(1) According to the documentation, when creating a multi-segment OMF file you are allowed to specify an ORG value in the link file. In practice this is rejected by v1.0. This should be setting the ORG field in the OMF segment header.

(2) The DS directive sounds like it should be setting the RESSPC field in the header, but doesn't appear to be.

(3) It's a little strange to require ProDOS filename syntax for the DSK directive.

(4) The docs repeatedly claim the default value for KND is $1100, which would be weird (you rarely want BankRel set). Fortunately the actual default value seems to be $1000 (code + NoSpecial).

(5) The docs for SNA are incorrect. If the directive is omitted, the segment name is left blank. (This is the desired behavior.)

(6) The existence of the LNA directive is somewhat dubious. As noted in the GS/OS reference, "This field is unused in a load segment."

(7) 4-byte ADRL generates a 3-byte relocation record (same as ADR). [ Update: code compiled with Orca/M does the same thing for DC A4'label', so this appears to be the correct/expected behavior. ]

(8) Docs say BSZ sets BANKSIZE, but: "unknown directive BSZ". The BANKSIZE value always seems to be set to $010000, even for data segments.

(9) "ALI Page" sets the ALIGN field to $0001, "ALI Bank" sets it to $0002. Should be 0, $100, or $10000.

Test project: Source.zip