One issue I've had reported was that the configuration was being reset. Thanks to a user report I finally was able to determine what was going on. It ONLY affected people running Windows XP *and* who had Terminal Services (TermService) disabled. The default setting for this service is Manual, and that is certainly what I recommend. Contrary to popular belief, disabling services really doesn't gain you much performance or save many resources. What it does do is muck with the operation of the system and applications. Now, this bug wasn't actually due to Terminal Services, rather a logic error in the GUI caused the configuration file to be reset when this condition was found. Basically the GUI was changing a setting to deal with the lack of Terminal Services availability, then saving the configuration file before it was ever loaded to start with. This bug likely crept in during the last beta as some of the initialization code was re-arranged.
This has been FIXED internally and is pending release in v5.0.0.28, a build that has an assortment of minor fixes and improvements. Even the graph has changed in appearance, for the better I do believe. This new build is being prepared now.
Sunday, 12 June 2011
Windows XP w/o Terminal Services config file reset bug
Posted on 15:15 by Unknown
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment