From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Willem Stumpel Subject: Re: comcom.com Date: Fri, 03 Jan 2003 20:18:13 +0100 Sender: linux-msdos-owner@vger.kernel.org Message-ID: <3E15E1F5.9040308@my.home> References: Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: List-Id: Content-Type: text/plain; charset="us-ascii" To: Bart Oldeman Cc: linux-msdos@vger.kernel.org Bart Oldeman wrote: > 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! > 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? >> 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