![]() ![]() You need to use sqlite3 to peruse and manipulate a database in your start up disk's file /var/db/SystemPolic圜onfiguration/KextPolicy And it may be dangerous to your system software if you mess up.Tips to Perfectly Uninstall EasyFind on Mac OS X In my case, software that I used many years ago on a previous iMac was long gone but that database still had a record of two items and they showed up only in that Disabled Software report. They didn't hurt anything, but it was irritating to see them. That database file is read-only unless you boot in Recovery Mode (Command - R), but you want to examine the contents and print the information in a normal session so you have it when you are in Recovery Mode. In my case, the annoying Disabled Software was in the "kext_policy" table. You will see several items (I had 12 of them) that look like:ĦHB5Y2QTA3|com.hp.kext.io.pound|1|HP Inc.|8 Then type the following sqlite3 command (you have to terminate every sqlite3 query that isn't prefixed with a. The columns separated by the | character are (in order) Team_ID, Bundle_ID, Allowed, Developer_Name, Flags This is something from HP printer software that I had installed at some point and is not causing me problems, so I left it (and several other items) there. You may not have a Team_ID on some items. Or, try a different file in that directory? Hopefully, you have lines associated with the software in *your* Disabled Software report. You will be root/administrator, so be careful! When there, in the menus choose Utilities -> Terminal Now, you are ready to boot in Recovery Mode. To delete an item if it has a Team_ID:ĭelete from kext_policy where Team_ID = 'X123456789' sqlite3 /Volumes//var/db/SystemPolic圜onfiguration/KextPolicyĪnd confirm you have the same information as before. If there is no Team_ID, for example, the "wacom" item in your list:ĭelete from kext_policy where Bundle_ID like '%wacom%' Repeat the select command to confirm it's gone. Quit to get out of sqlite3, reboot and your system report disabled software should be clean of those items you deleted from the database. As discussed in another thread, I noted a log entry for a Spotlight crash on the internal drive which I saw only when booted from the external, cloned drive. I did not see that log entry when booted from the internal and found no problems there with Spotlight. I'm in way over my head on this one and need some fairly simple directions, if possible. I solved the problem of the crash log entry, at least for now, by making a new clone, and moving the cloned volume prior to cloning into Spotlight/ Privacy. Localhost mds208: crash data for /.Spotlight-V100 in volume /Volumes/Hard Drive/.Spotlight-V100?!?\n I no longer see the crash log entry when booted from the clone, but the matter of this problematic "file" remains. It was recommended that I delete the /.Spotlight-V100 file on the clone, which is likely corrupted or incompatible with the spotlight index on the internal volume. My original plan was simply to use the "Destroy" function in EasyFind, but I have since learned that the. Spotlight-V100 is a directory, not a file, and, as such, can not be deleted directly. It would require using Terminal commands, which may appear in the following X Lab article on Spotlight. ![]() ![]() But I'm not sure exactly which commands, if any, from that article I would use. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |