It probably means that you should try uninstalling the game and re-installing the game after all the updates. It may have something to do with that, perhaps, and it is worth a try at least.
Okay I will try and be humorus about all of this Critical Security problems other people see!
However, if one had an OS that does not need constant updating and the Government to help solve Critical Security Problems as Microsoft is doing now, then I would try and blame other programmers, but to lumpsum all other programmers into saying that it is them and not the programmers from Microsoft first, is like trying to say that -- why don't everyone run Linux?
And I am reasonably sure that other software vendors distinctly go by what Microsoft does report on doing to make their programs.
So, without checking out the entire reason for a *.dll which is not an Executable program in the first place, then how can one assume that since the *.dll runs by other Executable programs - that first it is not the other program that is making the security issue instead of the *.dll programs!
To me, it all seems a little moot when such Critical Security Problems exist to such a high degee with the OS first, instead of with add-on programs -- that are added-on because of the way the OS is made in the first place.
Just to me though, it is like saying that there was no Big Bang that started off this Universe first, when that is the most developed theory one can come up with!
In other words, I can write a program that calls a number of functions provided by the OS, so therefore, my program would not be wrong and the Security Problem issue, it would be the OS instead, since mainly calling routines in the OS is done by the third-party program.
Yes, Drivers can be an issue, such as with hardware, but these program do not seem to be that sort of problem.
They are made to interface with the existing OS, and call the OS, or else no one would have API programming in the first place. They are not separated from the OS, but are called into action with the OS, and third party programs can not be enacted without a proper OS system.
It is impossible to me to think that way!
I defy anyone to make a program that does not call routines in the OS to make it work in the first place -- it can not be done!
Therefore, my attempt at humor may be wrong, but still, it seems to be common thinking that somehow the OS is separated from all the issues when it clearly can not and never can be separated out -- until one has a different OS to begin with!
It seems to be bantering by the person as to my way of thinking, and that is all I can say about any of it!
With over 700 function calls involving the OS and perhaps even thousands, then it is entirely possible that all the issues with any security rests within the OS of the system, instead of with the other programs!
Okay I will try and be humorus about all of this Critical Security problems other people see!
However, if one had an OS that does not need constant updating and the Government to help solve Critical Security Problems as Microsoft is doing now, then I would try and blame other programmers, but to lumpsum all other programmers into saying that it is them and not the programmers from Microsoft first, is like trying to say that -- why don't everyone run Linux?
And I am reasonably sure that other software vendors distinctly go by what Microsoft does report on doing to make their programs.
So, without checking out the entire reason for a *.dll which is not an Executable program in the first place, then how can one assume that since the *.dll runs by other Executable programs - that first it is not the other program that is making the security issue instead of the *.dll programs!
To me, it all seems a little moot when such Critical Security Problems exist to such a high degee with the OS first, instead of with add-on programs -- that are added-on because of the way the OS is made in the first place.
Just to me though, it is like saying that there was no Big Bang that started off this Universe first, when that is the most developed theory one can come up with!
In other words, I can write a program that calls a number of functions provided by the OS, so therefore, my program would not be wrong and the Security Problem issue, it would be the OS instead, since mainly calling routines in the OS is done by the third-party program.
Yes, Drivers can be an issue, such as with hardware, but these program do not seem to be that sort of problem.
They are made to interface with the existing OS, and call the OS, or else no one would have API programming in the first place. They are not separated from the OS, but are called into action with the OS, and third party programs can not be enacted without a proper OS system.
It is impossible to me to think that way!
I defy anyone to make a program that does not call routines in the OS to make it work in the first place -- it can not be done!
Therefore, my attempt at humor may be wrong, but still, it seems to be common thinking that somehow the OS is separated from all the issues when it clearly can not and never can be separated out -- until one has a different OS to begin with!
It seems to be bantering by the person as to my way of thinking, and that is all I can say about any of it!
With over 700 function calls involving the OS and perhaps even thousands, then it is entirely possible that all the issues with any security rests within the OS of the system, instead of with the other programs!
Comment