Previous page history was archived for backup purposes at Talk:Microsoft Windows/LQT Archive 1 on 2018-02-15.
Content is available under Creative Commons Attribution Non-Commercial Share Alike unless otherwise noted.
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.
Kill programs instantly with Ctrl+Alt+F4
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
I have modified windows registry too many times to believe an automatic solution (especially of this level) is the proper method to suggest.
Dude, its not literally automatic, did you even test it yourself. All it does is bring you to the path you are looking for, instead of having to tediously go through each folder manually, that's it.
Right now I am tired and I can't be bothered to word it better.
I don't see the point.
It seems an additional step to annoy the average joe
I like to keep things simple, but that doesn't mean that I'm doing that only for the average dude, power users also use this website if they need to, and honestly editing the registry is a very, tedious, boring, and repetitive task, I was mostly trying to find a way to streamline things out.
Also that doesn't mean that I should limit myself to stupid workarounds. But really it's not honestly that hard, there's no fancy UI but that's about it. You should honestly be happy that I actually bothered to waste my own time learning how to add that, just to make things simpler for everyone, instead I was hoping you'd maybe help me improve things around, not just tell me that I should remove this because you don't like it, jesus.
I'm just saying I don't see all this improvement.
"Manual" seek isn't such a long process to require help. And I just can't understand how opening cmd, cd-ing into another folder and then pasting the command could be considered faster
The Registry Editor doesn't exactly feature a very user friendly UI, really I thought you would've understood the reasoning behind all of this by now but whatever, let's just take all those %APPDATA% paths, it's really nice to know that you can just paste the entire path somewhere and just go directly to it, that's what the second more "advanced", thing, is ment to solve, or help you with. If you do have all the paths you need to go, all already nicely listed, readily available, then you can just directly go to them, instead of tediously opening, every single, god damn folder, sub folder, each time you need to make a change.
You literally setup the thing once, you leave the command line open, if you wish to move to a new path, then you copy the already known path, and just fucking go to it. I seriously do not understand how you don't see the improvement over the basic method. Like really, and it's not like I forced people to use the command line, they can always just use the first thing.
Oh sorry if sound angry, didn't mean to.
I believe what we may really call automatic is something like this magic
It's literally a single command, and I guess it could be adapted for a lot mooore situations
I guess, but I had used the word "automatic" seeing as I didn't know what to name this thing. That's it. I don't really care otherwise.