Odd Console (CUI) Behavior in Win 8

[wraithdu]

I'm not sure whether to classify this as a bug or not yet, but this simple script no longer seems to work in Win 8 when compiled as CUI. It should pause and wait for input as it does on Win 7, but it just exits immediately. You can still see that the 'pause' command prints its text however. Any ideas, or go with bug and I'll open a ticket?

#NoTrayIcon
#AutoIt3Wrapper_Change2CUI=y

RunWait(@ComSpec & " /c pause", "", Default, 0x10)

It's strange that something as basic as this would change from Win 7 to 8.

Edited December 11, 2012 by wraithdu

[Richard Robertson]

What happens if you were to run that command line yourself in the prompt?

[wraithdu]

Normal behavior, just like a .bat file.

[Richard Robertson]

Ok. Couple questions on the code.

Why are you passing the default keyword for window state? That results in a hidden window which seems like it would cause issues when you want it to share the CUI. I don't imagine that's the problem though.

Second, what's this 0x10 flag? I don't see that documented anywhere.

[BrewManNH]

From looking at the help file for RunWait, using 0x10000 in the last parameter spawns a new console window, but you're hiding it by using the Default keyword.

[wraithdu]

The show state is irrelevant. The 0x10 flag means to use the existing console window (as opposed to creating a new window, see the Run() command), which is visible by default since it is compiled as a CUI. So the command runs in the context of the existing console window. Try it on Win7, it works as it should. The diff on Win8 is that it doesn't pause and wait for input, it just blows right through and exits.

You really think I'd post non-working code without testing it... gimme a little credit here

Edited December 13, 2012 by wraithdu

[BrewManNH]

No offence intended, I just confused 0x10 and 0x10000 in my head.

Perhaps when that value ($STDIO_INHERIT_PARENT = 0x10) was added to the Runxxx commands something was done incorrectly and it took Windows 8 to discover it.

Edited December 13, 2012 by BrewManNH

[wraithdu]

I think you're probably right about the flags param. There was some other weirdness I remember as well when trying to read console input using Mat's console UDF (ReadConsole API function). Here's the addition and note I made:

; ugly fix for input handle when script is compiled as CUI, otherwise reading input fails
_WinAPI_CreateFile("CONIN$", 2, 6, 6)

So I definitely think that console mode and IO streams needs to be revisited.

Edited December 13, 2012 by wraithdu

[Richard Robertson]

I never said it was invalid, only that I didn't see it documented anywhere.