Hi;
I am also seeing this issue in 2.00.030. The problem did not manifest itself in earlier versions. Even with multiple bug submissions fromyour users, it appears that no one from Defragger has come up with a fix yet. All I see is that they ask the users to submit a bug report, which they all do, but that is the end of the thread. The ball is in Defragger's court now. Please respond to these user submissions with an indication that you understand the bug, or that you need the users to help you with more bug submission.
The alternative is that your users will just use other products, or as in my case, revert to the older product that doesn't crash. I love your company, but as a user, I have my own job to do and unless you ask for help, I cannot babysit your product other than report if there are issues.
Paul
