voidtools forum

Following your directive on the -exit -wait switches for the "-exit not being respected" bug report, I built a custom script to implement it and everything seemed to worked accordingly on the server (Windows Server 22). But upon upgrading to the latest update of everything with the -exit -...

Because of how large the database is, I will have to run a scheduled task that kills the first instance each half hour and then starts a new instance. But would be nice for everything to be able to execute, update, then exit. This is in relation to the new cloud storage "E:\\" drive issues...

When running a command to update a database, the -exit command is not being respect in the sense that I apply it. I run: & "C:\ProgramData\Kane\VoidTools\Everythingx.exe" -config "\\cloud-dc1.kane.local\NETLOGON\Programs\VoidTools\configs\KaneComm.ini" -db "\\cloud-dc1.k...

Sorry for the super late response. We deployed our cloud solution alongside the everything tool and ran into a MASSIVE performance hit, which ended up being due to Everything. Because of it being a live connection, Everything was trying to index the subfolders and because everyone's system was doing...

Everything 1.5a ..1367 Digging into the ini file to create custom settings upon install, when the [folders= ] is set to a volume letter without a subfolder, it gets treated like a disk instead of a custom folder path. Example: folders=%USERPROFILE%,E:\ Even though E: is specified with the "\&qu...