This problem is fixed in most cases. The command line compiler reports the correct error and location for a config file that does not have a .ecf extension. So does estudio, if the error is introduced after the project is added. But trying to add a configuration file named Ace which has contents that looks like a .ecf file but has a syntax error still causes the incorrect error report. To reproduce: Start estudio and try to add the project whose configuration file is named Ace (use attached file). Estudio reports: Configuration Loading Error Unable to load the ace file `/marten/test/Ace'. Parse error in /marten/test/Ace (line 1, column 3) It appears that when *adding* a new project, estudio doesn't try to figure out if this is an Ace file or a .ecf file. Reopening report.