| Hello.
If I read this right, then it means it just skips using the hardware caches, then, but that the possibly corrupted hardware caches still floats around until the next regular reboot.
Then I’d rather use Onyx, for removing those hardware caches once and for all, and then perform a reboot afterwards, as an extra step after the safe reboot. Then the system should be in “ship shape”.
The Onyx step, once made a corrupted Spotlight work again for me. The cache corruption occured at the same time I had *lots* of dyld errors in the console.log. (On SnowLeopard).
Cheers and a Happy Easter
Tommy/McUsr Le 03/04/2015 à 17:43, Paul Berkowitz < email@hidden> a écrit :
On 3/23/15, 8:11 AM, "Luther Fuller" < email@hidden> wrote: Try rebooting, that often cures strange Applescript errors.
Better yet, also
do a Safe Boot (use the shift key) followed by a normal restart.
This seems to clean the cobwebs from your system.
Just out of interest, what is the main purpose of a Safe Boot, do you know? And why does it need to be followed by a regular boot - does it leave things in an irregular situation, or is this just for good luck? -- Paul Berkowitz
Hello
(1) A Safe Boot apply a sort of Spring Cleaning removing some caches . (2) It load only a short set of extensions so, the running system include only some ones delivered by Apple. This is why we must re-boot to get the complete system at work.
Other actions : - Safe Boot forces a directory check of the hard drive. This is
identical to using Disk Utility's Repair Disk or the fsck -fy terminal
command.
- The cache of kernel extensions used to speed startup is ignored. (The cache file is /System/Library/Extensions.kextcache )
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden
|