plainab

I can not speak for the OP in the other thread. As far as my system goes, I had installed the new version over top the earlier version (ASC). The program did an automatic initial scan where I had the opportunity to look at each file set to be removed. I saw nothing that looked like the "missing" file. But at that time I did not know about the issue. In exploring the new features of the new version of ASC, I found Game Booster and gave it a try. It worked just fine. A few days later, I tried to use the Game Booster and was given the aforementioned error (see thread I linked to in earlier post). I came to the forum to see if someone had already reported the issue. I saw that someone did, but there was no information anywhere about a solution. I scanned my computer for the "missing" file and found it right where it should be within the ASC program directory. When I noticed the Sup_GameBooster.exe, I ran it and GameBooster executed correctly. However, when I go back into ASC and try to run GameBooster from there (as it's meant to be) the "missing" file is still missing even though it is present and is properly read in a direct execution of GameBooster. This leads me to believe that somehow during the first initial run of GameBooster the pathway pointing to servicelist_xp.ini gets broken. I tried GameBooster within ASC on my wife's Windows Vista laptop and it functioned properly as it should for several tries. This leads me to believe that the issue is only on versions using Windows XP. For your information, I am using the Free version of ASC. I do not know if the paid version has this issue. For now to get around this issue, I've created a short cut for Sup_GameBooster.exe on my desktop. It works with this method, it just does not work when accessed within ASC on the second and later attempts.

Game Booster Issues See this thread here for details on the problem and a current work around. The issue right now seems to be only with machines operating with Windows XP. Windows Vista has no noticeable errors. Could there be some Windows XP setting that interferes with the proper usage of the program? What information would be necessary to determine what exactly is going wrong and how to properly fix it?