DosTips.com

Just tried your code and made the first line of the code be a TITLE statement. Then put more TITLE statements in the code. The Window Title changed every time. Thank you for letting me know the result of your testing, Squashman. It seems as if these things are never as straight-forward as I imagine...

I've been experimenting setting up different console sessions (configured for different purposes) using basic commands like title, color, prompt etc. via the cmd.exe /K switch. After much trial and error (mainly error) I mostly got things working as I wanted. However there were certain instances whe...

Aacini wrote: ↑

28 Oct 2018 14:57

As I understand it, they want to enter "closeall" from the keyboard only ...

Correct.

This should work: doskey closeall=taskkill /IM "cmd.exe" /f ^>nul 2^>^&1 Thank you SO much, Antonio. This works perfectly, and it's exactly what I wanted. 8) This time I will make a careful note of how it's done, so that I can use it as a template guide for achieving a similar effect for other comm...

You can, however, set "closeall=taskkill /IM "cmd.exe" /f >nul 2>&1" %closeall% Thank you, This now hides the output, but in order to get it to work I have to type %closeall% including the percentage marks. How can I get it to work with just the word closeall on its own? I had a similar issue to th...

How do I get the following command to work from within a batch file? doskey closeall=taskkill /IM "cmd.exe" /f >nul 2>&1 I want the output of taskkill to be suppressed. It works perfectly if typed at the command line, but when the above command is used in a batch file, you still see the output text ...

Thanks for your reply, but I'm having trouble understanding it. To clarify what I am trying to achieve: In the batch file that I showed in the first message of this thread, I want only the code that is before/above the :choice command to run by default when the batch file is run (the rest of the cod...

I am trying to learn a bit more about the very basics of batch files, so I am messing around with a simple batch that I am testing as an autorun script for an elevated privileges cmd prompt window. The autorun batch file is basically just a few commands that run on startup of the command window (in ...

I think you never mentioned before that you used a batch file.Steffen I did, actually. I am using a stripped down batch file shown below. (I removed various other macros and comments from my main batch file for purpose of testing). I even posted a full copy of the batch file that I was using: @ECHO...

OK, final update. I have managed to fix it myself (which I can't quite believe). I was trying out various different things and I ended up running the command doskey / macros to see if there were any clues in the output. Doskey listed all of my macros exactly as I had entered them into my batch file,...

Further to my post above, I have now tracked down the issue. It wasn't any kind of system problem, but rather just something specific to the way that I was using the commands on my main system compared to what I did differently when using the virtual machine. The purpose of me creating these macros ...

Thanks for doing that test. As I mentioned in my last post, I had eliminated psexec as the source of the problem because I experienced exactly the same issue when I did a test using just notepad on its own. I therefore decided to try doing another test, but this time on a virtual machine, and it wor...

Ok, I have done some more testing and it does not seem to be psexec that is the problem. The problem is specifically with the command %$*% . I'm not sure what it's doing, but it is not enclosing the text with percentage signs (at least not on my system). I tried using notepad as a test (to remove ps...

Hi, the problem is something to do with this line: doskey su=psexec -s -i %$*% If I remove the % marks from before and after $* and then type su %regwork% , then it works fine. But if I use the command shown above (which is what you gave me to have the macro perform the expansion itself) then it doe...

This is exactly the kind of solution that I was hoping for. Thank you. Unfortunately I can't get it to work though. I am using a stripped down batch file shown below. (I removed various other macros and comments from my main batch file for purpose of testing). @ECHO Microsoft Windows [Version 6.1.76...