here it is!
This screenshot is not very useful since it does not tell an awful lot.
The primary purpose of the crash handler is to allow you avoid a crash and to do a graceful shutdown and to preserve as much data as possible, in defiance of any real occurring crashes.
Nothing sucks as bad as losing your work if you haven't saved for an hour and you encounter a crash.
If you press "Abort", the crash handler will simply return control to the system exception handler (reading what's displayed in the message helps), so after you do that, the application *will* crash.
If you click on "Ignore", the crash handler will increment EP before returning control, this will in most cases cause the program to continue "just normal", but it will of course not write out a RPT.
It is generally still recommended that you save your work and close the application, even if everything seems to be "normal" afterwards, as you really cannot have a clue what internal effects the crash might have had.
and the folder cb-crash-recover is empty.
I have not had a crash in many weeks now, but when I initially wrote this crash handler, it worked reliably. The code that's writing the backup copies has not been changed since then. All that was changed is that the crash handler is now generally enabled in the nightly builds thanks to dynamic linkage (which it was not before).
If the crash recovery folder is empty, then you probably did not have any documents open.
Administrator or not should not matter for writing out the backups, since it writes to your "MyFiles" folder -- unless something is horribly screwed up, you always have access to that location.