All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Grigory Batalov" <grisxa@mail.ru>
To: linux-msdos@vger.kernel.org
Subject: Re: line 496 parse error
Date: Mon, 23 Dec 2002 00:48:52 +0300	[thread overview]
Message-ID: <20021223004852.7bdfef38.grisxa@mail.ru> (raw)
In-Reply-To: <3E06242F.8060100@yahoo.com>

[-- Attachment #1: Type: text/plain, Size: 995 bytes --]

On Sun, 22 Dec 2002 23:44:31 +0300
Stas Sergeev <stssppnn@yahoo.com> wrote:

> > I get strange error while starting dosemu in console:

> What does you dosemu.conf look like?

  ~/.dosemurc applied,
 /etc/dosemu.{conf,users} are absent.

> The tricky part now (when everything
> is intended to be commented out) is
> that when you uncomment some option,
> you have to uncomment also all the
> related options.
> I.e. if you, say, uncomment $_sound,
> you are forced to uncomment also all
> the $_sb_xxx options, otherwise parse
> error.
> This is logical only partially, I think
> this must be changed (non-trivial).

  I tought there is default options that
 can be overwritten with dosemu.conf or
 ~/.dosemurc ?

  Also some diagnostics:
 - When started under Midnight Commander
   (in console), dosemu works!
 - I use FreeDOS kernel 1.1.28.
   Versions are:

C:\>ver /r

FreeCom version 0.83 Beta 54 [Nov 13 2002 22:21:04]
DOS version 5.0
FreeDOS kernel version 1.1.28

-- 
 Grigory Batalov.

[-- Attachment #2: dosemurc.bz2 --]
[-- Type: application/x-bzip2, Size: 4478 bytes --]

  reply	other threads:[~2002-12-22 21:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-22 20:44 line 496 parse error Stas Sergeev
2002-12-22 21:48 ` Grigory Batalov [this message]
2002-12-27 16:15   ` Bart Oldeman
2002-12-30  8:12     ` Reinhard Karcher
2002-12-30 17:14       ` Bart Oldeman
  -- strict thread matches above, loose matches on Subject: below --
2002-12-22 20:11 Grigory Batalov

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=20021223004852.7bdfef38.grisxa@mail.ru \
    --to=grisxa@mail.ru \
    --cc=linux-msdos@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.