You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With Process Monitor I figured out that you can get user commands to work by renaming the program's directory to "bin".
Initially it can be noticed that dar.exe is looking for the shell in the parent directory of the program folder (..) and then under ..\bin. So, my first try was to move the program directory to C:\cygwin of a parallel Cygwin installation.
That changes the error from "execve() failed. (process table is full ?)" to "returned error code: 32512" when sh.exe is found in C:\cygwin\bin.
Copying the DAR program files into C:\cygwin\bin worked, but copying the C:\cygwin\bin files to a DAR program directory didn't work (error 32512). It took me a while to test out the only difference: the directory name.
Then I confirmed that you don't need other Cygwin resources, installing DAR into "bin" is the only adjustment required.
For error 32512, I can't find any suspicous fails in Process Explorer. That's why I guess it's probably a Cygwin error that makes sh.exe unusuable outside a bin directory.
But it could be addressed by a FAQ or the packaging of the Windows release.
Best,
RS
The text was updated successfully, but these errors were encountered:
The findings above were a bit premature, since I got confused by my test setup.
In fact, you need at least this folder structure with sh.exe and additional Cygwin libraries to run a simple "echo test" user command wihtout errors:
<DAR main dir>\bin\<all DAR for Windows files>
<DAR main dir>\bin\sh.exe
<DAR main dir>\bin\cygreadline7.dll
<DAR main dir>\bin\cygncursesw-10.dll
<DAR main dir>\tmp
It appears that e.g. a "sleep" would also require sleep.exe from Cygwin, so I tend to integrate all files from Cygwin's bin directory with my DAR install.
Hi,
Thank you for this great software!
Just wanted to share an observation about user command scripting on Windows, which seems to have been a problem for some time: https://sourceforge.net/p/dar/mailman/dar-support/thread/20140430141912.A7CD.4698F931%40iol.ie/
With Process Monitor I figured out that you can get user commands to work by renaming the program's directory to "bin".
Initially it can be noticed that dar.exe is looking for the shell in the parent directory of the program folder (..) and then under ..\bin. So, my first try was to move the program directory to C:\cygwin of a parallel Cygwin installation.
That changes the error from "execve() failed. (process table is full ?)" to "returned error code: 32512" when sh.exe is found in C:\cygwin\bin.
Copying the DAR program files into C:\cygwin\bin worked, but copying the C:\cygwin\bin files to a DAR program directory didn't work (error 32512). It took me a while to test out the only difference: the directory name.
Then I confirmed that you don't need other Cygwin resources, installing DAR into "bin" is the only adjustment required.
For error 32512, I can't find any suspicous fails in Process Explorer. That's why I guess it's probably a Cygwin error that makes sh.exe unusuable outside a bin directory.
But it could be addressed by a FAQ or the packaging of the Windows release.
Best,
RS
The text was updated successfully, but these errors were encountered: