return codes of a shell command

[pmu5757]

Agraham,
As I'm not a B4PPC expert, I think I need an example of using your library with its "lastexitcode" property.
Could you do it for me ?
I just need to launch a shell command and put its return code in a variable.
Thank you.

Pascal.

[agraham]

I misquoted the name of the property, it is actually called ExitCode not LastExitcode. See example.

[pmu5757]

Hello Agraham
Thank you for your example, it's very clear for a newbie like me.
But unfortunately, it doesn't work.

In a dos windows I type :
C:\>c:\nqc.exe -Susb -raw 120901
It answers :
54 00
This works

In your example, I use the line :
Process.Start("c:\nqc.exe" ,"-Susb -raw 120901")
Result : the command is launched (I can see the red light on the infrared lego tower), but a 0 is returned.

I suppose that your example only gets error codes and that "54 00" is not an error code. So it answers "0" that means "no error".

I then tried to redirect the result of the command in a text file :
In a dos widow, I type : C:\>c:\nqc.exe -Susb -raw 120901 > sortie.txt
Then the file "sortie.txt" contains "54 00" : it works.

In your code I then use the line : Process.Start("c:\nqc.exe" ,"-Susb -raw 120901 > sortie.txt")
I obtain the number "-13" that indicates an error I presume, because the file "sortie.txt" is neither created, nor modified if it exists...

I think I still need help...

Pascal.

[agraham]

Originally Posted by pmu5757

How can I do to set a B4PPC variable with the return code of this dos command ?

My example does just this. The problem is that it is not the return code that you require

In a dos widow, I type : C:\>c:\nqc.exe -Susb -raw 120901 > sortie.txt
Then the file "sortie.txt" contains "54 00" : it works.

It looks like that app writes the number to StdOut. StdOut and redirection of it only exists for a console app running in a DOS window. Executing it directly under Windows using Shell doesn't provide access to StdOut. The following code line starts the command interpreter "cmd" and instructs it "/c" to execute the rest of the argument string then terminate.

Process.Start("cmd", "/c c:\nqc.exe -Susb -raw 120901 > " & AppPath & "\sortie.txt")

[taximania]

Reminds me of the old days when I wrote a mouse driver in assembly for a 286 that couldn't run windows.

ax
dx

etc ha ha ha

[pmu5757]

Thank you Agraham.
your "cmd" works well with a line like :
Process.Start("cmd", "/c c:\nqc.exe -Susb -raw 120901 >> c:\sortie.txt")

But not with your line with the AppPath statement...

It doesn't matter, it's enough for me.

Best regards

Pascal.

[agraham]

Originally Posted by pmu5757

But not with your line with the AppPath statement

It should work - it does for me. Did you make a typo in appending the strings?

Note that you could revert to using the standard B4ppc "Shell" function as you don't need the return value.

[pmu5757]

Sorry, but with my poor english, I don't understand what you mean with "make a typo in appending the strings".

Anyway, your other idea is good : using the "cmd" only when I need to return a value, and using the standard shell command if not.

Pascal.

[agraham]

Originally Posted by pmu5757

"make a typo in appending the strings".

Make a mistake when adding the three strings for the arguments parameter
"/c c:\nqc.exe -Susb -raw 120901 > " & AppPath & "\sortie.txt"

using the "cmd" only when I need to return a value, and using the standard shell command if not.

What I meant was that you can use cmd with the standard Shell command instead of using Process as you don't want the exitcode of the app, only what it writes to StdOut.