Hi everyone
Sorry if this has already been answered.
If I download a newer version of Everything 1.5 portable, because I want the latest bugfixes and improvements, is there a way to retain the database of the files, with their metadata, from a previous portable version? So that the app doesn't have to scan everything again.
For example, I have some folders with many videos, and I have added some columns with 'Length' (of the videos). It took quite some time for the app to scan and retrieve all the Length attributes for all the videos. It would really be helpful for me to not go through the scan again.
Thank you for any help!
Updating Everything 1.5 portable, retaining database of metadata
-
adriancornea52
- Posts: 8
- Joined: Sat Jun 26, 2021 7:35 pm
Re: Updating Everything 1.5 portable, retaining database of metadata
What version are you on?
Everything will keep your index when updating.
If you are using a really really old version a rebuild might be required.
Before you update, make a backup of your %LOCALAPPDATA%\Everything\Everything-1.5a.db
Everything will keep your index when updating.
If you are using a really really old version a rebuild might be required.
Before you update, make a backup of your %LOCALAPPDATA%\Everything\Everything-1.5a.db
-
adriancornea52
- Posts: 8
- Joined: Sat Jun 26, 2021 7:35 pm
Re: Updating Everything 1.5 portable, retaining database of metadata
I have version 1.5.0.1396a.x64 Portable. From what I remember, the portable version is just an archive which extracts into a folder. So I am not sure what is meant by "updating" when it comes to this. Because it's not like an installer. Sorry if I misled by using the word "updating"; but I did mention "portable" in the topic title and in my first post.
Also, you mention %LOCALAPPDATA%\Everything\Everything-1.5a.db, but I think that is the case only for the Installer, not for the Portable. I cannot find such a path in my case. I have the Everything-1.5a.db in the main folder where the Portable archive extracted.
So, for the Portable version can I copy and replace the Everything-1.5a.db from the previous version to the latest version in the specific program folder?
Thank you for any help!
Also, you mention %LOCALAPPDATA%\Everything\Everything-1.5a.db, but I think that is the case only for the Installer, not for the Portable. I cannot find such a path in my case. I have the Everything-1.5a.db in the main folder where the Portable archive extracted.
So, for the Portable version can I copy and replace the Everything-1.5a.db from the previous version to the latest version in the specific program folder?
Thank you for any help!
Re: Updating Everything 1.5 portable, retaining database of metadata
Correct.From what I remember, the portable version is just an archive which extracts into a folder.
The portable exe is the same as the installed exe.
The installer simply sets Tools -> Options -> General -> "Store settings and data in %APPDATA%\Everything" and installs the Everything Service.
To update the portable version:So I am not sure what is meant by "updating" when it comes to this. Because it's not like an installer. Sorry if I misled by using the word "updating"; but I did mention "portable" in the topic title and in my first post.
Exit Everything (File -> Exit)
Open the Task Manager. (Ctrl + Shift + ESC)
Click the Services tab.
Right click Everything and click Stop Service.
Overwrite your Everything.exe with the latest version.
Launch Everything.exe
For the portable version, settings and data are stored in the same location as your Everything.exe.Also, you mention %LOCALAPPDATA%\Everything\Everything-1.5a.db, but I think that is the case only for the Installer, not for the Portable. I cannot find such a path in my case. I have the Everything-1.5a.db in the main folder where the Portable archive extracted.
Please make a backup of this whole folder.
Yes, if you have multiple folders for different version.So, for the Portable version can I copy and replace the Everything-1.5a.db from the previous version to the latest version in the specific program folder?
I recommend copying your Everything-1.5a.ini too
Exit Everything (File -> Exit) before launching Everything.exe from another location.
-or-
just replace your Everything.exe with the latest version.
-
adriancornea52
- Posts: 8
- Joined: Sat Jun 26, 2021 7:35 pm
Re: Updating Everything 1.5 portable, retaining database of metadata
Ok, understood. I will do that. Thank you very much!
-
Herkules97
- Posts: 220
- Joined: Tue Oct 08, 2019 6:42 am
Re: Updating Everything 1.5 portable, retaining database of metadata
I actually switched to a new Windows install and certain property-heavy instances, basically it contained all properties available, no longer ran.
I have since then done what Void advised and made exports of those type of instances.
If you have some MBs or even KBs if your instance is small enough, you should probably export the list as at least an .efu and make a copy over at least 2 storage devices.
If by a long time you mean several days, you could then use that efu in the meantime, ctrl+o or File-Open file list, to do what you were planning while the database is busy rebuilding. I don't think opening exported file lists causes issues with the live function of the database but you could always make a separate instance for only loading file lists if you want to be sure.
If you really want to avoid indexing the same files again if you do need to re-build and it doesn't keep the property intact, you could move all existing videos into a separate root folder before adding more videos to whichever folder they were in, unless they're all over the place then you may have to take the hit or exclude all of them, if they will never see further changes, for the whole instance to avoid duplicate entries.
Then import the exported .efu as a file list, IIRC .efu does not contain date accessed, date run and run count but all other properties like video length would be in there..Idk. I rarely look at my exports and I don't have any instances that indexes video lengths anyway. If you import .efu(within the settings, not the ctrl+o option) to the live instance, I presume at least date run and run count would still be counted from the run history file. Maybe that happens even when you load the file list temporarily(ctrl+o option). I haven't checked or don't remember. This is irrelevant if you don't use the run history feature.
You could also make a folder-indexed instance and remove the extra properties from the device instance and add them to the folder indexed one. Then you will never get a rebuild(but making backups is a good idea still) unless it's a database update but I think Void mostly keeps those to major executable versions like 1.4, 1.5 and 1.6. Idk if there will be a database update in 1.6, if there is something new he intends to add to it. But then I presume you'd have to re-build any instances that aren't stuck in time like exported .efu, so you could take the hit or stick with 1.5.
However at least in my experience, folder-indexed instance can miss things that NTFS ones don't. Maybe it's an issue of too many file changes and too low of a change cache. I have done no tests on this. There could be a way to configure it to not miss things, I haven't had a use for fixing this so I've never bothered finding out.
I have since then done what Void advised and made exports of those type of instances.
If you have some MBs or even KBs if your instance is small enough, you should probably export the list as at least an .efu and make a copy over at least 2 storage devices.
If by a long time you mean several days, you could then use that efu in the meantime, ctrl+o or File-Open file list, to do what you were planning while the database is busy rebuilding. I don't think opening exported file lists causes issues with the live function of the database but you could always make a separate instance for only loading file lists if you want to be sure.
If you really want to avoid indexing the same files again if you do need to re-build and it doesn't keep the property intact, you could move all existing videos into a separate root folder before adding more videos to whichever folder they were in, unless they're all over the place then you may have to take the hit or exclude all of them, if they will never see further changes, for the whole instance to avoid duplicate entries.
Then import the exported .efu as a file list, IIRC .efu does not contain date accessed, date run and run count but all other properties like video length would be in there..Idk. I rarely look at my exports and I don't have any instances that indexes video lengths anyway. If you import .efu(within the settings, not the ctrl+o option) to the live instance, I presume at least date run and run count would still be counted from the run history file. Maybe that happens even when you load the file list temporarily(ctrl+o option). I haven't checked or don't remember. This is irrelevant if you don't use the run history feature.
You could also make a folder-indexed instance and remove the extra properties from the device instance and add them to the folder indexed one. Then you will never get a rebuild(but making backups is a good idea still) unless it's a database update but I think Void mostly keeps those to major executable versions like 1.4, 1.5 and 1.6. Idk if there will be a database update in 1.6, if there is something new he intends to add to it. But then I presume you'd have to re-build any instances that aren't stuck in time like exported .efu, so you could take the hit or stick with 1.5.
However at least in my experience, folder-indexed instance can miss things that NTFS ones don't. Maybe it's an issue of too many file changes and too low of a change cache. I have done no tests on this. There could be a way to configure it to not miss things, I haven't had a use for fixing this so I've never bothered finding out.