Are you also annoyed and tired by Spotify’s notification badge in the dock of Mac OS X? I totally was and found a simple list of instructions on apple.stackexchange.com and want to show you how to remove this “feature”.
If correctly used, notification badges are a cool thing. They notify you when an app wants your attention. Spotify abuses this feature and shows the number of pending notifications inside its app. That means: If you ever subscribed to somebodies playlist and this playlist is updated, you will be notified. Same goes for stuff like new tracks of your favorited artists. You have no control over these notifications and will always be notified. Otherusers are also annoyed by this misbehavior but nothing changes Thats why my Spotify is mostly minimized to the background and when opened it shows this ugly notification badge in its UI:
Its annoying and always tries to steal my attention. Same goes for the Mac OS X dock icon:
Normally, you can open the system preferences and can disable the notifications. However, Spotify isn’t listed (although it uses the notification APIs of Mac OS X).
The instructions from stackoverflow write this missing entry into the notification database, so that it shows up in the list. Only after that you are allowed to disable Dock notifications:
Here’s the code of Ryan Patterson’s stackoverflow entry, in case it ever gets deleted:
# "Usernoted" seems to be the "user notifications daemon", so get it's PID.
# Find the sqlite3 database that this program has open. It's in a "private" folder (app sandboxing).
It’s unbelievable: Microsoft Office Mac 2011 cannot open files from network folders when the share name contains “home”. My Synology NAS uses shared folders for each of its users. The user folders can be reached under the “home” share and are automatically mapped to the user’s home folder on the Synology. This is the default setting for every new standard setup of Synology NAS.
I’ve tried recently to access an Excel file from my home folder. After double clicking in the Finder, Excel opened with this error message:
So it cannot find the file. This is due to a known Office bug that exists now for several years and appears to be still unpatched.
It’s inexplicable how an error of this severity is still unpatched. All my search results suggest me to stop using the home folder and use instead a different name. That’s working for my user, because it has admin rights and can open the “homes” share with a subfolder to my username. However, not all of the users on my network should have this right.
I only hope that the new Mac Office will address this issue. The currently available preview is pretty unusable and tends to crash when I’m working with network volumes.
WP-Sweep is a new WordPress plugin which only uses the official WordPress API to delete and clean up orphaned and unused data.
I’ve given it a try on my personal blog and it worked flawlessly. Unfortunately I’ve forgot to write down the exact percentages on what could be sweeped and saved but I have now a good feeling that at least my > 3000 blocked spam comments are finally gone
Don’t forget to backup your data, before you try this!
I’ve decided to install Java manually with the packages provided by Oracle, because they are in a higher version and have less security holes. However, this will lead to problems as some Java applications which where build for Java 6/7 cannot start on Java 8 from Oracle.
I’ve tried it then with the most current Arduino Beta 1.5.8 which supports newer Java versions. While Arduino now starts, it cannot compile Arduino sketches. If you try the older Arduino 1.x versions, it will not start at all.
Only after installing Apples Java for OS X 2014-001 update, I could start Arduino 1.0.6 again and then compilation was also no problem anymore. If I check my java version with
java-v in a terminal, I’ll see that the system is using java 8 instead of the installed 6. So I think its safe to use. What do you guys say? Leave a comment if I missed something!
I’m currently switching from Windows 7 to Windows 8 and I wanted to make a clean install. Therefore I completely removed the Bootcamp Partition with the Bootcamp assistent of Mac OS X. However, it could not remove the partition. I’ve decided to delete the partition manually and to recreate the partition.
The Mac OS X disk utility only allows me to create exFAT or FAT partition, because NTFS is not natively supported. I’ve decided to use ExFAT and deleted my old Windows 7 installation. After installing Windows 8, I wanted to use my Bootcamp installation on Mac OS X. So I started VMWare 4.1.3 (The latest version is 5, but I’m not willing to buy the upgrade, the old version works fine under Mountain Lion.), removed the old entry for my Windows 7 Bootcamp installation and wanted to create a new one.
But this failed with several error messages, indicating that the Bootcamp disk could not be configured. After a short Google search, I’ve found the problem with the exFAT format of the Bootcamp partition: VMWare Fusion only supports NTFS formatted partitions.
The lessons learned from my experience:
If you create the Bootcamp Partition with the Mac OS X assistent, you will get a 32GB large Partition in the correct useable format.
If you delete yourself old Bootcamp partitions and want to reinstall, make sure you format the partition with NTFS instead of any other offered formats. Instructions for this can be seen here.
If you use Paragon NTFS4Mac or if you use MacFuse, you could preformat the partition with NTFS. But Windows 7 and 8 want to create a small boot partition for themself, so I would not recommend to go this path. Format the partitions from Windows setup.
A small update:
I was not able to use VMWare again with Bootcamp. Therefore I decided to delete the partition with the Bootcamp assistent, which crashed during this operation. I had to enter the recovery mode of Mac OS X and had to recheck and repair the complete HDD and its partition. I’ve then changed the size of the HFS+ Volume on the HDD back to its original size and created a new Bootcamp partition using the assistent:
No good news to report… Windows was finally recognized correctly by VMWare, but I couldn’t add the Bootcamp installlation. The setup wanted me to reboot into Windows and reboot into Mac OS X, because it thought the Bootcamp partition was not cleanly unmounted:
So I decided to try the new VMWare Fusion 5.0.1 version and suddenly my problems were all gone… It’s sad to see, that you always need a newer software version to work correctly. Especially when Windows 8 runs just fine inside a normal VMWare VM, but not when you are using Bootcamp. My guess would be that you could install Windows 7, configure Bootcamp correctly in VMWare Fusion and then upgrade to Windows 8. But this takes awefully long, so I’ll stick to the newer Fusion version. You can test it 30 days for free and after that you have to buy it for 44,99Euro