I have the same problem under XP/32bit except that I kept 3RC1 and installed 3RC2 in a new subdirectory.

During program start:
"qcad.exe hat ein Problem festgestellt und muss beendet werden"

Problemsignatur:
AppName: qcad.exe AppVer: 0.0.0.0 ModName: qtcore4.dll
ModVer: 4.7.3.0 Offset: 000e7ea3

Thanks Husky

I have installed 3RC2 to a new subdirectory as you suggested and all is working fine now!

Regards

Clive

Sometimes reproducible. Seems to be caused partly by stored value in Appearance/DockappWindows.

Changing in autostart.js

appWin.readSettings();
appWin.show();

to

appWin.show();
appWin.readSettings();

seems to fix it.
Possibly a Qt bug.

An RC2b package with the above fix will be available shortly.

A potential fix is now online as RC2b. Please let me know if it does not work.

Nope - also RC2b doesn't work on my machine. Still a problem with the qtcore4.dll

Please attach your QCAD.ini file:
C:\Documents and Settings\username\Application Data\RibbonSoft\QCAD3.ini

Where 'username' is your user (login) name. The exact path might depend on your system.

Bitte QCAD.ini Datei anhaengen:
C:\Documents and Settings\username\Application Data\RibbonSoft\QCAD3.ini

Wo 'username' Ihr Benutzername ist. Der Pfad kann von System zu System unterschiedlich sein.

Already in your inbox at info@ ......

Thanks.

This seems to be related to user defined commands / shortcuts stored in the QCAD3.ini file.

At least deleting sections [Shortcuts] and [Commands] avoids the crash here.

I will continue to look into this.

Step 1:
After this hint from you I went back to RC1 and "restored to default" the two Shortcuts what I have changed in RC1. Note: I never deleted a Shortcut or Command.
Now RC2 is starting as expected - now crash!

Step 2:
I changed two shortcuts in RC2, saved the changes, restarted RC2 and was still able to start RC2 as normal.

It seems that you are on the right way ....

installed RC2b. So far I did not notice the previous problems after editing the config file.
Thanks

Hi Andrew

RC2b installed and working fine now - no problems.

regards

Clive