Process overload when running commands through switch

[Spikeedoodles]

Hey there, I am making a tool that automates commands on the command prompt.  Here is an example:

expandcollapse popup

While 1
      Switch GUIGetMsg()
         Case $GUI_EVENT_CLOSE
            Exit
         Case $b_ipconfig
            Call ("ipconfig")
         Case $b_netstat
            Call ("netstat")
         Case $b_arp
            Call ("arp")
         Case $b_proc
            Call ("tasklist")
         Case $b_user
            Call ("user")
         Case $b_group
            Call ("localgroup")
         Case $b_sysinfo


      EndSwitch
   WEnd
EndFunc
Func ipconfig()
   Run(@ComSpec & " /c " & 'ipcofig > '&$path&"ipconfig.txt", "", @SW_HIDE)
EndFunc
Func netstat()
   Run(@ComSpec & " /c " & 'netstat -an> '&$path&"netstat.txt", "", @SW_HIDE)
EndFunc
Func arp()
   Run(@ComSpec & " /c " & 'arp -a > '&$path&"arp.txt", "", @SW_HIDE)
EndFunc
Func tasklist()
   Run(@ComSpec & " /c " & 'tasklist > '&$path&"proc.txt", "", @SW_HIDE)
EndFunc
Func user()
   Run(@ComSpec & " /c " & 'net user > '&$path&"users.txt", "", @SW_HIDE)
EndFunc
Func localgroup()
   Run(@ComSpec & " /c " & 'net localgroup > '&$path&"group.txt", "", @SW_HIDE)
EndFunc

When I run the tool, I get completely overloaded by these "Console Window Host" (conhost.exe) applications that almost crash my PC if I dont stop the script quick enough.  What are these and how can I make them not appear?  Originally I made the Run commands happen within a switch but moved them to separate functions to see if that would help .... it didnt.

[Jos]

What is the name of your script and it might help to show the total script?

Jos

[clicked]

I might consider putting a sleep inside the While loop.

[Jos]

I might consider putting a sleep inside the While loop.

There is one already by using GUIGetMsg().

The issue is it keeps shelling CMD sesions which could be trigger by giving the script the "wrong" name.

Jos

[Spider001]

https://www.autoitscript.com/autoit3/docs/functions/GUIGetMsg.htm

i use $idMsg = GUIGetMsg() this way i had the same problem like you a long time ago.

i use it normal, the moment i got problems i use it this way and it works then

Local $idMsg = 0
    ; In this message loop we use variables to keep track of changes to the radios, another
    ; way would be to use GUICtrlRead() at the end to read in the state of each control
    While 1
        $idMsg = GUIGetMsg()
        Select
            Case $idMsg = $GUI_EVENT_CLOSE
                MsgBox($MB_SYSTEMMODAL, "", "Dialog was closed")
                ExitLoop
            Case $idMsg = $GUI_EVENT_MINIMIZE
                MsgBox($MB_SYSTEMMODAL, "", "Dialog minimized", 2)
            Case $idMsg = $GUI_EVENT_MAXIMIZE
                MsgBox($MB_SYSTEMMODAL, "", "Dialog restored", 2)

            Case $idMsg = $idButton_1
                MsgBox($MB_SYSTEMMODAL, "", "Default button clicked:" & @CRLF & "Radio " & $iRadioVal1)

            Case $idMsg >= $idRadio_1 And $idMsg <= $idRadio_3
                $iRadioVal1 = $idMsg - $idRadio_1

        EndSelect
    WEnd

Edited December 29, 2014 by Spider001

[mikell]

Did you try RunWait instead of Run ?

[BrewManNH]

Instead of coming up with irrelevant suggestions, wait until the OP posts the script he's using.

My bet is one of his controls doesn't exist, and one of his case statements is running a program with the same name as his compiled script (probably using the non-existent control ID). But, like the rest of you, it's just a guess and we don't have nearly enough information yet to be giving suggestions to the OP.