Ahhh, darnit, why didn't I think of that? Seems Billrich didn't either as he also suggests replacing the > char with the \ char.
But Billrich was on the right track. Consider: You have a command window in a folder, D:\Path\folder. Here is the prompt that you see:
(1)
D:\Path\folder>
You want to run a program called Program.exe (which is in that folder) so what do you type at the prompt? Why, its name (and extension probably). So, just before you hit Enter the command window looks like this:
(2)
D:\Path\folder>Program.exe
You want to supply it with with a parameter string: /a:b:\cdef\*.ghi so you add that after the program name:
(3)
D:\Path\folder>Program.exe /a:b:\cdef\*.ghi
Now: how do you put all that in a one line batch file so that you can just e.g. plonk it on your desktop and thereafter double click its icon when you want to perform the operation? Why, you need the path to the program, its name and extension, and the parameter string:
(4)
D:\Path\folder\Program.exe /a:b:\cdef\*.ghi
The only difference visually between (3) and (4) is that the final > character from the prompt has been replaced by the final \ character of the program folder path. What Billrich needed to add were the double quotes necessary because "Program Files" contains a space.
"C:\Program Files\PrintFile\prfile32.exe" /s:c:\test\*.txt