|
Upgrading woes?v4 For downgrading from version 4 (or later) to an earlier version, please refer to the relevant section of the installation page. How to Uninstall?v4 Follow the instructions on the installation manual page. Problems during start up.v4 ABFA 4 stops working after a while or just after an upgrade. This indicates corrupted or incorrect startup files.If you experience this problem, there is a simple solution to it: 1) got to Home:Library:Preferences (where Home is your personal home folder) 2) remove the "net.publicspace.abfr4.plist" file (if it exists) 3) remove the "A Better Finder Attributes Pref" file (if it exists) 5) restart ABFA; it should work now I have trouble setting dates before 1972.v4 ABFA 4 can change your file dates to the distant past if you so desire, but this does not mean that Mac OS X will "accept" those dates as genuine. In theory, the creation date of a file is the moment when the file was first saved to disk; this is different from the creation date of the content of the file. So if you have scanned in a photo of Edinburgh in 1912 on the 5th of January 2008, the file's creation date should be the 5th of January 2008, not sometime in 1912.. or at least that's what Mac OS X assumes. ABFA will happily set the creation date to 1/1/1912, but when the Finder looks at files it does a few "sanity checks": when it sees that file it "reasons" a bit like this: "in 1912 there were no hard disks, so the file creation is obviously wrong. Let's correct it to X/X/XXXX". Unfortunately, Apple have never settled on the exact value of X/X/XXXX and when precisely the cutoff date for a "legal" date is. Different versions of Mac OS X will do different sanity checks and apply different corrections and this behavior changes apparently on the whim of the software engineer doing the fix "this time around": dates are set to nonexistent (the file has no creation date!?) or to a random date such as 1/1/1972, etc. The whole situation is further complicated by the fact that different parts of Mac OS X store dates in different ways (for instance in whole milliseconds from 1972, or in floating point seconds from 2000, etc.). The offspring of all this is that dates are liable to change in unpredictable ways based on which part of the operating system (Cocoa, Carbon, Unix, Kernel, Classic, etc.) last processed them. The conclusion is simple: it's not safe to use file dates before the 1st of January 1972 on Mac OS X. ABFA will set dates before then, but there's no guarantee that the Finder or some other program won't change the date afterwards by "correcting it" or simply miscalculating it. Something isn't working and I have FruitMenu, WindowShade X, Labels X or anything else using Unsanity's Application Enhancer installed. With Application Enhancer installed, all bets are off. This is "wicked cool" software specifically designed to undermine OS X's built-in protection features. Uninstall it and see whether the problem persists. Blaming other people for your bugs is plain bad manners, so in our defense let us quote George Warner from Apple Developer Technical Support: Our (Apple's) official policy is that we don't support APE'd systems. Period. The data miner that parses all the crash logs that are sent to us automatically ignores any report that has APE api's in the backtraces or dylb lists. Likewise If DTS receives a crash incident with API in the backtrace or dylb list we will not investigate it. Our "standard answer" in this case is to inform the developer that we don't support APE and that we'll only be able to help them if they can reproduce the problem without APE installed. I would suggest that you do the same for your "user X". ;-) Any other bug at all. Especially right after a new version is released. Email us immediately! It could be that many other people have the same problem. We can only fix the problems that we know about. We do test each version carefully before a release, but with so many different factors (OS version, installed products, specific hardware, installers, builds, etc..) to consider, it is always possible that a bug does get into a release. Unfortunately occasionally a bug affecting all users goes unreported for days and causes no end of frustration for everyone. Simply dropping us a line would allow us to fix the problem immediately.. don't be afraid of getting in touch! |
Download versions for Mac OS X 10.3, the combined A Better Finder Attributes/ A Better Finder Rename disk image or older versions for existing users. A Better Finder Attributes costs only $14.95 on its own, and $34.95 together with A Better Finder Rename. Get detailed information about our upgrade policy and purchase upgrades. User Manual
Blog This is the first place you should look for solutions to common problems, including how to un-install. |
