Bash should work from there on, if there's no other reason why it shouldn't. From the opened settings page just check the 'Developer mode' option, click yes on the dialog and restart the computer. HWndChild is the window handle ID of cmd.exe or calc.exe, and hWndNewParent is the window handle ID of the parent in this case the application that (indirectly) runs this code. For anyone having this problem, just open the settings and type 'developer' in the search bar, and click on the 'Use developer features' result. This SetParent function is declared in this way Public Declare Function SetParent Lib "user32" (ByVal hWndChild As Long, ByVal hWndNewParent As Long) As Long LSuccess = CreateProcess(sApplicationName, _Īfter some debug i have found the problem, when its invoked SetParent function (after Create Process) the cmd.exe closes, but not calc.exe. WCurrentDirectory = "C:\Windows\system32" SApplicationName = "C:\Windows\system32\cmd.exe" If i run calc.exe, this process does not closes immediately, this just happens with cmd.exe. When i run the following code to create a cmd.exe process in windows 10, the console application opens and then closes immediately.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |