-
1. Re: Dreamweaver (CS4) interface got corrupted :-(
Lon Winters Sep 14, 2009 5:39 PM (in response to Ziggizag)I hate to be the one to point out the obvious, but how about uninstalling Nero?
-
2. Re: Dreamweaver (CS4) interface got corrupted :-(
SnakEyez02 Sep 14, 2009 5:43 PM (in response to Ziggizag)You need to delete the preferences file. Unfortunately I use a Mac so the process is a little difficult for me to explain here, so sending you to a KB article should do:
http://kb2.adobe.com/cps/401/kb401102.html
Just realize that you don't have to do this for every program, just the one that is affected.
-
3. Re: Dreamweaver (CS4) interface got corrupted :-(
Nadia-P Sep 15, 2009 12:07 AM (in response to Ziggizag)If Dreamweaver is behaving in an odd way, it frequently means you have a corrupt personal configuration folder.
Close Dreamweaver, locate the personal configuration folder, and rename it.
When you restart Dreamweaver, it should create a new configuration folder with all the program defaults.
For details of how to find the configuration folder, see this page in the Dreamweaver FAQ.
-
4. Deleting configuration folder is not helpful :-(
Ziggizag Sep 15, 2009 2:50 AM (in response to Nadia-P)Thank you all for your kind help but alas - I deleted DW configuration folder, restarted application and found the corrupted interface again.
Honestly - there must have been something go wrong with the system I suppose as I think interface elements are often system-dependent. And when I look at the DW now I can see a lot of subtle corruptions here and there like this one:

As you may see - page title font is not as usual (looks a bit smaller than normal), source code and styles panels titles are a bit "cut" - you can't see lower part of letter "g" for instance (in the word "dialog").
Is it possible that some system DLL file has been overwritten with a version not fully compatible with DW4? Any idea which one?
There are DLL files like ctrl32.dll and Ctrl32.ocx in Windows what normally may exist side-by-side in multiple versions and these libraries contain regular system control elements definitions like labels, text fields, combo box, etc. How about Dreamweaver - does it use some Adobe proprietary controls or what?
Anyway - there is no Side-by-Side generated errors in the Event Viewer application log, so activation context generation must have been fine for all Dreamweaver dependencies... or there are no explicit restrictions in the application manifest, so SxS is unable to catch assembly discrepancies...
Any ideas?
Rgs,
Ziggi
-
5. Re: Deleting configuration folder is not helpful :-(
Nadia-P Sep 15, 2009 3:06 AM (in response to Ziggizag) -
6. Re: Deleting configuration folder is not helpful :-(
A.Translator Sep 15, 2009 5:57 AM (in response to Nadia-P)Thanks, Nadia, I thought my problem was finally solved, but I cannot find the settings mentioned in then KB note. It does not say which Windows version they are talking about.
My Windows Vista Home Premium cannot do this:From the computer's Start button, choose Settings > Control Panel > Display. I can get to Display by right clicking on the Desktp, though, but that does not lead to the Properties etc.
Is Settings not the same as Control Panel anyway?
(It does not help that I have a Dutch Windows here, but I normally don not have any problems following advice given for the English version)
-
7. Re: Deleting configuration folder is not helpful :-(
Nadia-P Sep 15, 2009 6:25 AM (in response to A.Translator)Hi Adriana :-)
Just tracked it down as I use Vista as well.
Control Panel>Personalization>Window Color & Appearance >Advanced tab
See if there's anything there that may need changing.
-
8. Re: Deleting configuration folder is not helpful :-(
A.Translator Sep 15, 2009 6:50 AM (in response to Nadia-P)Thanks for the tracking down. I got to the Advanced tab but none of the options in the drop down menu seem to apply. It seems one can adjust font and font size for several Windows-windows etc. but that is no good to me.
Anyway, thanks again but never mind. I don't understand why Adobe redirects us to Windows Settings when it is obviously perfectly possible for them to design a UI that does not get maimed when the dpi is set to larger. Just look at the property inspector in CS3 for example... Why didn't they just let it be? -
9. Problem solved - thank you, Nadia !!!
Ziggizag Sep 15, 2009 9:28 AM (in response to Nadia-P)Thank's a lot !
Setting CONTROL PANEL -> DISPLAY -> TEXT SIXE SMALLER (100%) has solved the problem !
It was incidentally set to MEDIUM (125%, default).
Indeed - Adobe should be more explicit in communicating this issue to its customer. It's really hard to guess default system setting may corrupt application performance !
Best regards and thank you for your excellence!
Ziggi
-
10. Re: Problem solved - thank you, Nadia !!!
Nadia-P Sep 15, 2009 9:32 AM (in response to Ziggizag)You're welcome :-)
Pity Adriana's problem can't be fixed so easily.
-
11. Re: Problem solved - thank you, Nadia !!!
A.Translator Sep 15, 2009 2:02 PM (in response to Nadia-P)Nadia> Pity Adriana's problem can't be fixed so easily.
Yes, especially since the problem is not just Adriana's :-)
But kudos for Nadia!





