DosTips.com

Is there a way to reliably get the count of arguments a batch file was called with, safe against odd inputs, and preferably without invoking external programs or temp files? Some test cases which fail most naive counting approaches would be... ⋅ " --- expected count 1 ⋅ &quo...

My PIPE.COM program is only 69 bytes in size, so it is a very good replacement of FINDSTR to be used in these cases. If you are worried about where to get my program from, here it is; just copy the 69 bytes below to a file named PIPE.COM and it is ready to run: ë2´)€ì!Í!ŠÐŠà€Ä!€ü.u.€þ+u)R²A€ê!´#€ì!...

dbenham wrote:I ran this in Vista.
Has it always been like this Are there any versions that act differently

Confirmed in Vista x64 (biz) and Win 7 x86 (pro), both at the regular and elevated cmd prompts.

XP (pro) has it always uppercase, though. Funny, indeed.

Liviu

In other words, the test checks if a variable contains =. It is not designed to test if a command argument contains =. The test can't begin until we have a value in the variable. Thanks for clarifying, though the way it was posted it sure looked like it was meant to test the command argument being ...

I don't have a good solution for replacing =, but I do have a quick test to see if a value contains = . This test may return false positives if the value contains '!' exclamation marks. For example, create a directory "C:\x=y" and make it current, so that "%cd%" is "C:\x=y&...