1343 Views 11 Replies Latest reply: May 22, 2006 5:50 AM by a brody
Repair permissions, I understand, but full backup? Not everybody has time to do this every single time Apple or any other software company releases an update. We cannot deny that this is a bad update. Why point it back to the end-user when it is in fact the company that released the update that is at fault? You should never ever release anything that has not been tested at least with the most used applications (eg. Adobe Version Cue). This is like using end-users as beta testers for the updates.
I'm not part of Apple. But I can say this, with 23,000 compatible products (at one level of compatibility or another), imagine the time it would take to make even half those products compatible with every single update that needs to be released? Backup your data, and don't assume that all the products you use have been tested. The developer of the software you use, not the operating system developer is responsible for making sure their software is to spec with the updates. Edit: and I've written a FAQ on why you should backup more frequently. It isn't just an issue of compatibility:
If you don't backup more frequently, hardware failure, accidental data movement, can all lead to issues where a backup is needed. Don't ever assume your data is safe in one place only. Make backups.
UPDATE: I have a fairly regular backup schedule, however in this case, I simply went back and reinstalled Mac OS X 10.4.6 Tiger from the boot disk. I did not do a clean install, rather a reinstall of the Operating System. This kept me from having to reinstall my applications (which I was considering). In any event, it appears Apple's latest Security Update is the culprit.
Once restored to the Original Install without the latest Security Update 2006-003, all the applications that were problematic, are nw working perfectly!
Guess I'll just have to wait until Apple fixes their UPDATE.
I'm not sure that I agree with you on this one. All of the software in question worked fine with OS X 10.4.6, but once the "Critical" Update was installed, it stopped working. Therefore, I would submit that the Update caused a "break" in the application structure that ultimately Apple will have to fix, not the program developers.
Hey, but that's just my opinion.
Yet, if the update was a security update and it made some other program fail, it sounds like poor programming on the part of the third party programmer. It might even have been taking advantage of the security loophole which was closed. I would definitely tell the programmer this thing had failed under that update. I don't think any update from Apple would solve the problem if the programmer is unaware of the issue. Inform the programmer of the program which broke. They'll need to know that their program had some issue with code that doesn't work under the new security update. Otherwise they'll never know to fix the problem. It is their program, not Apple's.
Put it another way, let's say Apple did fix the problem for that program. Guess what might happen? 10 other programs might break. Why? Because Apple would be pitching to the lowest common denominator. A single program which doesn't work in an update where many others do. Regardless, believe what you like. I don't think the program will ever get fixed until people actually ask the programmer who made the program to fix it, and not the people who made the side program which just happened to break it.
I had the same problem with Adobe Acrobat 7 Pro. It is useless to contact Adobe because they will not work to fix the current problem with their apps that run under Rosetta. They say they are working in developing new versions of applications that will work native in the Intel Macs. So the solution to the problem is precisely to re-install OSX w/o the recent updates and perhaps not to update for a long time unless "its broken, then fix it"...
The fix suggested in macfixit of version tracker of going to Library then Caches and find the only cache with an ending of .lock and Trash that.
I found that Adobe Acrobat reader would not work properly and I had to Force Quit.
After trashing the .lock cache I tried openning an AAR file and it worked and I then Quit AAR normally. That is the extent of my testing.
With all Apples resources and their reputation to consider I would have thought that they would test software a lot more thoroughly before releasing it. They dont seem to be popping up with solutions to this problem either.
I could not find a file in "Library then Caches" ending of .lock to Trash it. My fix was to uninstall Acrobat 7 Pro and install and use Acrobat 6 (not the Adobe Readers, since I had no problem with these). I also could no longer use Netscape (which worked before the update and I needed for a couple of sites where I could not use Safari). I am lucky now to be able to use Firefox for these. I have not installed the firmware update for fear of opening another "can of worms" and I am still debating whether to do an archive and install the OSX again w/o the 2006-003 update. For my G4 powerbook, I have not installed the 2006-003 Security update because I do not have any problems there and I want to keep it that way...
Adobe issues seem to be mainly around Adobe Version Cue and use of Adobe software to save directly to server over AFP. If you are having trouble with the former, look in Apple menu -> System Preferences -> Accounts -> Startup Items to disable Adobe Version Cue. If the latter, there are solutions in this thread:
The issue seems to relate to Adobe still using Mac OS 9 comment fields in their saved files and Mac OS X not knowing how to handle them.
As for Apple's testing, there are over 23,000 possible software and hardware packages on http://guide.apple.com/ With 23,000 factorial possibilities of interaction. It would be impossible to test all of them. Even with 100 possible packages, you have 10^157 possibilities. Basically any software developer has to make a best effort and hope to hear back from their users when they make something that doesn't work. This being a user to user forum, I suggest calling AppleCare directly if you have an issue with how Apple's software works, or submit a bug report on:
if you just want to leave feedback.