https://www.ugmfree.it/forum/messages.aspx?TopicID=911 SyMenu - Troubleshooting & Bug Reports - Windows Command problem - Messages en-us http://blogs.law.harvard.edu/tech/rss Tue, 08 Oct 2024 18:15:26 GMT Tue, 08 Oct 2024 18:15:26 GMT https://www.ugmfree.it/forum/messages.aspx?TopicID=911
If you run the app, you can choose which columns are visible in the process list. If you add "Command Line" to the columns you can see it. I usually either try to find the process, or, using the small target icon on Process Explorer, you can drag that target over the window you are interested in and process explorer will take you right to that specific process.

I'm open to testing anything you might try to cook up. Sorry for the delayed response.]]> Tue, 08 Oct 2024 18:15:26 GMT https://www.ugmfree.it/forum/messages.aspx?TopicID=911
Wow... I think this is the first time I receive a bug report so detailed. Thank you for this.

You are right, with the last version I changed the escaping command system.
Before that version escaping a forbidden char was done with the ^ char.


So for example:
C:\(MeAndYou)
that's a perfectly allowed name in Windows but created some problems if executed in a process, was changed in:
C:\^(MeAndYou^)


But this method had some drawbacks for example with the & character.

The solution with the double quotes seems a good one with a minimum impact and instead... some commands fail because of this one.


So a command like:
"ipconfig"
works well regardless the double quotes but:

"ipconfig /all"
won't work at all.... Windows mysteries...

So what can we do now?

I think I could try to recognize when the command contains a path and only in that case I can escape it.
This solution should fix any problem.
What do you think about it?

BTW how are you able to sniff the command send to the shell? I'm asking because it could be a useful technique for me too.]]> Thu, 26 Sep 2024 21:31:47 GMT https://www.ugmfree.it/forum/messages.aspx?TopicID=911 Thu, 26 Sep 2024 15:21:24 GMT