Quote
Hello again,
Please uinderstand that we are just users of the software, like you. All members can do is report how the software functions on their systems & try to replicate issues.
That is not a fact for the others, as my case suggests.
As far as I'm aware, no other users have reported issues with the 2817 patch for ADR8. Could you please shed some light on your statement?
If you haven't done so already, contact the CL Technical Support team. They may be able to provide you with the help you need.
PIX
)))
Well, the statement actually is
"the program is working or not, ALWAYS depends on specific system IF the program is poorly tested before release".
It all goes to probability. The normalized probability of the new patch to fail or not = 1.
Then, the fail ratio is: number of cases reporting fail divided by number of cases reporting success.
So far, since the patch was only recently released, we have:
1 report it fails (mine)
3 reports it does not fail
Which makes 4 in total and 1/(3+1) ratio, i.e. 25% of fails.
That means that so far, from the reports available, the patch fail rate is 25%.
A good beta testing is a screening procedure aiming to reduce fail rates below 1%, according to industry producing standards, before a product is published. Otherwise, costs of technical support will overcome the benefits of making a patch.
Thus, so far, from the data available so far, one might say that the quality of beta testing is poor )
When there will be another 27 success reports about the patch, then this rate will drop to 2.5% and still it will not be acceptable generally)
But I cannot see the reports,
thus, so far, and unless I see them,
"Whether the patch is working or not is ALWAYS system specific, and you are playing lottery with this patch".
This is the statement and I consider it is proved )
This message was edited 4 times. Last update was at Jun 18. 2018 08:04