Re: Problems with directory length
- Posted by mattlewis (admin) Sep 16, 2009
- 1613 views
What compiled the 'binder'?
The reason i ask is because every other .exe file i put in there runs just fine, it's only the Euphoria bound .exe's the give that problem. I even tried an old old program made for Windows 3.1 and it opened just as usual, without a problem.
The way that bound programs work, is that the compressed IL of your program is appended to the backend runner (the same executable that you use to run a shrouded program). When the backend runner starts, the first thing it does is to check to see if it's a bound program or if it should look at the command line for a shrouded file.
So it opens itself up to read itself and check to see if it was bound. It figures out who it is (i.e., the actual path to the executable being run) by looking at the command line. So it begins executing just fine, but since the command line is apparently being truncated, it doesn't have the full path to open itself up.
I believe that when you run the program from the command line, in the same directory, you get a relative path in the command line, thus it has no problem in opening itself up. I wasn't able to figure out, via google, the specifics of the command line limits of double clicking on a program from within explorer.
Matt
