SystemWontAccept

That's what I was looking for... THANKS!!!!

That would work but I was wondering if there was a simple math way to accomplish it. Like... Int ($InputVar - ($InputVar * (1-(168/200)) + 0.5)) My math just seems unnecessarily complicated. I was hoping a math geek out there could simplify this task.

I'm reading a variable that will be in the range of 0-200. I need to take the input of 0-200, and output 0-168. Is there a math statement that I can apply to the input variable to get my adjusted output range? The output range will be fixed when the project is complete, but during development, the upper limit may change. i.e. it may be 0-169, 0-170, etc.

Maybe I understand now.... You say the PID is unique for every process. That's the same as the handle that Taz mentioned right? And so my DOS command can only be called once with that $SNMPget variable. Even though the $SNMPget variable is the same, it can't be used again. Now I understand why you said it has to be run twice. The variable must also be defined each time so a new PID is created for the process. Right?

I keep asking because it's you who doesn't seem to understand the question. I have *never* asked how to fix it. In my first post I said "this does work". Then in post #5 (after a question to show the problem), I altered the code so that it *doesn't* work by changing the second $SNMPget variable to a remark. So, in this thread you have post #1 which works, and post #5 which doesn't. But... Maybe I'm not understanding you either. You say "run it a second time". I assume you mean run my DOS command? Yes I know I have to run my DOS program a second time. But why doesn't the second run work? The second result is blank if I just leave the $SNMPget variable as is (I mean if I don't redefine it). Why does my DOS program return a result the first time and not the second? The $SNMPget variable is still defined isn't it? I checked the $SNMPget variable *before* and *after* the first run of my DOS program and it doesn't change. ***** So if the $SNMPget variable hasn't changed, why does it need to be redefined? ***** I did a MsgBox(0, '', $SNMPget) to display the value of the $SNMPget variable both before the first DOS program call, and before the second DOS program call. The $SNMPget variable doesn't *appear* to change. Is there something about the $SNMPget variable that *has* changed? If so, how can I display that change for troubleshooting purposes. Please be specific. I'm not trying to be a jerk, I'm trying to understand this. I'm trying to learn how/why this works like this. Don't use the word "it" in your explanation, be specific so can I understand what your saying.

I admit this appears confusing but I think if you read it throughly (as I've done dozens of times), you'll see the point. I'm not asking how to fix it, I know how to fix it. I'm saying that the "fix" doesn't make sense. There are thousands of ways to do things wrong, that still appear to work properly. Just because it works, doesn't make it right. In that same post #9 I said that I can run the same code (two passes)... but if I don't redefine the variable, it fails. Why? I'm saying that defining the same variable more than once, with the same exact data, shouldn't be necessary. Please read my post throughly.

Thanks Taz, I like your design better and I've implemented it in my code. But your design does what mine did and that is, it redefines the $SNMPget variable before each use of that same variable. Now, it's less apparent in yours because it's just part of the design. But since we started this as a question on why it has to be defined each time, that question still hasn't been answered. For that original question, my original code is a better example. Again, if you look at the line that is ;remarked out, between the two While loops... why does that line (that $SNMPget variable) have to redefined for the code to work. You mentioned that the StdOut process is completed and the process dies and it's handle as well. I've done a message box and the $SNMPget variable (the handle) remains the same. It's a number and that number is the same before and after the first While loop. As I mentioned it's different each run. But it does stay the same *within* the run. Wouldn't that mean the handle is still good? Anybody know what's causing this? Thanks again Taz, your code was very helpful. Ed

Don't ask what I'm trying to do, because this isn't it. I've just simplified the code so you can replicate the results. #include <Constants.au3> Local $Test = Run (@ComSpec & " /c dir, @ScriptDir, @SW_HIDE, $STDERR_CHILD + $STDOUT_CHILD) MsgBox(0, 'WTF', $Test) I thought the MsgBox would display the same contents I put in the variable but it doesn't. It displays just a number, that changes every run. 6180, 7316, 6604, etc. What's going on? Ed

BTW, I did change it so it uses &= $result1 &= $line No change in my problem though, same results.

Thanks for noticing the '7', but that's not the problem, just a typo. Good eye. :-) Dave, your explanation of StdOut is very helpful! A few comments... 1) Absolutely correct, I need to call my utility twice so I can subtract one from the other to calculate the amount of change. 2) I have a question about using &=. I agree, I thought that would be needed but it isn't. Well, I don't think it is. It works most of the time with just =. Meaning it reads my child process properly and I get the expected results (excluding the double variable definition we're discussing of course). Are you stating that the &= is needed? Or that it's simply better syntax? Or that it will change my "works most of the time" to "works *all* of the time"? 3) This is the core of my original question... You said that the first loop exits and therefore there is never anything to read in the second loop. If that is the case, then why does simply redefining the $SNMPget variable (you see where I have it remarked out), why does that make the second loop read. As I said, I know how to fix this so it works... Redefine the $SNMPget variable before the second loop, it works. Don't redefine the $SNMPget variable before the second loop, it fails. What I don't understand is why? It's so crazy to have to define the same variable again, that I'm certain that I'm doing something wrong. That's my question. Ed

This code, with the remarked out $SNMPget variable, only displays $result1. Local $SNMPget = Run (@ComSpec & " /c c:\windows\system32\snmputil.exe get 10.10.10.10 public .1.3.6.1.2.1.2.2.1.10.4", @ScriptDir, @SW_HIDE, $STDERR_CHILD + $STDOUT_CHILD) Local $t, $line, $result1 = "", $result2 = "" While 1 Sleep(100) $line = StdOutRead( $SNMPget ) If @error Then ExitLoop $result1 = $line WEnd $t=StringInStr($result1, "Counter32") sleep(1000) ;Local $SNMPget = Run (@ComSpec & " /c c:\windows\system32\snmputil.exe get 10.10.10.10 public .1.3.6.1.2.1.2.2.1.10.4", @ScriptDir, @SW_HIDE, $STDERR_CHILD + $STDOUT_CHILD) While 1 Sleep(100) $line = StdOutRead( $SNMPget ) If @error Then ExitLoop $result2 = $line WEnd $t=StringInStr($result1, "Counter32") MsgBox(0, "Octets", StringMid($result2, $t+10) & StringMid($result1, $t+10 ) )

The code I uploaded does work. It displays two variables, $result2 and $result1. You'll notice that the $SNMPget variable is defined twice, exactly the same. Second one after my sleep(1000), before the second WHILE loop. Local $SNMPget = Run (@ComSpec & " /c c:\windows\system32\snmputil.exe get 76.7.88.30 time .1.3.6.1.2.1.2.2.1.10.4", @ScriptDir, @SW_HIDE, $STDERR_CHILD + $STDOUT_CHILD) If I remove the second definition (which I think I should be able to do), then instead of displaying two variables, it will only display $result1. Does that make sense?

I'm reading an SNMP MIB from a DOS program called snmputil. This does work and it reads into my $line variable properly. I want to read it once, wait 1 second, and read it again so that I can see how much it changed. BUT... this only works if I redefine the $SNMPget variable AGAIN before the second read. Why is that, what am I doing wrong? Local $SNMPget = Run (@ComSpec & " /c c:\windows\system32\snmputil.exe get 10.10.10.10 public .1.3.6.1.2.1.2.2.1.10.4", @ScriptDir, @SW_HIDE, $STDERR_CHILD + $STDOUT_CHILD) Local $t, $line, $result1 = "", $result2 = "" While 1 Sleep(100) $line = StdOutRead( $SNMPget ) If @error Then ExitLoop $result1 = $line WEnd $t=StringInStr($result1, "Counter32") sleep(1000) Local $SNMPget = Run (@ComSpec & " /c c:\windows\system32\snmputil.exe get 710.10.10.10 public .1.3.6.1.2.1.2.2.1.10.4", @ScriptDir, @SW_HIDE, $STDERR_CHILD + $STDOUT_CHILD) While 1 Sleep(100) $line = StdOutRead( $SNMPget ) If @error Then ExitLoop $result2 = $line WEnd $t=StringInStr($result1, "Counter32") MsgBox(0, "Octets", StringMid($result2, $t+10) & StringMid($result1, $t+10 ) ) MsgBox(0, "works? ", (StringMid($result2, $t+10) - StringMid($result1, $t+10))*8/1000000 ) ;MsgBox(0, '', StringMid($snmp, 1)) If I don't define the $SNMPget variable a second time, my $line variable is empty on the second read.

I did some searching and it appears the way to do this is send the output to a temp text file and then read it back. Is there a simpler way? RunWait( "cmd /c c:\windows\system32\snmputil.exe get 176.88.15.30 Public .1.3.6.1.2.1.2.2.1.10.4" & ">" & "temp.txt" ) $output= FileRead( "temp.txt", FileGetSize("temp.txt") ) FileDelete( "temp.txt" ) This works, just looking for input on the best way to run a DOS app and dump the output to a variable. Is the step of writing to a file needed?

The code is golden! You guys are AWESOME! My servo initializes AND moves. I'll go though this code as my tutorial. This will allow me to build a real world gage that shows my Internet utilization... I hope. I've got some math to do but that's easy. This is exciting! Thank-you, Thank-you, THANK-YOU!!