This discussion is archived
4926 Views 20 Replies Latest reply: Apr 17, 2006 4:01 PM by Michael Burke
Currently Being ModeratedApr 3, 2006 8:50 PM (in response to rtkramer_mac)Instead of "rolling back" which you would not be abe to do unless you re-install anyway, why don't you back up your data, and do a clean install? This way you will get a proper install of the update, minus whatever is causing your issues now. I do ths with every update. This update is fantastic. My Airport connection is strong, my computer runs cooler, etc. It takes a little time but is worth it.Macbook Pro 2.16 GHz Intel Core Duo, 100GB 7200, 2GB DDR2 SDRam, Mac OS X (10.4.5), 5G iPod, 20" ACD
Currently Being ModeratedApr 3, 2006 8:53 PM (in response to Peter K. Grether)To much pain. I clone my machine to an external once a week. I guess that would be a roll back of some sorts.A load of really expensive CRAP, Other OS, Stuff that will be useless in 6 months to a year
Currently Being ModeratedApr 3, 2006 9:27 PM (in response to rtkramer_mac)Then go ahead and roll back to the system, that contained something that caused the update to be a failure on your computer.Macbook Pro 2.16 GHz Intel Core Duo, 100GB 7200, 2GB DDR2 SDRam, Mac OS X (10.4.5), 5G iPod, 20" ACD
Currently Being ModeratedApr 3, 2006 10:13 PM (in response to rtkramer_mac)Instead of rolling back, you might want to try re-installing the update. But this time, download the "combo update" version as a standalone file, instead of installing automatically. Then try installing the combo updater, with the computer in as base a state as possible -- off network, no apps running, and as many peripherals removed as possible.
Even better if you can "repair permissions" before installing, and again after, using the Disk Utility by booting from the original install disk.
Macfixit.com currently has even more detailed instructions on getting a clean upgrade.G4/533,powerbook G4/667 iMacG4flat/MBP
Currently Being ModeratedApr 3, 2006 10:52 PM (in response to rtkramer_mac)Our studio has a number of machines at various points of update and we've made the following discoveries:
1. Mac OS 10.4.6 + Photoshop CS2 = crash when saving (file saves ok though)
2. Mac OS 10.4.5 (or earlier) + Photoshop CS2 = no crashes
3. Mac OS 10.4.6 + Photoshop CS1 = no crashes
In short, if you're running CS2 then don't do a system update (unless you don't mind restarting Photoshop every time you save).
Currently Being ModeratedApr 3, 2006 11:23 PM (in response to Adrick)Just upgraded to Mac OS 10.4.6 on my MacBook 2.0 GHz and restarted. I tried opening different image files from my Photoshop CS2, edited them, saved and didn't experienced any problems nor CS2 crashed.2.0Ghz MacBook Pro, Mac OS X (10.4.5)
Currently Being ModeratedApr 4, 2006 4:09 AM (in response to rtkramer_mac)Try repairing your permissions. Applications --> Utilities---> Disc Utilities. Click on the hard drive icon, then click repair disc permissions. That should solve your issue. If not d/l a utility called Cocktail and run that.Dual 2.0 G5 / PBG4 1.25Ghz / mini 1.5Ghz / MacBook Pro 1.83 (7200 HD), Mac OS X (10.4.4)
Currently Being ModeratedApr 4, 2006 4:17 AM (in response to rtkramer_mac)Try this:
- Open Apple Disk Utility (located in the utilities folders)
- Repair permissions
- Download the Mac OS X 10.4.6 COMBO installer for your system (Intel or PPC)
- Install it
That should do it.
Currently Being ModeratedApr 4, 2006 9:07 AM (in response to rtkramer_mac)i read your post too fast...thought you were running photoshop 5 (which requires classic). you actually CRASHED 5 times...sorry.
donMacBook Pro 1.83GHz; 12" PowerBook 1GHz; 4g Nano :-), Mac OS X (10.4.6), the usual sysadmin stuff
Currently Being ModeratedApr 4, 2006 9:33 PM (in response to rtkramer_mac)A number of common issues that crop up after incremental Mac OS X updates can be resolved by deleting specific cache files -- specifically kernel extension caches -- and restarting.
This can most easily be accomplished with a shareware utility like Tiger Cache Cleaner, but also bears a manual process which involves dragging the following files to the trash:
com.apple.kernelcaches (a folder in /System/Library/Caches)
Extensions.kextcache (a file in /System/Library)
Extensions.mkext (a file in /System/Library/)
com.apple.ATS (a folder in /Library/Caches/)
Files that start with com.apple.LaunchServices (in /Library/Caches)
You will be prompted to enter your administrator password when dragging these files to the trash. You may need to restart after moving them to the trash.PB G4 1.0, MiniMac G4 1.42 and MacBook Pro 2.0, Mac OS X (10.4.6)
Currently Being ModeratedApr 4, 2006 9:35 PM (in response to Adrick)
In short, if you're running CS2 then don't do a
system update (unless you don't mind restarting
Photoshop every time you save).
That's absurd. I've been running PS CS2 all day and night after the 10.4.6 update and haven't had any issues at all.
I used the combo update (I NEVER use the System Software Update) and repaired permissions after.
One thing, and this may not have anything to do with this particular issue (but is the cause of a Disk Utility problem), you might want to delete the "Legal" folder inside ALL your Creative Suite application folders. One of the foreign language html files has been know to cause havoc on otherwise healthy systems.
G5 2ghz X2 (Rev. B), G4 1ghz X2, iBook 500mhz Mac OS X (10.4.6)