Scary: Remove the activation crack and everything will turn to normal.
Just done a seach and found that.
It’s a genuine version from my work, and i havent tried to crack it.
Ill try reinstalling it and looking for keyboard drivers.
Cheers. 🙂
To quote from another forum: "Yes, you are using the Paradox Crack to avoid activation. Also every version of Photoshop CS from Paradox are beta versions.
R: "It’s a genuine version from my work". So you don’t want to activate it on your home machine. This is what activation was designed to reduce: "casual copying".
Good try, but new "keyboard drivers" will not help.
Why would he not want to activate it on his own machine? Both the license and the activation scheme allow for that. I currently have a copy of it installed both at home and at work, both are activated, and both are working wonderfully.
There are other legitamate reasons that this problem is showing up in. I believe I read a post by Chris Cox confirming this somewhere.
ID,
updating keyboard drivers have worked for a couple of users who we’re not using any cracks and experienced this issue.
There are other legitamate reasons that this problem is showing up in.
The only one so far is the keyboard driver needing to be re-installed.
-Scott
I hope Adobe is looking into that, how can you release an app that may screw up /or not work your keyboard drivers (however infrequent)?
Have you found which keyboard drivers are causing the problem yet?
Don’t you think that’s a bit unfair ID? Could you perhaps name for me the last software application released that was bug free?
Bob
ID,
There was no way we could have known that there would be issues with some users keyboards. The application was run on many hundreds of systems prior to release without a single case of the Ctrl key not working. Even now, there are relatively few users having the problem and fewer still who come back and confirm that reinstalling the keyboard driver did the trick.
–Steph
Robert, re:"Could you perhaps name for me the last software application released that was bug free?"
As far as I know I’ve never had a problem with Photoshop 7 (or 5.5 for that matter), Acrobat 4-6, Painter 7, Dreaweaver 1-6, OmniPage Pro (although their registration was poorly implemented), SystemSuite in any of its incarnations, ………….
Well, I’m glad I’m sitting this one out for the time being, first time I haven’t gotten the new versions on release of Photoshop, Illustrator & InDesign.
Photoshop 7 had several bugs in it when it came out. The one that I can think of off hand was that the cursor had this untimely habit of acting like it was about 20 pixels below where it actually was on screen. I really appreciated 7.0.1.
Dreamweaver maybe wasn’t buggy, but it certainly didn’t work the way it should have. (i.e., it was a huge memory hog, and crashes constantly.) This was especially the case in 4, which felt like it should have been released by Microsoft.
It isn’t a particular driver, just a couple of isolated cases here or there (I actually know of just one confirmed case myself) where the driver was probably in an unstable state already, and Photoshop CS just tipped it over the edge.
-Scott
You don’t know what you’re missing with InDesign. It’s a major upgrade.
Bob
Re: "You don’t know what you’re missing with InDesign. It’s a major upgrade."
No doubt, the service bureau I use will not be implementing IDCS for several months for use in production output, so ID 2 will do fine for the time being. I’m putting out two magazines a month, so I stay with the money.
The current crop of apps have served me quite well for the last year and I’m sure they’ve got at least another year of production time in them.
Jonathan: I’m not sure what was meant by Dreamweaver 4 being a ‘resource hog’, never caused me any trouble, but then I use multiple HDs, dualies, lotsa RAM and NT OSes.
