Skip to contentSkip to conversation

comcom.com

DISCUSSION Jan Willem Stumpel 2 participants 4 messages Jan 3, 2003

lore
Share & tools
lore
#0 lore raw

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

#1 lore raw
Quoted 3 lines · Jan Willem Stumpel

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?

dosemu, preferrably in the SF bug tracker.
it is built into dosemu.bin indeed.

Quoted 6 lines

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.

comcom.com is the DOS stub. It itself hasn't changed, but several bugs in the dosemu.bin part of comcom have been fixed in the mean time (and it shows the title of the DOS prog in the X title bar now). Anyway, if you don't like it then you can always use another command interpreter such as the FreeDOS command.com (FreeCOM) or 4DOS.

Quoted 3 lines

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

yes, this is a known bug.

Quoted 6 lines

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.

this one I haven't observed before. Thanks.

Quoted 10 lines

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

well, first fix bug 1 and then look again :)

Bart

#2 lore raw
Quoted 4 lines · Bart Oldeman

comcom.com is the DOS stub. It itself hasn't changed, but several bugs in the dosemu.bin part of comcom have been fixed in the mean time (and it shows the title of the DOS prog in the X title bar now).

Ah, yes, indeed it does. Nice!

Quoted 3 lines

Anyway, if you don't like it then you can always use another command interpreter such as the FreeDOS command.com (FreeCOM) or 4DOS.

Or, I suppose, MS-DOS's command.com. So comcom.com is just something for passing command line input to the 'real', built-in, command interpreter? Does this mean that when 'alternative' interpreters are used, the 'built-in' command interpreting code is completely bypassed? BTW where would a new user (only having, say, a 1.1.4.0 source package) find his/her comcom.com?

Quoted 5 lines
Quoted 3 lines

3) Problems with a TSR [..]
C:\WS\TEXT>cd\
cd\: insufficient memory

well, first fix bug 1 and then look again :)

OK, I'll have a go.. In the meantime I found another one:

4) Sidekick refuses to load
C:\>\oldc\tsr\sk
Sorry, unknown PCDOS version. Please report to BORLAND.

Regards, Jan

#3 lore raw
Quoted 5 lines · Jan Willem Stumpel

Or, I suppose, MS-DOS's command.com. So comcom.com is just something for passing command line input to the 'real', built-in, command interpreter? Does this mean that when 'alternative' interpreters are used, the 'built-in' command interpreting code is completely bypassed?

yes

Quoted 2 lines

BTW where would a new user (only having, say, a 1.1.4.0 source package) find his/her comcom.com?

for 1.1.4.0, after a "make install" it is, by default, at /usr/local/share/dosemu/freedos/dosemu/comcom.com just like lredir, exitemu and friends.

When you first run dosemu it is symlinked using
~/dosemu/freedos/dosemu/comcom.com ->
/usr/local/share/dosemu/freedos/dosemu/comcom.com

Note that Debian's dosemu package uses a slightly different setup, using a readonly C: drive.

Bart