Feeds

Updating to Windows Phone 7.5

The stone in the Mango

Secure remote control for conventional and virtual desktops

Review Just like Apple iPhone users needn’t own a Mac to sync data and apply updates, Windows Phone 7 users needn’t be reliant on a PC either. To broaden the appeal of Microsoft’s latest handset OS, the company offers a Mac software alternative.

Windows Phone Connector for Mac

Nice to know there's an update, but what version is it?

Unlike Apple’s dual platform iTunes offering, MS keeps Zune exclusively for its PC clientele and Mac users get Windows Phone 7 Connector. It’s even available to download from Apple’s Mac App Store. I’ve been using this Mac app with an HTC Trophy, eagerly awaiting the opportunity to update it to Windows Phone 7.5, aka Mango.

The other week, I thought it had arrived early, but this was just an update to version 7.0.7008.0. As far as installing goes, it all went smoothly. Download, instal, reboot – that sort of thing. The only grumble I had with the experience is that Windows Phone 7 Connector for Mac doesn’t actually inform you of the update revision number that you’re applying. You’re flying blind. And it was only at the end of that particular update process that I realised that Mango hadn’t ripened yet.

Windows Phone Connector for Mac crash

Mango crushed: Windows Phone Connector for Mac retires early

A few days ago, my phone started nagging me about updates again. This time, I was more hopeful despite there being no information about the version. However, Windows Phone 7 Connector for Mac didn’t play nice on this occasion. It detected there was an update, but installing it was another matter. Going through the motions to apply the update resulted in an instant app crash. I’m no coder, but I’m guessing it’s not good news when I get this every time:

Exception Type: EXC_BREAKPOINT (SIGTRAP) Exception Codes: 0x0000000000000002, 0x0000000000000000 Crashed Thread: 6 Dispatch queue: com.apple.root.default-priority

Application Specific Information: *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Invalid parameter not satisfying: aString != nil'

Maybe it’s another app causing trouble, but one thing seemed certain, getting a recent Windows Phone 7 update onto my HTC Trophy wasn’t going to be happening with Windows Phone 7 Connector for Mac.

Providing a secure and efficient Helpdesk

Next page: I Zunes

More from The Register

next story
TEEN RAMPAGE: Kids in iPhone 6 'Will it bend' YouTube 'prank'
iPhones bent in Norwich? As if the place wasn't weird enough
George Clooney, WikiLeaks' lawyer wife hand out burner phones to wedding guests
Day 4: 'News'-papers STILL rammed with Clooney nuptials
iPAD-FONDLING fanboi sparks SECURITY ALERT at Sydney airport
Breaches screening rules cos Apple SCREEN ROOLZ, ok?
Crouching tiger, FAST ASLEEP dragon: Smugglers can't shift iPhone 6s
China's grey market reports 'sluggish' sales of Apple mobe
Apple's new iPhone 6 vulnerable to last year's TouchID fingerprint hack
But unsophisticated thieves need not attempt this trick
The British Museum plonks digital bricks on world of Minecraft
Institution confirms it's cool with joining the blocky universe
How the FLAC do I tell MP3s from lossless audio?
Can you hear the difference? Can anyone?
prev story

Whitepapers

Forging a new future with identity relationship management
Learn about ForgeRock's next generation IRM platform and how it is designed to empower CEOS's and enterprises to engage with consumers.
Storage capacity and performance optimization at Mizuno USA
Mizuno USA turn to Tegile storage technology to solve both their SAN and backup issues.
The next step in data security
With recent increased privacy concerns and computers becoming more powerful, the chance of hackers being able to crack smaller-sized RSA keys increases.
Security for virtualized datacentres
Legacy security solutions are inefficient due to the architectural differences between physical and virtual environments.
A strategic approach to identity relationship management
ForgeRock commissioned Forrester to evaluate companies’ IAM practices and requirements when it comes to customer-facing scenarios versus employee-facing ones.