Download Pelles C here: http://www.pellesc.se
Quote from: Michele on Yesterday at 09:12:40 AMI had a similar problem, the cause was an addin that increments the build number at each compilation.
Quote from: John Z on March 26, 2026, 10:50:20 AMTesting many programs now, but a question -If project build as stdcall, it didn't crash.
Will each program compiled in V14_RC1 on a 'modern' CPU then need to be run/tested on a Windows 7 system and/or with an older CPU not supporting the MOVBE op code?
Essentially will programs completed with V14 possibly include the MOVBE op code in the exe?
GDIpTest program fails under V14, but OK under V13. Not sure why yet no error during creation but crashes on opening file to display. Sources , picture and exe files included. The picture is what makes the upload so large but wanted to include exact test case. Can be deleted later to release space. Didn't find MOVBE in the exe btw
John Z
Seems you can use a HEX Editor and search for HEX 0F38F1 (found in several places poide.exe) or 0F38F0
Quote from: John Z on March 26, 2026, 03:33:23 PMWeirdnessI had a similar problem, the cause was an addin that increments the build number at each compilation.
On a rather large 64 bit program V14 keeps popping up a message box "The main.rc has been changed outside of the editor. Do you want to reload it?" Even if clicking Yes and Save All, next build/run it pops up again. Needless to say. but I will, nothing I am doing is changing the .rc file. It happens immediately after starting the program within the IDE environment. Checking the .rc file date-time, it is changed to the time the program was started. When I run the program outside of the IDE in the same directory, the .rc file does not change date-time.
Page created in 0.069 seconds with 15 queries.