I've just made a fresh 10.6.7 install on my MacBook Pro 2 GHz Intel Core Duo. I loaded it from a 10.6 Install Disk and then did the 10.6.7 combo update.
Unfortunately ShhMBP no longer works, so I now have to put up with the terrible processor whine that ShhMBP was designed (very cleverly) to stop.
After startup and login I know receive the message:
Insecure Startup Item disabled.
"/Library/StartupItems/ShhMBP" has not been started because it does not have the proper security settings.
I tried changing the attributes using BatChmod, to system -r -w -x wheel -r -w -x, and then did the same in Terminal using "sudo chown -R root:wheel /Library/StartupItems/ShhMBP/".
I then tried removing a possible quarantine attribute using "sudo xattr -r -d com.apple.quarantine /Library/StartupItems/ShhMBP". I doubt that was the issue anyway.
I'm a bit puzzled and more than a little ticked off about this. Any help from anyone would be hugely appreciated.
Thanks in advance,
Mark.
P.S: I've followed the advice through the thread at https://forums.macrumors.com/threads/779410/ but to no avail. This appears to me to be a new problem with 10.6.7, yeah?
Unfortunately ShhMBP no longer works, so I now have to put up with the terrible processor whine that ShhMBP was designed (very cleverly) to stop.
After startup and login I know receive the message:
Insecure Startup Item disabled.
"/Library/StartupItems/ShhMBP" has not been started because it does not have the proper security settings.
I tried changing the attributes using BatChmod, to system -r -w -x wheel -r -w -x, and then did the same in Terminal using "sudo chown -R root:wheel /Library/StartupItems/ShhMBP/".
I then tried removing a possible quarantine attribute using "sudo xattr -r -d com.apple.quarantine /Library/StartupItems/ShhMBP". I doubt that was the issue anyway.
I'm a bit puzzled and more than a little ticked off about this. Any help from anyone would be hugely appreciated.
Thanks in advance,
Mark.
P.S: I've followed the advice through the thread at https://forums.macrumors.com/threads/779410/ but to no avail. This appears to me to be a new problem with 10.6.7, yeah?