New Version (1.2.7) of Fetch Art Released

The changes are:

• This version fixes a Perl error on systems that did not have the Apple development tools installed. (The message looked like, "Can't locate LWP/Simple.PM...")
  
• Select All under the Edit menu now works. Also remember there is a Copy All Art to iTunes command under the Fetch Art menu.
  
• The problem with the installer not placing Fetch Art in the Applications directory, or creating a script menu in iTunes for some users has been corrected.
  

This version is still NOT compatible with Intel Macs. To donate and help the development of an Intel Mac version, please visit my donations page www.aric.org/fetchart/donation.html

To download the latest installer: www.aric.org/fetchart/

There's actually been renewed interest in Fetch Art since the release of iTunes 7. I figured that with iTunes including an album artwork download, I would no longer be contacted by people interested in Fetch Art. However, I've been told that the iTunes art download doesn't work as well as Fetch Art for several reasons:

• It requires an iTunes account, which not everyone has or wants.
  
• According to what I've been told it only works for U.S. customers.
  
• It actually isn't that great at finding artwork, leaving many popular albums without art.
  

Found a bug in the built in Mac OS X FTP server

So let's say you are using the FTP sharing abilities in Mac OS X to share a 5GB file.

Now, as a 5GB FTP download will likely get interrupted a few times before completion, you use the REST (restart or resume if you like) command to resume the download from where it last stopped. That will work fine if your download is less than 2GB. It appears for anything over 2GB it won't work, as the FTP server reports: "Restarting at 2147483647" no matter what. Apparently it can't go higher than 2147483647 bytes for the start of a resume download. I've done some searching and Mac OS X isn't the only FTP server to have this problem, however, many do work fine over 2GB.

If anyone is aware of a fix for this, let me know. Until then, I'll be submitting this as a bug to Apple in the next few days.