From: mert0407 AT sable DOT ox DOT ac DOT uk (George Foot) Newsgroups: comp.os.msdos.djgpp Subject: Re: Allegro - Mouse Problems Date: Sun, 17 Aug 1997 19:24:27 GMT Organization: [posted via] Easynet Group PLC Lines: 37 Message-ID: <33f7479c.5111986@news.easynet.co.uk> References: <01bca110$a1ac3ee0$234747c3 AT 486> <33e90e00 DOT 362572 AT netnews DOT hinet DOT net> <01bca373$0e1bca00$1a4747c3 AT 486> <33ea8cf0 DOT 36291792 AT netnews DOT hinet DOT net> NNTP-Posting-Host: foot.easynet.co.uk To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Precedence: bulk On Fri, 08 Aug 1997 03:13:25 GMT, wisher AT ms6 DOT hinet DOT net (Wisher) wrote: ><"Ingo Ruhnke" >: >>> Is your mouse a Logitech one? >> >>Yes, it is a Logitech Mouseman. >>I discoverd now that the mouse is under MS-DOS 7 fast enough, only under >>Win95 it gets too slow. So, I think it's more a Win95 problem, then an >>Allegro. It's not Allegro since other applications suffer too, and yes, it does only seem to occur when running Windows (95). >If you don't need very precise mouse position feedback, (e.g. just >want a normal-speed mouse to use grabber.exe), here is a DIRTY fix: ... >Any suggestion about how to complete the fix? Would it be possible to use the mickey reading instead of the absolute location, and update an internal location inside the code? This way the mouse sensitivity would be more adjustable in general, since mickeys are pretty fine units, and it shouldn't be hard to code, either. I can't try this out since I'm going away, but I thought of a few possible problems: [1] Is it possible to call the mouse interrupt inside another interrupt? My knowledge of the hardware is a little lacking here. [2] Does the mouse driver call the callback function whenever the mouse moves, or just whenever it thinks the cursor should move? In the latter case some timer poll would be required (if [1] allows it), and might end up being too strenuous on the system. -- george DOT foot AT merton DOT oxford DOT ac DOT uk