version problem

"I want to compile it with another machine"

Can you compile anything on that machine?
ie, are you sure that the configuration is correct?

If your project builds on one machine but not another, it is almost invariably because you have relied upon something specific about the first machine; eg, include paths, library paths, etc.

Possible, though far less likely, is that you have relied upon some feature specific to v7.02a that has changed in v7.50...
(possibly, an obsolete feature that still just happened to work in v7.02a, but was removed by v7.50)
Check the release notes.

"I got environ 254 errors"

What does that mean?

"What can cause to this problem ?"

See above - it is impossible to say without more details of precisely what errors you are getting.
How about posting the full text of, say, the first six errors?

As any experienced programmer will know, one error early on in a build can very easily cause the compiler to be out-of-step for the whole of the rest of project and, therefore, generate huge numbers of errors.
So, look at the first error first - attend to that, and see what happens...

Since one of the first things in most 'C' files is the #includes, would certainly check your include paths first...

"I want to compile it with another machine"

Can you compile anything on that machine?
ie, are you sure that the configuration is correct?

If your project builds on one machine but not another, it is almost invariably because you have relied upon something specific about the first machine; eg, include paths, library paths, etc.

Possible, though far less likely, is that you have relied upon some feature specific to v7.02a that has changed in v7.50...
(possibly, an obsolete feature that still just happened to work in v7.02a, but was removed by v7.50)
Check the release notes.

"I got environ 254 errors"

What does that mean?

"What can cause to this problem ?"

See above - it is impossible to say without more details of precisely what errors you are getting.
How about posting the full text of, say, the first six errors?

As any experienced programmer will know, one error early on in a build can very easily cause the compiler to be out-of-step for the whole of the rest of project and, therefore, generate huge numbers of errors.
So, look at the first error first - attend to that, and see what happens...

Since one of the first things in most 'C' files is the #includes, would certainly check your include paths first...

I've tried to compile on the same machine just after upgrading my keil software. I've analyzed two map files.

And I saw that at one bank all the same expect a segment changed only one byte, all other same the same.

But at the other code banks some segment size changed remarkable.

You should expect that after changing tool versions!

Changing compiler versions is never a trivial excercise - you need to thoroughly re-test your software to ensure that nothing has broken.