Traveller version 6829 contains significant changes in order to prevent the access violation error message that can occasionally appear on some users configurations. To continue to improve the situation we need to pursue and investigate each error, especially if they appear consistently in the same area of Traveller.
If you experience an Access Violation the first steps you should take are :
1) Make a note where the error occurred. What were you doing?
2) Can you make the error happen again by exiting Traveller and following the same procedure, if so write that procedure down.
3) Notify support with what you have found. Take screen shots if possible.
4) Restart Traveller.
Steps 1 to 3 are critical in order to help our developers eliminate these errors, step 4 is possibly the most important step for the user to carry out. You should not continue to work in a session that has experienced an access violation, more often than not Traveller will be extremely unstable after this error and further errors such as locked clients are likely to occur. It is thought that the main reason for continual, repeating access violations is working in a system that has had one already.
Any user that has a system which sees this error frequently despite adhering to the above should contact support who will take a comprehensive look at the configuration on site and endeavor to resolve the problem.
~ Version Contents ~ Select Version ~ Main Contents ~
