Mis *.err file

[Habro]

Hello

I have switched from Proton IDE to Positron

now when I compile a file in Positron, Positron does not create a file with the extension .err

which means I cannot start Proteus to simulate.

if I compile the same file with Proton IDE, the file *.err is created.

what am I doing wrong.

this text has been translated from Dutch to English by Google

[RGV250]

Hi,
I think it is something else as I use Proteus VSM and do not have the .err file. In fact I would hazard a guess that .err is an error file.
I use the original IDE and none of my projects (the ones that do compile) have an err file.
Perhaps you could give a bit more information like a test file that does not simulate. What version of Positron and Proteus you are using.

You could also look inside the .err file using notepad or notepad++ to see what is in there.

To prove a point, if you do think it is the .err file, you could try to create a blank file with the err extension and see what happens.

Regards,
Bob

[RGV250]

Hi,
I have just found a project that does have an err file, this is the contents so I do not think the VSM would need it.

Message[308] C:\BG_WORK\PIC_PROJECTS\CAN_SPI\A.S 24 : Warning level superseded by command line value. (2)
Error[113]   C:\BG_WORK\PIC_PROJECTS\CAN_SPI\A.S 2211 : Symbol not previously defined (FONT_TABLE)
Error[113]   C:\BG_WORK\PIC_PROJECTS\CAN_SPI\A.S 2214 : Symbol not previously defined (FONT_TABLE)
Error[113]   C:\BG_WORK\PIC_PROJECTS\CAN_SPI\A.S 2223 : Symbol not previously defined (FONT_TABLE)

Bob

[Fanie]

As far as I have it, if compiling code has an error, the files are not created.

[flosigud]

.err files are only created if there is an error.

[top204]

The proteus simulator uses the ".bas" file, or the ".cof" file.

If using the ".bas" file, it also uses the ".lst" file for the simulation.

This is how it has always been.

The ".err" file is created when assembler errors occur, and it is deleted by the compiler, and the errors are transferred to the ".pbe" file for the IDE to report them.

Regards
Les

[Habro]

Thank you
it is still strange that if I compile a program file in Proton it works in Proteus, but if I compile the exact same program in Positron it does not work in Proteus.
but now I know a bit more.
I will keep looking.
I think something else is going on.

Thanks everyone

[Stephen Moss]

it is still strange that if I compile a program file in Proton it works in Proteus, but if I compile the exact same program in Positron it does not work in Proteus.

Try ensuring that the optimiser is off (Declare Optimiser_Level = 0).
If you are using the same filename for both Positron and Proton, then rename the .BAS files by adding _Pro to the Proton File and _Pos to the the equivalent Positron file to help better identify them when comparing.
Compile and if you are still having problems use something like WinMerge to compare the Proton and Positron versions of the following file...

• .BAS source files for the compiled code
• .ASM files for the compiled code
• .HEX files for the compiled code

If there are no differences between the Proton & Positron versions of those files then also try comparing the .PPI and .DEF files for the device you are using.
If WinMerge indicates that any of the files are different, selecting the file will open it and the differences will be highlighted, any differences could give a clue as to why one works with Proteus and the other does not.