I recently upgraded from X6 to X7. I cannot get the edit bitmap feature to work, it is grayed out. I had this same problem when upgrading from X5 to X6. That problem was rectified by a re-install and reboot. After perusing the forum, I have tried, to no avail the following:
1.) Did a complete uninstall of all Corel products. Ran CCleaner to clean up registry entries. Did a complete reinstall. Rebooted. Did not fix.
2.) Went into both Corel Photo-Paint and CorelDraw and reset the "Associate" file extensions under Tools/Options. Made sure that CPT was selected in Corel Photo-Paint. Double checked the association in Windows explorer. Did not fix.
3.) Reset my workspaces (F8) command during start-up. Did not fix.
4.) Removed my workspaces under C:\Users\sccarter.DDS\AppData\Roaming\Corel\CorelDRAW Graphics Suite X7\Draw\Workspace. Restarted CorelDraw. Did not fix.
5.) Uninstalled Corel Windows Shell. Reinstalled Corel under custom options and installed the shell. Did not fix.
6.) Waved my magic wand, did a chant, said a prayer. Did not fix.
I am running Windows 7, 64 bit version of x7.
If any other users have experienced this same problem and was able to fix it, please forward the magic potion to me... it would be much appreciated!
Scott, this sounds like a registry issue.
Can you look up a few of these values in the Registry Editor (regedit.exe) ?
1) what is the value of this key?
HKEY_CLASSES_ROOT\.CPT
(Should be "CorelPHOTOPAINT.Image.17")
2) Assuming 1 was correct, can you look up this key:
HKEY_CLASSES_ROOT\CorelPHOTOPAINT.Image.17\CLSID
Should be a long guid here,
{a43cbf70-0ffa-3a89-42f9-11edfed78598}
3) If everything is ok so far, then have a look here:
HKEY_CLASSES_ROOT\CLSID\{a43cbf70-0ffa-3a89-42f9-11edfed78598}
You should see a LocalServer32 key with the value pointing to your PhotoPaint executable.
Let me know if you find any issues there.
Thanks,
Andrew
Hi all, I had exactly the same issue and this suggestion resolved it. Checked the registry as described by Andrew the COREL guy and found the Image.17 was missing. Open regedit. Find file as described. Right click the word 'Default' and choose modify. Change .15 to .17 and OK.
Not that I believe end users should be "digging around in the registry" to fix installation problems.
However, adding to this issue since my situation is similar where "edit bitmap is greyed out even though I just converted a vector to a bitmap within draw x7.
I looked into the registry settings and .cpt is fine and registered to ...Image.17. However when I try to look at CorelPHOTOPAINT.Image.17 I get an access denied message:
I'm guessing, based on this thread, that this is the cause of the problem.
My steps to reproduce:
So was wondering if this a result of x7 being a trial version?
... to follow up...
this is unbelievably crazy... the x7 uninstall failed/crashed and I'm now having to go through every single x7 registry setting, performing multiple permissions/ownership changes because I'm "locked out" of all of them.
Thanks Corel for completely wasting my entire afternoon (at least) I'll see if i can get it working again tomorrow.
Not happy about this!
I don't think it is a trial version problem. Usually, the trial version will behave exactly like the permanent version, until the trial expires.
But your mention of purchasing department implies a company installation of some sort, so perhaps your IT department has placed some sort of access restriction on either the registry or photopaint.
Hi,
Thanks, but I don't think the PC security setup is to blame. I install software frequently and this is the first time I've ever had a problem.
Additionally I just:
Nothing changed. Still can't edit a bitmap...
This literally makes the whole package completely unusable for me since it's the only way I can get accurate pixel to pixel export. (For example opening cdr in Paint or copy paste from Draw to Paint does not give accurate results. That's a different issue of course!)
Heading, very rapidly, towards a complete OS rebuild...
... just in case anyone was wondering I've checked the registry settings and tried all the registry hacks listed here... everything is "as it should be" - aside from the weird permission stuff that I'd guess is the actual cause of this problem....