New
#31
No Changes
Got working finally, have to wait for long time for potoshop to open and then when i reopen it doesn't take any time and showed stoneage image immediatelty. I am still have problem in closing tough. Now it takes long time to close and goes on waiting.
Not sure for how much time Photoshop will open immediatelty as it happened before also but after some time it again started taking long time again to open. Anyways thanks to all for using your valuable time to help me :)
Just as I said after restarting windows, the problem appears again and it doesn't seem to open even if I wait longer.
Hmm.. I download the trial version from Adobe.com. Why?
yeah, I extected before running. I think I am close to find solution. Last couple of days Photoshop was working fine without any loading problem at startup (there was loading problem at closing tough and it is not solved yet). I didn't enter the key neither I did anything with Product key. I was running trial of 30 days but somehow when I click help, the activation, registeration, deactivate options were disable (I mean I was not able to click then and they were grey in colour unlike others). Yesterday, Suddenly I got error in PS when it was opened for long time that there is some problem with licensing and it needs to reinstall. And from then loading at startup problem appears again and it never opens. I did some research and found license error was because it's service was disable (Run>Service>Flexnet License). I enable it's service but no changes in long loading of Photoshop and when I disable service I got License error and PS closes.
Hopefully someone can solve it now
I had a problem with CS3 and Windows 7 on an AMD based machine. I am running a raid 0 and used the onboard AMD controller to configure it. CS3 installed without an error (all 5 times on two different OS) but when I went to launch PS the activation screen never did come up to allow me to fill it out. I found an old post that someone was having the same problem with CS3 and XP when using a raid configuration. I switched to the Gigabyte raid controller and the problem was solved. I have no idea what difference it makes but it worked for me.