Index syndication
comment syndication

Bootcamp 3.0 fixes WinXP BSOD for Multitouch Trackpad

Apple released Bootcamp 2.1 with OS 10.5, which allows you to dual boot to Windows XP/Vista on your Mac.
Subsequenet to that release, there was a driver update for the Multitouch trackpad which was suppose to improve souble tapping, etc. However it caused a Blue Screen of Death (BSOD) the moment you double tapped, courtesy of applemtp.sys.

Many people sent suggestions to Apple to fix this, but it seemed to be falling on deaf ears.

Little did we know that Apple were releasing a new version of the touchpad driver included with Bootcamp 3.0 on the Snow Leopard install DVD.

I’ve updated my Bootcamp to 3.0, and indeed the applemtp.sys driver version has increased to The FAQ for the Snow Leopard update states that Bootcamp 3.0 has:

“Improved tap-to-click support – The ability to tap the track pad to click the mouse button is now supported on all Mac portables that run Boot Camp.”

In my tests, so far, there has been no more crashes. I get to use double finger right click tap, and the track pad responsiveness that I got in the older buggy driver is back as well.

Thanks Apple. No more BSOD.

Snow Leopard: WWAN using Merlin XU870 ExpressCard

This is the same issue I’ve posted on a couple of forums. It’s seemed detailed enough to be a blog post, so here it is. Under 10.5.8 (Leopard) I was successfully using my Merlin XU870 ExpressCard (supplied by ISP) with Three Broadband (3) in Australia. I did not use the 3 drivers, but used the Leopard WWAN built-in to connect. There was never an issue as Leopard detected the card as a “Novatel Wireless HSDPA Modem”, and I configured the Network Advanced settings for 3 postpaid services as:

  • Vendor: Novatel Wireless Inc.
  • Model: GSM
  • APN: 3netaccess
  • CID: 1

I installed Snow Leopard as an Upgrade (not a fresh install) after having a CCC backup and a Time machine backup in place.

When I plugged in my 3 expresscard, 10.6 detects the card, initialises and populates the WWAN icon with “Telstra 3G: Not Configured”.
Screenshot 1
It detects the card as a “Novatel Wireless HSDPA Modem”, and automatically configures the Network Advanced settings of the card, as shown:
Screenshot 2
The question is: Why is the APN telstra.datapack setup as default?

I am able to change the APN to 3netaccess, which results in a successful connection to 3:
Wed Sep 2 15:38:25 2009 : Initializing phone: ATE0V1&F&D2&C1S0=0
Wed Sep 2 15:38:25 2009 : Initializing PDP context: AT+CGDCONT=1,"IP","3netaccess"
Wed Sep 2 15:38:25 2009 : Initializing with secondary command: AT$NWPDN=0
Wed Sep 2 15:38:25 2009 : Dialing: ATD*99***1#
Wed Sep 2 15:38:25 2009 : Waiting for connection
Wed Sep 2 15:38:25 2009 : Connection established
Wed Sep 2 15:38:28 2009 : Serial connection established.
Wed Sep 2 15:38:28 2009 : Using interface ppp0
Wed Sep 2 15:38:28 2009 : Connect: ppp0 <--> /dev/cu.wwan
Wed Sep 2 15:38:32 2009 : Could not determine remote IP address: defaulting to 10.64.***.***
Wed Sep 2 15:38:32 2009 : local IP address 115.130.***.***
Wed Sep 2 15:38:32 2009 : remote IP address 10.64.***.***
Wed Sep 2 15:38:32 2009 : primary DNS address
Wed Sep 2 15:38:32 2009 : secondary DNS address

The annoying thing is the WWAN menu still shows Telstra when connected.
Screenshot 3

Looking at the WWAN system file:
cd /System/Library/Extensions/IOSerialFamily.kext/\
less countryCodes.plist

it has only Telstra, Optus and Vodafone carriers listed. I think this could be the cause of the default APN being populated in the Advanced settings. I can’t find where the “Telstra 3G” in the WWAN menu item is coming from though.

I’d appreciate if anyone can give their thoughts on how to fix this.