Expected behavior of forfiles.exe on Windows 2000
How can I tell that forfiles.exe has been installed correctly? Is the behavior of forfiles.exe on Windows 2000 different than other versions of Windows? I'm calling forfiles.exe on Microsoft Windows 2000 [Version 5.00.2195] as follows: c:\>forfiles /v /c "cmd /c echo Found @file" forfiles.exe is returning information similar to "dir /A /B". The above command is listing the files and does not appear to be performing the /c switch, or any of the switches. The command does not seem to recognize /?. Based upon the documentation that I have come across, /? should return the available switches and /c should carry out the respective command.
August 1st, 2011 1:28pm

I'd ask them here. http://social.technet.microsoft.com/Forums/en-US/ITCG/threads Regards, Dave Patrick .... Microsoft Certified Professional Microsoft MVP [Windows]
Free Windows Admin Tool Kit Click here and download it now
August 1st, 2011 1:42pm

Thanks!
August 1st, 2011 1:57pm

You're welcome. Regards, Dave Patrick .... Microsoft Certified Professional Microsoft MVP [Windows]
Free Windows Admin Tool Kit Click here and download it now
August 1st, 2011 1:59pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics