Jump to content

Recommended Posts

Posted

I've written a script to catalog DVDs to text file, though it will do any file tree. It list folders, files and the file sizes. It is based on using the _FileListToArray and FileGetSize functions, working through the selected tree. With disks it is slow going when you have 40-50,000 files in the tree. It is however comparable in speed with the commercial software I have been using (emulating their format) and more accurate.

When you browse any file tree using Windows Explorer or in my case Directory Opus, all the information is visually available in a fraction of the time, including a complete *.* file listing. Isn't there some means of tapping into that almost instant information? Is the bottleneck simply the time taken to move the information to where you want it?

The file listing is fairly quick. Getting the file sizes seems to take the most time. The _FileListToArray function in the File.au3 is purely related to path. I suppose one could add the FileGetSize at that stage rather than later?

Posted

Thanks for the tip. I've been using _FileListToArray. In order to use the posted UDF I'll have to start from scratch reading into a 2D array (name and size) but that's fine.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...