14th February 2017, 8:41
Thanks AJ. I realise the following is probably philosophically rhetorical, but here goes anyway...
If my Tower had not booted, or if something glaringly bad had immediately occurred following the boot & login, or then my launching of my regular programs, i suppose it would have been reasonable of me to speculate a higher than average probability of the root cause being the incomplete 4.9.9 installation. Ie, solving those 2 errors would be critical.
Conversely, it's now several hours later & so far Tower is still going great. That fact does not yet prove that my 4.9.9 is "perfect", or even "good enough", but it must lower the probability of my new kernel being "bad". It also certainly does not yet prove that the new kernel has finally fixed those accursed chronic Maui freezes [though i hope it has], coz history shows that several days can elapse between freezes.
However, as more & more time elapses [hours, days, weeks?], with/if Tower remaining "happy", the probability of my 4.9.9 being "bad" must logically get lower & lower. But here's the philosophical [unanswerable] bit... what if Tower stays good for say, 3 weeks or 2 months, but then one day after that it seriously falls over? I mean, there's no way i'd be able to rationally attribute that putative crash to my 4.9.9 after so much [fingers crossed] uneventful time. Between now & then i might have installed new programs, made various system changes, upgraded to Maui 3.7 [ ;-) ] etc, any one or combo of which might be the real culprits.
Given that me / you / nobody could factually answer the timing of the above speculative events, i suppose that means it's not actually possible to know how many more hours/days i should wait, then if still nothing bad had happened, i would know it's safe to permanently forget about any need to fix those initial 4.9.9 make errors.
Alternatively, a counter-view might be i should proceed immediately now to try to fix my 4.9.9, which would then unequivocally rule out my new kernel as root cause in ANY future crash, regardless of how far into the future, & despite the fact that at time of writing now everything seems excellent...?
BTW the answer to the question you're probably asking yourself as you read this crap ["why the hell did she waste all her time writing that, rather than just grasping the nettle & fixing the kernel?"] is that whilst following the procedure in that link you supplied is doubtless trivial & easy for experts like you, it is complicated & confusing to people like me. Ie, i'll try to do it if i really really really have to, but if i can avoid it without my Tower suffering, then i will.
If my Tower had not booted, or if something glaringly bad had immediately occurred following the boot & login, or then my launching of my regular programs, i suppose it would have been reasonable of me to speculate a higher than average probability of the root cause being the incomplete 4.9.9 installation. Ie, solving those 2 errors would be critical.
Conversely, it's now several hours later & so far Tower is still going great. That fact does not yet prove that my 4.9.9 is "perfect", or even "good enough", but it must lower the probability of my new kernel being "bad". It also certainly does not yet prove that the new kernel has finally fixed those accursed chronic Maui freezes [though i hope it has], coz history shows that several days can elapse between freezes.
However, as more & more time elapses [hours, days, weeks?], with/if Tower remaining "happy", the probability of my 4.9.9 being "bad" must logically get lower & lower. But here's the philosophical [unanswerable] bit... what if Tower stays good for say, 3 weeks or 2 months, but then one day after that it seriously falls over? I mean, there's no way i'd be able to rationally attribute that putative crash to my 4.9.9 after so much [fingers crossed] uneventful time. Between now & then i might have installed new programs, made various system changes, upgraded to Maui 3.7 [ ;-) ] etc, any one or combo of which might be the real culprits.
Given that me / you / nobody could factually answer the timing of the above speculative events, i suppose that means it's not actually possible to know how many more hours/days i should wait, then if still nothing bad had happened, i would know it's safe to permanently forget about any need to fix those initial 4.9.9 make errors.
Alternatively, a counter-view might be i should proceed immediately now to try to fix my 4.9.9, which would then unequivocally rule out my new kernel as root cause in ANY future crash, regardless of how far into the future, & despite the fact that at time of writing now everything seems excellent...?
BTW the answer to the question you're probably asking yourself as you read this crap ["why the hell did she waste all her time writing that, rather than just grasping the nettle & fixing the kernel?"] is that whilst following the procedure in that link you supplied is doubtless trivial & easy for experts like you, it is complicated & confusing to people like me. Ie, i'll try to do it if i really really really have to, but if i can avoid it without my Tower suffering, then i will.