All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stas Sergeev <stssppnn@yahoo.com>
To: linux-msdos@vger.kernel.org
Subject: Re: 1.1.3.7 issues
Date: Tue, 05 Nov 2002 23:57:54 +0300	[thread overview]
Message-ID: <3DC830D2.50601@yahoo.com> (raw)

Hello.

J.P. Morris wrote:
> device=c:\dosemu\emufs.sys /mnt/c
> ..this worked in 1.1.3 and with 1.0.2.  I can't easily regress because 
> I now have a video card that doesn't like DOSEMU in console mode (hence my 
> interest in the new releases).
Please be more specific. Do you have
a video card that doesn't like the
old dosemu's, but OK with the new ones?
Some Radeon?
If yes, then the fix can be easily
backported, so that you can do a
regress.
Or do you have a video card that doesn't
work with dosemu in console no matter
what the version is?

> The second, less important issue is the mouse.. it has inertia.  I 
> think this happened in one of the earlier 1.1.3.x builds, too.
In console, or under X? If in console,
then it is because now mouse uses a
large event queue, the events from which
gets thrown to PIC one-after-another. This
works rather slow, but it is DPMI-safe.
Before, the events were passed to the
driver immediately (no queue, no PIC),
but that caused crashes.
If it is under X, then it is a bug as
the queue is not used (though the PIC is).

> cursor will continue to circle for about three more seconds!
That's too much even for the queue.
Maybe setting $_hogthreshold to 0 can
help?

> Has anyone else seen this effect?
Not really, even though in theory it
is now possible (under console).


             reply	other threads:[~2002-11-05 20:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-05 20:57 Stas Sergeev [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-05 19:46 1.1.3.7 issues J.P. Morris
2002-11-05 19:47 ` Bart Oldeman
2002-11-05 22:22   ` J.P. Morris
     [not found]     ` <Pine.LNX.4.33.0211051724160.1716-100000@enm-bo-lt.localdomain>
2002-11-05 22:51       ` J.P. Morris

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=3DC830D2.50601@yahoo.com \
    --to=stssppnn@yahoo.com \
    --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.