I found an internet discussion about disabling USB drives, and even for disabling USB entirely on OSX. If you have the option of using a Bluetooth KB & Mouse on that machine, this might be an option. Then again, it may prevent using USB devices, and still put up the alerts.
It sounds like just moving or renaming IOUSBfamily.kext AND IOUSBMassStorageClass.kext may solve your problem. I am assuming IOUSBMassStorageClass will use IOUSBfamily, if not, then you may be able to leave IOUSBMassStorageClass in place.
Look for Jul. 6, 2005 - Allan Marcus
http://www.macintouch.com/readerreports/...
If that does not work, you could write an AppleScript deamon to dismiss the alert every so many seconds. Run the script at startup, headless (no GUI).
The over-current alert comes up every 30 seconds, right?
If I was willing to fry one of my USB ports/chips/regulators, I could write the script for you, but I am not.
You have to turn on Enable GUI Scripting via AppleScript Utility to get AppleScript to control alerts...
This is a sucky solution, but the best software solution I have seen for this problem.
If Growl would catch these alerts, that would be your perfect solution. Growl only snags application alerts, and only for applications that are Growl aware. Maybe someday Apple will choose to make system alerts Growl aware...
FYI - forums.macrumors.com notes this issue for several users, but no software solution http://forums.macrumors.com/showthread.p...
1 
7 
댓글 1개
Which version of OSX, 10.6?
Dave 의