updated: 8-Dec-2009

 Copan for Windows

Bugs and Other Problems

Copan is a work in progress and there may still be some problems. Please be patient.

Bugs

A bug in a program is something that doesn't work the way it's supposed to. Some bugs in Copan are known and documented in the relevant user manual page and some are not. If you encounter a bug, please check if it is already documented. If it's not, please note the details and send them to support@underhill.ca. Please note the software version and release date (see § Software Version) in all communications.

Crashes

A crash is when a program shut's down when it's not supposed to. If you encounter a crash, please check if it is already documented or not. If not, please note the circumstances that led to the crash and keep us informed.

You can help by — before starting Copan again — sending us two files:

both being located in the folder Send them to support@underhill.ca.

Assertion Failed!

Occasionally, a Microsoft Visual C++ Runtime Library pop-up appears saying Assertion failed! It means that something that shouldn't have happened just has. Usually, the information provided can be helpful in pinpointing the problem. Please note and send us this potentially useful data:

The Expression that appears may provide a hint as to what's wrong but it's not required.

After noting the file name and line number, try Ignore. Sometimes, after you choose Ignore, Copan carries on as if there were nothing wrong, so it's worth trying. Other times it will crash. Either way, please let us know what you did just before the message appeared, what you tried, etc.

Error Messages

Sometimes you, the user, make mistakes — whether you tried to do something inappropriate for the current situation or you entered some bad data.

There's a large set of error messages and warnings that Copan can give, and we've tried to make them clear and polite. If you have a problem with any message, please let us know. support@underhill.ca

updated: 8-Dec-2009