No FireWire port on the new Aluminum MacBooks... Now what?

Many of us end users utilize the FireWire target disk mode to diagnose issues, retrieve files from otherwise defunct computers, run disk repairs while booted from another drive in lieu of a Mac OS X startup disc and perform other procedures.

In addiction, iMovie users, who will no longer be able to directly connect cameras that use the FireWire port. The new MacBooks still ship with iMovie, but Apple apparently expects users to work with a USB-capable camera or import data to another system first. What if we don’t want to buy a NEW USB-capable camera? Does someone know of a way to connect a FireWire-capable camera to the new MacBook?

Maybe USB 2.x is the wave of the future, but what of the present? What is the bridge between the two ways to connect peripherals like the FireWire cameras? Is there a new way to connect the new computer in Target Disk Mode?

This post is not to “fire up” people to gripe. It is here for us to find a way to help the FireWire people connect to the new MacBook, until they move on to full USB peripherals. There has to be a way. An adapter of some kind maybe? "Mickey Mouse" fixes are not okay to me or many others. ie: Using a CD or DVD to transfer data is so 1997. Target Disk Mode is the very best way to go for the average user.

Ideas?

-Apple //GS

20" iMac C2D 2.33Ghz, PB G4 12" 1.5Ghz, iMac DV400, Mac OS X (10.5.5), 60gig iPod 5G

Posted on Oct 15, 2008 7:00 PM

Reply
29 replies

Oct 24, 2008 9:24 AM in response to Douglas McLaughlin

Douglas McLaughlin wrote:
Intel-based Macs can startup off a USB hard drive with Mac OS X installed on it. This gives you ability to access all files on the computer and will allow you to make a disk image with the Disk Utility.

Ok, so I plug the MacBook in to another computer, say a desktop, with a USB cable. The desktop computer will be used to create the disk image of the MacBook. I then boot the MacBook by holding down whatever key is used to boot it into USB Target Disk Mode and then make the Disk Utility backup that way? Is that how I do this? Since we don't have any USB drives at my job that we can use for this process, plugging directly into another computer would be our only option at this point. I typically have a spare computer in my office for just this reason.
A hardware failure of the drive will not allow you to use FireWire Target Disk Mode to recover files. If it's a software fault/file directory problem then booting from an external hard drive through USB will allow you to repair the file directory with Apple's Disk Utility or a more powerful utility like DiskWarrior.

I had meant a software failure. Sorry I wasn't clear. In the time I have been using computers (20+ years), I have come across only about a dozen hard drive failures where data could not be recovered without drastic measures. Any other time it would be something like software, a drive controller, a motherboard problem. More often that not when a drive stopped booting, It's because the user had gone in and changed the startup disk for whatever reason but didn't change it back. Then the computer sits there looking for something that doesn't exist anymore. An easy fix, but the user still get hysterical when their computer doesn't boot.
Really? Nowhere?

Again, here is where target disk mode comes into play. The Migration Wizard doesn't work for our setup. This is because of the way the user accounts get setup on the computers. The accounts are handled through Active Directory. Because there isn't a lot of server space to keep all of the files up on a network share we have the home directory set to to be saved locally. We also have the accounts set to be mobile accounts if the AD server were to ever go down, uses can still log in to their computers.

Because the accounts are set up this way the Migration Wizard thinks that they are Network accounts and gray's out the user account not allowing for the migration to occur. The best way we have found to move the data over has been with FTDM.

Oct 25, 2008 8:40 AM in response to Douglas McLaughlin

I found the site you direct Redclaw not to be that helpful for setting up the ethernet network for migration. And, indeed, I found the staff in the apple store and on their tech support phone line to have not been trained at all in what to do without firewire -- lots of misinformation on wireless and ethernet migration (and the woman on the tech support phone line kept telling me to make sure I was using firewire even after I kept pointing out this was impossible! and that I did already have an ethernet network set up).

I didn't mean to get to griping. All I meant to say was that the following site I found most helpful in setting up my ethernet network for migration -- including a list of which computers would need an ethernet crossback cable (mine did) and which can get by with just a plain ethernet cable:
http://www.applelinks.com/index.php/more/handson_mac_connecting_two_macs_via_a_simple_ethernetnetwork/

One caveat: if you are running anything below 10.4 on your old machine (mine runs 10.3.9), you won't be able to use migration assisant (10.5 hours of painful manual migration for me!), despite the fact that some of Apple's own webpages claim that if yours was a late 2004 model shipping with 10.3.4 this would be possible (I did confirm this on the phone -- indeed, insisted on talking to a second person beyond the woman who just couldn't get it through her head that there was no firewire). I found the following site most helpful in finding various preferences, bookmarks, etc. for the manual move:
http://www.procata.com/blog/archives/2007/02/16/how-to-transfer-mac-os-x-applica tion-data-between-computers/

Oct 26, 2008 3:23 PM in response to Alex-H

Alex-H wrote:
Check here for Usb2.0 to firewire adapter:

http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=250311685438


1 I suspect that that's a USB to miniUSB adapter.

2 assuming that it was a FireWire to USB adapter, that's a FW 800 to USB adapter; you'd need an additional adapter to connect to FW400. You lose speed with each additional adapter.

3 again assuming that this is a FW to USB adapter, it will work at USB speeds at best... and probably much slower, as it has to have conversion overheads subtracted from whatever speed it can deliver. As the whole reason why I (and many others) use FW is that it's faster than USB, it would be of very limited use, as it would be considerably slower than USB which is too slow in the first place.

4 finally, even if it actually worked which I greatly doubt, it would not be able to deliver such technologies as Target Disk Mode. It is a USB device, and USB does not support TDM. It can't. USB's physical and logical design prohibits doing any such thing.

Oct 27, 2008 3:03 PM in response to Bea AuntGeek

Thanks.

Also I can boot from a cloned FireWire/USB 2.x HDD. The iomega I have has both FireWire and USB 2.x on it. I cloned my iMac to the external HDD using USB 2.x and it worked. However there is still no way to have a miniDV FireWire based camera work. When I connected the camera to the FireWire port in the iomega HDD while still running MacOS 10.5.5 through the USB connection, iMove did not see the miniDV at all. iMovie did see the built in iSight camera though.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

No FireWire port on the new Aluminum MacBooks... Now what?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.