From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stas Sergeev Subject: Re: 1.1.3.7 issues Date: Tue, 05 Nov 2002 23:57:54 +0300 Sender: linux-msdos-owner@vger.kernel.org Message-ID: <3DC830D2.50601@yahoo.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: linux-msdos@vger.kernel.org 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).