Just a point of information - it isn’t the command that does the wildcard substitution on UNIX - it’s the shell. That’s why it works with everything. You type “argle *.txt” and “argle” is invoked as if you had typed “argle foo.txt bar.txt blech.txt”
Rather than address your specific problem, I’m going to make a reccomendation.
If you are used to UNIX utilities, you are ahead of the game getting ahold of a set of them for the PC, including a shell. For years every PC I’ve had any control over has had the MKS toolkit installed on it.
Trouble with MKS is that you have to pay for it. The cygnus utilities are free:
Personally, I think MKS is a lot better[sup]1[/sup], but, again, Cygnus is free. Either of the solutions should provide you with a UNIX look-alike shell, and common utilities like “sed”, “grep”, et al. The MKS toolkit provides a good version of vi for a Windows environment.
[sup]1[/sup] - MKS adapted UNIX commands to work with Windows metaphors, such as paths including drive letters, preserving the idea of a current directory on each drive, and so on (their ksh version knows the distinction between “cd d:” and “cd d:/”). MKS also comes with ksh, my shell of choice, rather than one of these various things that sprouted from csh. Cygnus has a concept of having to “mount” Windows paths as something which Cygnus utilities can then see as a UNIX directory structure. This sounds elegant. In practice, it’s annoying, particularly if you wish to do shell scripts which invoke normal Windows executables - you have to get back to the Windows file syntax to invoke them.