XStudio Recorder has been designed to be as trouble-free as possible and has been thoroughly tested. However, not every usage scenario can be anticipated. This section is intended as a starting point diagnosing and solving problems, but should not be viewed as an all-encompassing source of problem resolution.
XStudio Recorder automatically generates an event log of its activities, which is a good place to start when trying to track down the cause of a problem. See the topic on Using Application Event Logs for additional information.
If the difficulty you’re experiencing is not covered in this document, contact the dealer who provided you with XStudio Recorder first. Alternatively, you can contact dcsTools.com - see the topic on technical support.
Bugs and errors generally fall into one of two categories - a bug, which is the application not doing something as you might have predicted it would, or; an error, which is the failure of the application to run or perform a specific task altogether.
If you find a bug, report it. Every effort is made to ensure XStudio Recorder performs as expected, but there may be circumstances that were not predicted in the development of the software. See the section on Technical Support for information on reporting a bug.
If you encounter an error, you will get an error message indicating a severe failure and XStudio Recorder may terminate. Provisions are made to "catch" such errors and log the error information to a file in the XStudio Recorder application directory. The file name is xsRecorder.elf. Again, report any application errors you encounter. You may be asked to send the appropriate log file for analysis.