TM> Ok, sure, Jonathan got steamed up a bit too much,
 TM> dropping such an overzealous complaint in this area, but I found his
 TM> explaination of what he expected but didn't get VERY clear. 

Thank you.

 TM> And, yes, even though I believe JP's technical support department 
 TM> to do a great job _in_general_, in _this_ case they HAVE failed 
 TM> to see beyond the MS-DOS limits, IMHO.
 TM> [...]
 TM> But JP slipped up, defending that error, which is NOT acceptable
 TM> provided Jonathan's description of the mistake was as clear in 
 TM> his mailing to them, as it was here.

It was clearer!  

I've done technical support myself, so I know how difficult it can be to
understand what the user is on about.  So I sent the sort of bug report
that I'd like to receive myself, complete with a one-line description of
the problem in FFIND, the platforms and product versions that I've found
the problem in, a detailed step-by-step demonstration of how to replicate
the problem on any of those platforms, and what the correct wildcard
handling behaviour (as seen in the DEL, DIR, COPY, MOVE, REN, and other
commands, no less!) should be.

Obviously it was clear enough, since I didn't receive a reply asking what
exactly my problem was.  (-:  That, I could have accepted.  Instead I
received a reply saying that "of course" the wildcard
"*S" should match the name "DOS.DAT" -- it matches any
name that ends in an 'S'.  As you say, that is *unacceptable*, because it
is so clearly wrong.

 ¯ JdeBP ®

--- FleetStreet 1.19 NR