This is a pretty selfish tip, because this issue has happened to me personally a few different times, and despite my many searches around the 'net, I've never found a quick, simple solution. So here you go: my suffering can be your gain.

Basically, iPhoto '08 and the iPhone don't always play nice -- sometimes, you'll take a bunch of pictures on your iPhone, bring them back to sync up with iPhoto '08, and whoops, iPhoto doesn't see them at all. You can see them on your iPhone, but iPhoto's "Import All" button is greyed out, and they're not showing on your screen (sometimes, I've gotten dotted lines where the pictures are -- I think this all has something to do with a corrupted cache that iPhoto keeps of what's on the iPhone). Fortunately, though it's frustrating, there's an easy fix. Open up Image Capture (you can find it in Spotlight or even Quicksilver if you swing that way) with your iPhone connected, hit the "Devices" menu item, and then "Browse Devices." You'll get a screen just like the one above, with your iPhone's name instead of mine.

Uncheck the "Connected" box, and then recheck it, and boom. Image Capture, and thus iPhoto, will see all of your pictures and happily upload them. Is it voodoo? Sure -- we still don't know why iPhoto loses its place every once in a while (like I said, I'm thinking a corrupted cache somewhere along the line). But it works.

Grand Theft Auto isn't out for the iPhone, but Payback is --it's basically a 3D version of the old top-down GTA gameplay, improved with better rendering and lighting. You control the game by pressing "buttons" on the screen, and tilting the iPhone around, and Touch Arcade says it works well. Some missions are apparently tough, but in terms of what GTA is really about -- driving around and generally causing mayhem -- Payback will deliver.

Unfortunately, textures (both visual and audio) are rough, as are the actual physics, so it seems Payback is more of a "GTA could work on the iPhone" demo rather than an actual game (though of course you can play it, it probably just won't be as fun). Still, we're in favor of any game reaching high on the iPhone, and this one definitely does.

Payback is out in the App Store now, for a substantial $6.99. But it's worth it, especially if you're a big GTA fan, just to see such a complex game on Apple's little handheld. Video on the next page.

Not a surprise for those who have suffered from the issue, but a welcome admission nonetheless: Apple has now acknowledged that some recent MacBook Pro models contain faulty GeForce 8600M GT chips that cause video display problems. Dell and HP have already told customers similar stories.

In a support document posted yesterday, Apple testily admitted that while NVIDIA assured Apple that Mac computers were not affected, an internal investigation revealed three models of MacBook Pro indeed had problems.

Our own Cory Bohon wrote about his experience with (what he now believes to be) the same issue back in August.

The models affected were all manufactured between May 2007 and September 2008:

• MacBook Pro (17-Inch, 2.4GHz)
• MacBook Pro (15-Inch, 2.4/2.2GHz)
• MacBook Pro (Early 2008)

If your MacBook Pro is displaying distorted or scrambled video on the screen, or no video at all, you can take your computer to an Apple Authorized Service provider to have it repaired, free of charge. If you've already had your computer serviced for this issue, Apple may issue you a refund for the cost of the service. Free service is available to owners who bought their computer less than two years ago, even if the computer is out of warranty.

The problem is likely to cost NVIDIA up to $200 million to fix; this does not include the likely fallout from shareholder lawsuits alleging that the video-card manufacturer deliberately withheld information on the scope of the chip flaws.

[Via AppleInsider.]

Brian A. sent a tip to say he called his FedEx delivery manager in Huntsville, AL, and they told him that they were backed up with Leopard deliveries. Apparently, they weren't able to make the 10:30 AM deadline in some areas, and though delivery is still scheduled for sometime this afternoon, they'll be showing up late. How late? We're not sure, but hopefully not too late for Apple stores to receive their copies. Hopefully, this is just a hiccup in shipping, and not the start of a widespread delay.

In other news, reader Don also had a problem with his Leopard delivery-- when checking his tracking number with FedEx online, he noticed to his dismay that someone named "Ramirez" had already signed for his package (and he doesn't know anyone named Ramirez). He called Apple and they blamed FedEx, saying that FedEx was reusing tracking numbers, and the signature Don was seeing was for a different package.

And even if you have your copy, you may still be having problems-- Paul got his copy in Australia last night, but says Software Update has been zerged to death. With so many people trying to sign on and get their new apps, it may be a rough road for installers this weekend. Good luck out there.

Update: We've also heard about a delay out of Indy. If you were expecting Leopard in the US by 10:30am, odds are you don't have it yet.

I have yet to jailbreak my personal iPod touch but interesting news has come to my ears from a variety of sources. Many iPod touch jailbreakers find that their systems lose read-write access after reboot. The iPod seems to "self heal" and "modify" the /etc/fstab file on their system.

The problem may simply arise from the file not getting written properly during the jailbreak itself. For the moment, iPod touches that are jailbroken using older (primarily Windows) versions of iPhuc are leading this trend while Mac jailbreaks resist the reversion. More as this develops.

For those still stuck in iPhone activation limbo, we have a couple of tips and tricks might help you to get on your way. While these might not be sure-fire solutions for everyone, they sound general enough and have worked for at least two individuals, so they just might work for you as well.

First up is a three-step process from Download Squad's Alex Hung which involves shuffling a couple of SIM cards around. After waiting far too long like so many others, Alex called AT&T who told him that the iPhone activation process involves two basic steps: the first is the SIM activation, while the second is some sort of iTunes verification process (if I had to guess, this is for Apple's records to keep track of who owns which phones and how many, since they get a cut of every AT&T iPhone contract). Like many others, Alex received the email that the SIM activation process had completed, but his iPhone still wasn't working. After a phone call and some clever deduction, here is Alex's trick that might help some of you get your iBricks to start working more like iPhones. Note, however, that this requires you to already be an AT&T customer with a Cingular or AT&T phone and SIM card separate from the iPhone:

1. Assuming you've already gone through the initial activation process and are stuck somewhere in limbo like so many others, power down your iPhone and swap out the iPhone's SIM (outlined in this downloadable iPhone User Guide - your first search result in that document for "SIM" should do it) for the SIM from your old phone. Power the phone back on.
2. Plug the iPhone back into iTunes to force a new activation process (every time you swap the iPhone's SIM, it will need to be plugged into iTunes and verified before your iPhone will work). Your activation might or might not work this second time around with your old SIM, but once you complete it, power the phone back down. Proceed to step 3.
3. Swap out the SIM cards again and re-insert the SIM that originally came with your iPhone. For the heck of it, wait a minute or two before powering the iPhone back on. If all goes well, your new iPhone SIM and iTunes verification will have finally straightened out, allowing you to use your iPhone as Apple originally intended.
   

You might have to power cycle the phone one more time (Alex did), as the iPhone might actually request you to do so, but this trick just might work for some of you. If it does, or if you have any modifications to the steps that ultimately get your iPhone up and running, please share in the comments. A catch with this method, however, is that we really aren't sure what will happen to your other activation requests if this trick actually succeeds. We also aren't sure whether this is a 'good' way to get your iPhone up and running, since you will technically be entering a second activation process into AT&T's (and possibly Apple's) systems, which could potentially cause more problems. If anyone knows something we don't about this trick, please share that in the comments as well and we'll be happy to update this post.

The second method is detailed by Rogue Amoeba's Paul Kafasis on the company's blog. This one is a bit simpler, though potentially more time consuming: Paul essentially called a specific AT&T number (1-877-800-3701), selected the proper extension (#1) and waited 45 minutes until getting a representative who explained the situation. Turns out that Paul's activation was a manual process that wasn't fully completed by the original rep who handled it. After this new rep apparently fixed a small issue by adding a required feature and clicking the "Yes, Paul can use his iPhone now" button, he was up and running with his iPhone.

Of course, these solutions might not work for everyone, but we sure hope they can bring a smile to at least some of you who have had a less-than-stellar experience getting their iPhones actually working like iPhones. Of course, if you have your own ideas or modifications to these solutions, please share them in the comments and we'll update this post.

I don't rely on .Mac's Backup, but I tinker with it from time to time. It's never seemed to be the killer app to fit all my needs, but others in the Mac web who are more passionate and knowledgeable about backup software seem to be quite upset with it. In particular, Jonathan 'Wolf' Rentzsch, Michael McCracken and Erik Barzeski more or less echo the same opinion: Backup needs help, and a lot of it.

All three of these notable Mac personalities have penned horror stories and useful overviews of what is so wrong with the little .Mac app that (someday) could, and I found them with a recent Apple kbase article John Gruber linked concerning a silly restriction of working with Backup 3 files.

After reading through these, I think I might leave my Backup tinkering as just that, and rely more on ChronoSync since it does machine syncing in addition to straight backup. Though the fact that I haven't seen ChronoSync written up as good or bad in any of the recent reviews makes me curious. Has anyone heard anything?

Looks like Microsoft's recent upgrading of Messenger for Mac to version 6 didn't go down as smoothly as they would have liked. Microsoft's own Messenger newsgroup is just one of the places buzzing with people having problems logging in.

I found this out while struggling through this jungle of versions myself. Going from 5.1.1 to 6.0.0 locked me out of the service, with only a typically vague error message to guide me. To make matters worse, I was able to log in to the fancy new Windows Live Messenger on PC. Trashing my preferences and going back to previous versions did nothing, and Google wasn't much more helpful. That was around the time I stumbled on to the newsgroup.

In the end, my solution was simple enough - I changed my admittedly weak Passport password to something a little more robust and, voila, I was in.

Are any of you having similar problems? Let me know in the comments if so and what workarounds you've found.

So the other night, while covering Sundance Film Festival for Blogging Sundance and Cinematical, we had a problem with Jason Calacanis's Powerbook G4. It would boot and run through the loading Mac OS X screen very quickly, but at the point where it was supposed to load the login screen, we were greeted by the default blue OS X background and the mouse pointer arrow and nothing else. And it just stayed there.

We tried rebooting, we tried zapping the PRAM, and we both booted into single user mode and booted the computer in target disk mode, attached to my laptop, and performed a disk check on the computer. No problems with the disk. The machine just wasn't booting.

After throwing up my hands and proclaiming there to be some odd hardware failure, it suddenly hit me: maybe the login window preferences were borked. We booted into single user mode again (reboot and hold down the command s button). I ran all the commands that you have to run in order to write to the disk (/sbin/fsck -y followed by /sbin/mount -wu /). Then I ran:

cd Library
cd Preferences
mv com.apple.loginwindow.plist BACKUPcomappleloginwindowplist

This makes a backup copy of the preference file associated with the login window and erases the original file in the process. After I was done, I typed reboot at the prompt and hit the return key. OS X rebooted and was forced to create a new preference file for the login window, thus fixing the problem. Huzzah!