hapbt wrote
can you please just make the fix standalone or post instructions on how to manually fix it? i bet many of us could manually repair the damage in regedit or some such..if i had some idea of where the damage was i would be willing to invest some time trying to fix my own pc and posting my results here.
I can't post instructions on how to manually fix it because I don't know what should be done. Atleast not yet, I had an idea and that was implemented in the private test build I posted a few days ago but it didn't work.
Here are all the facts of this matter:
* The Startup Manager of the initial release of jv16 PowerTools 2008 contained a serious bug in a third-party component (i.e. a component not developed by me or anyone at Macecraft) which caused problems with Vista.
* Simply starting the Startup Manager caused the problems to occur but the problems only occur with Vista.
* This bug has since been fixed and the current latest version does not contain this problem any longer.
* The buggy Startup Manager did not remove or modify any registry keys, entries or values, nor did it not remove or modify any files from the hard disk drive.
* The bug was present in all test versions of the product but not a single person found the bug during in-house alpha stage testing, large scale beta testing by volunteers nor a hired professional software testing company.
* The bug caused the Startup Manager to create empy registry keys to the registry due to incorrect Windows API call OpenKey with the CanCreate parameter incorrectly set to True.
* Since the discovery of the bug, an additional layer of safety has been added to the product making sure nothing like this can ever happen again. The additional layer of safety in practice is a definition of which instances of the registry access component are working in read-only mode (e.g. the creation of Startup Manager's view) or in full access mode (e.g. the Delete button of the Registry Cleaner).
* A list of keys the buggy Startup Manager created under my test run is included in the private test build as file data6.xbin located at the root of PT's installation directory. The file can be viewed with any text editor.
I will be working to find a fix to the problem and I will post more information when I know more. I already have one idea that I need to test.