| CIT has confirmed this to be a problem in
Citect for Windows versions 5.00. This problem has been fixed in
version 5.01.
This is not normally a problem as by default Citect always
compiles your project with debug information and by default the
automatic starting of the debugger is disabled. You will only
encounter this problem if you disable the debug information by
setting the [General]DebugInfo=0 parameter and enable the automatic
starting of the debugger. The Citect Example project is compiled
using this setting and if you run the Example project directly
after install you may get this problem. By recompling the Example
project the debug information will be added.
To work around this problem when you have compiled your project
with no debug information, disable the debugger from being started
when a hardware error occurs. In the Cicode editor select
Tools|Options and uncheck the 'Break on all hardware errors'
property.
|
