Still does not address useless registry entries
Leonardo wroteActually jv16PT could NOT remove the >300 errors, but the message indicated it DID!
I agree, this is indeed a bug. I'll report here when the bug is fixed.
redseujac wroteTried the links in this post?
http://www.macecraft.com/phpBB3/viewtopic.php?f=10&p=24842#p24832
I will try this when I get a little time to work on it.
Different subject: Since the JV program claims it deleted them (in the debug log) but clearly did not isn't this another bug. One bug is the showing that there are errors graphically. Second, the debug log states it deleted the errors when it did not. Ah, and a third error in that the program is not handling the super protected register errors. (Note to developer: If we can delete these manually as outlined in the above URL, should the program not be able to do the same thing to eliminate the errors automagically?)
Thanks!
Eldereth wroteredseujac wroteTried the links in this post?
http://www.macecraft.com/phpBB3/viewtopic.php?f=10&p=24842#p24832
I will try this when I get a little time to work on it.
Different subject: Since the JV program claims it deleted them (in the debug log) but clearly did not isn't this another bug. One bug is the showing that there are errors graphically. Second, the debug log states it deleted the errors when it did not. Ah, and a third error in that the program is not handling the super protected register errors. (Note to developer: If we can delete these manually as outlined in the above URL, should the program not be able to do the same thing to eliminate the errors automagically?)
Thanks!
See one topic up in this forum-thread, for the reaction of the developer on the misleading completion message after your unsuccesssfull removal of the >300 protected Registry items. This is now recognized as a bug and will be fixed!
Eldereth wroteDifferent subject: Since the JV program claims it deleted them (in the debug log) but clearly did not isn't this another bug. One bug is the showing that there are errors graphically. Second, the debug log states it deleted the errors when it did not.
I have now fixed this. Starting with the next version, both Registry Cleaner and the Clean and fix my computer will report to the user any registry data they fail to modify.
Eldereth wroteAh, and a third error in that the program is not handling the super protected register errors. (Note to developer: If we can delete these manually as outlined in the above URL, should the program not be able to do the same thing to eliminate the errors automagically?)
It could be a good thing to do, I'll try to implement this in the future.