Prosecurity v1.40 BSOD

From the ProSecurity Forum:


1.42 What's new? [Jan. 9, 2008]
-----------------------
1. [FIXED] A bug of log module may cause ruleeditor.exe crash.
2. [FIXED] A bug of driver may cause BSOD on Windows 2000.
3. [FIXED]Other small bugs.
4. [IMPROVED] The ability to detect the state of the warning box to avoid dead-lock.
5. [RULES] The default File/Folder protection rules protect PE files, which are located in the Windows folder, to be modified and deleted.


1.41 What's new? [Dec. 31, 2007]
-----------------------
1. [NEW] Add hints for the source program and target object in the warning box.
2. [FIXED]The PS Session Service can't been installed correctly.
3. [FIXED]The registration dialog shows unreadable characters.
4. [FIXED]A bug of driver may cause BSOD.
5. [FIXED]A bug cause the "clean useless rules while closing learning/installing mode" option invalid.
6. [FIXED]The warning box didn't show on the right position in the multi-display environment.
7. [FIXED]A bug causes the USB-disk can't be pull-up in some cases.
8. [FIXED]A bug of keylogger detection function may cause the number key can't be protected well in some cases.
9. [FIXED]The "More Compitibility" mode of learning/installing mode can't work well for OLE/COM actions.
10.[FIXED]A few bugs of the GUI.
11.[FIXED]Can't uninstall ProSecurity when the trial period is expired.
12.[CHANGED] The rule files are moved to the ProSecurity folder from the windows folder.