public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Willem Stumpel <jstumpel@planet.nl>
To: Bart Oldeman <oldeman@math.ohio-state.edu>
Cc: linux-msdos@vger.kernel.org
Subject: Re: comcom.com
Date: Fri, 03 Jan 2003 20:18:13 +0100	[thread overview]
Message-ID: <3E15E1F5.9040308@my.home> (raw)
In-Reply-To: Pine.LNX.4.33.0301031318300.28653-100000@enm-bo-lt.localdomain

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



  reply	other threads:[~2003-01-03 19:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-03 13:15 comcom.com Jan Willem Stumpel
2003-01-03 18:24 ` comcom.com Bart Oldeman
2003-01-03 19:18   ` Jan Willem Stumpel [this message]
2003-01-03 22:36     ` comcom.com Bart Oldeman
  -- strict thread matches above, loose matches on Subject: below --
2003-01-12 17:15 comcom.com Stas Sergeev
2003-01-15 12:50 ` comcom.com Clarence Dang
2003-01-17 15:56   ` comcom.com Jochen Reinwand
2003-01-12 17:16 comcom.com Clarence Dang
2003-01-12 10:26 ` comcom.com Jan Willem Stumpel
2003-01-15 12:55   ` comcom.com Clarence Dang
2003-01-15  3:04 comcom.com Stas Sergeev
     [not found] <3E2576E0.6050605@yahoo.com>
2003-01-17 14:38 ` comcom.com Clarence Dang
2003-01-17 18:47 comcom.com Stas Sergeev
2003-01-17 23:03 ` comcom.com Jochen Reinwand

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3E15E1F5.9040308@my.home \
    --to=jstumpel@planet.nl \
    --cc=linux-msdos@vger.kernel.org \
    --cc=oldeman@math.ohio-state.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox