D.Draker

accessibility.force_disabled=true app.shield.optoutstudies.enabled=false beacon.enabled=false browser.laterrun.enabled=false browser.shell.checkDefaultBrowser=false

Not only! See about the mismatches in 7. https://github.com/win32ss/supermium/issues/797#issuecomment-2303311131

347.90 came out after, it even includes Titan X. I think the first driver to officially support 950 is 347.09 or 347.25. I was asking about the brightness changes.

Looks like some artificially implemented block, like in the case with Nvidia drivers capped to low refresh rates. H265 10bit works in the driver 382.16 (if you followed my written tutorial). Or in the driver 398.11 made by win32, but for 398.11 you need to have the ex-kernel installed.

lol, I dunno, prolly it's not popular among the devs? So, 372.60 is in the lead, then. Did you notice the brightness changes among those drivers?

Thank you for the test, would you be willing to test the unique 372.73 it's also my favourite, it's a leaked developer driver which was added only via MS update. And if you do, please compare the brightness, as it seemed to me 372.73 is a bit brighter than 372.60. No one has this driver, no one knows about it. 32-bit https://catalog.s.download.windowsupdate.com/d/msdownload/update/driver/drvs/2016/09/20926157_0d7cd25eb8d6143283c1d6302695f3fc38a0daaa.cab 64-bit https://catalog.s.download.windowsupdate.com/d/msdownload/update/driver/drvs/2016/09/20926155_2f5bb23b249fd6c60a37d064e211d872d2fe9d42.cab

Vista boots up and is overall much faster than Win7, but I always ran it on Intel, maybe it's AMD specific only. I'm not sure what good all those outdated patches can achieve though.

Looks like it's simply another telemetry for USB introduced with Win7. That logger can be safely disabled, if I'm not mistaken, it wasn't even active in the original Vista without that KB. https://df-stream.com/2014/01/the-windows-7-event-log-and-usb-device/

Thank you for the test, 372.60 is also my favourite, it's a leaked developer driver which was acquired by iCafe. 372.70 is of course the usual throttling crap. Mind me asking, is there a benefit of using 6003 Vista over 6002 build? I didn't like 6003, it gave me slower performance overall.

People told you, uBlock Origin Lite wouldn't be enough, obviously, maybe wait a couple of years while it develops into something more prominent? (hopefully)

Then try this one, much newer driver. Works on Vista (despite what nvidia says) https://drivers.softpedia.com/get/GRAPHICS-BOARD/NVIDIA/NVIDIA-GeForce-iCafe-Graphics-Driver-37260-64-bit.shtml

With all nVidia officially distributed drivers, I noticed they start to throttle after some time spent in a game, Perhaps, they simply don't want to exchange bad cards, if they go kaput under load? Anyways, Guru3d is a somewhat good source. Giving a link just as an example. https://forums.guru3d.com/threads/nvidia-please-read-major-drop-in-performance-with-new-drivers-446-14-vs-460-79-benchmarks.435665/

I noticed that, too! Dietmar, by any chance do you edit GPU BIOS? Need to change RGB values. Thank you

You're welcome, glad we could help, enjoy your setup!

347.90 is a unique, unlocked developer driver without throttling; I found it a long time ago. https://msfn.org/board/topic/184793-gtx-980ti-unity-crashes-vista-x64/?do=findComment&comment=1246223 "runs even better it now runs at 240 fps ... before that it would run at 120 to 140 fps" https://msfn.org/board/topic/184793-gtx-980ti-unity-crashes-vista-x64/?do=findComment&comment=1246209

Thanks, that I know, but there's a software driver and Intel ME management interface, isn't it the same as the PCI controller driver, no?

app.update.auto.migrated=false app.update.auto=false app.update.badge=false app.update.channel="" app.update.checkInstallTime=false app.update.enabled=false app.update.mode=0 app.update.service.enabled=false app.update.silent=false app.update.staging.enabled=false

Would you tell him, I forgave him a long time ago. If you have a chance, thanks.

I'll help with what I can, starting with, did you apply the fix for the well known bug? # SSL selfsigned fix security.enterprise_roots.enabled=true

Yeah, but wouldn't system think it now has a fully functional device and is allowed to communicate with Intel ME through it, no? Like OS communicates with BIOS.

Guys, will this driver work with a Kabylake CPU/ H110 chipset mobo? Thanks.

Wow! Thanks for the info! So, modding CentBrowser, then?

I don't have the patience to use quad CPU computer in this age. I remember using it in the days of simpler WWW (2006-08), it wasn't anything to be thrilled about. I was in shock how poorly the over-popularised Q6600 was performing at the age when all games where optimised for two cores at most (2007-10), I was in shock when I tried to install the 2015 version of 10 on that PC, it took a day! The PC was prepared for a friend, trust me or not, I never loaded Win10 to even have a peek.

Chrome devs (don't know about FF ones) like to revert changes, I just keep some old flags and whatnot in case they bring it back.

Yes and no. Let's see, Opera has its own VPN, when you choose to always "connect at start", it will, it's not spying, technically. I read FF now has a VPN, too. Is it any good?