We've had a few users tell us about performance lags that they're experiencing with their brand new 27" iMacs. Our own Casey Johnston even wrote a quick article about the problem last month. Now that everyone has had a few days to play with the issue and try the obligatory troubleshooting steps, we've been tipped about a possible solution.

One of our readers claims that this isn't just related to Flash playback... it's possible that this lag problem is consistent across the system. Flash taxes your system more than most applications so it would show the lag problem more consistently than another application -- thus making it look like a problem only with Flash.

The suggestion at this point: cycle your wireless connection. By turning AirPort off and on again, some people are seeing the computer regain responsiveness. Obviously this isn't a permanent fix because the issue will most likely appear again after you reboot your machine... we can't say if the fix will persist for the entire session, either; the problem could come back before reboot.

Fellow TUAW blogger Joachim Bean suggests that the issues may be something related to PCI Express. Both the AirPort and graphics card are using PCI Express to communicate with the system. There's a possibility that the lines of communication are crossing during use. I'm still betting on a software issue -- at least, let's hope for that.

Let us know if this helps, or any other possible solutions you might have in the comments.

Thanks, Simon!

Welcome back to Ask TUAW, our weekly troubleshooting Q&A column. This week we've got questions about using a joystick as a mouse, remotely accessing a Mac from a PC, creating zip files without the Mac-specific metadata, replicating certain Windows features, and more.

As always, your suggestions and questions are welcome. Questions for next week should be left in the comments. When asking a question please include which machine and which version of Mac OS X you're running (we'll assume you're running Snow Leopard on an Intel Mac if you don't specify). And now, on to the questions.

Update: Cnet reports that Apple is acknowledging the problem, while calling it "extremely rare."

There's a few threads on Apple's Discussion Boards describing a problem that's affecting some Snow Leopard users. An issue with the Guest account feature in SL appears to be chomping down on user data with extreme prejudice. Cnet/MacFixIt first took notice of the issue back in early September, but a 2nd report & a link from 9to5Mac have raised the threat level quite a bit.

According to affected users, the guest account's logout wipe -- a standard feature intended to prevent guests from leaving files on the machine -- is inadvertently clobbering the home directories of the non-guest accounts, with catastrophic results. One user writes, "I hadn't used my Guest Account since upgrading to snow leopard, and I accidentally clicked it instead of my user account this morning, to find that when I logged into my normal account ALL my files, settings, mail etc had been reset."

Worse of all is that he's not the only one.

MacFixIt reports that it isn't an epidemic, but readers have described the same issue in the comments to their post. For now, we offer this simple advice. First, make sure your backups are current. Secondly, turn off the Guest account feature if you're not using it (simple instructions here); some suspect that the issue is triggered by having it turned on prior to the SL upgrade. If and when the culprit is identified and squashed, we'll let you know.

Thanks to everyone who sent this in.

[Via Engadget]

Welcome back to Ask TUAW, our weekly Mac troubleshooting Q&A column. This week we've got lots of questions about syncing, as well as customized keyboards, sharing iPhone apps, managing iTunes, and more.

As always, your suggestions and questions are welcome. Questions for next week should be left in the comments. When asking a question please include which machine you're running and which version of Mac OS X (we'll assume you're running Leopard on an Intel Mac if you don't specify). And now, on to the questions

There's a great post at creativebits today listing some basic troubleshooting techniques. I like it because it lists some simple tasks that anyone can perform. Some of the tried-and-true techniques include:

• Restarting
• Quitting unused apps
• Installing updates
• Re-installing a misbehaving app

Back when I was a part of an IT team, we always checked the simplest solution first. Printer isn't recognized? Is it plugged in? How about turned on? You may laugh, but ruling out the easy answers makes things clearer and it often solves the problem. There are many more tips at creativebits so read the whole post.

It's true that the Mac OS still has its problems, but least we've moved beyond the Extension Conflict Hell that plagued many pre-OS X users. Or my other favorite, The Chooser. "That port is in use ...."

Good times.

Welcome back to Ask TUAW, our weekly Mac troubleshooting Q&A column. This week we've got questions about making photo contact sheets, adjusting properties for multiple files at the same time in the Finder, automatically managing settings based on location, changing the spell check language in iWork and more.

As always, your suggestions and questions are welcome. Questions for next week should be left in the comments. When asking a question please include which machine you're running and which version of Mac OS X (we'll assume you're running Leopard on an Intel Mac if you don't specify). And now, on to the questions.

Got troubles? Feeling the mobile device blues? Is your iPhone or iPod touch seemingly bricked without a recovery solution after the 3.1 update? Join us for an informal, interactive debricking-clinic this evening (14 September, 9:30pm ET) for hands-on therapy. We'll look into a variety of fix-it lore that may (or, sadly, may not) help you get your device back to working order. Check in with the discussion to see whether there's a tip that might help.

Click this link or "Read More" below to see & participate in the CoverItLive event.

In the wake of our earlier post on possibly time-bombed Time Capsules, there was some confusion as to whether or not the Time Capsule would be covered under any AppleCare Protection Plan you might have. The suggestion was made in the comments to Mel's post that extended coverage would apply, but we decided to double-check.

In short, it's true. if you have an AppleCare Protection Plan that is currently in-force for a Mac that you own, your Time Capsule is covered under that agreement. In fact, there is no need for the Time Capsule to be on the same receipt as the computer you purchased. As long as the Time Capsule is owned by you and "in use" along with the covered Mac system, it is covered along with the product for which you have an existing AppleCare Protection Plan.

Of course, this does not cover any damage you inflict on the Time Capsule, and it must not be hacked or used in any way other than it was intended. In other words, don't use your Time Capsule as a doorstop and expect to get AppleCare coverage on it when it breaks.

In addition to the Time Capsule, this "in use" coverage extends to the following products:

• AirPort Extreme Card
• AirPort Express
• AirPort Extreme Base Station
• Apple-branded DVI to ADC display adapter
• Apple RAM modules
• MacBook Air SuperDrive

And, naturally, while coverage does not extend to products that are subject to their own AppleCare Protection Plans (such as an iPhone, iPod, or, of course, another computer) it does extend to a single Apple-branded display if the display was purchased at the same time as the computer you're using it with. Otherwise you need to purchase a separate AppleCare Protection Plan for the display. Clear as mud?

All of the above is contained within the terms and conditions of the AppleCare Protection Plan for North America. In addition to those actual terms, an Apple Genius I spoke with said that coverage also typically extends to Apple-branded hardware on the same receipt as the covered computer purchase, and in general he and his colleagues endeavor to extend the best courtesy they can to their customers when the situation permits. So you may, in fact, receive coverage better than the terms within the agreement itself if you are pleasant, don't yell at the nice Geniuses and say "pretty please." Complimenting their shoes is always a nice touch. They also like chocolate.

If you'd like to check to see what agreements are current, you can click here to check them out, see when they expire, and read the terms and conditions yourself. If your agreement is not registered or is not listed under your Apple ID, you can check by agreement number and computer serial number. Also, if you are not in North America, you can read the terms specific to your agreement here -- many European countries have stronger consumer protections than the US does, and longer warranties may be standard where you live.

Welcome back to Ask TUAW, our weekly Mac troubleshooting Q&A column. This week we've got questions about Apple Up-to-Date program, non-black LCD monitors, video management software, connecting to an old PowerMac 7200 to salvage files, and more.

As always, your suggestions and questions are welcome. Questions for next week should be left in the comments. When asking a question please include which machine you're running and which version of Mac OS X (we'll assume you're running Leopard on an Intel Mac if you don't specify). And now, on to the questions.

Welcome back to Ask TUAW, our weekly Mac troubleshooting Q&A column! This time we've got more questions on migrating user data when upgrading to Snow Leopard, expanding Apple's built-in Dictionary application, accessing iPhone notes without Mail.app, and more.

As always, your suggestions and questions are welcome. Questions for next week should be left in the comments. When asking a question please include which machine you're running and which version of Mac OS X (we'll assume you're running Leopard on an Intel Mac if you don't specify). And now, on to the questions.

While I love the functionality of Apple's microphone-enabled headphones (both the Apple Earphones with Remote and Mic, which comes with the iPhone 3G S, and the iPhone Stereo Headset, which came with previous iPhones), I've found that the extra layers of functionality also bring extra layers of troubleshooting when they're not working right. For simplicity sake, I'll refer to said models as "iPhone headphones" in this post (non-volume control model pictured).

The most common issues I've come across pertain to the microphone. Unlike most non-microphone enabled headphones, which use a standard two-ring TRS connector (tip, ring, sleeve), the iPhone adds an extra ring to support microphone functionality. This is what the hardcore audiophile refers to as TRRS (tip, ring, ring, sleeve).

But if your pockets are consistently filled with lint and dust (or tater tots if you happen to store them there), that extra ring won't make full contact with the iPhone's headphone jack. Which means that you, unfortunately, will lose microphone functionality.

One way to fix this is to remove any dust or lint trappings in the phone's jack. I've found that wrapping a toothpick with a thin layer of toilet paper and brushing it lightly against the walls of the headphone jack helps out a great deal. It's also important to not dip said toothpick in water or moisture. There's a moisture sensor in the iPhone's headphone jack. When exposed to moisture, it changes color and could potentially void your warranty. Also, the usual disclaimer in do-it-yourself scenarios apply: you're doing this at your own risk, so proceed with caution.

My MacBook Pro and I had a bit of a rendezvous this past weekend. She's a 15 inch Core Duo with 2GB of RAM. Although she'll occasionally get as hot as a toaster oven (leaving red marks on my lap at times) and mooed like a cow when we first met, she's been a consistent workhorse for me.

But her hard drive needed a transplant. Sick of her sluggish performance and hard drive clicking noises, I decided that it was time to fix her up. So, I replaced her 320GB hard drive with, surprise, a 320GB hard drive -- this time a Fujitsu model instead of the Toshiba it replaced. Not because I thought the Fujitsu was any better than the Toshiba it'd be replacing, but because it was the least expensive drive I could find.

Although the hard drive installation went successful, it wasn't without its fair share of bumps along the road. Hopefully, the bumps I experienced could provide many some guidance on what to do as well as what not to do when upgrading your hard drive.

Welcome back to Ask TUAW, our weekly Mac troubleshooting Q&A column! This time we've got questions on migrating to a new Mac, using a Time Capsule for wireless backup, speeding up podcasts, syncing two Macs, and more.

As always, your suggestions and questions are welcome. Questions for next week should be left in the comments. When asking a question please include which machine you're running and which version of Mac OS X (we'll assume you're running Leopard on an Intel Mac if you don't specify). And now, on to the questions.

A few weeks back, Microsoft released its Service Pack 2 update for Microsoft Office 2008 for the Mac. While adding a host of features and refinements (such as Custom Path Animation in PowerPoint and increased speed and load times in Word and Excel), the service pack apparently packed too much of a punch.

The update has prevented some Open XML files from opening, for which Microsoft provides the following suggestions, and I've done a bit of MS-to-English translation (with apologies to DF)... read on to get the gist.

Welcome back to Ask TUAW, our weekly Mac troubleshooting Q&A column! This time we've got questions on using an AirPort Extreme as a wireless to ethernet bridge, automatically backing up a USB flash drive, building smart playlists in iTunes, migrating an iTunes Library and more.

As always, your suggestions and questions are welcome. Questions for next week should be left in the comments. When asking a question please include which machine you're running and which version of Mac OS X (we'll assume you're running Leopard on an Intel Mac if you don't specify). And now, on to the questions.