How to use ffind to find older files?

[Rodolfo]

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

 

[Kachupp]

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

 

[Rodolfo]

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)

 

[Charles Dye]

Does it work as expected if you omit the end date, e.g. /[dw2011-07-28] ?

 

[Rodolfo]

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

 

[Charles Dye]

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:\*.*

And if you use C:\* instead of C:\*.* ? (You understand that the latter only returns filenames which contain a period, right?)

 

[Rodolfo]

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

 

[Kachupp]

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)

 

[Kachupp]

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)

 

[Steve Pitts]

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