Adobe trips over Photoshop copy protection

Send to a friend Print

Help more people find out about this story

Del.icio.us
StumbleUpon

Stephen Withers19 October 2007, 4:13 AM

What do you do when a freshly purchased copy of Photoshop refuses to install because it thinks it is already installed? Not even Adobe is quite sure.


Just because you've paid a significant amount of money for a piece of software, you don't always get the customer service you expect, as one Photoshop user recently discovered.

Geoff Wallace runs Macfixer , an independent Macintosh troubleshooting and training service. One of his clients - a professional photographer - called him in after experiencing problems installing a newly purchased Photoshop CS3 Upgrade.

It turned out that the CS3 beta had previously been used on that computer and the installer thought it was still present and refused to work, so Wallace started by trying the fixes suggested on Adobe's knowledge base. None of them worked and he was reluctant to try a wholesale nuking of Adobe-related files as other apps from the company were present, so he rang the tech support line - and that's where our tale really starts.

That call was made at around 12.30pm on September 6, and the agent said some research was needed and he would ring back. The return call hadn't materialised by 5pm, so Wallace called again. The agent had "no idea" according to Wallace, and requested a copy of the installation log, which was emailed within a few minutes.

No reply was received within 24 hours, so Wallace sent a reminder. On September 10, Adobe rang him to say they hadn't received the log files and asked for them to be resent, and Wallace did so. The same day, the client was invited to take part in an Adobe technical support customer satisfaction survey - not a very tactful move!

When Wallace rang again on September 11, the agent claimed the resent message wasn't received either. The log was sent again at 12.14pm, and an acknowledgement received at 12.48pm.

There was no further communication from Adobe by lunchtime on September 13, so Wallace sent another reminder. That fell into a black hole - presumably the same one that absorbed his previous emails - so he rang Adobe again at around 12.30pm on September 14, and was promised that someone would ring him back that afternoon.

4.40pm arrived, and Adobe hadn't called back, so Wallace placed yet another call, only to be told that the log file had been received (which had already been established) and that the issue was being escalated.

By now, over a week had elapsed since the initial call, and it's worth remembering that we're talking about a professional user of a professional program. And this is not an isolated case: other users are reporting the same problem on forums such as MacFixIt.com, Wallace says.

After another six days and six phone calls, Wallace finally got the agent looking after the problem on the phone, only to be asked for more information about the hardware and software configuration, which he provided.

By September 24, the customer was fed up with waiting and drastic steps were necessary. Wallace fitted a new hard drive to the Mac Pro, and installed the operating system and applications from scratch. That sounds extreme, but it was quicker then backing up all the user files and reformatting the original drive, and the client could use the extra storage space anyway.

On September 28, Adobe tech support suggested a process that had been tried and found lacking at the outset of this saga. When that was pointed out, the agent emailed a list of files and folders to be deleted manually. Wallace plans to try it next time - more out of curiosity than anything - next time he visits the client's premises.

It's possible that the client didn't correctly uninstall the beta, but you do have to question why the released installer wasn't capable of overwriting or deleting any traces remaining from the beta. "I've never come across a program that's so difficult to uninstall," says Wallace.

Even if we give Adobe the benefit of the doubt over the missing emails, Wallace has a point when he says "they've been very inefficient" in providing technical support.

Mark Phibbs, marketing director at Adobe Asia Pacific, said "From this feedback we acknowledge that in this instance our customer care has not met our usual high standards. We are sorry that we have inconvenienced Geoff and are working with him to resolve his issues as quickly as possible.

"Adobe prides itself on listening to its customers and works to deliver great products and a high quality of service. As a result, we are reviewing our customer processes and will take the appropriate action to ensure that this experience is not repeated.

"We appreciate continual feedback and encourage our customers and watchers to engage with us further to ensure that our customer experience is a positive one."


Post your comment



Reader Comments

RSS feed Email alert

Hammer of truth:

The problem is the way Adobe now writes Apple software. There are so many files everywhere in the library folder that sometimes they are easy to miss. In the old days when you wanted to delete a program from the mac, you just dragged it to the trash and that was it. The prefs file was still there, but savvy users would trash that too. Now you have so many different folders where they put libraries and other crap, plus in my case, when I was trashing files so that I could load CS3 on my macbook, I had to trash older Adobe prefs before the installer would acknowledge that I had removed the beta correctly.

It's a big headache if you don't run the "uninstall" program, worse if it crashes while trying to uninstall.

RON :

Use AppZapper to get rid of all vestiges of an application.

Carl:

That story is a bit unbelievable. Anyone that has access to and the courage to install a beta on a primary machine is either an expert or a fool. Assuming expert, the Adobe beta CS3 clean script was readily available from all of the Mac helpsites and Mac magazine sites. Due to the activation methods of CS3, the beta would retain information that would disable the release candidate.
Part of the installation process of the release candidate was a CS3 applescript that removed all traces of CS3 only files. Adobe is just being polite here. This was a simple procedure, widely publicized by all Mac media and the script was readily available. One could assume that a fresh, new user to the computer world may have missed this, but someone capable of acquiring and installing beta software must have had some familiarity with the online Mac community. A simple inquiry on a forum (which Adobe also has, as well as Apple, MacLife, MacWorld, Macfixit) would have provided a solution within hours.
So this guy runs MacFixer and is a troubleshooter? I think this guy needs to find a new line of work. This was not even an issue at the time and the script was standard procedure.

BetterBetaUser:

Never install beta software on a computer used for production. Never! Adobe told you shit could happen but you didn't listen. Next time use a different computer.

Brian:

I've had the same problem... and Photoshop CS3 is not the only application affected. All CS3 apps fail to run. I ran Adobe's uninstaller application, ran their uninstaller script, and manually deleted all Adobe files. None of these were effective.

Luckily I tested this on Adobe's demo versions an haven't yet upgraded my suite, and frankly, even though I've since changed drives and could probably safely install, I'm in no hurry to purchase CS3 as this isn't acceptable behavior from a 'professional' application.

Rula Lenska:

I am still amazed people are using Adobe (or Microsoft) products.

OPEN SOURCE, PEOPLE! I am super-sorry that guy had those problems, but all of these overly-priced, hard to install and uninstall apps must go! There are open source solutions for most (if not all) of these apps! If you must pay for an app, get graphic converter or something. It's SEVERAL HUNDRED dollars less!

--Rula Lenska
Poland.

PS: I still smoke fantastically LONG cigarettes!

Craig:

I fully agree about using good open source software whenever possible but when it come to professional level graphics work there is no serious alternative to Adobe software yet.

Justin:

I agree with Craig. There are often times when you have no choice but to use the industry standard. And graphic converter falls very short of providing the features and abilities photoshop affords. As an engineer, my only option is autocad as it is the industry standard despite its shortcomings.

And, again, you should always know the risks of installing any beta software. If your aim is to evaluate the software, wait for the full version to do the trial. Beta software should only be used for identifying and fixing bugs, not to evaluate features.

anonymous user Anonymous user