Firefox/4.0.2pre SeaMonkey/2.1   
   From: Dave Yeo    
      
   Ruediger Ihle wrote:   
   > 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   
      
   I have HRTX-V1.1R01 here. Not sure where I got it but I note the license    
   says it's only redistributable by the authour.   
      
   >   
   > 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.   
      
   Perhaps we should be recommending everyone to set NSPR_OS2_NO_HIRES_TIMER ?   
   Is the alternative of using DosQuerySysInfo(QSV_MS_COUNT, QSV_MS_COUNT,    
   &msCount, sizeof(msCount)); that much more inaccurate? I note that    
   Windows just uses timeGetTime(), I have no idea of how fine of    
   resolution it has.   
   Dave   
      
   --- Internet Rex 2.31   
    * Origin: Aioe.org NNTP Server (1:261/20.999)