> JRS: In article <uvacvaq1f8k...@corp.supernews.com>, seen in
> news:comp.lang.pascal.borland, Femme Verbeek <fv@[at]> posted at Tue, 10
> Dec 2002 01:22:42 :-
> >"Dr John Stockton" <s...@merlyn.demon.co.uk> schreef in bericht
> >news:bu2a3rDCR389Ew8x@merlyn.demon.co.uk...
> >> JRS: In article <3DF312C8.1090...@freenet.de>, seen in
> >> news:comp.lang.pascal.borland, Markus Humm <markus.h...@freenet.de>
> >> posted at Sun, 8 Dec 2002 10:37:12 :-
> >> >What parameters do y<ou give FINDFIRST?
> >> >Do you operate on the same directory? Which one? Root?
> >> The given name, Anyfile or $3F, and a record. It uses the current
> >> directory, which is not root.
> >I assume you knew that CON is a reserved word in DOS.
> I assumed that we all know that.
> > It is treated as
> >a file but it refers to the keyboard. This is probably not the same as
> >the console mode in Delphi.
> In Delphi, what is found is not a true file; the *current* time is
> shown.
> >BP/TP usually has it's own routines for dos calls, therefore I don't
> >think that you can find it with findfirst, since that will try to find
> >the keyboard on the HD.
> As I said before, HUNT is also a 16-bit BP7 program, and finds CON - the
> same CON as Delphi, AFAICS.
> >If you want to have a command line parameter string CON, you must simply
> >discriminate it from the parameter list, and react to it in the ordinary
> >way with readkey etc.
> This is not a matter of reading the contents of CON; these programs read
> directory entries only. But a CON 'file' is standard input; it does not
> use ReadKey. Crt is *absent* from these programs.
> The problem is one of why the 16-bit BP7 program FILGEN fails to see CON
> with FindFirst, when the 16-bit BP7 program HUNT sees CON and the 32-bit
> D3 console mode program FILGEN also sees CON - all being run in the same
> Win98 DOS box.
> FILGEN16 cannot see CON or con.
> None of them, however, show CON on being asked for CO* or CO*.*.
> I am reminded that, given CON, HUNT actually seeks CON.* and finds CON;
> given CON., it seeks CON. and finds CON.
> FILGEN32, given CON or CON., finds; but does not find for CON.*.
> FILGEN16 finds for none of those.
> The problem is the *difference* between the two 16-bit versions, and
> that between FILGEN 16 & 32, while HUNT (16) matches FILGEN32.