Mid to late May work
lDOS kernel
Fix to not find a character device on FindFirst with an exact name match and the volume label attribute bit set. (Contains testfind.asm, a test case.) This bug used to be
documented in the interrupt list, except the sense is wrong. The intended (MS-DOS v5) behaviour is to never find devices when searching for labels. The DEVNAME function checks "Attrib" to determine that a label search is in progress, but it was set from "SAttrib" only later. The fix, copied from tracing MS-DOS v5, is to init Attrib from SAttrib before calling DEVNAME.
-
The first changeset apparently patched the not selected part of an
%if 0 construct. This changeset corrects this,
copying the patch to the selected part of the construct.
FIXUPP
tractest/convlist.pl
Support .CODE directive in medium model (prepends module name to _TEXT section name) or with name (uses the name as section name).
Support TASM > in dump (used for REPE/REPNE prefixes) and
sr far relocations (8 hexits + multiple of
[sore])
lDebug / Loader
Yet to be done:
An ELD or ldmem.eld mode to display the position and size of the Low Memory Area, and of NLDR, NDEB, NEXT, NSYM, and EBDA allocations above the top of the Low Memory Area, plus those of a bottom or top positioned NLDR
nreserve.eld support uninstalling an installed NEXT allocation.
The List
ecm 2026-05d: 21.4301 list attribute bit 6 as indicating character device (for FindFirst and FindNext), update 21.4E character device size and v3/v4 label search bug.
ecm 2026-05e: Update the 21.4E label device search bug fix date for lDOS kernel, as the first fix was to the wrong leg of an
%if construct.
Volkov Commander
The source texts of Volkov Commander v4.05 and v4.99.09 have recently been released under the simplified 2-clause BSD license. I've been looking into linking them with WarpLink, and might work on porting them to assemble with NASM instead of TASM.
Unfortunately, I noticed that the v4.99.09 revision does not include a working editor. Some of the sources do relate to the editor, but uncommenting them does not result in a working application. One problem is that TASMX (the assembler running as a 16-bit DPMI application) always runs out of memory trying to assemble the modified sources. Using TASM32 instead is possible, but then the assembling fails in different ways as some symbols aren't resolved.