- Aug
- 2,038
- 82
If I have the following files;
...and I try to use FFIND on said files;
Is this WAD?
I can understand if this is not supposed to work on <SYMLINK> files (it would be nice if it could).
If FFIND is not meant to work on <SYMLINK> files,
should there be a better error message instead of "The system cannot find the path specified."?
Joe
Code:
E:\Utils>dir mmf*.btm
Volume in drive E is New Volume Serial number is 2c1e:6e61
Directory of E:\Utils\mmf*.btm
2023-06-20 10:15 2,567 mmf.btm
2023-06-09 8:44 473 mmfclose.btm
2023-06-03 8:42 <SYMLINK> mmfopen.btm [E:\Documents\GitHub\TakeCommandConsole\Using Memory Mapped Files with Take Command Console\mmfopen.btm]
2023-06-05 19:16 <SYMLINK> mmfread.btm [E:\Documents\GitHub\TakeCommandConsole\Using Memory Mapped Files with Take Command Console\mmfread.btm]
2023-06-05 19:17 <SYMLINK> mmfwrite.btm [E:\Documents\GitHub\TakeCommandConsole\Using Memory Mapped Files with Take Command Console\mmfwrite.btm]
3,040 bytes in 5 files and 0 dirs 8,192 bytes allocated
...and I try to use FFIND on said files;
Code:
E:\Utils>ffind /vt"remode" mmf*.btm
TCC: (Sys) The system cannot find the path specified.
"E:\Utils\mmfopen.btm"
TCC: (Sys) The system cannot find the path specified.
"E:\Utils\mmfread.btm"
TCC: (Sys) The system cannot find the path specified.
"E:\Utils\mmfwrite.btm"
0 lines in 0 files
Is this WAD?
I can understand if this is not supposed to work on <SYMLINK> files (it would be nice if it could).
If FFIND is not meant to work on <SYMLINK> files,
should there be a better error message instead of "The system cannot find the path specified."?
Joe