comcom.com

[Jan Willem Stumpel <jstumpel@planet.nl>]

When I use freedos, the command interpreter (in my system
/usr/lib/dosemu/commands/comcom.com) has several bugs. Should they
  be reported to the freedos people or to the dosemu people? This
program announces itself as

   DOSEMU built-in command.com version  1.0

which suggests it belongs to dosemu.

I have this program still from my original 1.0.2.1 installation.
New versions are not built when I compile newer versions of
dosemu; however, in src/plugin/commands I find a comcom.c, -.d,
and -.o. I'm a bit confused. Is this built into newer versions of
dosemu.bin itself? But if I do not have my old comcom.com (or a
link to it) in the dos boot directory, dosemu complains of a
missing command interpreter.

Anyway the bugs I found are:

1) changing directory:
C:\>cd\ws\text
cd\ws\text: file not found

A space is needed. This is unexpected (MS-DOS command.com does not
need it) and therefore (IMHO) a bug.

2) running a program in a directory above the present one:
C:\>cd \ws\text
C:\WS\TEXT>..\ws
..\ws: file not found

The file extension is needed: the command ..\ws.exe succeeds.

3) Problems with a TSR
C:\WS\TEXT>cd\
cd\: file not found

Same as bug 1): but now I install a TSR and do the same:

C:\WS\TEXT>\oldc\tsr\minimon
MiniMon Version 1.0 installed. Activate with <Ctrl-Alt-M>
C:\WS\TEXT>cd\
cd\: insufficient memory

Not "file not found" this time, but "insufficient memory",
apparently caused by the TSR (even though freedos "mem" shows 619
k free at this point).

Regards, Jan