Monday, September 22, 2008

Corel Draw X4 Startup Crashes?!..a working fix!!

Now, I wont claim I fixed this myself, as I got the fix from http://designer.com/forums/t/8250.aspx?PageIndex=2. but just in cash you were almost frustrated like me with coreldraw X4 crashes, follow the steps below to get it done, and trust me, it works!:

"Hi all,

So, I bit the bullet and installed SQL server 2008 express.  Sure enough, I can no longer run Draw. 


Alex V. and I did some debugging and discovered that a new version
of the MFC dlls are installed (version 1833) with SQL2008.  Although
Draw specifies in it's manifest that it should use version 762, it uses
the newer version instead.


Unfortunately, there seems to be a bug in the newer version of
MFC and Draw crashes whenever a docker is opened which uses Internet
Explorer control in the docker (e.g. the hints docker, concept share,
any internet docker addons (like my table styles addon)).


There doesn't seem to be any symbols for the new MFC dll, so for now, we can't debug into it.


For the time being, you can start Draw by turning off the hints docker (which is defaulted on).


Open up DrawUI.xml (you may want to back up the file) found in
<DRAW INSTALL>\Programs\UIConfig\CorelDRAW\, and find the line


<dockPage guidRef="bc1e2f70-3b58-41cd-8406-aaa550482972" visible="true" selected="true" />


and replace with:


<dockPage guidRef="bc1e2f70-3b58-41cd-8406-aaa550482972" visible="false" />


Similarly, in Photopaint, PPUI.xml in UIConfig\Corel PHOTO-PAINT\, find the line



<dockPage guidRef="1c56c2ec-07c1-46f0-baf7-441a555d595c" visible="true" selected="true" />


And replace with:


<dockPage guidRef="1c56c2ec-07c1-46f0-baf7-441a555d595c" visible="false" />


You'll have to run while holding F8 the first time after doing this to overwrite the old settings.


If you open up conceptshare or the hints docker, Draw/Photopaint will crash.


I'll have a bug logged and hopefully we'll be able to find a real fix for it.


Regards,
Hendrik"

As I said I got it from coreldraw.com/forum, and apparently, it was fixed by a corel employee. As indicated there, it seems to have something to do with SQL2008.