Content is available under Creative Commons Attribution Non-Commercial Share Alike unless otherwise noted.
Kill programs instantly with Ctrl+Alt+F4
So, basically a shortcut key to taskkill /f /im <program name>?
taskkill /f /im <program name>
This post by Mirh was moved on 2017-06-20. You can find it at Thread:Talk:Microsoft Windows/DVD freezing.
Microsoft's AppLocale is discontinued and should be replaced with something like Locale Emulator.
Disclaimer: this is just for judicious testers for fix researching affairs. I don't think "the mass" is wise enough to take the liberty of disregarding a security measure
So.. we all know the story. Bcdedit, DSEO, self-signing and all. But did you know:
Watermarks can possibly be tinkered with this
EDIT: everything from Α to Ω [clause]EDIT2: Loading unsigned code into kernel in Windows 10 (64) with help of VMware Workstation Pro/Player design flaw (should work up to Player 12.5.2)
Especially if you own non-TN monitors, this will be a godsend
EDIT: or this under multi-mon XP
Neat, that's reall useful.
Any advantages over Color Sustainer?
Oh man, solution that doesn't require dll injecting and is monitor/mode specific? Thanks for this!
Judging by "sister thread", it's not like some games can't only work with injection.
Anyway, there's even CPKeeper.
This post by Mirh was moved on 2016-06-27. You can find it at Thread:Talk:Microsoft Windows/Mouse pooling problems.
I need to test a few things that's why I'm asking.
Oh well I found it, I hope? Will need to do some more things.
Nevermind, it's probably something else.
Microsoft's generic Bluetooth driver is included with consumer editions of Windows from Windows XP SP2 onwards (there is nothing to download). Microsoft's driver uses the functionality built into Windows, so there is no extra software when using that driver. Some Bluetooth hardware may need the manufacturer's driver.
See General Bluetooth Support in Windows for more details.
When there'll be a guide for ACT (to slim down actual instructions in this page) it should be worth to be mentioned in force affinity issue
As I've mentioned on a previous thread, the problem there is that the Application Compatibility Toolkit is highly specific and requires some level of understanding of the problem--and the ideal solution is to then provide a game-specific fix package. As a result I'm not sure how useful generic instructions would be.
It's usually difficult to pinpoint what's the compatibility bit required, yes... but the point here was instead to provide yet another way to (permanently) force affinity on a single core, assuming you already know that's needed