FreePascal doesn't run my programs (any)

[fxeconomist]

I'm returning to this problem, because somehow it still puzzles me.

I have two Windows 11 partitions. On one of them, FP works perfectly. On the other, FP doesn't run my programs. Any program. I reinstalled it and Lazarus, but the error was still there.

It does compile, and then at run it tells me "The program ... does not run. DosError = 13". I didn't find any description for DosError 13.

However, the program exists there and can be run from cmd.

I also found that it can't run the shell.

But here's the kicker. I found a strange fix. I adapted the FP shortcut. I made a cmd file that launches FP, and have the shortcut cmd run that file.

Only this way, it can run programs, and can run the shell. Only if FP runs from CMD, but not if FP runs directly from Windows.

The thing is, I don't wanna wipe that Windows just because FP has a tiny snag.

[dbannon]

A picky point, no solution (you are very unlikely to get a windows solution from me !).

May be its a terminology issue but I am struggling to make sense of your report. Firstly, lets get this clear. You start with some source code, FPC complies that into an executable (Lazarus asks FPC to do it) and then Lazarus runs your program for you.

So, by my reckoning, your fix of a cmd file instead of fpc would make no difference when running the program (fpc is not, then, involved) but would possibly make a difference when compiling.

Now, if what you appear to be saying is literally true, your fix is somehow building a different binary at compile time, one that will run on your system.  Thats an important clue to what is happening.

I hope you don't think I am being awkward here, its just that what you seem to be describing is unlikely but, never the less, possible.

Could you clarify please ?

Maybe compile (ie "build", or even "clean up and rebuild") in both modes, with and without your fix, and see if the two binaries are different ?

Davo

[Aruna]

It does compile, and then at run it tells me "The program ... does not run. DosError = 13". I didn't find any description for DosError 13.

DOS Error LIst

Error Code 13: Invalid data
Description     : The data provided is invalid or not in the expected format.

[jamie]

https://courses.cs.umbc.edu/undergraduate/CMSC211/spring02/burt/lectures/Chap18/DOSerrors.html

Open mode is invalid

Sounds to me you need a console operating and the CMD most likely gives you that.

[ASBzone]

The thing is, I don't wanna wipe that Windows just because FP has a tiny snag.

Does everything else work properly in that partition?

I suspect that there is a bigger problem with the partition itself.

Also, it would help us to know what code you are compiling, to what platform type. 

And when you say "you cannot run the shell," I think it would be very helpful if you would provide more clarity on that.  What shell?  What error message? What version of FPC and Lazarus?  What method of Install?   What specific edition of Windows 11?  And what else do you run there?

[Thaddy]

doserror 13 means permission denied. It is not likely to be caused by a damaged disk, although that is possible. If your drive supports S.M.A.R.T, use that to check the disk.
But usually it it just a rights issue.
It can be one of:
- windows rights for the user for that disk.
- accessing files or directories that are read-only
- file is in use
- file does not exist
- accessing a directory as a file

See the msdos documentation (except for the first)

In a fpc program you can compile a console app in {$I-} state and check IOResult. That would also be 13. (or any error from 17 downwards, which are all OS errors)
Alas, error 13 is not documented in the fpc documentation, which is an omission.

[Thaddy]

Side note:
languages like Python handle that correctly as 13.

[TRon]

fwiw the bingo game was won by Aruna 

[Thaddy]

No, it isn't. My version is a bit more complete.

[TRon]

@Thaddy: Except for the fact that you are referring to error code 12 (same as jamie did).

link

[Bart]

Since we have no reply from TS yet, let's just wait a bit.
All else is speculative.

Bart

[Aruna]

fwiw the bingo game was won by Aruna 

Guys, look what I found MS-DOS v1.25, v2.0, v4.0 Source Code

[Thaddy]

fwiw the bingo game was won by Aruna 

fwiw Bingo delay is due to switch from cable to fiber - and also mobile, and a different provider - and lack of connection between devices..
The modem is still missing so everything goes over mobile access points. Should be solved soon.

[fxeconomist]

A picky point, no solution (you are very unlikely to get a windows solution from me !).

May be its a terminology issue but I am struggling to make sense of your report. Firstly, lets get this clear. You start with some source code, FPC complies that into an executable (Lazarus asks FPC to do it) and then Lazarus runs your program for you.

So, by my reckoning, your fix of a cmd file instead of fpc would make no difference when running the program (fpc is not, then, involved) but would possibly make a difference when compiling.

Now, if what you appear to be saying is literally true, your fix is somehow building a different binary at compile time, one that will run on your system.  Thats an important clue to what is happening.

I hope you don't think I am being awkward here, its just that what you seem to be describing is unlikely but, never the less, possible.

Could you clarify please ?

Maybe compile (ie "build", or even "clean up and rebuild") in both modes, with and without your fix, and see if the two binaries are different ?

Davo

I can show you the screenshots.
(https://i.postimg.cc/F1w9JnVb/fp-refuses-to-run-program.png)
(https://i.postimg.cc/65pTgk7P/fp-refuses-to-run-program.png)

(https://i.postimg.cc/Gt2rg1MJ/fp-cannot-run-shell.png)
(https://i.postimg.cc/r0vvz72K/fp-cannot-run-shell.png)

Now, I'm thinking it's gotta be something like a registry setting or a path. It would be nice if a dev could tell exactly what's in the fp code there to trigger these errors.

Now, if's a denied access - which is unexplainable - it reminds me of another problem that I have, which nobody found a solution for, in Lazarus. A big program of mine cannot overwrite files. So, once a file is saved thru the usual scheme : assign - rewrite - write stuff - close,
when the procedure is run again it returns error 5 on rewrite. Nobody found an explanation for that, but it doesn't piss me off greatly, least for now.

[Bart]

OK, so the fp IDE gives an error when you try to run the program from within the IDE, but you can run the program from the commandline just fine.

What's the content of your %COMSPEC% environment variable?
Does it matter on which drive the the program resides?

Bart