Just installed Pelles C and unable to run poide

[PabloMack]

It has been years since I ran Pelles C so I installed the most recent release and I get the following message after trying to run poide:

Unable to start POIDE.EXE (error code 2)

[John Z]

Hi PabloMack,

Welcome back - I believe.

Not a lot of information provided - Error 2 is file not found.

Have you checked the shortcut properties?
Have you looked in "Program Files\PellesC\bin" for poide.exe?

I just did a clean install - worked fine.  Windows 11, 25H2, 64bit of course.

You might just try uninstalling and re-install after re-downloading from
https://www.pellesc.se/

John Z

[Vortex]

Hi Pablo,

Kindly, what is your operating system? Is the User Access Control enabled? Do you have any antivirus software? Are you operating under an administrative account?

[MrBcx]

Hi Pablo,

For 20+ years, I've kept C:\Pellesc\ in the root of my drive and I tell
Windows to exclude that folder from Windows Defender wanting to scan it.

I never have problems using Pelles C with that arrangement.

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

[John Z]

Sage advice IF one uses various Pelles C tools outside of the IDE.

However if staying within the IDE I've never had an issue with installing Pelles C into directories with spaces, all the way back to at least Windows ME  .

My current install path C:\Program Files\PellesC_14_5\
My current source code path C:\Program Files\PellesC\Files\
even a path like C:\Program Files\PellesC\Files\BBBBuilder_PS - Copy (2) works without any problems.

I've never had Windows Defender flag Pelles C neither has my GData antivirus program. Although we've heard many stories about the 'free' antivirus programs flagging Pelles as well as programs built by Pelles C.


So just another viewpoint -

There is not enough information to be able to help Pablo until he posts more IMO.

John Z

[PabloMack]

I am running Windows 10. I installed PellesC in an Admin account for everyone but I am trying to use it under a non-privilege account.

[TimoVJL]

Try it once with Admin account, if it check file like sysdefs.tag

An old Depends.exe might show if it fails with files.

[Vortex]

Hi Pablo,

Did you remove the previous version of Pelles C? Any remnants from the old installation?

[Pelle]

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.

[Pelle]

I am running Windows 10. I installed PellesC in an Admin account for everyone but I am trying to use it under a non-privilege account.

This have been tested in the past, but not recently. Then again, I doubt much have changed (in the installer at least)...

[MrBcx]

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.

[PabloMack]

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.

[MrBcx]

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.

[PabloMack]

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.

[John Z]

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?