This works flawlessly for me, with the same binary.
There are half-confirmed rumors that Microsoft changed their
implementation of how quoted strings are handled when the arguments
passed to a C program are expanded. You said you were on Windows 7,
so perhaps this is what causes this problem for you. It is possible
that programs need to be linked in some special way to avoid these
very serious regressions.
To help find a workaround, can you run "depends find.exe" on find.exe
from the package
If quoted arguments work "as I'd expect" (i.e. quotes are removed,
unless escaped by a backslash, in which case the backslash is removed
and the quote stays), then this command should display the list of all
*.c files in the directory where you invoke this command. (Do it in a
directory where *.c files do exist.) If quoted arguments don't work,
then the result will probably be the exact replica of the --eval
argument, or maybe some weird error message.
> The "find.exe" in this package
> http://unxutils.sourceforge.net/ > produces:
> C:\emacs\lisp>find . -name *find*
> C:\emacs\lisp>find . -name "*find*"
> I don't know why.
> I think the second "find.exe" is more powerful in my env..
Can you please run "depends find.exe" on this version of find.exe as
well, and see which DLLs it uses?