I just wanted to draw some attention to a potentially fairly nasty Finder/Mac OSX bug that hasn't gotten the attention it probably should. A few days ago I posted on the latest Tiger release, what it fixes, what it doesn't. And in the comments section of that article, two people wrote in about a problem wherein the Finder loses the creation dates of files saved to MS-DOS formatted disks. That is, any file saved to a Windows formatted disk (and I don't know if this only applies to fat-32 disks or all Windows formats, but I would suspect the latter) will lose its creation date, which will be set to nothing. It will simply be blank, from my understanding of the problem. And please be aware, I have not experienced this problem myself. But a number of people have. We don't hear about it much in the Mac community, because much of the Mac community tends to work only on Macs. To be affected by this bug, you'd have to be both working from Mac to Windows, and have a serious need for file creation dates. This is not everyone, but it is a serious problem nonetheless, and Apple should hear about it. Though I have not personally suffered from this problem (yet), I sincerely sympathize with folks who need to get things to work cross-platform. I have the need myself, and it can be a real bitch. But when basic functionality like the preservation of file creation dates begins to fail when working cross-platform, it's way more than a bitch. It's a fucking nightmare. A lot of people turn to Apple for cross-platform compatibility, because -- let's face it -- no one else is doing half as good a job as Apple in this arena. But sometimes it seems like it's the cross-platform arena that gets the short-shrift when it comes to Apple's priority list. This is understandable, I suppose. We're the minority. Still, when basic things go wrong, Apple should hear about it, no matter how small the affected group may be. And they should fix it. Promptly.
So, if anyone out there in Mac-Land is having a problem with this, I say go vent. If you want to do it here in the comments section, by all means, be my guest. But you may want to take a moment and let Apple know about your problem as well (and trust me, they don't read this blog). There are a few good places to do this:
- Apple's Mac OS X Feedback Page
Here is the best, and most appropriate, place to lodge a complaint or report a bug. Keep it business-like and polite, but specific and thorough. Vent someplace else.
- Apple's Discussion Forums
Here you might actually find some help for your problem (though I think this particular problem is up to the Apple Developers at this point). Help notwithstanding, enough complaints on the discussion forum are likely to escalate the problem in the queue of stuff-needs-doin'. So it's worth a shot.
- Call AppleCare (1-800-275-2273)
Again, a good place to get heard. It might be a pain. You might get put on hold. A lot. But if you've got the time -- and, of course, your machine is still under warranty -- this could escalate your cause up through the ranks of the Apple engineers. As always, be polite but firm. You may need to explain your problem to -- and humor -- a number of lower-tier help-desk types before you get someone knowlegeable. But it might pay off. Don't do this, though, unless you've got some time and patience. Trust me.
- Finally, spread the word
That's what I'm trying to do with this post. Start writing to forums and blogs of some prominence. MacOSXHints is a good one to post on. There's also The Unofficial Apple Weblog. Hell, there are a ton, and they're all more prominent than this one. Start hitting them up. No one likes bad press. Least of all Apple. The more noise people make, the more likely they'll be heard.
So, anyway, hopefully this does somthing to draw a tiny bit of attention to an easily-overlooked, but non-trivial problem. I'm pushing for you kids. If anyone hears of a solution, please post it here in the comments. I'll do the same.