A fellow user in another (German) Forum asked for a way to change a photo file's creation date to the date the picture was taken. We also found out that touch also changes Mac OS X's creation date, provided that it's prior to the file's creation date. After a lengthy (German) discussion, I've created an AppleScript (see source links below) that takes care of (I hope) almost all possible cases:
If the photo's date is prior to the file's date, a simple touch is done.
If the photo's date is prior to today's date, the photo file is copied, so it gets today's date. Then it is touched.
Otherwise you have a picture from the future and I'd like to meet you soon ;-) No.. .The script complains and suggests you fix your time settings.
The script is usable in three ways:
Standalone: You will be asked to select the JPEG files that shall be changed.
As a droplet: You may drop JPEGs and folders on it and any JPEG file (recursively) found, will be changed.
As a Folder Action: Like a droplet, but working on all items added to the folder.
The script is in V0.3, and I have had no feedback yet, so I appreciate any feedback. I hope it's useful to some of you. The latest source can be found in this thread on the above-linked forums. The boards are in German, but the AppleScript itself is fairly obvious.
[robg adds: I copied the V0.3 version of the script and added it to our archives, just so there's at least one version always available. But be sure to check the forum link above for newer versions in the future. I have not tested this script.]
The Drag to save Mail attachments in Terminal hint reveals a security hole in Mail.app for FileVault users. When you drag an email attachment from a Mail message window to a Finder window, a temporary file is created in the hidden directory /private -> var -> tmp -> folders.UID -> TemporaryItems -> com.apple.mail.drag, where UID is replaced by your numeric user ID. This copy of the attachment is not encrypted. The temporary file will be automatically deleted at the next startup, but anyone who has physical access to the machine before then can easily retrieve it. Even after the file is deleted, it may be recoverable with a low-level disk editor. This defeats the pupose of FileVault.
I confirmed that when you save an attachment by clicking the Save pop-up menu in the Mail message window that no temporary file is created. So anyone who uses FileVault security (or, like me, keeps their whole /Users directory on an encrypted disk image) should not drag attachments from a Mail window, if privacy of those attachments is a concern.
The installation of the Security Update 2006-007 apparently changes the way SSL certificates are validated by WebKit-based applications. If you ever changed the certificate security policies, you may be unable to connect to SSL sites with Safari. A notable example is https://mail.google.com/mail/.
The fix is to revert to the default certificate security policy by removing the file ~/Library -> Preferences -> com.apple.security.revocation.plist.
Note that if you are not experiencing any connection problems, you do not need to perform this action!
My Spotlight menu was refusing to drop down -- clicking on the blue Spotlight icon on the right side of the menubar was not showing the mini Spotlight textbox at all. I tried trashing the Spotlight preferences file, but that was useless. However, using Onyx to clean the fonts cache was the solution -- after I did that, the Spotlight drop-down returned to life.
[robg adds: You can clean these caches yourself, though a tool like Onyx makes it much simpler. To clean by hand, remove the entries in the com.apple.ATS folder within the top-level Library -> Caches folder. I tested removing these myself to make sure nothing bad happened, and so far, nothing has.]
I just had a little problem occur with the use of launchctl. I was looking to reduce the amount of memory used on my system, and found a server process (bfobserver) that was using a great deal of real memory. On checking, I found in the developer's Read Me that this process is not needed if you are not using xgrid compilation. Great. I will stop it from starting. I used launchctl to change its startup via launchd with the following command:
The problem was I accidentally put a space between /System/Library/LaunchDaemons/ and com.apple.dnbobserver.plist. The result was a wild card to launchctl for that directory, and caused all of the daemons listed to be killed and all the daemon startups were disabled. This meant that the system was now unusable, and a reboot just ended in a blue screen.
To fix this, I had to come up in single user mode (Command-S on startup). Remount the root file system read/write, compare all of the LaunchDaemon entries with my other system, and then re-enable them. This was a time consuming and stupid mistake, but easily done.
[robg adds: Hopefully nobody else will need this hint, but just in case...]
As discussed in this recent hint, 10.4.8 added a new "zoom screen via control-scrollwheel" feature. Hold down control and spin your mouse wheel up to zoom in, then reverse the process to scroll back to the default 100% scale. Someone asked me if it were possible to use a keyboard shortcut to jump back to the no-zoom view -- they found it time consuming to have to manually un-zoom after looking at whatever it was they wanted to see. I thought the answer was no, it's not possible to use the keyboard, but after some experimentation, I found a solution.
Open the Universal Access System Preferences panel, and click the Options button in the Zoom section (and make sure Zoom is enabled!). Change the Maximum Zoom slider to anything other then its default left-most position. Note that whatever you set here will not affect the operation of the control-scroll zoom feature. It will, however, affect the zoom level you see when using the Command-Option-= Universal Access zoom mode. So if you use that zoom, too, then set the slider to 20x. Otherwise, just pick any setting other than the default. Click the Done button and you're, well, done.
After zooming in, just press Command-Option-minus to return to no-zoom mode. The screen will animate out as it un-zooms, but it's still much faster than control-scrolling back out to the normal view.
In OS X, the default permissions for items created by most programmes is -rw-r--r-- (644) for files and drwx-r-xr-x (755) for folders. This previous hint describes a useful method for changing the default permissions for GUI applications by adding an NSUmask property to the .GlobalPreferences.plist file to set a umask differring from the default 022. Unfortunately, this property only applies globally, and doesn't work when applied to the .plist files of individual applications.
This seems to be new in Tiger, but the default umask for the Finder can be set independently by adding a umask property to the com.apple.finder.plist file, either in an individual user's Preferences folder to apply to that user, or in the startup disk's main /Library/Preferences folder to apply to all users. The new permissions don't just apply to new folders -- they also apply to anything new created (but not copied) by the Finder including clippings, .xxxloc files, etc. However, note that folders created from the Save dialogues of other programs will have the default permissions of items created by that application.
First, props to this hint, which inspired and provided critical data for this hint. I have found that most, if not all, of the Olympus C-Series (and possibly other series) cameras' RAW formats can be supported by the dict entry for the C8080WZ.
The file that needs to be edited is in /System -> Library -> Frameworks -> ApplicationServices.framework -> Versions -> A -> Frameworks -> ImageIO.framework -> Versions -> A -> Resources -> Raw.plist. Use your favorite text editor to find a line containing C8080. Next, copy everything from that line to the line containing the term </dict>.
Once you have made a fresh copy of the dictionary entry, simply change the name to match your camera's identification string. For the 5050, this is OLYMPUS-C5050Z. If you don't know your camera's string, import an unsupported RAW image into Aperture and look at the camera designation in the metadata, or, do a strings command on one of your .ORF files.
If you're like me and don't want to waste a blank CD when installing Windows drivers via the Boot Camp Assistant 1.1.2, you can click Utility> Save Macintosh Drivers to Folder. You can then save them to a memory stick, network share, etc.