Macfacts, Anything “Apple”
Lockergnome
Home

Archive for March, 2008

OS X Error Codes and What to Do With Them

Thursday, March 27th, 2008

Once in a while I get a phone call with a question much like this:

Customer: “I wanted to copy some files, but it doesn’t work!”

Me: “OK, do you get an error of some kind?”

Customer: “Yes, it says: Error 33″

Me: “Oh, OK, that helps” (to be honest I don’t have a clue because I don’t know every error code in OS X)

Most of the time after talking with the client I finally figure out that it’s a full disk or some of the files are corrupt, or something else, either way I get it fixed! Still I thought to myself; “Need to digg a little deeper into this error code thing”.

So I (finally) did and today I got pointed to a very nice overview on all the error codes in OS X. It’s an Apple document which gives you a good idea on what the error means. Just follow the list and you get pointed in the right direction.

Apple Document 9805

This could be very helpful when helping clients out. I’m going to learn some fairly common errors so that I can impress my clients by saying…

Me: “Ahh, error the good ‘ol -34. It means that your disk is full. Time to do some spring cleaning on your harddisk”

Client: “Wow, you are amazing!” (client thinks: “I have the best computer engineer in the world”)

Me (thinks): “Need to increase my hourly fees”

Follow me on Twitter: John van Leeuwen

Updates Lightroom and Camera RAW buggy

Tuesday, March 18th, 2008

Adobe dropped the ball on a couple of updates they released last friday. The bugs in the software could cause a lot of grief. Hopefully some of my clients did not installed the updates, otherwise it’s going to get a busy week. No phone calls yet, so fingers crossed!

The thing I can’t understand is that when you release an update you don’t test it thoroughly. I mean this is not a little company with one or two developers, this is Adobe!! They should now what to do and what is expected of them when they are releasing an update. Test, development, test, development, test, accept, release… How hard can it be?

Either way, the following bugs are discovered in this latest update:

EXIF Timestamp Error: There is an error in the EXIF time stamp update technology that causes Lightroom to believe that the files are out of sync with the correct time stamp as displayed in Lightroom. Any ensuing metadata update will attempt to incorrectly modify the EXIF time stamp in the original raw file itself. This is the only metadata field that Lightroom will write to an original proprietary raw file. This error will not impact the integrity of your image data.

The Camera Raw plugin: The Camera Raw plug-in also will incorrectly change the EXIF time stamp in files converted by the plug-in. The information written to the XMP sidecar files or XMP metadata in the converted files will remain correct.

DNG Conversion Error (Windows Only): With the latest version of the Lightroom 1.4 and Camera Raw 4.4 applications, Adobe has included technology to verify that the image data in a DNG file is unchanged from when it was originally converted to DNG. Unfortunately, when converting to DNG using Lightroom 1.4 on Windows, the application will write an incorrect verification tag to describe the image data. When Lightroom attempts to work with those files in the Develop module, the application reads that incorrect tag, believes that there is something wrong with the raw data and will present an error. Rest assured, there is nothing wrong with the integrity of your image data or metadata. For those that have already converted their files to DNG using Lightroom 1.4(Windows only) we recommend using the DNG 4.3.1 converter to convert the DNG files you’ve created with Lightroom 1.4.

Olympus Conversion Error: There is an error in converting Olympus JPEG files to other formats in Lightroom 1.4 and the Camera Raw 4.4 plug-in.
The recommedation is that you uninstall this update. Here is how you should do this:

On the Mac
Delete the Lightroom from the Application folder and delete the following file: Library/Receipts/Adobe Photoshop Lightroom.pkgL

On windows
Running the uninstaller would do the trick.

It’s a sad that users should deal with stuff like this. Especially when the lack in testing is to blame!

Follow me on twitter: Benignus