iPhoto bug: there is not enough disk space ... how annoying ...

Apple - Discussions - Error exporting iPhoto4 slideshow to quicktim

I think it's an iPhoto bug arising from multiple causes. I do think that if you change your free space (either increase or DECREASE it) iPhoto will often decide you have enough room.

Try mucking with your disk space (heck, try using up some of it) and let us know if it works. The most common problem is a corrupted image however, and the only fix I know of is to hunt it down by serial export attempts.

Most recently this happened to me when I tried to export 512 images. I divided the set into half and exported the first half. Then I did the same and exported the next quarter. I repeated the process until I identified a SINGLE photo that, when I tried to export, produced the spurious error. The photo appeared fine -- iPhoto reported the normal size, etc.

I edited the photo in iPhoto 4, making an arbitrary crop. I then reverted to original. I then exported ALL of the remaining images without an error.

As an experiment I returned to the original 517 photos and tried exporting them en masse. This time it worked without any error message.

I'm told iPhoto 4 had a disastrous development process and a brutally short timeline to get from nothing to something that could be shoveled out the door. If there's one single thing that shows Jobs persistent weaknesses, it's Apple's attitude towards this key piece of software.

Very cool portable ethernet device, on fascinating web site

RoadWired

Auto-Retract Network/ISDN Cord
Price: $32.95
In stock, ready to ship!



Click on any image to enlarge
If you need to connect your notebook to a network or high-speed hub, particularly when traveling, this is a must-have accessory. Seven feet of high-quality, "Cat. 5e" certified cord with RJ-45 (network-type) connectors at either end, stored in a protective housing. Pull out to use, push button to retract. Built-in adapter system adds amazing versatility (see specifics at right).

---

The phone connectors are wild. The only thing it needs is a crossover converter.

Members wanted: the Society for the Preservation of the True PDA (SPTPDA)

I moved this posting to a new blog dedicated to our society/cult.

Compucable FirePod Universal FireWire AC/DC adapter and USB/FireWire 12VDC charger kit (p/n FXU-PWR-KIT-DX)

Compucable FirePod Universal FireWire AC/DC adapter and USB/FireWire 12VDC charger kit (p/n FXU-PWR-KIT-DX): "3 pcs. FirePod Universal FireWire, AC/DC adapter and USB/FireWire 12VDC charger kit (p/n FXU-PWR-KIT-DX)"

---

I can't tell for sure from the description, but this $25 device might just charge my iPod, my phone, and my Tungsten E ...

Apple KB Fix: Mac OS X 10.3: Mail quits when you click Junk Mail

Mac OS X 10.3: Mail quits when you click Junk Mail

---

reset preferences.

Blogger Unofficial FAQ blog - archived version

Blogger FAQ blog

---

I couldn't find a more recent version, need to look further?

Fixing problems with OS X preference files (from Macintouch)

MacInTouch Home Page

Ben Levi's note yesterday about fixing common problems with Mac OS X preference files brought several tips:

[Byron Han] From the Terminal, you can issue the following commands:

find ~/Library -name '*.plist' -exec /usr/bin/plutil -lint {} \;

and it will scan all of the plist files in your Library directory to see if they are corrupt or not....

[Alan Goates] The nice thing about most preference files is that they are actually well-formatted XML with DTDs to validate against. You can
do this with any validating XML parser, but here's an easy and free way to validate them all in one command line.
First download Xerces for Java, then cd into that folder (i.e. 'cd Desktop/xerces-2_6_2') from the command line and type

java -cp xercesImpl.jar:xercesSamples.jar sax.Counter ~/Library/Preferences/*.plist

If the file is really corrupted, this should catch it.

[Andreas Junghans] I suggest running the following in a terminal window:
sudo fs_usage | grep 'Sherlock' | grep 'plist'

This line monitors all file system access (sudo fs_usage) and filters out everything except access by Sherlock (grep 'Sherlock') regarding preference files (grep 'plist'). Note that you will be asked for your admin password since monitoring file system access is not allowed for ordinary users.

With this command running, start Sherlock, and you get a nice output of preference files (ending in .plist) that Sherlock accesses. The preference file causing trouble will usually be in '/Users/[your username]/Library/Preferences' or '/Library/Preferences'.

[Randy B. Singer] The corrupted preferences problem in Mac OS X isn't as complex as the extension conflict problem in Mac OS 8/9, so dealing with it is not as difficult. All that is required is a utility program that can make a backup copy of all of your user preferences files when your Mac is working well, and which can substitute all of the good preferences files for the suspect ones when a problem arises. This [free] program does exactly that: Back up user prefs.