Maria’s Guides

Not a good combination.

I finally got around to installing my Canon LiDE 30 scanner — I know it’s cheap junk, but that’s all I need — on my iMac. Much to my surprise the driver installer didn’t see Photoshop as a place to install a plugin. So I manually installed it And then it wouldn’t work.

So there goes another hour of my time to troubleshooting the problem.

It appears that Canon doesn’t have an Intel-native plugin for the scanner. The plugin was written for Power PC Macs. And Photoshop CS3 won’t run Power PC plugins on an Intel Mac.

This explains why the setup worked perfectly well on my Dual G5 (did I mention it’s for sale on eBay?) but won’t work on my new iMac.

I found information for a workaround on the Adobe forum. (Can you believe actually found helpful troubleshooting information on Adobe’s site?) The topic title is Scanner not recognised in Photoshop CS3. Someone named Buko suggests running Photoshop in Rosetta and explains how to do it:

do a get info on the CS3 application and check the start in Rosetta button

I followed these brief instructions (see screenshot) and restarted Photoshop. And guess what? It worked.

Rosetta is an Apple technology that makes it possible to run non-Intel native or non-Universal Mac OS applications on an Intel Mac. As this Info window illustrations, Photoshop gives you the option of running Photoshop in Rosetta when necessary to ensure support for older plugins. You can turn this option on before you start Photoshop to access otherwise incompatible software-driven features. You can turn the option off and restart Photoshop when you don’t need those features.

I’m no under-the-hood programming expert, so I was wondering what the pitfalls of running Photoshop in Rosetta were. I Googled and found an article on tuaw.com titled, “Photoshop seems to run fine in Rosetta.” Although the article is nearly 2 years old, I agree that Photoshop seems to work okay.

The suggestion on the Adobe support forum was to run Photoshop in Rosetta only when you expect to scan something. This is probably a good idea, especially if you do a lot of intensive graphics processing. But there are other ways to scan that don’t require Photoshop at all. The CanoScan Toolbox software, which comes with the scanner, works fine and can send the image to Photoshop to be opened. That seems to be a good workaround, especially if, like me, you don’t scan often.

Information from Software Update.

This update provides important bug fixes and is recommended for 20-inch and 24-inch iMac models with 2.0, 2.4, or 2.8GHz processors.

For further information on this Update, visit http://www.info.apple.com/kbnum/n306707

My 5th generation iPod turns up its nose at my new iMac; later they become friends.

If you’ve been following this blog, you might remember that I recently replaced my Dual G5 Power Mac — currently available on eBay! — with a 24″ iMac. This was a big splurge for me, but one that I truly think I deserved after working my butt off on my Leopard book for months.

Anyway, the biggest task when setting up a new computer is moving data files across the network from the old computer to the new one. I did this in steps. One of the first steps was to move my iTunes data over and get my 5th Generation iPod — you know, the first video-capable iPod — able to sync.

Problems Abound

The data transfer went well. That wasn’t a problem. And hooking the iPod’s dock into the new machine was fine, too.

When I set the iPod in the dock, a dialog told me that the iPod was synced with another Mac. Did I want to sync with this one instead? I responded that I did.

And then the trouble began.

The computer began by telling me that it couldn’t sync 12 of my songs because I wasn’t authorized to play them. That’s weird. I only have one .Mac account, which I used to buy music on iTunes. Over the years I’ve bought 700+ songs there. Why are only 12 of them unauthorized? (And yes, I did authorize the new computer to play iTunes store purchases.)

(A side note here. This is one of the reasons I believe DRM has to go. It’s a pain in the ass to deal with authorization crap like this. And it’s one of the reasons I don’t buy much music on the iTunes Store these days.)

I decided to ignore the problem when a new problem came up. A dialog told me that I didn’t have enough space on the iPod to copy the music. How odd. I had the same amount of space on the iPod when I synced it with my Dual G5, which had the same exact iTunes library on it.

I decided to restore the iPod. I clicked the restore button in iTunes and went through the process. Restoring an iPod, in case you don’t know, erases it and reinstalls all the basic iPod software on it. My software was up-to-date and I had time, so I figured, why not?

Trouble is, when the restore was done, the computer still told me it didn’t have enough space on the iPod to copy the music.

Now I went into troubleshooting mode. I went to Apple’s Web site and found a support page that said putting the iPod into “Disk Mode” would help troubleshoot iPod problems. It then proceeded to explain how to do this. I followed the instructions.

I’m not linking to the page because I think it made the problem worse. Once the iPod was in Disk Mode, it stopped acting “normal” when connected to the dock.

Here’s how I define “normal”:

• When you place the iPod in the dock while iTunes is running, an icon for the iPod should appear in the Source list. This didn’t work. The iPod’s icon appeared on the desktop but not in iTunes, so I couldn’t access its settings.
• When you place the iPod in the dock while iTunes is not running, iTunes should launch and display the iPod’s icon in the source list. This worked fine and was my workaround for accessing the iPod’s settings.
• If the iPod’s icon appears on the desktop, the Enable Disk Use check box should be turned on in iPod options. (In the latest version of iTunes, select the iPod icon in the source list and click the Summary tab in the main window to access iPod options.) In my case, it wasn’t. I was able to access the iPod as a disk with the Enable Disk Use option turned off.

No, my iPod was not acting normal. It was acting weird.

But yes, I was able to sync my iTunes content.

My iMac Goes Catatonic

The worst part came the next day when I went into my office. My iMac is set up to start before I arrive so it downloads e-mail and podcasts before I get in. But that morning, all it showed me was a blank white screen.

Holy cow, I thought. (In reality, I used a different phrase.) I already broke my new iMac.

Various restarts — even with the Restore disk inserted and the C key held down — didn’t solve the problem. I was just reaching for the phone to call Apple for help when I realized that the iPod was sitting in its cradle with the big “Do Not Disconnect” indicator showing.

Screw that, I thought. And I ruthlessly pulled the iPod out of the cradle.

I restarted the iMac and it came back to life. Whew.

Evidently, the iMac was attempting to boot from the iPod’s disk. So now I had to remember to keep my iPod out of its cradle at the end of the day.

The Solution

The solution, when I found it a few days later, was pretty simple.

It wasn’t as if I found the solution online. I didn’t. If I did, I’d just link to it and write about something else this morning. Instead, I let my subconscious work on it, as it works on many of my problems. And while I was driving or showering or flying or doing something else that’s relatively mindless, my subconscious popped a suggestion into my conscious mind.

The iPod thinks Enable Disk Mode is turned on, right? Why not actually turn it on in iPod options?

So the next time I was at my desk, I Quit iTunes and put the iPod in its cradle. iTunes launched. I displayed iPod Options and turned on the Enable Disk Use check box. The iPod appeared on the desktop. I ejected the iPod, pulled it out of the cradle, and quit iTunes. Then I launched iTunes and put the iPod back in its cradle.

The iPod’s icon appeared in iTunes but not on the desktop. I displayed iPod options and saw that the Enable Disk Use check box was turned off. If you recall from the previous paragraph, I’d turned it on.

Very weird, but it’s working right, so who cares?

This is Tiger, Leopard is Next Week

Now in case you want to blame the problem on Leopard, don’t. All this happened under the latest version of Tiger. I haven’t moved my production machine up to Leopard yet. I wanted to get all the files and apps over first and make sure everything was running right.

Next week I’ll install Leopard on that machine. And if I have any problems or tips, you’ll be able to read about them here.