I am using the FileDir command to generate a list of files over a year old.

When I pipe the output to a text file we only capture 266 lines of data. If we simply disply the results to the screen we see several hundred lines more of data.
C:\temp\24x7\FileDir.exe /N /F /A 365 /O /S C:\*.* > C:\temp\24x7\list.txt

I have tried redirecting the output to a different drive with the same results.

Your suggestions are appreciated.

~Joe

Here what I think is happening. You run this with /S option (for recursive directory processing) and somehow only files from the main directory get written to the log, probably because FileDir calls itself recursively for subdirectories.

Try creating a batch file containing 1 line
C:\temp\24x7\FileDir.exe /N /F /A 365 /O /S C:\*.*

and then calling the batch with output redirection to a log file.

: I am using the FileDir command to generate a list of files over a year old.

: When I pipe the output to a text file we only capture 266 lines of data. If
: we simply disply the results to the screen we see several hundred lines
: more of data.
: C:\temp\24x7\FileDir.exe /N /F /A 365 /O /S C:\*.* > C:\temp\24x7\list.txt

: I have tried redirecting the output to a different drive with the same
: results.

: Your suggestions are appreciated.

: ~Joe

I get the same results with my test server and my production server.

~Joe
: Here what I think is happening. You run this with /S option (for recursive
: directory processing) and somehow only files from the main directory get
: written to the log, probably because FileDir calls itself recursively for
: subdirectories.

: Try creating a batch file containing 1 line
: C:\temp\24x7\FileDir.exe /N /F /A 365 /O /S C:\*.*

: and then calling the batch with output redirection to a log file.

What version of FileDir are you running?

: I get the same results with my test server and my production server.

: ~Joe

Version 1.03

: What version of FileDir are you running?

It works for me.

Check if you have any file with a broken name that causes the system stop writing to the output file.
I remember a while ago I found a file in the winnt/system32 whose name contained ASCII 0 character ( I guess some program failed then and created an invalid file name).

: Version 1.03

I decided to use the windows resource kit forfiles.exe. I had to add an additional line of code to my 24x7 scipt to skip directoies. Other then that it seems to be fine.

~Joe

: It works for me.

: Check if you have any file with a broken name that causes the system stop
: writing to the output file.
: I remember a while ago I found a file in the winnt/system32 whose name
: contained ASCII 0 character ( I guess some program failed then and created
: an invalid file name).

: It works for me.

: Check if you have any file with a broken name that causes the system stop
: writing to the output file.
: I remember a while ago I found a file in the winnt/system32 whose name
: contained ASCII 0 character ( I guess some program failed then and created
: an invalid file name).

If you use >> instead of > you won't overwrite your txt file.

Lamar