I'm not sure why you bring up other consequences of the (overall/general) changes they made, since, as you explain, they have nothing to do with CAS specifically, which is the topic of the recent posts here (
"checks to help prevent running the CAS OS on the models sold as non-CAS, spread throughout the OS."). Nobody said there were no other consequences (nor talking about 3.6
only) ?
Yes, the changes did a lot of things, and among those, they do indeed prevent a direct run of CAS-on-nonCAS to work correctly (to quote you:
"don't only prevent CAS on non-CAS"). That's what Lionel meant and said (he just did not talk about the other consequences since that's not the topic), so I really don't see the issue... ?
The other consequences you mention can very well be only done by one check, indeed you're probably way more informed than most/all of us here.
In "3.6+", the + really means any other versions after that, and we know clearly that TI added lots of CAS-related checks in recent OS version(s) (I don't know which one(s) precisely), spread around the OS, since that is precisely what parrotgeek fought against and patched in his code.
This is nothing new, and in general you have even mentioned
"hundreds of protections to patch" yourself, and parrotgeek+someone else needed and made a "patchfinder" tool to generate automatically all the patches, since there are too many to do manually (screenshot for all that sentence,
here)
That's also what Lionel meant, said, and clarified as well later on. I'm pretty sure everyone reading these posts (especially when knowing the context) will have understood that.
Really, I don't see why there's even an issue here about all that. And it doesn't even matter at all. So instead of us wasting time over a specific wording in a post that did not discern version-specific particularities (it wasn't the point), it's more important to focus on the issue at hand already mentioned several times:
the fact that parrotgeek published a launcher that has CAS-enabling patches built-in (something he said twice he would not do (see here and here), so that's just plain lying now, regardless of the excuses he wants to try to hide behind), and even more importantly, having it in the archive on TI-Planet. Actions against this needs to be taken ASAP according to rules that were already established.Apparently, from what was discussed, a potential longer-term solution would be to
only have the patch(es) that allow to get past the grey screen, and not any of the ones enabling the CAS engine to work. Those can be elsewhere, for all I care, and parrotgeek can have all the fun in the world fighting those who could come at him to C&D/remove that. Not on TI-Planet == OK for the staff.
