V2.14 to V2.38

Can you please elaborate on this? We should be documenting ANY deviations from default settings in the release notes and in the manuals. The fact that you are having these kinds of problems indicates that we either do not document these changes or that the documentation is not getting read.

There has been a few "nuisance problems due to this but, the BIG one was when I upgraded to 6? and 7and everything fell apart.
Every program I had, but the most minuscule got data oveflow errors.
I tried several times (I think 3) here in the forum, and contacted Keil support several times (I think 5) to no avail.

Finally in the last attempt at the forum, someone posted that overlaying did not take place if the compression was set to less than 2 and adding "OT (2)" took care of the problem.

I fought this problem for more than 6 months (fortunately the upgrade was not "needed") before someone gave me the solution.

In this line: could you please make it so that intalling a new release does not oblitterate the old, I - for one - like to have the ability to go back when I discover problems in the new. Of course, now that I know this I have means.

Erik

Can you please elaborate on this? We should be documenting ANY deviations from default settings in the release notes and in the manuals. The fact that you are having these kinds of problems indicates that we either do not document these changes or that the documentation is not getting read.

There has been a few "nuisance problems due to this but, the BIG one was when I upgraded to 6? and 7and everything fell apart.
Every program I had, but the most minuscule got data oveflow errors.
I tried several times (I think 3) here in the forum, and contacted Keil support several times (I think 5) to no avail.

Finally in the last attempt at the forum, someone posted that overlaying did not take place if the compression was set to less than 2 and adding "OT (2)" took care of the problem.

I fought this problem for more than 6 months (fortunately the upgrade was not "needed") before someone gave me the solution.

In this line: could you please make it so that intalling a new release does not oblitterate the old, I - for one - like to have the ability to go back when I discover problems in the new. Of course, now that I know this I have means.

Erik

Finally in the last attempt at the forum, someone posted that overlaying did not take place if the compression was set to less than 2 and adding "OT (2)" took care of the problem.

Hmmm. That's strange. I checked our documentation and OT(0) and OT(1) have never overlayed variable memory. So, I'm not sure how you got overlaying to work with any optimizer level less than 2.

In this line: could you please make it so that intalling a new release does not oblitterate the old, I - for one - like to have the ability to go back when I discover problems in the new. Of course, now that I know this I have means.

If you install the software in a different folder, it won't overwrite the previous version. There has never really been a problem with that.

Jon

Hmmm. That's strange. I checked our documentation and OT(0) and OT(1) have never overlayed variable memory. So, I'm not sure how you got overlaying to work with any optimizer level less than 2.

The crux of the matter is that the first release (please do not ask - installed by my predecessor) I used here defaulted to OT "something that overlaid"


Erik