Tweet
Re: Z97 Extreme6 Sata3_3 and Sata3_4 problems
I'm not surprised that nothing was resolved after working with the EaseUS technical support staff. The problem is caused by the way the EaseUS Agent Service code is written. That can't be changed on the fly or apparently even by running the Agent Service program with different options. A decision was made in the design process regarding how the destination drive for an automatic backup would be identified if the drives in a system were changed.
Rather than deal with the many possibilities, methods, and problems needed to resolve that situation, they chose to treat the drive arrangement as static and unchanging. They seem to lock the SATA ports used for the backups from being used in any other way than the original configuration when the automated backup was defined by the user. This method is not perfect even in solving the main problem, and causes the side affects that you experienced.
It's even possible that the programmer(s) were not aware that the commands/instructions they used would cause what you discovered.
I worked as a programmer for many years, you would be surprised how complex and difficult seemingly simple things are to accomplish when they are translated into a program. Most of the programming effort is not applied to the basic goal itself, but on dealing with exceptional situations and error conditions. Reducing or removing the amount of "what if..." scenarios from a program's design makes it so much easier to accomplish.
I'm not surprised that nothing was resolved after working with the EaseUS technical support staff. The problem is caused by the way the EaseUS Agent Service code is written. That can't be changed on the fly or apparently even by running the Agent Service program with different options. A decision was made in the design process regarding how the destination drive for an automatic backup would be identified if the drives in a system were changed.
Rather than deal with the many possibilities, methods, and problems needed to resolve that situation, they chose to treat the drive arrangement as static and unchanging. They seem to lock the SATA ports used for the backups from being used in any other way than the original configuration when the automated backup was defined by the user. This method is not perfect even in solving the main problem, and causes the side affects that you experienced.
It's even possible that the programmer(s) were not aware that the commands/instructions they used would cause what you discovered.
I worked as a programmer for many years, you would be surprised how complex and difficult seemingly simple things are to accomplish when they are translated into a program. Most of the programming effort is not applied to the basic goal itself, but on dealing with exceptional situations and error conditions. Reducing or removing the amount of "what if..." scenarios from a program's design makes it so much easier to accomplish.
Comment