Custom Query

Using beta 3.2.11.0 on XP SP2:

If the RunAs function is called in a script by a limited user, the RunAs function will fail if the target run-as user's Profile is already loaded; as in the case that another process has already been invoked with the run-as user's credentials with the option to load the user's profile. The failure occurs whether or not RunAs is called with the flag to force-load the run-as user's profile, and whether or not AutoIt spawned the earlier process that loaded the run-as user's profile.

Example code:

; N.B. MUST BE RUN AS A LIMITED USER TO EXHIBIT FAILURE
; declare yourself
Dim $ourPID, $ourPID0, $ourRead
; Run an initial process as the desired user
; This is only significant in this example in that
; it pre-loads the target user's profile; we could
; have right-clicked a program and chosen to Run As...
; this user and achieved the same effect.
$ourPID0 = RunAs("is", @ComputerName, "smacksmack", 1, @SystemDir & '\notepad.exe', @SystemDir)
; Run child task with option to access STDOUT
$ourPID = RunAs("is", @ComputerName, "youwantanother?", 1, @ComSpec & " /c set", @SystemDir, @SW_HIDE, 2)
; Read the child task's STDOUT output
While 1
  $ourRead &= StdoutRead($ourPID)
  If @error Then ExitLoop
WEnd
; Display result
MsgBox(0, "Debug", @AutoItVersion & " yields:" & @CRLF & $ourRead)

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 Developers,

i did some tests on vista and windows XP, the sleep times of the sleep command is really vagua. I'm working on a software, where i need a sleep of 1 ms, but if i use Sleep( 1 ), the real stop time is 10 ms on Vista and 15 ms on xp. Here is a source code of testing the Sleep() function:

while 1
	
	$begin = TimerInit()
	Sleep( 1 )
	$dif = TimerDiff($begin)
	ConsoleWrite($dif & @CRLF)
	
Wend

The strange thing is: If you give a time of 11 ms on Vista, the sleep time is 21 ms (on xp the time is given: 16 ms -> 31 ms), or 22 for 32 ms on Vista etc.

it would be nice if the Sleep() function is preciser...

sorry for my bad english XD