Office Mac 2011 cannot open files from network folder with home in its name

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:

Excel File cannot be opened

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.

How to enable Xbox 360 Audio over HDMI connection

I was trying to connect my Xbox 360 to my shiny new Sony Bravia KDL-46EX720BAEP Flatscreen. I thought it would be sufficient to plugin a HDMI cable and I would be all set. The screen was immediately detected, but I heard no sound from the console. It took me a few minutes to find this awesome hint which allowed me to hear sounds from the Xbox 360 again:

You have to disable the automatic screen detection inside the Xbox 360 console settings. The console will restart and after this restart I was able to hear again.

Windows 8 Developer Beta & VMware Fusion 4

This time it’s in english 😉 I hope that this will get me faster answers than if I would write it in german. So bear with me please 🙂

Today Microsoft released a public developer beta of Windows 8. I thought it would be nice to test, so I decided to install it on my Macbook Pro with Lion running. Windows 7 runs fine in VMware Fusion 3, however a Windows 8 VM will not boot. You will always get an error like „vcpu-0:NOT_IMPLEMENTED“. Reading this post about configuring Virtual Box, I thought this problem would have something to do with Intel VT-X extensions. However this setting did not fix the problem. Only todays update for Fusion 4 will let you use Windows 8.

I upgraded my Fusion installation and tried my old Windows 7 VM. It works just fine. So I gave Windows 8 another try and configured a new VM, just to be sure. With this VM I am able to start the graphical setup of Windows 8, however it will always ask me for a CD/DVD driver:

I tried using IDE and SCSI HDD configuration, but that did not change anything. The DVD drive is a mounted ISO image, from which the setup boots. I wonder myself why the Windows setup asks for a driver, if it boots from the asked device… anyways I don’t know what else can be done. I already tried to mount the VMware Tools installer (it’s just another ISO mounted to the DVD) and pointed setup to the drivers folder on that ISO image, but setup does not find any drivers at all.

Any hint on solving this problem would be highly appreciated 🙂

Microsoft Windows Phone 7 und der erste Virenscanner

Small update: please use Google Translate for an english version. I still need time to think about a good multilanguage solution for this blog 🙂

Es war nur eine Frage der Zeit, bis der erste Virenscanner für Microsoft Windows Phone 7 erscheint. Gestern war es dann „endlich“ soweit: AVG Mobilation Anti-Virus Free

Nun ist es aber so, dass die App ganz normal vom Microsoft Marketplace geladen werden kann. Was bedeutet das für die App?

Microsoft Windows Phone 7 und der erste Virenscanner weiterlesen

Office 2010 unter Windows und Office 2011 unter Mac OS X

Dieses Mal gibts keine Kritik, sondern eher mal was Positives 🙂

Die neuen Versionen der Microsoft Office Suite sind erstaunlich gut zu bedienen unter Mac OS als auch unter Windows. Die in Office 2007 eingeführten Ribbons wurden verkleinert und die so als schrecklich befremdlich befundene Benutzeroberfläche wurde positiv überarbeitet. Was mich dabei sehr freut, dass die Mac Version endlich keine eigene Toolbox mehr als eigenes Fenster hat sondern alle Bedienelemente zusammen mit dem Dokument angeordnet sind. Wenn man dann also mit Expose zwischen den Fenstern hin und her springt hat man dadurch kein nerviges Extrafenster mehr zur Auswahl und es verdeckt auch nicht dauernd genau den Text, den man gerade bearbeiten möchte.

Ansonsten möchte ich noch die hohe Startgeschwindigkeit loben. Auf einem kleinen Netbook mit 10″ Bildschirm und Atom 1,6GHz CPU starten Word, Excel und Powerpoint in etwa 2s. Wirklich erstaunlich. Auf meinem Macbook Pro brauchen die Programme immer noch gut 5 bis 10s zum Starten. Allerdings liegen diese Werte immer noch weit unter dem von Office 2008. Insofern doch eine Verbesserung gegenüber vorher.