Currently it saves on window exits, search history was given the ability to save on search.
Can you make a toggle to save on runs?
Like
search_history_save_on_change
You can make
run_history_save_on_change
Why weren't both added for the same build? They accomplish the same thing.
I am fine with dbs not being saved at all times, I wish I knew how to read them properly in cases where it fails to load them. Like if Firefox rejects places.sqlite, but I can still use DB Browser for SQLite to see what's inside.
Right before this I was going to post about 1.4x dbs no longer loading on my system before I tested read-only and found they did load with that on and checked lister32 where barely anything is readable. Hopefully this read-only solution applies to all 1.4x dbs, would be a shame if not because these are too old to still have online, can't just re-scan. Some devices have broken since. Some are modified. The folder I was looking for was 29GB on db save. The current folder is 21GB, so something happened to the 8GB within 4 years. Wouldn't know that if db didn't read.
I wish I knew how to read all sorts of documents like EBV's databases. Unless there are methods to making it more readable, I am sure there are documents that I've wanted to read but have no idea how to, like foobar2000, that just requires certain methods to making them readable and they're out there. Would be nice if I could read Enhanced Playback Stats' file properly instead of having to use the in-program way of reading it. It might contain the full timestamps like PS does, not just down to seconds.
And if I could read it, maybe I could write to it and add in old data to make it complete.
Run history saved on runs, like search history on searches
-
Herkules97
- Posts: 220
- Joined: Tue Oct 08, 2019 6:42 am
Re: Run history saved on runs, like search history on searches
To read the Everything database, there are 2 options:
- Use the Database Recovery Tool db2efu.
This is not available for the alpha version of 1,5, but will very likely be released when out of beta.
- Copy the database and everything64.exe to a new folder and run
(You can then export the results to an EFU file or similar)
- When done, close with Menu => File => Exit.
Can't help with saving the Run History. To me it is perfectly fine that it gets saved when the search window closes.
- Use the Database Recovery Tool db2efu.
This is not available for the alpha version of 1,5, but will very likely be released when out of beta.
- Copy the database and everything64.exe to a new folder and run
Code: Select all
Everything64.exe -instance CRASH -readonly -db Everything.db
- When done, close with Menu => File => Exit.
Can't help with saving the Run History. To me it is perfectly fine that it gets saved when the search window closes.
-
Herkules97
- Posts: 220
- Joined: Tue Oct 08, 2019 6:42 am
Re: Run history saved on runs, like search history on searches
I keep forgetting certain things like this tool. Do you know any other tools for EBV?NotNull wrote: Thu Feb 20, 2025 10:11 pm To read the Everything database, there are 2 options:
- Use the Database Recovery Tool db2efu.
This is not available for the alpha version of 1,5, but will very likely be released when out of beta.
- Copy the database and everything64.exe to a new folder and run(You can then export the results to an EFU file or similar)Code: Select all
Everything64.exe -instance CRASH -readonly -db Everything.db
- When done, close with Menu => File => Exit.
Can't help with saving the Run History. To me it is perfectly fine that it gets saved when the search window closes.
I should probably add any to all my instance folders so I can't forget it, alongside any other tools. Or in their own folder depending on how they are used.
I only recently, after months of thinking, made a folder to load all efus. I am not done adding them all, but it took maybe 5 months of thinking about it and 1 minute to execute from start to finish for current .efus I could find lying around.
This could be path, I haven't made the tools folder yet but it'd be at the top always reminding me when I go into EBV folder:
"C:\[user-made folder]\Portables\EBV\()Tools"
"C:\[user-made folder]\Portables\EBV\EverythingVoidtools v1.4.1.1024 x64"
"C:\[user-made folder]\Portables\EBV\EverythingVoidtools v1.5.0.1373a x64"
"C:\[user-made folder]\Portables\EBV\EverythingVoidtools v1.5.0.1382a x64"
"C:\[user-made folder]\Portables\EBV\EverythingVoidtools v1.5.0.1383a x64"
"C:\[user-made folder]\Portables\EBV\EverythingVoidtools v1.5.0.1386a x64"
"C:\[user-made folder]\Portables\EBV\EverythingVoidtools v1.5.0.1390a x64"
I only send this because what if someone reads my entire messages and finds the inspiration to do it themselves. Unlikely, but is it ever 0..
It is already unlikely anyone reads the entire messages, given that I often get replies about a question already answered in the message they are replying to.
I wonder if there is something similar for index journals. I've finally set up a folder for exporting on very recent db separation when journal nears overflow but it is unknown if I can load all dbs to export their journals. I should do it ASAP and not be lazy, but I know I will be lazy and not end up doing it.
It is fortunate he made it save as csv instead of efu, as csv should contain all data of the main db as I doubt this program only exports loaded columns as it presumably does not have any.
Re: Run history saved on runs, like search history on searches
By void? Not that I know of.
Non-Everything related: voidimageviewer and voidmouse (search the forums if interested).
Maybe MasterEFU can help here?
Read it till the end!
-
Herkules97
- Posts: 220
- Joined: Tue Oct 08, 2019 6:42 am
Re: Run history saved on runs, like search history on searches
I don't know what it is meant to help with, as I already have the db with efus loaded?
Also it seems to be about merging efus, which would make it impossible to know what a given search result entry belongs to.
I use efus and then usually make an archive after that with the same beginning of the name.
That way if I search an efu, I can know which archive should have the file. Because compression can save significant space.
Granted sometimes multiple folders start with the same name and I forget to exclude the others when exporting an efu.
So efu may have 4 folders, archive may only have one.
But typically they are accurate.
Here is one such combo of efu and archive names:
"2025-02-21 0850 VGS 1.5.0.1386a - KWsystemshock1remakev1.2.18830+(v1.2.18898)#2-1KWsavesKWefu - 0850 Finished first session.efu"
"2025-02-21 0850 VGS 1.5.0.1386a - KWsystemshock1remakev1.2.18830+(v1.2.18898)#2-1KWsavesKWarchive - 0851 CL9,12GB,1000M N-S.7z.001"
If I merged, it could be
"2025-02-22 0730 MasterEFU 1.5.0.1390a - KWmergedallefusKWefu - 0730 Yeah Idk why I would ever do this.efu"
"2025-02-21 0850 VGS 1.5.0.1386a - KWsystemshock1remakev1.2.18830+(v1.2.18898)#2-1KWsavesKWarchive - 0851 CL9,12GB,1000M N-S.7z.001"
Would not be able to find the archive
Yay
Re: Run history saved on runs, like search history on searches
With this:Herkules97 wrote: Fri Feb 21, 2025 11:34 pm I don't know what it is meant to help with, as I already have the db with efus loaded?
Herkules97 wrote: Fri Feb 21, 2025 8:14 am made a folder to load all efus. I am not done adding them all
OK, so maybe not suitable for you ...
-
Herkules97
- Posts: 220
- Joined: Tue Oct 08, 2019 6:42 am
Re: Run history saved on runs, like search history on searches
Oh I see, no..I only have some available in their original form which have already been added to the efu db, but maybe 80% remaining are in archives so I'd have to extract them from any archive where they may be.NotNull wrote: Fri Feb 21, 2025 11:51 pmWith this:Herkules97 wrote: Fri Feb 21, 2025 11:34 pm I don't know what it is meant to help with, as I already have the db with efus loaded?Herkules97 wrote: Fri Feb 21, 2025 8:14 am made a folder to load all efus. I am not done adding them all
OK, so maybe not suitable for you ...
Re: Run history saved on runs, like search history on searches
Everything can help here too:Herkules97 wrote: Sat Feb 22, 2025 12:19 pm I'd have to extract them from any archive where they may be.
Code: Select all
zip: container-filenames:*.efu
Re: Run history saved on runs, like search history on searches
If I'm not mistaken, an easier way to open everything dbs read-only, is using the File/Open filelist... menu option, you can open E databases from there, not only EFUs.