This happened to me a while ago.
My Digital Rebel images started having the prefix _MG_ instead of IMG_.
I figured I'd run by some strange numbering threshhold. It was odd though. Sometimes I'd see IMG_ again ...
It bugged me.
I should have googled it long ago. Photo.net explains - this is what Canon does when you switch from sRGB to Adobe 1998 RGB color space. It's a JEITA specification mandate. I probably see IMG_ when I shoot JPEG instead of RAW.
Thanks photo.net.
Last June I put Google's Blogger on the Dead list, in part because of the lack of a mobile template. This morning Blogger in draft offered me a mobile template.
Blogger isn't dead after all.
It wasn't designed to support parental control and supervision, but Google's new email delegation function is very helpful (emphases mine) ...
Google Apps update alerts: Email delegation now available for all Google Apps customers
.... Administrators must first enable mail delegation by checking the 'Mail Delegation' checkbox under 'Email Settings' in the administrator control panel.
To enter a delegate, users can select the 'Accounts' tab under 'Settings' in Gmail and click 'Add another account' to enter their delegate's email address.
Once the delegate is signed into their own own Gmail account, they can then access the other person's account from the account selection menu at the top of Gmail....
You can only add delegation accounts that are a part of the Google Apps domain, you can't add external Gmail accounts.
It takes a while for the "account selection" menu to appear. About fifteen minutes after I set up delegation on my son's account a small arrow appeared to the right of my bold email address on the top right of my Google Apps Gmail page.
In fact currently my son does not directly use Gmail, it's just an IMAP service for OS X Mail.app. Only I know his Gmail password. So this doesn't let me do anything I couldn't already do, but it's much easier to monitor his account.
Our 3 yo Dual USB MacBook (Intel dual core) is having intermittent wake from sleep problems. It's on a WiFi network and running Leopard - 10.5. On lifting the lid it spins up then hangs with a faint blue screen. There's no cursor.
I haven't found a fix yet, but here's a list of what I've tried [4]. They're listed in the order I'd suggest. Of course the first thing to do with any ill-behaved machine is to check that your backups are good...
I'll update this post with the eventual outcome. As of this moment I'm trying Permissions [1] and SMC reset (more likely to help) and I'll try run the hardware test tonight in loop mode.
Update 12/18/10: The hardware test worked. The problem is much better. I wouldn't say it is perfect, but clearly some of the above measures helped. The two I'd most favor are "clean out list of remembered WiFi networks" and "reset SMC". I suspect this problem is less common with 10.6 and that, at least with 10.5, there are many contributing factors to "wake from sleep" failure. The fixes I made reduced the frequency, but it will still occur.
By way of comparison, there were NEVER any issues with the pre-hibernate sleep mode of 10.3 and MacOS Classic, but XP sleep mode is completely unusable. (I've no experience with Win 7 sleep.)
Update 6/17/11: This problem resolved. I think it was finally fixed in 10.6
See also:
-- footnotes
[1] OS X has reams of permission related issues. I have never, however, seen repair permissions help with any of them, much less anything else. It always finds things to "repair", but the "repairs" fix nothing. Repair Permissions is the OS X equivalent of a disconnected thermostat. It's there to distract the customer. Still, when all else fails, I suppose it's worth trying. Onyx will conveniently run Repair Permissions.
[2] Safe Boot, loop mode hardware test and zap PRAM all need a wired keyboard. There are terminal workarounds for Safe Boot.
[3] An Apple identified cause of wake from sleep issues - Intel-based Macs: Resetting the System Management Controller (SMC): "A portable Mac doesn't appear to respond properly when you close or open the lid." I have noted that sometimes the green light on my magsafe connector doesn't come on ...
[4] An infamous Discussion thread on MacBook Pro problems is a good source of ideas.
[5] I had at least 20-30 in my machine. I removed every one.
[6] I have done this in the past, but not on this machine.
[7] I had a leftover version from when I used a Win XP Retrospect Pro backup server. I had to find an old installer to safely uninstall this low level app that runs on startup.
Credit to the data freedom team at Google - the new OS X web uploader can also download albums and even ALL albums - including video.
Does any other free image service allow such easy download of "all albums"? (I pay for extended storage, but most don't)
Joel Barriere's Onyx troubleshooting utility for OS X is free. It comes well recommended, so when my main machine was misbehaving I tried it again.
This time the Onyx startup test told me I had a drive directory structure problem. I was a bit surprised; It's been years since I ran into something like that. Onyx recommended I run disk utility from my 10.6.2 installer disk.
I was lazy, so I tried safe boot instead. Safe boot won't work with a wireless kb, so I plugged in a wired kb and held the shift key down on restart. Surprised again -- it didn't work! I thought safe boot would run fdisk if it found an error, but I guess not.
So I gave in, found my OS X installer disk, and ran Disk Utility from there. It found a missing directory item and fixed it. The behavior has changed over the years, now if Disk utiliy fixes an error it runs a second time to look for uncovered problems. It was fine, but I ran it a third time because I'm that kind of geek.
I don't know if this had any relationship to my problems. My iMac's screensaver uses images hosted on a Time Capsule external share; for some reason it's been dropping the wireless share and failing to reconnect. This is a pain to debug, because there could be multiple causes and because, even at the best of times, OS X doesn't recover from dropped shares very well.
Still, I'm glad to have found something fixable. I made a donation to Titanium Software. I meant to give $10, but I didn't pay attention to the denomination so I gave 10 Euro (about $13 or so).
I wonder if Onyx will be sold in the OS X App store come January. Since it's always been donation-ware (free) that would probably cause some complaints, but this is a venerable and well regarded utility. Barriere surely deserves some revenue.
One of the problems with migrating from iPhoto to Aperture has been that all of the descriptions associated with iPhoto events and albums are lost.
In Aperture 3, however, projects now have descriptions ...
Working With the Project Info Window | Aperture Users Network
The Enter description field is a place to add descriptive text to add to your Project. This is a great concept, which we’ll talk about more in other tutorials, but essentially it’s designed to hold text to describe a whole Project as opposed to individual images in the Project. You can include any information you’d like here, and it’s searchable. For example, let’s say that you were doing a shoot for a client, but you didn’t want to add the client’s name to the metadata of your photos. You could add that to the Project description field and search for that later on.
Aperture 3 projects now behave like iPhoto events, they can be created automatically (fixed 1 day interval, less flexible than iPhoto). There's a good description of the project description field in this support thread. Along the way rwboyer mentions using a one page book template with a large text area for notes associated with project.
This is encouraging. So has Apple finally addressed a major issue with migrating from iPhoto to Aperture? Will event descriptions be saved in project descriptions?
I couldn't find any documentation on this, but it was easy to experiment. I created an iPhoto 8.1.2 Library with an annotated Event and imported that Library into Aperture. The iPhoto Library became an Aperture folder, and the iPhoto Event became an Aperture Project.
After I did this, the Aperture Project description field was ...
...
empty.
I would love to see Apple sued for false advertising when they claim Aperture 3 is a natural migration path for iPhoto users.
