z2TzI+CgKdvcNyksQ/z3LYrHVnOUhahXO1C8OibxBJcqzxbHg==   
   LTwju6NNP3rnN769SPh1CK5ssFA4QAvY2SXtq3Eil/s1LP2/88gOFw0+QIgPyVRg   
   UVuj+hNDi1rQpTJ36liFylpo6rpwyzvMNQ4ZK8oCK2GqBMIb"; mail-complain   
   s-to="abuse@albasani.net"   
   From: "Ruediger Ihle"    
      
   On Tue, 12 Jul 2011 04:29:19 UTC, Steve Wendt  wrote:   
      
   > As I understand it, if Mozilla is using TIMER0.SYS, other apps can't.   
   > I don't know all the details, but I don't think this is a Mozilla    
   > problem: http://www.os2site.com/sw/drivers/sound/misc/hrtx-v1.0r03.txt   
      
   Actually Mozilla isn't using TIMER0.SYS, but the DosTmrXXX APIs. The   
   problem is, that these APIs cease to work when an(other) application   
   in the system uses TIMER0.SYS in it's standard version. AFAIK, this   
   behavour is not documented anywhere.   
      
      
   > I'm also not certain what it actually uses the timer for, but I    
   > suspect any issues with it are exacerbated with SMP.   
      
   ISTR, that a long time ago a developer wanted a better timer accuracy   
   in order to perform benchmarking. He added the DosTmrXXX code (which is   
   similar to the Windows implementation) without knowing/caring about the   
   TIMER0 side effect. In result of my complaint, Mike Kaply introduced   
   the environment variable. At that time it was thought that it would be   
   a good idea to use the newer implentation by default. However, over the    
   years it turned out that it would have been better to do the opposite.   
      
      
      
      
   --    
   Ruediger "Rudi" Ihle [S&T Systemtechnik GmbH, Germany]   
   http://www.s-t.de   
      
      
   --- Internet Rex 2.31   
    * Origin: S&T (1:261/20.999)