Contribute
Register

A way to Uninstall/Remove the installed kexts previously

Status
Not open for further replies.
Joined
Feb 21, 2012
Messages
6
Motherboard
Toshiba Satellite® P755-S5262
CPU
Mobile QuadCore Intel® Core™ i7-2630QM 2600 MHz Sandy Bridge (26 x 100) Processor
Graphics
Intel® Processor Graphics HD 3000
Mac
  1. iMac
  2. MacBook Pro
Classic Mac
  1. 0
Mobile Phone
  1. iOS
Please adopt a way to Uninstall or Remove kexts installed previously through checkboxes or something like that.
 
Having a register of what was installed and an auto uninstall would be nice.

But to make this simpler, it would be nice if the extensions installed by Multibeast were color labeled by default. That way you could tell what is not original.
 
their used to be a kext installer on here for download its not here anymore ,best one you will ever use does install remove and even disable enable without removing ,not sure if it works in ML anyway here is a link http://www.deanwray.co.uk/site/
 
+1 that would be great both color labels and a uninstaller :) great idea
 
If you want to color your kexts you can do it after you run MultiBeast as the document has the names and locations for every option.
 
+1 that would be great both color labels and a uninstaller :) great idea

+1

And maybe put only necessary kext in system and what can be in Extra...
 
+1

And maybe put only necessary kext in system and what can be in Extra...
Kexts can ONLY be in /System/Library/Extensions.

The use of /Extra/Extensions was originally designed for use in earlier versions of OS X and is no longer supported.
 
Kexts can ONLY be in /System/Library/Extensions.

The use of /Extra/Extensions was originally designed for use in earlier versions of OS X and is no longer supported.

Good to know...

I was using Digital Dreamer script with 10.5 a couple years ago and I didn't follow the scene much until few days ago...

Thanks for the update !
 
"...The use of /Extra/Extensions was originally designed for use in earlier versions of OS X and is no longer supported. ..."

Do you know the reason for this decision? In my limited understanding this was a great concept to make sure kexts are not overwritten by osx updates.
 
Status
Not open for further replies.
Back
Top