How to use your old Huawei E169 UMTS Stick on Mac OS X Lion

It is time to take care of older Hardware running on Mac OS X Lion. This blog post will be about my old Huawei E169 USB UMTS stick, which I use from time to time when no WLAN is available.

Its software was designed to be used under 10.5, so the upgrade to 10.6 was also problematical.

Lion uses a new 64 bit kernel, therefore the older drivers from Snow Leopard do not work anymore. After searching Google, I found this blog post which links to a new driver package. This package is from the english support page of the provider three, however its mpkg installer package contains the necessary drivers for Lion. So you can go ahead and extract the downloaded zip. You will find a file called “3Connect”. You can right click and view its content. In Contents/Resources you will find the wanted “mobilemanager.mpkg”. Right Click again and go into Contents/Packages. If you deciced to just upgrade from Snow Leopard to Lion, then you won’t need the “mobile_manager_application.pkg”. This should be already installed if you used the stick before. However you will need the “huawei_universal_425_05.pkg”. This file contains the necessary drivers for Lion.

After you installed these drivers, you can go check your network settings and devices in your system preferences pane. My Mobile Partner complained about a missing phone number, which needs to be called. This was a crucial part of the installation, because I thought that the Lion Update kept all necessary network interfaces and settings. However it will forget the number that needs to be called. So you need to add “*99#” to the network adapter.

You should be ready to go by now, press connect and try to establish a connection on Lion. Of course you should at least run once the MobilePartner application so that you can enter your SIM pin number.

Windows Phone 7 Mango RTM Update experience

Yet another post in english 😉

So yesterday Microsoft announced that their Windows Phone 7 Mango Update would be available to all phones, that do not run any customized or branded version of the OS on their phones. Luckily, my HTC HD7, which I use for my master thesis, is unbranded.

Instead of booting up my Windows 7 VM, I decided to use this time the native Windows Phone Connector Client which is only available to macs running Snow Leopard or Lion. This is because the software is only available through the Mac App Store. The phone asked me to setup synchronization and after that I was allowed to search for new firmware. Up to then, my phone was running with the 7720 Mango Beta 2 refresh, which was available to registered developers.
Windows Phone 7 Mango RTM Update experience weiterlesen

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 🙂