The Gizmo Report: One new iPod classic, two new iPod bugs
As I said last week in my post about Apple's iPod announcements, I ordered a new 160GB iPod classic as soon as the Apple Store was back online.
It arrived today (Monday)--five days later, from Shanghai--with my custom engraving. I think that's pretty darn excellent.
The iPod packaging has gotten a lot smaller. A box the size of those that contained my first two iPods (a third-generation model, then a fourth-generation iPod when the third-gen model died) could probably hold about six of the new iPod classic packages. I saw the new iPod nano packaging at a local Apple Store this evening, and it's much smaller--and very cool, since it presents the iPod itself under clear plastic.
Anyway, when my iPod arrived, I turned it on and selected English as my preferred language. After a few minutes of checking out the new menu designs, I hooked it up to my MacBook Pro, which started iTunes, and in turn, the iPod initialization wizard. That all worked quite nicely.
I left it doing the initial sync operation during lunch. When I came back, the iPod thought it was no longer connected to the computer, but the computer thought it was.
That was bug #1. After further study, I realized that iTunes thought the new iPod should not be used in disk mode (probably because that's the default configuration for a new iPod) but Mac OS X thought it should be (probably because my previous iPod, which had the same default volume name, was set to use disk mode). My clues were these: iTunes didn't have a checkmark in the "enable disk use" checkbox, but the iPod was mounting on the desktop each time I connected it.
The result of this conflict was that iTunes would tell the iPod to dismount itself as soon as syncing was complete, but the OS hung onto the notion that the iPod was present. iTunes continued to act as if the iPod was present, but trying to do anything with it would cause an error.

The error message associated with the disk-mode bug.
(Credit: Peter N. Glaskowsky)I decided that the best way to solve this problem would be to select the "enable disk use" checkbox. But this was not so easy. Connecting the iPod always started the sync process. When the sync process ended normally, or was terminated, the iPod was ejected by iTunes. Selecting that checkbox and clicking Apple while the iPod was syncing merely scheduled the change of mode to take place after the sync, but the iPod ejected first.
Ultimately, after trying several times, I managed to click the checkbox and the Apply button between the time the iPod showed up in iTunes and the beginning of the sync process. That solved the problem; my iPod now works normally in disk mode.
But I've been glossing over bug #2, which cropped up while I was trying to figure this one out. Sometimes, shortly after being ejected by the Mac, when the iPod menus appeared, the iPod would crash. Sometimes it locked up, sometimes it just rebooted. When it woke up again, sometimes it would be back to the language-select screen. Sometimes it just worked.
All these mount/dismount cycles, therefore, carried an extra risk--that the iPod would crash after being dismounted from the Mac.
To make a long story short, after watching the iPod crash, I realized it was crashing at exactly the same moment when--normally--the right side of the main menu would begin to display preview images taken from album cover art. My initial suspicion was that some piece of cover art in my collection was corrupted in a way that was no problem for iTunes but a fatal problem for the iPod. (iPod hackers, this probably means there's a buffer overflow waiting to be exploited. If you figure it out, please give me credit for discovering the original weakness--I've always wanted to be a footnote in a security patch.)
Once I solved the disk-mode problem, I was able to uncheck the "Display album artwork on your iPod" checkbox under the Music tab of the iPod settings window in iTunes. After clicking Apply, iTunes told the iPod to remove all the album art, and that problem was solved too.
This isn't a fix--I still can't use album art on my iPod, which it's supposed to be able to do--but at least it's a work-around.
With all that grief out of the way, I can say I really like this little thing! It's two-thirds the thickness of my old fourth-generation model, which has only slightly more than a third as much capacity. The black metal face looks very classy; I wish that surfacing carried around the back of the unit too. The video support is neat; I doubt I'll use it much, but it's nice that it's there. The new menu design is a definite improvement, but mostly in the sense of being appropriate eye candy rather than being functionally superior.
The hard disk is a bit clattery, honestly; seek operations are clearly audible. Turning off the album artwork (and the Cover Flow feature, which is useless without album art) actually helped a lot with that by eliminating some seek operations.
Otherwise, this is just a nice set of improvements over my old 4G as well as the previous 5G (iPod video) products. I like it.
There's one trivial little thing I'd like to see changed--the backlight timeout setting goes up only to 30 seconds. I think a maximum of 3 minutes would not be out of line.
On Wednesday morning here on Speeds and Feeds, I'll review the Belkin TuneTalk Stereo for iPod. Although it says on Belkin's Web site that this product is compatible with the iPod classic (when you ask which Belkin products are compatible with this iPod, this gizmo is one of the products listed), I've found it isn't fully functional on this iPod. Tune in tomorrow for the full report.
Peter N. Glaskowsky is a technology analyst for The Envisioneering Group. He is a member of the CNET Blog Network, and is not an employee of CNET. Disclosure.
- Tags:
-
Apple,
-
iPod,
-
bugs,
-
iTunes,
-
Belkin TuneTalk Stereo
- Bookmark:
- Digg
- Del.icio.us





album artwork on your iPod" checkbox and see if the problem
comes back. You can always uncheck it again if the problem
returns.
backlight timeout setting only goes up to 30 seconds. I think a
maximum of 3 minutes would not be out of line."
While I totally understand your desire for this, you of course recall
Apple getting sued over their batteries not having a long lifetime.
Including a potentially battery-killing feature (if it was overused by
a moron, obviously) like that seems like just asking for trouble.
For some reason it also disconnects disk mode when sync starts... then windows tries to reconnect it... the vicious circle goes back and forth (ding... dong... ding... dong...) until I just finally said screw this and yanked it out of the cradle.
I havent went back in and messed with it since. I figure I will wait till either my battery is low or iTunes releases an update.
Using the "ignore it and it might go away" approach. LOL
slightly more than a third as much capacity."[/i]
Please explain how a 4 GB model has more than a third the capacity
of a 160 GB model.
generation iPod took a little over 48 hours Shanghai to Georgia.
My problem, it seems like 50% of the time that I plug something into or disconnect from the bottom, be it the cable to PC, FM transmitter, or Logitech dock, the iPod locks up. Sometimes the screen backlight stays on.. but it is always locked up and I have to do the "switch HOLD back and forth and Menu/Select" combo to reset the iPod, each time wiping out my menu settings.
It now now Wed, I have owned it for less than 6 days now, and I have had to reset the iPod due to lockups at least 24 times in those 6 days. Not a very good first impression. When I asked other co-workers who have the last gen iPod nano if they have the same problem, every one of them said YES, all the time. If this is such a rampant problem with the iPods why isn't it making more noise on the net? I understand it's not hard to reset it and nothing gets lost, but it is quite annoying none the less.
BUT it seemed that Vista no longer recognized my CD/DVD-drive ! Devide manager gives a code 10 error (?) and only tells that the device can't be started, because of 'driver not found'. On line checking for a driver says 'your driver is up to date'.
What is happening ? Who recognizes this problem ? Thanks for reading.
Chodko