Run command prompt in background in Windows

[ghost]

In Linux the terminal doesn't show, yet it does in the Windows TorChat version. I understand this, although I was researching on ways to hide a command prompt, and apparently it might be possible (though I haven't tested this out).

It looks like the use of a "START" command is supposed to run processes in the background, akin to Linux "command &". Might make things slightly nicer in Windows since there will be no command prompt visible. :)

From what I can see, something like START /B program

References: http://superuser.com/questions/198525/how-can-i-execute-a-windows-command-line-in-background http://www.tomshardware.com/forum/34598-45-windows-command-background-unix (checkout the /b toggle comment) http://www.computerhope.com/starthlp.htm

[prof7bit]

are you running it from source (the .py file) or are you running the .exe version? The .exe is not supposed to open a command prompt, it was built with console=False in pyinstaller. What version of windows are you using? What version of TorChat are you using? Maybe some unofficial debug version with activated console?

[ghost]

Using Windows XP, Pidgin, and the Pidgin TorChat plugin alpha 14, with the Tor Expert Bundle installed. When I run TorChat in this configuration, I am getting a command prompt window that shows up, and shows Tor establishing the circuit, etc. My friend which is running Windows 7 (I think) is getting the same thing (he's using alpha 13 libtorchat plugin for Pidgin).

[prof7bit]

2012/9/2 Roejames12 [email protected]

Using Windows XP, Pidgin, and the Pidgin TorChat plugin alpha 14, with the Tor Expert Bundle installed. When I run TorChat in this configuration, I am getting a command prompt window that shows up, and shows Tor establishing the circuit, etc. My friend which is running Windows 7 (I think) is getting the same thing.

Ok, sorry, I thought you were referring to the classic standalone Python version of TorChat.

It is indeed not intended to show the running Tor process in a console window, It seems I enabled this temporarily only for debugging purposes must have forgotten to disable it again in the latest release. I develop on Linux (and cross-compile from there) and only test on windows (XP) when I change things that might work differently on windows. I should have noticed this console window but usually when testing on windows I run it from within a console anyways, so this might be the reason I did not notice it. The next release will not have this behavior anymore.

Thank you for reporting this.

[berrythesoftwarecodeprogrammar]

lol would be nice to have a release just for this fix ;-;