All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gabor Csuri <csucsu@dunasor.hu>
To: linux-msdos@vger.kernel.org
Subject: Re: dosemu and paradox 4.5
Date: Sun, 05 Feb 2006 10:00:22 +0100	[thread overview]
Message-ID: <1139130022.2590.3.camel@localhost.localdomain> (raw)
In-Reply-To: <43E5A9D3.2090104@aknet.ru>

Hi,

 with -extk xxxx argument works fine! /dosemu-1.3.3/.

thank you guys!

On Sun, 2006-02-05 at 10:31 +0300, Stas Sergeev wrote:
> Hello.
> 
> Enrique Baraibar wrote:
> > Paradox memory problems and not
> > DOSemu's.  Try paradox -extk 8000.
> In this case you may want to increase one of the
> $_xms, $_ems or $_dpmi values in your dosemu.conf,
> if the default ones are not enough for paradox.
> "-extk" suggests that it should be $_xms.
> If you find the value that suits, we may consider changing
> the defaults, so that paradox can work without any extra options
> with the future dosemu releases. Actually, the current defaults
> look very small indeed.
> 
> > Paradox 4.02 has run fine for me on DOSemu 1.2.1.  since it appeared.
> 1.2.1 is too old and is usually problematic to run on the modern
> systems like FC3.
> The performance problems of the newer releases you were mentioning
> elsewhere, can be "cured" by setting $_hogthreshold=(0) in your dosemu.conf.
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2006-02-05  9:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-05  7:31 dosemu and paradox 4.5 Stas Sergeev
2006-02-05  9:00 ` Gabor Csuri [this message]
2006-02-07  2:05 ` Enrique Baraibar
  -- strict thread matches above, loose matches on Subject: below --
2006-02-02  4:59 Stas Sergeev
2006-02-01 17:25 Gabor Csuri
2006-02-04 15:11 ` Enrique Baraibar

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=1139130022.2590.3.camel@localhost.localdomain \
    --to=csucsu@dunasor.hu \
    --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.