Recent posts

#71

Beginner questions / Re: Just installed Pelles C an...

Last post by MrBcx - July 21, 2026, 03:52:00 AM

Your batch file is modified from PoVars64.bat which is found in your PellesC\bin\ folder
When you scrape off all the obvious non-Pelles path folders, your batch file leaves you with this:
PATH=C:\PellesC\Bin;C:\bin;D:\Pelles\bin
I suggest running PoVars64.bat instead of your batch file and then try running your experiment.

I did as you suggested and I get the same result.

Bummer -- I'm out of ideas at the moment.  Hopefully someone can help unravel this.

#72

Announcements / Re: Version 14.50 is now relea...

Last post by John Z - July 21, 2026, 02:56:11 AM

Thanks Pelle!

DPI fix perfect BTW 👍

John Z

#73

Beginner questions / Re: Just installed Pelles C an...

Last post by John Z - July 21, 2026, 02:48:26 AM

Strange thing is that I still get the same failure after typing:

poide<CR>
Unable to start POIDE.EXE (error code 2)

But if I explicitly type: C:\PellesC\Bin\poide<CR> it runs just fine.

At the cmd prompt type set <ret> to verify the PATH variable is actually set correctly and not overridden by something else.
Or
Use echo %PATH% to just see it.

Code Select Expand

C:\Program Files\PellesC_14_5\Bin>echo %PATH%
C:\Program Files\PellesC_14_5\Bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\dotnet\;C:\Program Files\PowerShell\7\;C:\Users\Owner\AppData\Local\Microsoft\WindowsApps;
Also as a crazy idea just try using poide.exe 

John Z

Also if you cd to PellesC bin directory and type poide does it run?

#74

Beginner questions / Re: Just installed Pelles C an...

Last post by PabloMack - July 21, 2026, 02:47:08 AM

Your batch file is modified from PoVars64.bat which is found in your PellesC\bin\ folder
When you scrape off all the obvious non-Pelles path folders, your batch file leaves you with this:
PATH=C:\PellesC\Bin;C:\bin;D:\Pelles\bin
I suggest running PoVars64.bat instead of your batch file and then try running your experiment.

I did as you suggested and I get the same result.

#75

Beginner questions / Re: Just installed Pelles C an...

Last post by MrBcx - July 21, 2026, 01:24:57 AM

This computer has never had Pelles C installed on it before.
I uninstalled it and then reinstalled it to C:\PellesC
I now run a batch file with the following contents after running cmd.exe:

@echo off
set PellesCDir=C:\PellesC
rem
set PATH=%PellesCDir%\Bin;%PATH%;C:\bin;D:\Pelles\bin
set INCLUDE=%PellesCDir%\Include;%PellesCDir%\Include\Win;%INCLUDE%
set LIB=%PellesCDir%\Lib;%PellesCDir%\Lib\Win64;%LIB%

Strange thing is that I still get the same failure after typing:

poide<CR>
Unable to start POIDE.EXE (error code 2)

But if I explicitly type: C:\PellesC\Bin\poide<CR> it runs just fine.

Your batch file is modified from PoVars64.bat which is found in your PellesC\bin\ folder

When you scrape off all the obvious non-Pelles path folders, your batch file leaves you with this:

PATH=C:\PellesC\Bin;C:\bin;D:\Pelles\bin

I suggest running PoVars64.bat instead of your batch file and then try running your experiment.

#76

Beginner questions / Re: Just installed Pelles C an...

Last post by PabloMack - July 20, 2026, 11:07:41 PM

This computer has never had Pelles C installed on it before.
I uninstalled it and then reinstalled it to C:\PellesC
I now run a batch file with the following contents after running cmd.exe:

@echo off
set PellesCDir=C:\PellesC
rem
set PATH=%PellesCDir%\Bin;%PATH%;C:\bin;D:\Pelles\bin
set INCLUDE=%PellesCDir%\Include;%PellesCDir%\Include\Win;%INCLUDE%
set LIB=%PellesCDir%\Lib;%PellesCDir%\Lib\Win64;%LIB%

Strange thing is that I still get the same failure after typing:

poide<CR>
Unable to start POIDE.EXE (error code 2)

But if I explicitly type: C:\PellesC\Bin\poide<CR> it runs just fine.

#77

Announcements / Re: Release Candidate #1 for v...

Last post by Vortex - July 20, 2026, 10:54:15 PM

Hi Pelle,

Thanks for the new release of Poasm fixing the issue.

[__stod()]

#78

Beginner questions / Re: Unresolved External Symbol

Last post by StevenCooper - July 20, 2026, 06:26:09 PM

POLINK: error: Unresolved external symbol '__stod' - referenced from 'C:\Users\steco\Documents\Pelles C Projects\LotteryScratchOffs\output\LotteryScratchOffs.obj'.

__stod() was an internal helper function, no longer needed, and (obviously) never documented.

This symbol can't pop out of thin air, so the most likely reasons are:
1) you are somehow pulling in (old) #include files from the wrong directory
2) the file LotteryScratchOffs.obj is not (re)built properly, or the associated source file (LotteryScratchOffs.c ?!) contains some private reference to __stod.

If I'm remembering correctly, when I jumped to version 14.5, I did NOT first uninstall version 10; so, maybe the Setup program did not overwrite some of the old files; it was a pretty big jump.

As it turns out, I really didn't need to abandon version 10 after all; the problem I had when I installed it on Windows 11 Pro was I would get this error message when trying to build a project:

Error Code: 1073741819

The .obj files would get built, then the above error message would appear, and the build would stop. I have since discovered that all I need to do when I get that message is click on the "Build" button again, and the build process will finish correctly.

I have found that Version 11 of Pelles C has the same problem, intermittently, and again, I just click on the "Build" button a second time and the process finishes and I have an executable program.

Before I left Windows 10, I saved the Registry keys for Pelles configuration, so I could restore my configuration in the new version. I installed those keys in the Windows 11 registry before I installed Pelles C Version 10.

Any chance those old registry keys are causing problems?

I do have a precompiled library called Srclib from Version 10; perhaps I need to re-compile it in Version 14.5 before I recompile programs that use that library (almost all my programs use it).

I may, if I decide to move to Version 14, try completely uninstalling Pelles c, and manually delete registry keys and residual files and folders before doing a "clean" install of version 14. However, for now, I'm perfectly happy with Version 11, more or less.

#79

Beginner questions / Re: Just installed Pelles C an...

Last post by MrBcx - July 20, 2026, 05:39:25 PM

The main thing is: DO NOT use spaces in your folder name.

Pelles C was tested from the start with spaces in the path. This has always worked here.

Sorry ... I should have been more clear.

Eliminating spaces in paths is a tenet that I adopted long ago. I did encounter problems
with paths containing spaces in the past.  Regardless of the cause(s), those instances
were always resolved by changing to unambiguous paths.

#80

Announcements / Version 14.50 is now released

Last post by Pelle - July 20, 2026, 04:10:15 PM

See https://www.pellesc.se/, Download (and Changes).

Changes from Release Candidate #1:
    Fixed minor linker problem with one (not very common) form of weak external symbol.