Custom Query (3910 matches)

When running a script like this one:

Dim $ourProcess, $ourOutput
;
; No output on STDOUT @ rev 3244 - 3372
$ourProcess = RunAs("chump", @ComputerName, "tolchock", 1, @ComSpec & " /c dir foo.bar", @SystemDir, @SW_HIDE, 2)

While 1
    $ourOutput &= StdoutRead($ourProcess)
    $ourError = @error
    MsgBox(0, "Debug", "@error returned: " & $ourError & ", @extended (chars read) is: " & @extended)
    If $ourError Then ExitLoop
WEnd
MsgBox(0, "STDOUT output:", "[" & @AutoItVersion & "]" & @CRLF & $ourOutput)

...on Windows XP RTM and XP SP1, no output is returned to StdoutRead and the child console window is briefly visible, seemingly in disregard of the flags provided in the RunAs function.

In Windows XP SP2 and Server 2003 SP2 output is returned as desired to StdoutRead and the console window is correctly hidden.

The test environments between the OS versions were as close as I could make them to identical, in that I was running as an Administrator, the RunAs user existed and had access to the test files. A matching test script using the Run function with STDOUT redirection worked as expected on all tested OS versions.

Hello,

@OSVersion reports as WIN_VISTA under Windows 2008; help file indicates WIN_2008 should be recognised.

System: Windows 2008 (64bit) Enterprise server, SP1; AutoIt v3.2.12.0

Example code:

msgbox(0,"", @OSType &";" & @OSVersion &";" & @OSBuild &";" &  @OSServicePack &";" & @OSLang & ";" & @ProcessorArch)
;2008 server shows 'WIN32_NT;WIN_VISTA;6001;Service Pack 1;0409;X64'

Apologies if this has been covered already.

Cheers, Pete.

There appears to be a 260-character limit for the filter string. If the string is any longer than this, AutoIt spits an error at the user stating that the filter is invalid (even though it obviously isn't). This limitation seems completely artificial, so I think it should be removed (or at least increased).

If not, then some remark definitely needs to be made in the help file so that the limit is clear to the user. Otherwise, anyone who runs into the limit and gets the error message might end up wasting as much time as I did trying to figure out where/why the valid filter string was considered to be invalid.