Reply to thread

Message

<blockquote data-quote="MacDulles" data-source="post: 1611467" data-attributes="member: 334921">OK, Have the prerequisite headache from reading all this , for a layman, poorly written description. It's like the code-elites don't want mere uninitiated layman to be able to read their holy script, like lawyers and the law . Sought out the possibility of a video tutorial on YouTube as I've been pleasantly surprised in the past, but *not* this time, just more daisy-chains of links to more code-centric gobblty-gook that fails to correspond to my iMac-generated open window of my iMac's record of its *KP* event . However I have found an awful lot of other such *Kernal Panic* threads online, some on recently purchased Mac hardware. &nbsp;I just need an actual human being to 'splain it as print just won't cut it. Print is hopelessly static and not dynamic which is the problem with text and why I prefer tutorials videos. At least they portray *behaviors* as we all experience them in real life , *in motion*. As I said there's just no direct &amp; clear explanation of which line of code is the most informative. It's all buried in explanation of code that does not correspond to the code report&nbsp; I've got right in front of me which I experience as infinitely frustrating.</blockquote>

[QUOTE="MacDulles, post: 1611467, member: 334921"] OK, Have the prerequisite headache from reading all this , for a layman, poorly written description. It's like the code-elites don't want mere uninitiated layman to be able to read their holy script, like lawyers and the law . Sought out the possibility of a video tutorial on YouTube as I've been pleasantly surprised in the past, but *not* this time, just more daisy-chains of links to more code-centric gobblty-gook that fails to correspond to my iMac-generated open window of my iMac's record of its *KP* event . However I have found an awful lot of other such *Kernal Panic* threads online, some on recently purchased Mac hardware. I just need an actual human being to 'splain it as print just won't cut it. Print is hopelessly static and not dynamic which is the problem with text and why I prefer tutorials videos. At least they portray *behaviors* as we all experience them in real life , *in motion*. As I said there's just no direct & clear explanation of which line of code is the most informative. It's all buried in explanation of code that does not correspond to the code report I've got right in front of me which I experience as infinitely frustrating. [/QUOTE]

Verification

Name this item. 🍎