From: nowhere@never.at   
      
   On 17/11/2023 16:28, Robert Pengelly wrote:   
   >>> ...   
   >>> "I store the X/Y limits to be used as bottom/right mouse limits"   
   >>   
   >>> Yeah that is the plan eventually, I'm just testing things at the moment.   
   Am I right by checking bit 4? If I am then how do I know that it's not byte 2   
   or 3 that has bit 4 set?   
   >> on PS/2 you check bit3 with TEST AL,8   
   >> but b3 would only show up set in byte2&3 when a motion is reported,   
   >> so there is a good chance to see only 1st byte have b3 set.   
   >>   
   >> But it is a crap design anyway, if you move your mouse fast it may jump   
   >> because of false indication of the sync bit.   
      
   > That's what I'm doing. Is there not anything I can do to stop false   
   detections?   
      
   I once checked and the only halfway working solution was to have all   
   IRQ-routines (especially IRQ_0 PIT) as short and fast as possible with   
   all event handlers apart (not within IRQ handlers) in an idle queue.   
   So the mouse packets will rare to never be split to fall out of sync.   
      
   I used this method for all interrupts and it sped up my whole OS by   
   magnitudes.   
   __   
   wolfgang   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)