A general guide for users to help us make the most of your crash reports:

a) Make sure you are running the latest patch to your software (as the cause of your crash may have already been fixed). We don't tend to read crash reports from old (minor) versions.

b) Try to tell us what you were doing when the program crashed. We are after the technical information. e.g. "Typing into a text frame" is helpful. "Writing a poem" or "Designing a website" is not very informative.

c) Always include your email address. We will ONLY contact you if we need more information to help us.

d) Always send your crash reports even if the crash has occurred before. Some have more information than others.

e) Don't include other contact info, feature requests, other enquiries, ultimatums (ultimata?) or irrelevant information. If we do read the crash report, it may not be for some time after you submitted it, so there is no point saying "please call me immediately else I am giving up on Serif for good" etc. If you need immediate help use the forum or call Technical Support. Remember that Technical Support won't have read your crash report and, if you are contacted by developers, they won't necessarily know about any Tech Support enquiries you have made.

f) You can include threats, swearing and general abuse if you want to. Lots of people do. It gives us a laugh here in the office, but doesn't get your bug fixed any faster. Remember we really DO care about the quality of the software and we work very hard to avoid crashes and other problems. However, no software is perfect and we will fix issues whenever we can.