andrese

Hi All, Just fixed this issue modifying optimize/forcemerge to call a different url depending on ES version(

I agree that remote command and remcom, stderr, out and in should be able to be managed in a more friendly way. As a small step in that direction I...

BTW if there is a poor soul that needs to execute against a 64 bits target right now, there is a "poor man" solution: Lets say you want to transfer...

Well as I really needed this to work I finally made some code patching. The patch makes remcom to transter comamnd to execute to %SYSTEMROOT% (p.e. c:\windows) instead of %SYSTEMROOT%\system32....

As a matter of fact, like it is now it should work from a 32 bits windows to a 64 bits windows (I am using it that way, and no...

About the compiled binary, the latest binary in git (https://github.com/kavika13/RemCom/tree/45e902f957c2d1bba519f5c2d47d1e6e8de648d0/bin/Release) from Feb 13, 2012 its the one I compiled with VS2005 with today's latest sources. Give it a try with...

As the last patch fixes the specific case of having a space as part of your filename it breaks executing "cmd.exe" commands (dir, cd, etc...) As an alternative I propose...

Confirmed it does work on Win 7 32 bits. Check issue #12 for 64 bits that has been fixed with a patch.

Now only slash is supported to pass parameters, but both slash and hyphen are filtered so you cant use them in your commands (for instance you can pass parameters to...

I agree, and it also seems quite a simple thing to do... at least copy a to TO the remote machine would be trivial as it is already doing that...