All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Komar <rkomar@telus.net>
To: linux-msdos@vger.kernel.org
Subject: Re: 1.1.5.1-5 regressions and other bugs
Date: Thu, 17 Jul 2003 12:13:20 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.53.0307171200540.1747@robpc2.home.org> (raw)
In-Reply-To: <3F16E3AF.6080508@aknet.ru>

On Thu, 17 Jul 2003, Stas Sergeev wrote:

> ... If you are unhappy with
> a performance setting the $_hogthreshold=(0),
> set it to another value, like 10, 50 etc.

I've tried playing Duke3D under dosemu with a
non-zero hogthreshold setting and always had
problems in the past.  I prefer playing with
the keyboard only, and sooner or later the
the framerate would suddenly drop drastically
(~ 1 frame per second) until I moved the mouse.
Then all would go back to normal for a while.
The times between the slowdowns would get longer
as I increased the hogthreshold, but would never
go away entirely.  Is this expected or a bug?

Speaking of Duke3D, I find that games that were
saved with older versions of dosemu (even 1.1.4)
usually start when running under newer versions,
but are very unstable.  Playing from a fresh start
works fine.  Again, is this expected or a bug?

Cheers,
Rob Komar

  parent reply	other threads:[~2003-07-17 19:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-17 17:58 1.1.5.1-5 regressions and other bugs Stas Sergeev
2003-07-17 19:07 ` Vedran Rodic
2003-07-17 19:13 ` Robert Komar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-19 22:05 Stas Sergeev
2003-07-18 16:25 Stas Sergeev
2003-07-19 20:04 ` Robert Komar
2003-07-18 16:09 Stas Sergeev
     [not found] ` <20030719101122.GA29021@quark.fsb.hr>
2003-07-19 10:12   ` Vedran Rodic
2003-07-17 15:52 Stas Sergeev
2003-07-17 16:48 ` Vedran Rodic
2003-07-16 19:45 Vedran Rodic
2003-07-17 20:10 ` Bart Oldeman

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=Pine.LNX.4.53.0307171200540.1747@robpc2.home.org \
    --to=rkomar@telus.net \
    --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.