If you see the following message, don’t get alarmed.
“There seems to be an occasional problem with WhizFolders on your system that causes it to exit abnormally. Please contact us at WhizFolders Support with the contents of this message so that we can look into this problem.”
The message appears in rare cases. It means that WhizFolders terminated abnormally at least a few times on your system and has detected this. We care for your documents and have such smart checks in WhizFolders to protect your documents from corruption.
So far, we have seen that this can occur only in rare cases when Microsoft RichEdit 4.1 can not handle some particular RTF formatting and terminates WhizFolders without giving it a chance to display an error message. If you were to paste the same RTF in Wordpad, you will see the same problem.
What you can do about this problem?
Solution 1. Update your RichEdit dll: Normally, WhizFolders uses RichEdit 4.1 by default unless you turned off its use in the Editor page of general options. You can always confirm which RichEdit you are using on the “Status” button of the Help–About screen of WhizFolders. The use of RichEdit 4.1 is recommended for better usage of WhizFolders, especially with tables.
The DLL file for this RichEdit 4.1 exists in Windows\System32 folder by the name msftedit.dll. You can search for this file using Windows Explorer in the above folder and check its version by right-clicking on its Properties. Here are the latest known versions of this file:
- On Windows XP: version 5.41.15.1514
- On Windows Vista: version 5.41.21.2507
If your dll shows an earlier version, you can update it by installing the latest Windows Updates. Or, you can even try installing the latest Internet Explorer.
If your dll shows a later version, please let us know immediately so that we can update this article. Note that the latest Microsoft Office might have a later version of this dll in its folders but WhizFolders only uses the one which is in Windows\System32 folders and which comes with Windows Updates.
If your dll shows the same version Then this problem may or may not be related to RichEdit 4.1. To confirm, please look at Solution 2 below.
Solution 2. Fix the document causing the problem:
Assuming that it is the RichEdit problem mentioned above, you can try to narrow down the problem causing document and then the topic by these steps:
- Close all your WhizFolder documents. This is just to make sure you do not loose any data.
- Go to the main window in WhizFolders, and do the advanced search in all the listed documents for any text. You can do this by menu “Search - Advanced search in All listed documents.”
- If WhizFolders terminates without giving any message during the search, then it seems likely that one of the documents is causing a problem with RichEdit 4.1.
- Now, select fewer documents by Ctrl-Click and do advanced search in “selected documents” only. This is a different menu item from the one shown above.
- Chances are, the search will go through the fewer documents successfully. It doesn’t matter if the text is found or not. Search should finish without terminating WhizFolders. That’s all we are looking for. If it doesn’t, select only one document at a time before repeating the search in the single selected document.
- Once you have found a document that causes WhizFolders to terminate, please open it and click on its topics one by one till it terminates. Once you know which topic causes termination, please contact us and we will tell you how to delete or fix that topic.
If the above test goes through without any problems, then your problem may not be related to RichEdit. In that case, please try to remember and get more clues. Have you ever noticed WhizFolders terminating without giving any message? In case you remember such incident, please send us the details on what operation you were performing at that time. If you don’t remember, please keep a watch from now on, and let us know the details when you encounter a case when WhizFolders goes away without giving a message.
Finally, there is no need to get alarmed by this message unless it occurs too frequently, several times a week. In all probability, the problem will go away once you update to the latest dll as described above.