Disabling CD/DVD-ROM

Remove IODVDStorageFamily.kext and IOCDStorageFamily.kext bundle from System>Library>Extensions

I suggest moving them somewhere else, just in case you need it later. You can write an Apple Script to do it fast. Don't forget to restart

Gabor

Open terminal and type the following commands in order.

sudo kextunload IOSCSIArchitectureModelFamily.kext/Contents/PlugIns/IOSCSIMultimediaCommandsDev ice.kext

sudo kextunload IOBDStorageFamily.kext

sudo kextunload IODVDStorageFamily.kext

sudo kextunload IOCDStorageFamily.kext

I´ve got the problem, that some instances are still running while I´m trying to unload.

Terminal in-output:

MYMAC:~ Administrator$ sudo kextunload /System/Library/Extensions/IOSCSIArchitectureModelFamily.kext/Contents/PlugIns/ IOSCSIMultimediaCommandsDevice.kext

(kernel) Can't unload kext com.apple.iokit.IOSCSIMultimediaCommandsDevice; classes have instances:

(kernel) Kext com.apple.iokit.IOSCSIMultimediaCommandsDevice class SCSIMultimediaCommands has 1 instance.

(kernel) Kext com.apple.iokit.IOSCSIMultimediaCommandsDevice class IOSCSIMultimediaCommandsDevice has 1 instance.

(kernel) Kext com.apple.iokit.IOSCSIMultimediaCommandsDevice class IOSCSIPeripheralDeviceType05 has 1 instance.

(kernel) Kext com.apple.iokit.IOSCSIMultimediaCommandsDevice class IODVDServices has 1 instance.

Failed to unload com.apple.iokit.IOSCSIMultimediaCommandsDevice - (libkern/kext) kext is in use or retained (cannot unload).

Can anyone help me how to terminate the running instances?

Next question:

After reboot I can do some kextunload. But The Devices are still working for CD,DVD. Why?

reboot after kextunload doesn't work.

I assume you could always just move them out of Extensions and reboot instead of doing the kextunload.

This manner is known. But I'm searching for a manner to restrict using CD,DVD,USB, SD-Memory with simble handling.

So I thought of an script running in background to disable the kexts.

When I move the kexts out of /System/Library/Extensions the usage is restricted, right. But when I want to enable usage I get message, that the *.kext is not properly installed.

Any ideas?

Not sure. I assume that with the "move technique" (out, in) the procedure would have to be symmetric, i.e., disable was move out and reboot, enable would be move in and reboot. The confusion (problems) may be arising from an inconsistency with the kext cache. That cache is rebuilt at boot time any time kexts are added or removed. It's why the boot time of the first reboot following a kext change is longer, i.e., the kext cache is being rebuilt.

Maybe if you could clear the kext cache before moving in the kext you wouldn't get that "not properly installed" message but I really don't know if that would work. And I don't know how you clear that cache nor would would happen when you do.

Frankly, rereading your post I don't really know why moving a kext into Extensions and doing the kextload doesn't work. I do believe however, the following reboot would still cause the kext cache to be rebuilt.

Just remembered something. Check the kextcache command (man kextcache in terminal, actually kextcache -h).