1
N.A.N.Y. 2013 / Re: NANY 2013 Release: Customizable Remote Administration Panel (CRAP)
« Last post by ConstanceJill on Today at 06:07 AM »Thanks!
So I extracted 2.1.0 build 70 BETA and tried running a few commands on my work computer, but I ran into a an error with a few of them.
For example, I have a button with the following settings :
Same problem with buttons that I set to direct launch mstsc.exe, explorer.exe or mmc.exe
From what I gathered, it would seem that, when using "Direct Launch" only, when the full path to the application is not specified, this version of the program tries to check if it finds the program in the PATH, but fails to find it.
However, it does find and launch successfully some third party executables that I've placed in other folders, which I added to my system PATH, without having their paths spelled out in the button settings.
I suspect that it probably has to do with the PATH relying on the %SystemRoot% environment variable for executables that ship with Windows (?)
Replacing the setting in the button with "%systemroot%\system32\ping.exe" also does not fix the problem, I have to put "C:\Windows" in place of "%systemroot%".
Another minor annoyance that I noticed is that, after editing a button, the contents of the Variable field is emptied.
So I extracted 2.1.0 build 70 BETA and tried running a few commands on my work computer, but I ran into a an error with a few of them.
For example, I have a button with the following settings :
Image File: <appdir>icons\Ping.pngWhen trying to run that command, I'm met with the following error message:
Application: ping.exe
Application Arguments :-t <var>
Start in:
Button Caption: Ping -t
Command Window : Skip (Direct Launch)
Ignore : Variable Whitespace
Launch cancelled. Application file listed bellow is missing.
ping.exe
Same problem with buttons that I set to direct launch mstsc.exe, explorer.exe or mmc.exe
From what I gathered, it would seem that, when using "Direct Launch" only, when the full path to the application is not specified, this version of the program tries to check if it finds the program in the PATH, but fails to find it.
However, it does find and launch successfully some third party executables that I've placed in other folders, which I added to my system PATH, without having their paths spelled out in the button settings.
I suspect that it probably has to do with the PATH relying on the %SystemRoot% environment variable for executables that ship with Windows (?)
Replacing the setting in the button with "%systemroot%\system32\ping.exe" also does not fix the problem, I have to put "C:\Windows" in place of "%systemroot%".
Another minor annoyance that I noticed is that, after editing a button, the contents of the Variable field is emptied.