Short question: is there any terminal multiplexer that runs in a Windows CMD shell? I suppose PowerShell could be enough too.
Complete question:
I have a Windows 7 SP1 on a powerful computer intended to run OCLHashCat, that is an intensive command-line number cruncher who uses to keep running for hours before finishing. Due to its needs of GPU power, this program must be run on this computer with Windows 7 SP1.
When I am "on the road", I use to connect to this computer to manage such program with my portable (netbook) and through a mobile internet line that is often very slow, expensive, and uses to disconnect unexpectedly.
I can connect to the GUI of my Windows 7 via, for example, VNC Server, but it consumes a great bandwith, it is slow, and the screen of my portable is too small (the Win7 computer features a 32" screen, and that makes window-moving rather awkward).
So the ideal solution would be to use only text/terminal transfers:
- Connect via remote text console (SSH, for example) to the Win7 SP1 machine.
- Manage OCLHashCat to start/stop/review the specific process.
- Disconnect keeping the process running when needed.
By working this way I will reconnect later to check the progress of OCLHashCat.
This is the default behavior of the classic GNU Screen in Linux.
But there is no screen for Windows capable of running in text mode, or I have not been clever enough to find it.
The best I have found until now is CygWin's Screen version, but it only runs in graphics terminal, like mntty
.
So, my question is: is there any GNU Screen or equivalent for Windows capable of running in text mode (not GUI), so I can run OCLHashCat remotely?
I have checked:
- CygWin's Bash terminal, that runs in remote SSH sessions, but can not work with
screen
ortmux
. They fail with aopen terminal failed: not a terminal
message. - Any other terminal I have checked, wheter Cygwin's or Windows native (Tera Term, Babun... etc), needs GUI to start, so it can not be run from remote SSH.
I know that there is a version of OCLHashCat for Linux, but I need my powerful computer to keep Windows 7 SP1 for now.
I know about this method based on PowerShell background jobs, but it does not allow me to check the progress of the remote command-line program.
Any ideas, please?