@PeterJones said: Your words said “Distraction Free Mode” without “Fullscreen”. “Fullscreen” is the aspect of DFM that covers the full screen. That is true, but to be fair I’ve also immediately clarified what I meant by “Fullscreen” in the first message : ) I’m assuming operates in Fullscreen mode, meaning it tries to always stay on top Not being a programmer, I can only talk about Fullscreen and Borderless by their observed effects in videogames. From videogame options, Fullscreen and Borderless both cover the entire screen, the only difference is Fullscreen behave as “Always On Top” (almost always), and Borderless doesn’t. Thank you for the Macro, it’s much less hassle than having to run that script manually every time, and I really appreciate it ^_^

Hi @guy038 , to your question about the 8 logical processors: they don’t really matter here. The load threads do very little computing, they mostly wait for the key to deliver the next file. How many reads can usefully run at once depends on the drive, not on the CPU. That’s why auto picks the count by drive type: 4 for local drives like your key, 8 for network drives, where every file waits for the server, and 1 for hard disks, where parallel reads would just make the heads jump back and forth. On a key with a weaker controller, 8 could just as well be slower than 4. On yours it’s slightly faster, so feel free to keep it. 8 is also the maximum. One more thing: your first comparison showed 27 053 hits in the same 646 files, now it’s 27 010. Did anything change on the key in between?