Download Pelles C here: http://www.pellesc.se
Quote from: John Z on July 21, 2026, 02:48:26 AMAlso 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?
C:\Program Files\PellesC_14_5\Bin>povars64.bat
Setting 64-bit environment for Pelles C...
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;
C:\Program Files\PellesC_14_5\Bin>poide <<< worked in BIN directory >>>
C:\Program Files\PellesC_14_5\Bin>cd\
C:\>poide <<< top level C drive
Unable to start POIDE.EXE (error code 2) <<<- didn't work from top level C drive >>>
C:\>poide.exe <<<- worked from top level of C drive >>>
Quote from: PabloMack on July 21, 2026, 02:47:08 AMQuote from: MrBcx on July 21, 2026, 01:24:57 AMYour 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.
Quote from: PabloMack on July 20, 2026, 11:07:41 PMStrange 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.
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;Quote from: MrBcx on July 21, 2026, 01:24:57 AMYour 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.
Quote from: PabloMack on July 20, 2026, 11:07:41 PMThis 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.
Page created in 0.073 seconds with 15 queries.