- RunAsHighest is never disable-able (Vista+)
- Application Compatibility Engine is forcefully always enabled (8.1+)
- Ruined "disable display scaling on high DPI displays" setting (W10 NU, potentially improved later - workarounds)
- some knobs to play with
Broken compatibility internals
How to specify .NET Framework and its version?
I couldn't find any template or example for this...
It is not really something officially covered anywhere at the moment, but since it’s a system requirement it would technically go into the “minother” parameter of that template:
SingleProcAffinity in ACT
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
EDIT: also mention about its potential banes
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
Ignored color calibration profiles + saturation enhancer
Especially if you own non-TN monitors, this will be a godsend
EDIT: or this under multi-mon XP
https://sourceforge.net/projects/saturationtoggler/ and https://vibrancegui.com/
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.
james bond 007 blood stone game is not starting
bro.. blood stone is not starting just apearing an icon on the taskbar and then its gone automatically pleas can anyone help me
Probably you use retail original game. I afraid the issue can be connected with SecuROM DRM.
x64 driver signature override ideas
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:
- until Vista SP1 the later wasn't needed?
- XP 64-bit (yes, it existed) didn't need signing at all?
- Malware used to dexterously bypass the enforcement?
- and Microsoft attempt to patch this further tightened requirements? KB2506014
- DRM compliant (graphics/audio) and boot-start drivers require additional signing?
- W10 and Secure boot enabled systems have even stricter policies? [possible workaround]
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)
So, basically a shortcut key to
taskkill /f /im <program name>?
Disable shortcut arrows (Win10)
This post by Mirh was moved on 2017-06-20. You can find it at Thread:Talk:Microsoft Windows/DVD freezing.