Step right up folks and feast your eyes on the rarefied, scarified, fluster-winged, double-throated pebkac.
Hey, Vivian:
Call Adobe Customer Service (link at the top of every forum page), and while you have your computer up and running, have them walk you through the process.
Not much anyone here can do to help you if all you do is squawk as loud as your beakety-beak will go.
There are thousands of people who have upgraded without any problems at all. Your situation must be special. Call Adobe and ask help. If your copy is legit, that’s what their customer service is there for.
This is just a forum of users like you. We’re not Adobe staff members.
And while you have them on the phone be sure to mention what a bunch of idiots they are that’s sure too speed the help process.
I agree w/ viv. the process shouldn’t be near as painful as it is for many…
(nothing wrong with a little venting.)
Uninstalling the demo copy was not a good idea. Why didn’t you just enter your licence key into the ‘demo copy’? While in demo mode, it asks you to do exactly this on every start-up—and it simply turns it into a full retail copy.
And within 30 days after entering the licence key you have to accomplish the Activation process. If you fail to do this your legit copy will stop working after 30 days. And it does tell you so on every start-up.
— Olaf
Being down is costing us valuable production time – so Phos4dots can keep his ill-informed thoughts to himself. Be a fan boi all you want – does not help the fact that a major corporation like Adobe have NOT thought through the installation process
Why reinstall ? Simple really, we only looked at a demo for Premiere CS3 – not the whole thing. PLUS, you’d expect that the one you download is the ‘very latest’ – you can have no idea how long code will have been sitting on a demo disk
Seemed the sensible thing to do, uninstall, clear out the system (System Mechanic), defrag, System Mechanic again – reboot – then reinstall the whole thing
Nothing wrong with the thinking…
….just Adobe’s install process that is knackered
ADOBE PROGRAMMING IN A NUTSHELL
After 25 years of the PC, and +10 generaltions of Premiere etc, NO USER should be asked questions about backing up their registry simply to get a product to uninstall.
<ends programming 101>
You are right of course.
A lot of people have had no problems but those that have had them have every right to be annoyed with an installer which needs computer expertise to be applied before it will work.
Adobe should be ashamed of the multiple cockups that have appeared with this CS3 release.
…. and of the deafening silence that’s followed. in the past we’ve (here in the forum) at least had help from the engineers right after a release. it’s been awful quiet lately. wonder if this is part of some new macroadobemedia stragegy or something…
(to be fair i have seen adam posting a few times, and a couple of people i didn’t recognize until they announced themselves as programmers/engineers, but for the most part it’s been quiet!)
When I have no answer for someone, or simply don’t care, I also remain silent. Actually that’s not completely true. I do answer my clients that have paid their money to me, expecting satisfactory service. I guess that is now considered "Old School".
Q
That would be a relevant simile, Q Photo, if the O.P. were addressing Adobe HQ and Engineers here, directly.
But that doesn’t mean I don’t agree with you. Even with difficult bone-headed jackasses for clients, if they pay up…ya gotta serve ’em the best you can.
The O.P. is yelling down the wrong damned hallway.
It seems that Adobe writes into the soppousedly protected boot record which can not be reached by mere mortals. This access should never be allowed by any program, but it seems like MS and Apple have given Adobe the access. Once Adobe writes there it can not be changed without special tools. PARANOIA SCREAMS by Adobe bean counters.
It seems that Adobe writes into the soppousedly protected boot record which can not be reached by mere mortals.
no, it’s worse. it apparently writes to an "undocumented" area. meaning, unallocated or marked as "bad".
and of the deafening silence that’s followed. in the past we’ve (here in the forum) at least had help from the engineers right after a release.
Let’s see:
1: Fired ’em all and moved development to India.
2: Moved them quickly to work on massive Flash upgrade to compete with latest MS attack. 3: All madly working on a service pack for things that should’ve been finished before release date.
4. They got sick and tired of people calling them incompetent and other
less than flattering descriptions.
Bob
While I agree that it is not polite to call names the fact remains that Adobe has released an upgrade with a number of flaws. It should be reasonable to expect customers to be upset. Let’s see: They can’t get it installed. They can’t keep it installed. And when they do manage to have it installed they can’t even print photos without a big hassle.
There simply is no excuse for these problems. Photoshop is suppose to make our lives easier. Is that not the reason for upgrades?
SOMEBODY dropped the ball. The printing issue alone is enough to cause a revolution. Why, in the name of all that is holy, was this changed?
Microsoft put out faulty X-Boxes. They then extended their warranty to three years. Adobe put out a very buggy Photoshop CS3. Hello, hello is there anybody in there?
Name calling is bad, but if the shoe fitsΒ
Q
4. They got sick and tired of people calling them incompetent and other
less than flattering descriptions.
that thought has crossed my mind too. π i’ve been my fair share of critical of adobe the company, but have always had and showed the utmost respect for the actual engineers in the trenches. especially those who’ve taken their own valuable time to hang out here and help with problems and give explainations for the way things work inside the app. pity some don’t see it that way.
I agree.
My criticisms are all aimed squarely at the strata of management above the engineers doing the real work, who have to abide by the constraints set by these people.
This was one of the reasons I left the aerospace industry, where the same thing happened.
