5137 Views 11 Replies Latest reply: Jan 20, 2008 3:31 PM by email@example.com
Yeah, I'd recommend deleting those items, one by one, and identifying which of them is causing the delay. I'll bet something is making a call that is timing out or failing.
Is there anything in the Console log? Often you'll get warning or error messages when things are slow like that which should point you in the right direction.
I took the advice of using the ultra cool benefit of Time Machine and blew away the following from my /Library/StartupItems directory but I had to do it booted off a cloned disk because WDNotifier is actually a binary that was running that would come back to life every time I killed it which wouldn't let me remove it.
Here's the list I removed:
M-Audio Firmware Loader
I then restored each one from my Time Machine backup one by one, each time followed by a reboot.
The login hang was gone until I restored the last thing on the list, WDNotifier! Then my login time jumped from 1 second to about 35 seconds as it was like before.
WDNotifier is part of the software that came with my Western Digital My Book Pro II. I've removed the WDNotifier binary as well as the WDBMService folder and my WD drive still works fine.
Yay...my "fast as Tiger" Mac is back!
Thanks everyone and I hope this helps other people too.
In my startup items folder I found..
HP Trap Monitor
I removed the WDNotifier file. But instead of having to boot from a clone I control clicked on it and selected show package. Inside there was the WDNotifier with a couple other files and I was able to delete it from the package.
After a reboot I was able to go back and delete the WDNotifier package. Now my MacPro is back to normal desktop load speed.
Thanks for your help!!
Well done! I just returned my WD MyBookPro for a LaCie Big Disk after deciding to to store backups off-site (and encrypted) with Amazon's S3, rather than use RAID 1. I had also noticed slow logins and two programs that needed removing:
/Library/StartupItems/WDNotifier and /usr/bin/WDdrv (or close to that, maybe sbin).
I could not remove either because they were running/open, so I used Lingon to disable WDNofier startup and also booted and logged in with shift key down. Then I could remove WDNotifier but could not find the WDdrv. After removing the former, login times are again fast and neither appear to run.
Due to my returning the drive, I have no need of these anymore, but I would recommend users of WD drives to consult WD support regarding their function.