As far as I know mice are polled and not interrupt driven on Intel
boxes.  Its always been a performance turkey for the boxes.  When mice
first became popular many Intel boxes only had 8 hardware interrupts,
XTs.  ATs 286 got an additional 8 but one of the first 8 had to be
used to chain to the second set. Thus 15 hardware interrupts on Intel
boxes.

Have you tried another USB mouse that works on the system to compare
what its giving back to you compared to what you're getting from the
problem mouse?  Or try a different box from a diff manufacturer that
has the USB support.  This is the core of finding hardware problems.
Swap shit til you find the component that's causing the problem.
Compare the behavior of the problem piece with one that works when
trying to debug code.  I hate to think a bad intermittent wire in the
mouse cord has been causing you all this grief!

Whatever the platform whenever I write in C, there's always a point
when I think the hardware is flaky.  Its just the nature of C
compilers when they get bad code.  This is why I do my best to get
solid hardware and a half assed OS to develop apps, even if they're a
little behind the latest and greatest.  That way you can be reasonably
certain its not the hardware and focus on the code.  And yeah some
hardware is never totally compatible.  You just have to give up on
that piece of crap or find a work around or write a patch.

I suspect the mouse was "tweaked" for performance on USB in a way that
is not totally legacy compatible.  FreeDos developers may be facing a
lot of that. Wankers who decide "Hell, nobody's ever gonna want that
again.  Lets skip it to save time/money and take advantage of new
hardware features to "beat the competition!"

CB

On 4/19/14, Jim Michaels <jmich...@yahoo.com> wrote:
>
>
>  I seem to remember being told that with the interrupt chip on x86, one of
> those interrupts or the mask was flaky/trigger happy.
>
>
>
>>________________________________
>> From: Christoph Nuscheler <christoph.nusche...@t-online.de>
>>To: freedos-devel@lists.sourceforge.net
>>Sent: Tuesday, March 25, 2014 2:59 AM
>>Subject: [Freedos-devel] Weird behaviour of "legacy USB" trackball
>>
>>
>>Hello,
>>
>>I'm writing straight away to the development list, because I think I'll
>>have to do some coding to fix my problem:
>>
>>My system is a Pentium MMX PC/104 board. Its BIOS does a pretty good job
>>in providing PS/2 access to USB keyboards and mice in DOS. For example,
>>a wireless KeySonic ACK-540RF keyboard/touchpad combo works absolutely
>>flawlessly using CuteMouse.
>>
>>However, connecting the Ortek PKB-1760 wireless keyboard/trackball combo
>>to the system causes problems: CuteMouse recognizes the PS/2 mouse
>>without issues, but the behaviour is totally off:
>>Horizontal motion (X) of the trackball moves the cursor vertically (Y).
>>Vertical motion (Y) of the trackball does nothing.
>>Clicking the buttons stepwise moves the cursor to the right (+X).
>>The touch scroll bar does nothing. (It doesn't need to, anyway.)
>>
>>Note: I tried several if not all of the command line switches. Also I
>>ran the original Microsoft and Logitech mouse drivers which produced the
>>same result.
>>
>>So I suspect, instead of the normal PS/2 protocol sequence:
>>
>>           1st byte          2nd byte         3rd byte
>>      +---------------+ +---------------+ +---------------+
>>      |?|?|Y|X|1|M|R|L| |X|X|X|X|X|X|X|X| |Y|Y|Y|Y|Y|Y|Y|Y|
>>      +---------------+ +---------------+ +---------------+
>>
>>the trackball produces something non-standard like this:
>>
>>           1st byte          2nd byte          3rd byte         4th byte
>>+---------------+ +---------------+ +---------------+ +---------------+
>>|?|?|?|?|?|?|?|?| |?|?|Y|X|1|M|R|L| |X|X|X|X|X|X|X|X| |Y|Y|Y|Y|Y|Y|Y|Y|
>>+---------------++---------------+ +---------------+ +---------------+
>>
>>
>>What I want to try out: Modify the CuteMouse source code so it discards
>>the first byte, and reads a fourth byte from PS/2.
>>
>>I already got my JWasm set up to build CuteMouse. I claim to know my way
>>around X86 assembly, but reading and comprehending someone other's code
>>is a different story. ;-)
>>
>>I would be grateful for any hints in modifying the PS/2 routines in
>>CuteMouse.
>>
>>Thanks,
>>
>>Christoph
>>
>>
>>------------------------------------------------------------------------------
>>Learn Graph Databases - Download FREE O'Reilly Book
>>"Graph Databases" is the definitive new guide to graph databases and their
>>applications. Written by three acclaimed leaders in the field,
>>this first edition is now available. Download your free book today!
>>http://p.sf.net/sfu/13534_NeoTech
>>_______________________________________________
>>Freedos-devel mailing list
>>Freedos-devel@lists.sourceforge.net
>>https://lists.sourceforge.net/lists/listinfo/freedos-devel
>>
>>
>>

------------------------------------------------------------------------------
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to