What is the main goal of Multiprocess ?

OK.

So this processes are Windows processes .... not a process in Citect terminology ... but why we must care about the distribution of processes by the operating system ? When we run any program in Windows we do not care about so much processes ant threads the program will generate .... it is a task for operation system or the program's programmer ...

If  "modern computer hardware becoming more parallel processor capable" why Citect don't run in multiprocess mode by default ?

About local variables - usually   I used to local DIGITAL variables tag1, tag2, tag3 and alarms for it to test my personal alarm page and run Runtime in single process mode, but when we started run Runtime in multiprocess this alarms stopped worked .... Not so fast I knew that it was because of multi process mode ....

About standard variable tags in Memory - we must give unique address (i100, d12 etc). Its requests to be carefully with  pairs tag-address . It is extra work. Plus local variable is unique on each Runtime client (for example one server and two clients) but with memory tags we will have one value for each client. Why Citect does not  automatically make an address for memory tag ?

I have never used redundancy in Citect .... I used redundancy in WinCC only ....

OK.

So this processes are Windows processes .... not a process in Citect terminology ... but why we must care about the distribution of processes by the operating system ? When we run any program in Windows we do not care about so much processes ant threads the program will generate .... it is a task for operation system or the program's programmer ...

If  "modern computer hardware becoming more parallel processor capable" why Citect don't run in multiprocess mode by default ?

About local variables - usually   I used to local DIGITAL variables tag1, tag2, tag3 and alarms for it to test my personal alarm page and run Runtime in single process mode, but when we started run Runtime in multiprocess this alarms stopped worked .... Not so fast I knew that it was because of multi process mode ....

About standard variable tags in Memory - we must give unique address (i100, d12 etc). Its requests to be carefully with  pairs tag-address . It is extra work. Plus local variable is unique on each Runtime client (for example one server and two clients) but with memory tags we will have one value for each client. Why Citect does not  automatically make an address for memory tag ?

I have never used redundancy in Citect .... I used redundancy in WinCC only ....