I've just started using Everything. I have a lot of external drives and this is a good tool to catalog them. I wrote a simple script that will catalog a attached hard drive to a efu file. I know this is already built in, what I added was to generate the file name using the drive label+serial number which makes it easy to identify.
Special thanks to member NotNull for his scripts!
My workflow :-
- attach external drives
- set env variable EFUPATH to e.g. d:\save\efu (defaults to .\efu)
- run listdrives.cmd - shows all attached physical drives
- for each of them run 'catd <drive>'
- backup efu folder to cloud (e.g. GDrive)
- run allefu.cmd to browse all combined efu's (this is very slightly tweaked version of NotNull's excellent masterefu.cmd, modified to read env variables)
Any suggestion is welcome. Perhaps the combined efu should also be stored on disk? (this will need change to masterEfu script). Another thing I am looking at is running this automatically whenever a new drive is inserted.
My scripts to catalog and browse multiple drives
My scripts to catalog and browse multiple drives
- Attachments
-
- myscripts.zip
- (1.76 KiB) Downloaded 82 times
Re: My scripts to catalog and browse multiple drives
Not yet tested, but take a look at viewtopic.php?f=2&t=6162
(although that contains just other methods to do the same as you are already doing, so might not be useful after all
)
(although that contains just other methods to do the same as you are already doing, so might not be useful after all
)Re: My scripts to catalog and browse multiple drives
So your script does a lot more and is obviously a bit more advanced, I'm learning a few things from it. I think I'll steal the code for drive label/enumerating (which I previously stole from stackoverflow 
) and some wmic tricks. Also I didn't now you could have exclude_folders etc in an ini file.
So you are storing everything in a separate database and invoke Everything with it. Is there any pro/con to this approach vs the one where you load an efu file? In both cases it will only use the contents of that db/efu right? I have it installed as service so don't need the portable functionality.
Is there anyway to browse with a tree? e.g. could you use the csv to generate a tree. e..g when I load the master efu made from ~10 drives, all of it will be loaded, and then to see contents of a disk I do 'filelistfilename:id'. I'm guessing same will be needed with the script above, but the drives will appear as a folder? Is there another way.
I enabled folder size indexing so I can see folder sizes, but I'm wondering how much that will slow things down?
) and some wmic tricks. Also I didn't now you could have exclude_folders etc in an ini file.So you are storing everything in a separate database and invoke Everything with it. Is there any pro/con to this approach vs the one where you load an efu file? In both cases it will only use the contents of that db/efu right? I have it installed as service so don't need the portable functionality.
Is there anyway to browse with a tree? e.g. could you use the csv to generate a tree. e..g when I load the master efu made from ~10 drives, all of it will be loaded, and then to see contents of a disk I do 'filelistfilename:id'. I'm guessing same will be needed with the script above, but the drives will appear as a folder? Is there another way.
I enabled folder size indexing so I can see folder sizes, but I'm wondering how much that will slow things down?