home bbs files messages ]

Just a sample of the Echomail archive

Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.

   OS2      Fidonet International OS/2 Conference      3,371 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 632 of 3,371   
   tholen@antispam.ham to All   
   Re: SNAP refresh rate   
   12 Jul 11 23:52:17   
   
   From: tholen@antispam.ham   
      
   "Lars Erdmann"  writes:   
      
   > "Remove the crtc*.dat and mon*.dat configuration files". "They get    
   > regenerated".   
      
   From what?  There must be some internal defaults or some current   
   settings or some monitor querying function to use during the   
   regeneration process, with no guarantees in the first two cases   
   that the values are valid, and in the last case, why hasn't the   
   querying process worked so far?   
      
   > You can now try that or continue bitching about it.   
      
   I'm sorry if it sounds like "bitching".  How would you describe   
   the situation in which you use the System object to change the   
   refresh rate, only to discover the change was undone at the next   
   reboot without it sounding like "bitching"?  And then change the   
   refresh rate using the Advanced option, only to discover the   
   change was undone again at the next reboot?  If I can't make the   
   change stick using the tools provided, an alternative needs to be   
   found.  Direct editing of the refresh rate setting is one way to   
   do it, if the location of that value can be determined.   
      
   There must be some sort of SNAP bug involved.  I discovered, for   
   example, that if I change the refresh rate using the GUI control   
   on the Screen tab of the System object, my monitors will go blank   
   for a second, then the desktop will reappear with SNAP asking   
   whether the new refresh rate should be kept, along with a countdown   
   timer, which was obviously put there as a safety precaution in case   
   the user couldn't see the message due to the change; no response   
   would cause the change to be undone automatically.  Yet I could see   
   the message, suggesting that the monitors support the 65 Hz refresh   
   rate.  But if I go into the Advanced option and use the Global   
   Refresh Rate control, the monitors definitely object to being set   
   to 65 Hz.  Totally inconsistent behavior.   
      
   I've also determined that the mon*.dat files are not where the   
   problem lies.   
      
      
   --- Internet Rex 2.31   
    * Origin: Aioe.org NNTP Server (1:261/20.999)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca