Convert | Adobe Photoshop CS3 | Fastest PS (to crash)

Adobe Photoshop CS3

Edit and transform your own images.

Version: 10.0.1

[ Views: 1134 ]

Fastest PS (to crash)

Feedback Type: Review

Contributed by: rcfa Monday, December 18 2006 @ 01:17 AM PST

Product Platform: MacOSX

Used Product For: Over One Year

Recommend Product: NO

The speed increase is enormous: I have not seen a version of Photoshop crash faster than this one. In fact, it crashes so fast, the icon in the Dock doesn't even have time to bounce once.

Adobe belongs into the programmers hall of shame. This is at least the fourth major Photoshop release that's "native" to Mac OS X, and still Adobe can't manage to make it run on HFSX (the case sensitive version of HFS+) or any other case-sensitive file system, even though Apple keeps reiterating to developers at WWDC they should not make any assumptions about case-sensitivity or lack thereof, and despite the fact that this bug has been reported dozens of times with previous releases of Creative Suite and its predecessors.

Further, if you program cleanly, it automatically "just works". A programmer has to go out of his way to write dirty code to make it break based on case-sensitivity issues.

The fact that Adobe can't get something that simple and trivial right gives you a general idea about the quality of their code. If this were a car, it might go fast, but if you'd open the hood, things would be held together by duct-tape, not by stainless-steel clamps.

Too bad, it's so difficult for the average computer user to "open the hood" of software.

Shame on Adobe, tripple shame!

Overall Rating:

Ease of Use:

Support:

Features:

Quality / Stability:

0 of 4 users found this helpful.

Rate this Review

Was this Review helpful? Yes | No

Comments

Re: Fastest PS (to crash) - Riot Nrrrd™

This comment is very apropos. I installed CS3 Beta onto a case-sensitive, journaled HFS+ filesystem (HFSX) and found that it wouldn't fire up.

About an hour and zillions of symbolic link kludges later, I got it to work. Basically everywhere under the CS3.app folder whenever you find directories called "resources", "macos", "support", "versions", and "a" (under Versions inside the Frameworks) you have to make symbolic links called "Resources", "MacOS", "Support", "Versions", and "A" respectively. Thank goodness I know how to get "under the hood" and use ktrace(1) on the actual binary!

Then you have to make similar links in the Frameworks directory for all the Frameworks that ended up with lower-case names on a case-sensitive filesystem (e.g. "abobe_registration.framework" needs a "Adobe_Registration.framework" symbolic link, etc.). It's a nightmare to get this to work! Hello Adobe! Wake up!

Even with that, it doesn't work completely - the Adobe Crash Reporter app won't initialize, I get this message:


Adobe Photoshop CS3[13453]: DebugAssert: Adobe Crash Reporter: theFrameworkBundle != NULL err AdobeCrashReporterInitialize: Couldn't find the com.adobe.AdobeCrashReporter framework[/Users/rquindoy/Perforce/esgqs/public/CrashReporter/Mac_2.1/AdobeCrashReporterFramework/main.cpp:376]

If I try to run the binary of the Adobe Crash Reporter app directly, I get a strange message:


% ./Adobe Crash Reporter

Adobe Crash Reporter[13589] No Info.plist file in application bundle or no NSPrincipalClass in the Info.plist file, exiting

This error is strange because it never actually tries to open the Info.plist file when it runs, and if you look upstairs in the Application Bundle, there it is!


% ls ..

..:

Frameworks@ MacOS@      Resources@  macos/
      
Info.plist  PkgInfo     frameworks/ resources/

And NSPrincipalClass is present in the Info.plist file, so I don't know what it's b*tching about. A real head-scratcher ...

Another thing to realize is that your old PowerPC Plug-Ins (like the stuff you'd add to Plug-Ins -> Import/Export for scanners, etc.) won't work ... that means the Digimarc stuff doesn't work out of the box, and for me personally, I mostly use Photoshop just for scanning photos and retouching, and right now I can't use my Canon ScanGear CS 7.0X Plug-In (since that's PowerPC-only) to read from my Canon N1240U scanner with, so to a certain extent this new CS3 beta is almost useless for me. :-(

Reply to This

Wednesday, December 20 2006 @ 09:47 AM PST