For people that play a lot of games the Windows key can be annoying, as a miss intended hit on the key can take you out of the game in the middle of an important multiplayer session.
For people that work a lot in Windows as well, it can be difficult to miss the function, so disabling it the traditional way is not optimal.
This utility will disable the windows key ONLY when you are in full-screen software (typical games) but keep it functional when you are working on windowed software in Windows. And it is fully automatic…
It uses the same none cyclic monitoring system as Project Mercury, which means it has no CPU usage when it is just sitting and waiting for you to change programs aka no CPU usage during you game session.
As some of you have reported my file sever (and thereby access to the donators versions), has been down for a few days. Or rather it has not been showing any files. A couple of power outages left the server software in a prior state where it was looking for files where they no longer are.
It should now be fixed.
If you have any issues downloading do no hesitate to contact me by the contact form.
A small bug fix release
– Fixed pause icon error in 32bit version
– Fixed typo Recieved to Received in balloon tip
– Unified punctuation in history tab
Current stuff I am working on for Project Mercury
– I/O priority adjustment
– Excessive mode CPU usage improvement
– Excessive mode customization
I am also working on a CPU bottleneck measuring tool. Which I hope will help people get better information to base computer upgrades on. Especially gamers.
The prior reported crash issue with Project Mercury V188.8.131.52 seemed to be a simple compiler/compression bug. All crash reports came from the public version and not from the donation version. After recompiling the crash issue seems to be gone.
Thank you to all of you that brought this to my attention, and helped out by providing feedback and system information.
Multiple reports on Project Mercury 64 bit crashing at startup reported. This issue seems to be with certain system as not all people are seeing this behavior.
If your Project Mercury 64bit version is crashing, but 32bit works flawlessly. Please ,if possible, report your system specifications such as
- Windows Version
- CPU make and model
- Are you running with administration right? UAC enable/disabled ?
- Antivirus software
- or any other information you might think can influence this.
Thank you for all the help. Hopefully I will be able to fix this soon
– Implemented “Excessive mode”.
– Fixed typo “Implanted” to “Implemented”.
Excessive mode monitors for background processes using more that 50% CPU time and lowers their CPU priority to “Below Normal”, thereby reducing the amount of CPU resources they “steal” from the main program.
This feature use a small amount of CPU resources on the monitoring part, so it is advice to only use in cases where the main feature is not enough, to keep operations smooth under heavy multitasking load.
Excessive mode is finally ready in its standalone form, and is available to download for donators. Hopefully it should be merged into Project Mercury within 1-2 weeks.
Excessive mode still uses approximate twice the CPU resources of Bitsum’s Process Lasso, but hopefully future tweaks and optimizations will get it below.
Project Mercury without excessive mode enabled, still use far less CPU and memory than Bitsum’s Process Lasso as well as Process Tamer due to its none cyclic behavior.