Photoshop CS2 and Enhanced Dialog problem
Wednesday, June 29, 2005 by Island Dog | Discussion:
When I would manually type in the extension such as .png, it would save it as a .png, but the file would be corrupted. I tried this several different ways with several different images, and the same happened with them all.
I went to the user forums on adobe.com and searched for a solution. I only found one other person with the same problem. This person mentioned he just installed Object Desktop and that's when some of his problems started happening. I unloaded windowblinds thinking that might be a problem, but Photoshop still would not save. Then it occured to me I have Enhanced Dialog installed. I went to SDC and uninstalled it, rebooted, deleted the Photoshop preferences file, and started Photoshop again.
Everything worked fine. Photoshop is saving as it should.
Reply #2 Thursday, June 30, 2005 6:21 AM

Reply #3 Friday, September 2, 2005 8:35 AM
I'm not sure but I could have sworn that I added Photoshop to the exlusion list and I still have the problem. I will have to confirm this when I get home to my laptop.
Reply #4 Monday, February 13, 2006 9:59 AM
i has this problem before too....after much discussion on the Adobe forums i was told it was because, at some point in the past i had installed tweak Ui, and the only fix was a complete re-install of windows...after much thought i eventually did just that and the problem went away...
i just decided to re-install enhanced dialogue,as it was useful, but i, of course, told it to exclude CS2, due to above problem...
now i have the same probelm as before...if you save any file in CS2, regardless of it's type, unless you specify it's file type, it will save the file without any file type extension...
i have completely un-installed enhanced dialogue, re-booted, and guess what? it hasn't fixed the probelm...
Enhanced Dialogue has permanently messed up my CS2...come on stardock, you have altered something somewhere and has affected and altered another program on my computer, and not a word of explanation to the above and no fix
i do not want to re-install XP again

Reply #5 Monday, February 13, 2006 10:07 AM
Reply #6 Monday, February 13, 2006 10:16 AM
| And have you learned a lesson about installing beta software on production systems |
yeah yeah...i'm a fool...
i will create a case, but with all the stuff on this forum about automated replies and lack of response, i'm not sure if can be bothered..
i've just un-installed then re-installed CS2, and no difference, so ED must change something on the OS level, and when you un-install ED it doesn't reset your system...please could stardock let me know what they changed and how to change it back? surely they know
Reply #7 Monday, February 13, 2006 10:31 AM
| i will create a case, but with all the stuff on this forum about automated replies and lack of response, i'm not sure if can be bothered.. |
I've gotten pretty good results from Tech support and even better since their new ticketing system.
If I were to rank "services" from Stardock they would be:
1. Development
2. Support
3. Documentation
And there would be some LARGE gaps between each item.

I think I ONCE (a few years ago) decided to call the SD office and got very satisfactory customer service.
Reply #8 Monday, February 13, 2006 10:47 AM

i'm going to go lie in my hammock, stare out at the caribbean on another lovely sunny day, enjoy a little down time and the world (and stardock) will seem a lovely place again after a few minutes

Reply #9 Monday, February 13, 2006 3:41 PM
http://www.adobeforums.com/cgi-bin/[email protected]@.3bbe17cf
Reply #10 Monday, February 13, 2006 4:13 PM
that worked !!!! fantastic....enhanced dialogue must alter this registry entry (please confirm stardock)..if so, why couldn't they have found this...
this is the regedit for anyone else with this problem
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\comdlg32\NoFileMru
change to 0 from 1
i really can't thank you enough

Reply #11 Tuesday, February 21, 2006 12:18 AM

Reply #12 Tuesday, April 18, 2006 8:11 AM
Reply #13 Tuesday, April 18, 2006 9:44 PM

Reply #14 Wednesday, April 19, 2006 10:40 AM
Whew, glad I found this thread. Installed ED fewminutes ago --- (hehehe I said ED) --- and Corel would crash on File Open. Uninstalled, no change. That little reg mod fixed it good. Thx a bunch. 
Reply #15 Wednesday, April 19, 2006 10:56 AM
The Photoshop problem was fixed in a build several months ago.
Reply #16 Wednesday, April 19, 2006 10:57 AM
----
A reboot will be required for the update.
Updated default settings. Details view, grid lines, full row select.
Fixed sizing issue when switching between large/small places bar.
Fixed template issues with mIRC DCC send dialog.
Fixed Photoshop saving to a different extension bug.
Fixed bug within settings dialog for default settings.
Fixed full row select not working correctly.
Fixed grid-lines not working correctly.
Fixed but with WM_NOTIFY when an app had a special hook or template.
7/11/05 14:01 32,768 enhdlginit.dll
8/05/05 8:35 233,472 enhdlg.dll
Please login to comment and/or vote for this skin.
Welcome Guest! Please take the time to register with us.
There are many great features available to you once you register, including:
- Richer content, access to many features that are disabled for guests like commenting on the forums and downloading skins.
- Access to a great community, with a massive database of many, many areas of interest.
- Access to contests & subscription offers like exclusive emails.
- It's simple, and FREE!







Reply #1 Wednesday, June 29, 2005 9:23 PM
Enhanced Dialog prevents Photoshop CS & CS2 (and InDesign CS & CS2 in the Export dialog) from actually using the file format you've selected in the Save As Type list. Instead, it saves the file as the same type used for the last successful save--probably a PSD. If you rename the file extension of your PNG to PSD, Pshop will read it (or if you examine the file in a hex editor or Notepad, you'll see the PSD file header).
I first noticed it with early CS2 betas (it affected Illustrator at that time, but no longer), but chalked it up to the fault of the CS2 betas (I didn't touch CS during that time, so I didn't notice until later that it affected that version of the apps as well). When the shipping release of CS2 hit with the same problem, I began trouble-shooting.
A few people (including yours truly) have provided feedback on these here forums about this and other show-stopper bugs in Enhanced Dialog, but thus far no response from Stardock to any of them.