Chrix Cox said:

And I wish I knew what forums povimage was reading - he seems to be drawing conclusions out of thin air....

Ok, Chris, I'll make this even more explicit than it was in my earliest post on this thread..

Scott Byer (Know Him?) said, at
"PS CS eventual slow down"
<http://tinyurl.com/2ja3a> :

Scott Byer - 12:22pm Feb 5, 2004 Pacific (#11 of 12)

Yes, there might be a problem, and we're still trying to collect enough information to reproduce the issue and to figure out exactly what's going on.

-Scott

And Dave Milbutt said in
"CS Problems"
<http://tinyurl.com/27gb8>

If you've read any of the threads on this issue you'd know that they suspect something is funky somewhere but they're having a hard time pinning it down.

Chris, it also doesn't help track down the issues when you blame it on users; as you posted in that same thread:

we have most of the systems. But the problems don't happen. That usually means it is some other software, or some non-standard configuration that the user changed that is causing part (or all) of the problems.

Since one of the suggestions Adobe has made to some users on the Windoze/M$ platform side is to "disable Hyperthreading in the BIOS," I'd say at least sometimes that it is Photoshop CS that REQUIRES a "custom configuration" in some cases to work properly. Moreso, your post indicates, as have the posts of other Adobe staff, that there is believed to be some problem, but it hasn't been isolated yet.

Beyond that Chris, I might note that as helpful as Adobe tech support has tried to be in my case (a dual PIIIe 1gHz system), ImageReady CS still doesn't even load fully.. It just dies! Their BRILLIANT answer after sending me tech documents on application crashes prepared specifically for PS 7.0? "Reformat your hard drive and do a clean install of PS CS and ImageReady CS. If you aren't willing to do that, we can't help you."

Funny thing is ImageReady CS worked fine in the Trial Version, but the Retail upgrade version has never worked since I loaded the software. Maybe I should have foregone the upgrade and simply hacked the trial version, at least the software would probably still work properly then!

I don't care how helpful the Tech Support people try to be, if the application doesn't work I deserve a partial refund for the missing ImageReady functionality.

To paraphrase a metaphor, talk about "the vendor always being right."

BTW: We all know that broader end-user/consumer BETA testing WOULD expose the software to more REAL WORLD prouction systems, and you'd see more of these problems then - when ISV's are supposed to isolate and address them. You'd think that Adobe would ensure the broadest possible BETA testing of its arguably flagship product.. These kinds of issues showing up in PS CS and mine in ImageReady CS, don't lead one to believe that sufficient time and effort is being spent on bullet-proofing during BETA. When I worked full-time in the IT biz, as a system analyst, EDP auditor, and computer security admin, I would have highlighted these problems and refused project completion payments until they were fixed. I DON'T pull stuff out of thin air, but THANK YOU for playing the toadying sycophantic defender of Adobe's corporate honor in this heart-warming little tableau, at the least it allows me to point out the facts and relate your own quotes.

HINT 1: Spend more time finding problems and fixing them and LESS time trying to shoot down people who can cite facts.

HINT 2: If are likely to need to contradict yourself, for whatever reason, don't leave a paper trail.

HINT 3: As was said in an old Monty Python sketch called "Crunchy Frog" when it was suggested that the chocolates bear on their box a large warning of some rather unusual components: "But our sales will plummit".. My answer is, as it was in the sketch, "F___ your sales, we've got to protect the public."

Keith

Joseph_Briggs

Replied in the following topics

PS CS and serious memory problems under OS X (Panther)