Date: Sun, 21 Apr 1996 11:41:41 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Orlando Andico <orly AT abigail DOT eee DOT upd DOT edu DOT ph>
Cc: calvid AT rpi DOT edu, djgpp AT delorie DOT com
Subject: Re: Allegro Mouse In Win95?
In-Reply-To: <Pine.LNX.3.91.960421003517.5737A-100000@abigail.eee.upd.edu.ph>
Message-Id: <Pine.SUN.3.91.960421113451.14512Z-100000@is>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Sun, 21 Apr 1996, Orlando Andico wrote:

> On 20 Apr 1996, David J. Calvin wrote:
> 
> > the mouse moves incredibly slowly.  It's fine in Dos, or in Windows before my
> > program is loaded, but as long as I'm using my program, the sensitivity is
> > horrible.  This happens with the Allegro "grabber" program as well, so its
> 
> I'm just guessing here, but I noticed that when I run the JED editor 
> (compiled with DJGPP) under Win95, everything else slows to a crawl. This 
> didn't happen under Win3.1, my guess is that the DPMI functionality in 
> Win95 stinks.

As long as we are guessing, here's another guess: it might be that all the
apps that slow Win95 to a crawl just aren't nice DPMI clients in a
multitasking environment.  If a program polls some resource (like the
mouse or the keayboard) and doesn't issue `__dpmi_yield' while waiting, it
might have similar effect on Win95.  (E.g., such problems were reported
with Emacs compiled under DJGPP v2, and fixed by adding a calls to the
above function.) Win3.x has an entirely different task-switching
mechanism, so you might not notice it there. 

I think it's best to double-check our own applications and libraries 
before blaming it on products of others (even if it's Microsoft).