How to use ffind to find older files?

May 20, 2009
293
5
57
ITALY
I upgraded my TakeCommand license to 12.11.73 and I tried to use the ffind command to find some older files, since it can work on all drives, but the command is too quick and does not find all files. I looked into documentation, but I could not find where I make a mistake. Does ffind is based on an index that I have to build? What is the syntax to use dir on all drives?

For example, from the root of "C:" drive (FAT32), if I use *dir I get:

[C:\]*dir /[dw2011-07-28,2011-07-28] /A:-d /M /S *log*

Volume in drive C is unlabeled Serial number is 4717:4a93
Directory of C:\*log*

28/07/2011 17:15 19.828 install_log

Directory of C:\LAVORO\clienti\BARNI\QLA2340_24P0960\SANsurfer\*log*

28/07/2011 17:10 777 SANsurfer_Install_Wizard.log

If I type

[C:\]*ffind /[dw2011-07-28,2011-07-28] /A:-d /Dc /S *.*
C:\install_log

1 file

[C:\]

So, the *dir, with the same parameters, seems to be able to find more files, I used *log* to find only some, wherease *ffind finds only one.

Any idea?

Thank You

Rodolfo Giovanninetti
 
Aug 9, 2009
229
1
ADD /V (VERBOSE)

-----Original Message-----
From: Rodolfo Giovanninetti
Sent: Thursday, 11 August 2011 9:27 p.m.
Subject: [Support-t-3063] How to use ffind to find older files?


I upgraded my TakeCommand license to 12.11.73 and I tried to use the
ffind command to find some older files, since it can work on all drives,
but the command is too quick and does not find all files. I looked into
documentation, but I could not find where I make a mistake. Does ffind
is based on an index that I have to build? What is the syntax to use dir
on all drives?

For example, from the root of "C:" drive (FAT32), if I use *dir I get:

[C:\]*dir /[dw2011-07-28,2011-07-28] /A:-d /M /S *log*

Volume in drive C is unlabeled Serial number is 4717:4a93
Directory of C:\*log*

28/07/2011 17:15 19.828 install_log

Directory of C:\LAVORO\clienti\BARNI\QLA2340_24P0960\SANsurfer\*log*

28/07/2011 17:10 777 SANsurfer_Install_Wizard.log

If I type

[C:\]*ffind /[dw2011-07-28,2011-07-28] /A:-d /Dc /S *.*
C:\install_log

1 file

[C:\]

So, the *dir, with the same parameters, seems to be able to find more
files, I used *log* to find only some, wherease *ffind finds only one.

Any idea?

Thank You

Rodolfo Giovanninetti
 
May 20, 2009
293
5
57
ITALY
Thank You, but I did not see any change. The /V parameter seems to be used only if I am looking for text inside files.

-----Original Message-----
ADD /V (VERBOSE)
 
May 20, 2009
293
5
57
ITALY
Does it work as expected if you omit the end date, e.g. /[dw2011-07-28] ?

No, it finds five files, but *dir and *pdir find each 238 files.

I tried also, but with the same result:

*ffind /[dw2011-07-28] /A:-d /S C:\*.*

Thank You again

Rodolfo Giovanninetti
 
May 20, 2009
293
5
57
ITALY
And if you use C:\* instead of C:\*.* ? (You understand that the latter only returns filenames which contain a period, right?)

No change at all, if I use "C:\*.*", "C:\*" or "C:\". And one of the files that it returns is "install_log" that is, without any period, in the root of "C:".

Thank You very much again

Rodolfo Giovanninetti
 
Aug 9, 2009
229
1
sorry about that Sir I was halfway between snoozing to full on crashing
into keyboard
although your cmd worked as expected under xp-sp3 4ntv8 with all files
in date range displaying

-----Original Message-----
From: Rodolfo Giovanninetti [mailto:]
Sent: Thursday, 11 August 2011 10:41 p.m.

Subject: RE: [Support-t-3063] Re: How to use ffind to find older files?


Thank You, but I did not see any change. The /V parameter seems to be
used only if I am looking for text inside files.

-----Original Message-----
ADD /V (VERBOSE)
 
Aug 9, 2009
229
1
Which is unusual because the help file doesn't enlighten me to why it
worked under 4nt-v8
*ffind /[dw2011-07-28,2011-07-28] /A:-d /Dc /S *.*

-----Original Message-----
From: Kachupp
Sent: Friday, 12 August 2011 2:23 p.m.
Subject: RE: [Support-t-3063] Re: How to use ffind to find older files?


sorry about that Sir I was halfway between snoozing to full on crashing
into keyboard
although your cmd worked as expected under xp-sp3 4ntv8 with all files
in date range displaying

-----Original Message-----
From: Rodolfo Giovanninetti [mailto:]
Sent: Thursday, 11 August 2011 10:41 p.m.

Subject: RE: [Support-t-3063] Re: How to use ffind to find older files?


Thank You, but I did not see any change. The /V parameter seems to be
used only if I am looking for text inside files.

-----Original Message-----
ADD /V (VERBOSE)
 
I can confirm that I see different results from otherwise identical dir and ffind commands when a date (or size) range is used. So these commands:

dir /[s250k] /A:-d /S d:\*log*
ffind /[s250k] /A:-d /S d:\*log*

return (very) different results, with the dir finding 235 files and the ffind none, whilst these

dir /[d2011-07-28] /A:-d /S d:\*log*
ffind /[d2011-07-28] /A:-d /S d:\*log*

output 197 and 1 respectively.

If I remove the range parameter then both commands return the same number of files.

FWIW both commands are aliased on my system - to add the /nj switch, because otherwise all such commands loop until they crash - but otherwise are unadorned. The D partition is NTFS (I don't have any FAT32 drives on this system and therefore cannot check).


TCC 12.11.73 x64 Windows 7 [Version 6.1.7601]
TCC Build 73 Windows 7 Build 7601 Service Pack 1
 
Similar threads
Thread starter Title Forum Replies Date
J ffind does not find files Support 4
T FFind - can we display n number of lines after the find? Support 2
B Fixed FFIND doesn't find last character in file without CR/LF at EOF Support 1
vefatica FFIND /S, find directory with specified name? Support 7
D Why doesn't ffind find directory? Support 3
D ffind hangs on large file Support 18
Alpengreis ffind dialog (/W) problem Support 4
vefatica FFIND, temp files? ... not deleted? Support 0
S FFIND text that includes " Support 7
D ffind /e hangs Support 7
vefatica FFIND needs work Support 12
Joe Caverly Multiple Text Searches at once using FFIND or TPIPE Support 4
Kachupp FFIND TPIPE Support 9
Gamegod ffind bug with chinese Support 2
vefatica FFIND and multi-line regular expressions Support 4
vefatica Make FFIND a bit more friendly? Support 14
M Trying to use ffind with a @file.lst doesn't work Support 4
vefatica Corruption from FFIND? Support 5
vefatica FFIND /S and System32? (and an OT mystery) Support 14
vefatica Help nit (FFIND and DIR with /S) Support 0
R ffind not setting %_ffind_ vars if /f is used Support 7
M FFIND wordA AND wordB Support 4
vefatica FFIND and _? Support 1
dcantor How to make line numbers fixed width in FFIND Support 11
C FFind /w works but FFind /= doesn't? Support 2
vefatica FFIND goes crazy Support 8
Stefano Piccardi TCC 13 vs. TCC 14 different FFIND /E"d$" output Support 1
Steve Pitts How to? FFIND, regular expressions and double quotes Support 4
vefatica FFIND /S in my profile directory Support 2
A How to? Pass output from ffind to another command in a BTM file Support 5
Phileosophos Can FFIND match file names with a regular expression? Support 19
vefatica FFIND and size ranges Support 1
J How do I - ffind - with multiple items Support 10
M FFIND and LIST does not work for UTF-8 fles Support 10
C FFIND ERRORLEVEL Support 2
L FFIND no result display Support 10
H Directory wildcards not working with ffind Support 3
D ffind and directories Support 2
Stefano Piccardi detecting BOM, FFIND multibyte regex Support 18
dcantor FFIND syntax -- is /E"regex" /X supported? Support 2
S FFIND and quoted strings Support 4
S FFIND /E"reg exp" : not case insensitive Support 4
J Problem with FFIND Support 1
Alpengreis List command: text truncated in find box (german) Support 9
R FIND command error Support 9
vefatica Find Files/Text dialog: does it work? Support 0
R How to? Find a specific file in subfolders Support 11
Patulus TCHistoryLog: TCC: (Sys) The system cannot find the path specified Support 15
D unzip fails to find valid license Support 3
R Find in screen buffer - find next behavior Support 0

Similar threads