jupe wrote:what exactly is the problem you are having?
Hi, jupe!
Something stupid happens.
I have an x.cmd that call xyplorer twice to run two scripts:
C:\...\xyplorer.exe /new /win=min /script="1.xys"
C:\...\xyplorer.exe /new /win=min /script="2.xys"
and it runs normally, xy returns to the x.cmd and x.cmd runs further.
Then the x.cmd contains a next call
C:\...\xyplorer.exe /new /win=min /script="3.xys"
and all ends: xyplorer can't be seen running and x.cmd ends abruptly on the command that calls xyplorer.
This 3.xys is ok itself: xyplorer runs it from "Scripting/Run script".
If I write a simple y.cmd that contains only the call
C:\...\xyplorer.exe /new /win=min /script="3.xys"
so the 3.xys will be completed normally.
It will run too if I start command line window and type the same command
C:\...\xyplorer.exe /new /win=min /script="3.xys"
manually.
I have even tested this situation by emptying the 3.xys by adding /* and */ for the whole content of the 3.xys to be sure that the script is not responsible for failures and nothing changes.
There is also another problem that I experienced:
7-Zip and rar.exe do not run in that x.cmd, if they are called after these scripts 1.xys and 2.xys .
Rar.exe complains to not have permission to create temporary archives and 7-Zip seems to have same problems.
At the same time being started by the same commands but from an z.cmd containing only the call to xyplorer
these both 7-Zip and rar.exe work good.