Dedicated to my late brave, beautiful and silly mummy, Debra Ross. I love you mumster.

Skip navigation

Category archive for hardware

Because archives are so much easier than having just hundreds of posts on the home page. I learned that the hard way.

My review was featured on Elgato.com!

I got quite a shock this afternoon when going through my server records. For the month of October 2008 I was getting hundreds of hits from Elgato.com, but I couldn’t figure out why. As it turns out, my review of the Elgato EyeTV digital TV tuner stick was featured on Elgato’s Media Coverage page alongside the likes of the The Age (an Australian newspaper), MacLife, MacWorld and PC Magazine!

This could be the highest profile mention of my blog and logo since I linked to it myself (ahem) on Whole Wheat Radio. This has made my weekend :-)

Possible reason why there’s no MacBook FireWire

The MacBook FireWire Debacle

I’ve been told by people that the reason why Apple didn’t include FireWire in their lastest MacBook computers was because they were phasing out support for a so called legacy port and that most video cameras and external hard drives use USB as well, amongst other reasons which I thoroughly debunked in a previous post.

Well we finally may have the real reason for why Apple removed the FireWire 400 port from the MacBook. As it turns out, it might not have been a decision by them after all, but one by NVidia who designed the new GeForce 9400M integrated chipset and graphics chip which the new MacBook uses.

Here’s the kicker: according to several sites I’ve been reading, this chip was designed without a FireWire controller.

The GeForce 9400M does not include a Firewire controller. When asked, Rene Hass mentioned that during the design of this chips, this function was not part of the feature list.
~ HardMac.com

This seems to change my perceptions somewhat. Given Intel’s lackluster onboard graphics, I can understand Apple’s decision to move to a NVidia’s chipset and graphics solution, especially in a computer like the MacBook. I can’t help but think though that they could have at least included a separate FireWire controller, granted they are substantially bigger than controllers for USB, but if my Sony Vaio PCG-C1VM ultraportable from 2001 could include one there’s no reason why Apple in 2008 couldn’t.

Promotional image for the new NVidia chip comparing sizes with Intel's integrated graphics
Promotional image for the new NVidia chip comparing sizes with Intel’s integrated graphics

Sophisticated MacBook Pro cooling consulting solution

My sophisticated MacBook Pro cooling system

What happens when your MacBook Pro has been busy compiling code for several hours and has started melting into the table? Put a box fan next to it. Not only is it an incredibility sophisticated solution, inexpensive and stylish, but it actually works. You read it here folks.

See Jim, I’m a person who provides consulting solutions too!

Temperature gauge showing 74 degrees Temperature gauge showing 74 degrees

Apple, these are my FireWire drives

The MacBook FireWire Debacle

I’m sorry, I just couldn’t help myself posting a screenshot of this Finder window this afternoon. Could you imagine transferring that much data through USB 2.0? Yuk!

I guess their argument would be that I’m a MacBook Pro user and not the target market for the MacBook. It’s a shame because I’ve always wanted to return to a souped up desktop and a smaller, more lightweight notebook computer combo again at some point, just like I used to have with my PowerMac G5 and my iBook G3.

I think I’ll be sticking with MacBook Pros now. Well look at that, their tactic worked!

Only problem so far with the iPhone: MobileSafari

Google Reader on the iPhone
Google Reader is wildly convenient on the iPhone, but is also one of the sites that crashes the most. Might be sticking with the desktop version for now.

Those who read this blog will know that despite my initial skepticism, I finally bit the bullet and bought an iPhone 3G in September. Looking back at it now, it may have been one of the best decisions I’ve ever made; it really is a phenomenal device. Other phones may have more features, or have features with higher specifications, but none I have ever used even remotely come close to the iPhone in usability.

With such constant glowing reviews, you might be under the mistaken impression that I think the iPhone is absolutely perfect and that I am now a blubbering fanboy. The fact is I have been taking notes whenever something has irritated me with it in the hopes I could create a post taking about the iPhone’s shortcomings and how it could be improved.

After a month, I feel it’s time to let ‘em rip, all one of them. And here it is: the MobileSafari web browser officially blows. It is the most crash prone, error riddled piece of s… oftware I’ve used in recent memory. It’s a shame because no other applications have been able to crash this iPhone, and a serious shortcoming considering it was billed as a phone, music player and an internet communications device.

WebKit logo
It’s a shame, WebKit itself rocks.

Typically the scenario plays itself out like this: I’ll browse to a web page, scroll down leisurely, perhaps pinch and wipe around a bit to increase or decrease the size of elements. Boom, crash, back to the home screen. It doesn’t crash every single time, but I’d wager it crashes once for every time it works properly twice. A 33.3% reliability rate is hardly a glowing record.

Different activities seems to exacerbate the problem. If I enter any information into a field on a web form barring simple login screens, it will crash. If I scroll down a page too fast, it crashes. If I click a link, then click another link before the page finishes loading, it crashes. Generally the problem can be partially alleviated by restarting the phone every few days and making sure I don’t have more than a few tabs open at any one time, but it’s by no means a quick fix.

What I find interesting is that for every person on a web forum or blog post comment feed that complains about MobileSafari reliability, there are two or three that claim to have no problems at all with it. Here’s hoping the next software update fixes this for everyone; I’d love to be able to use MobileSafari carefree on this phone. WebKit is still one of the best rendering engines.

Stay tuned for my real world scenario review of the iPhone that I compiled last week but still need to clean up. It really shows how you can use this thing to take over your life and how fantastic that is… provided you stick to applications other than MobileSafari for most of the time :).

Sent from my iPhone.

MacBook a winner, unless you need FireWire

The MacBook FireWire Debacle

When I claimed this was going to be the last post on the MacBook FireWire Debacle, I didn’t think another writer would share a similar view to me on this issue. This will be the last post! Ironically, I found about this USAToday article through Apple’s official start page which chose to summarise the article as such:

Apple, says Edward C. Baig (usatoday.com), “has fashioned a winner with the new MacBook.” The new model features a “bold new metal design with a glossy backlit widescreen LED display, spacious buttonless trackpad and souped-up Nvidia graphics for gamers.” In fact, Baig reports being “pleased with the detail and fluid motion as I played Spore from Electronic Arts and Call of Duty 4 from Activision.

Conveniently they didn’t disclose any of Edward’s comments regarding the lack of a FireWire port, and the less than adequate number of USB ports as replacements:

But Apple risks ticking off users who rely on FireWire. Like many people, I still have a FireWire camcorder, not to mention an external FireWire hard drive. Apple may want to drive customers to the FireWire-capable MacBook Pro — models that start at $1,999 — which are certainly better equipped for video editing.

The company also figures many of the folks who would do a lot of video editing own newer camcorders that more likely use USB rather than FireWire. Apple isn’t generous there, either: There are just two USB ports on the new MacBooks.

You can still get FireWire on the entry-level plastic MacBook, but it doesn’t have the muscle for heavy-duty video editing.

Exactly! I am so fed up with reading comments from people that tell people who can’t afford a MacBook Pro to buy an older MacBook that still has FireWire for video editing, or that people who need FireWire should buy a MacBook Pro. Not everyone is swimming in money.

If you think I’ve started to dislike Apple though over this hiccup, the last line of Edward’s article pretty much sums up my own opinion:

Apple has fashioned a winner with the new MacBook. Unless you can’t live without FireWire.

The penultimate plus one MacBook FireWire post

The MacBook FireWire Debacle

Much to delight of most of the people who read this blog I’m sure, we’ve come to the end of my coverage of the MacBook FireWire Debacle. I’ve learned so much over the last few days about the FireWire 400 standard, especially with regards to it’s uses in audio and video production that I knew very little about. The removal of this port from MacBooks is a real shame, though it’s probably time to face the facts and admit that the MacBook won’t ever have FireWire again; it’s future in the Mac Mini and iMac are probably also shady.

At least I can tell people they can still buy svelte new Japanese laptops and load them up with FreeBSD if they need a current and inexpensive FireWire solution.

As I said I could easily post dozens more posts on this subject, but I think I’ve already said enough. If you’re still interested though, there’s still some extremely active discussion (more active than I’ve ever seen before after an Apple product launch) going on across web forums, blogs and news sites which I’ve linked to below.

Don’t forgot, if you want FireWire in the MacBooks again, you can send feedback directly to Apple. Steve Jobs has already responded to at least two comments sent, so let’s raise some more hell!

News and articles

Web forums

MacBook FireWire Debacle posts

Addressing some MacBook FireWire arguments

The MacBook FireWire Debacle

ASIDE: I had not intended my critique of Apple’s disastrous decision not to include FireWire on their MacBooks to become a multiple post saga, but the more I learn about this decision and the more I read up upon it, the more I think this really is a mistake.

We love Apple’s products and we want them to succeed, so we think this really is a terrible decision. We know Apple will probably ignore us, but it’s worth a shot generating some noise right?

In today’s investigation of the MacBook FireWire Debacle, I’ll be looking into some of the arguments that seem to appear time and time again in every 600 page MacBook FireWire removal forum thread across the intertubes.

Removing FireWire it is the same as removing the floppy drive on the iMac.
This question went first, because I can tell rebuttals of my responses below would probably discuss obsolescence and the idea you can still buy older versions.

That there is a substantial difference between getting rid of a floppy drive or other legacy devices, and getting rid of FireWire. In the case of the floppy drive, CD burners and the “super floppies” (LZ120, Zip) were clearly superior replacements, and you could buy inexpensive USB floppy drives. With these MacBooks, USB 2.0 is the only possible replacement, and it’s not superior.

Most people I know have never heard of FireWire
Most people I know have. And if they haven’t, tech savvy friends or family have bought them FireWire drives for use with Time Machine, camcorders for iMovie etc. Would the removal of a port to save a few dollars make up for the money they would lose from customers holding off purchases?
You can just buy a USB 2.0 to FireWire cable
Even if we assumed such devices for Mac exist (and I’m not sure they do), they would not address the underlying problem. Serial and ADB to USB adaptors worked because USB is an improvement.
Grilled cheese sandwiches taste great with maple syrup and hot fudge
I’ll have to take your word on that.
If you can afford expensive FireWire cameras, you can afford to buy the MacBook Pro which has FireWire.
Many professional users use powerful desktop computers, and a more lightweight laptop for when they need to go. For many, the MacBook Pro is simply too big and heavy.

The statement is a tad arrogant. Given people who buy MacBooks are buying them because they’re cheaper, doesn’t it make sense that said customers would also be less able to buy new audio and video equipment too that might be older and only have FireWire ports? The primary school right here in my suburb use MacBooks and MiniDV video cameras. MiniDV cameras can only use FireWire. What about them?

It also amounts to false advertising: Apple bundles their machines with iLife which include two consumer-grade video editing applications. Their prosumer Final Cut Express is also targeted at a similar market. What about the thousands of consumer video cameras that use FireWire?

This really isn’t a big deal. The financial crisis, world hunger, hello?
True. But as a person who knows about, endorses and uses this standard I feel as though I’m in the position of letting people know. And by that definition, really nothing else matters right now!
Apple still sells the older MacBook with FireWire
The older, heavier hardware version with the 5x slower graphics performance and slower front-side bus? For how long will they be available? And isn’t it ironic and counter intuitive that someone would tell you to buy an older version of a product because it has faster ports than the newer one?
Complaining on your blog or on forums isn’t going to make Apple change.
This is probably the only argument that makes some sense. It’s true Apple probably doesn’t care. This is why it’s important to have as many people as possible talking about it, and more importantly sending feedback to Apple. Even gigantic corporations such as Apple aren’t completely immune from the demands of their customers.