Nvidia is ending GPU driver support for 32-bit operating systems
40 replies, posted
[QUOTE=J!NX;53001191]I don't seem to notice that too bad, but hey, it doesn't bluescreen when I turn shit on any more
the old version was the worst[/QUOTE]
I'm sure I could just log in with google and it'd work great but the point is I really shouldn't have to.
[QUOTE=gk99;53005324]Debatable. I have two Windows installations on my main PC with a 1060, reason being that older games either break or won't install on my 64 bit Windows 10.[/quote]
That's less 'This program doesn't like 64 bit Windows' and more 'That program doesn't like this ten year newer version of windows'. I can't play Fallout 3 standalone on 7 x64, but I could run it just fine on Vista x64. I can't run King of the Road on 7 x64, but I can run it just fine on Vista x64.
Windows' 32-bit compatbility in 64-bit mode is stellar. The problem is those older games require features that the OS has dropped over the years, and/or can't get along with modern hardware or the new security measures in modern OS's or who-the-fuck-knows-what-else. I highly doubt I would be able to run FO3 or King of the Road if I installed 7 x86 on my machine.
[quote]Of course I don't need the latest features and optimizations that new drivers would provide, but only one more year of security updates is certainly an issue unless it becomes a legal requirement to give games to GOG so they can fix and re-release them[/QUOTE]
There's no security updates coming in video drivers. It's not an issue.
[editline]26th December 2017[/editline]
[QUOTE=EE 20 D0;53004991]Bigger isn't always necessarily better, moving to 64-bit (48-bit) increases the sizes of some data structures and adds complexity to the hardware, which takes up space that could either be left unused, saving power/$, or used to increase
performance.
Generally you gain more than you lose but for small systems where you aren't dealing with data bigger than ~4 GB at
once it isn't exactly necessary. You only need as many address bits as the data in RAM needs.[/QUOTE]
You're aware that 64 bit operating systems have been available to the end user for so long that you can't buy a computer with 32 bit only hardware anymore, right? Even the cheapest, shittiest fucking Walmart Special laptop is fully x64 compatible on a hardware level. And, hell, with modern OS's being so monstrous, you NEED 8 gigs of ram just to get a web browsing machine to function properly. Windows hoovers up damn near three gigs on average and Firefox/Chrome/IE/Edge will happily swallow down a gig and a half if you do anything more complex than have one tab of Amazon and one tab of Facebook open. Throw in Incredimail(Try as I might I can NOT get my mom to drop this for Thunderbird), at least two active anti-malware solutions(Because old people tend to have NFC what they're doing on the internet and will get cryptolocker bullshit at some point), a software firewall(Hopefully in addition to the hardware one in your router), and an allowance for a few toolbars here and there (They're going to get installed on an older person's rig) and even 8gb is starting to feel cramped.
You have to go out of your way to buy hardware that isn't x64 compatible these days and even grandma's email box needs more ram than 32bit can address.
[QUOTE=TestECull;53007923]That's less 'This program doesn't like 64 bit Windows' and more 'That program doesn't like this ten year newer version of windows'. I can't play Fallout 3 standalone on 7 x64, but I could run it just fine on Vista x64. I can't run King of the Road on 7 x64, but I can run it just fine on Vista x64.
Windows' 32-bit compatbility in 64-bit mode is stellar. The problem is those older games require features that the OS has dropped over the years, and/or can't get along with modern hardware or the new security measures in modern OS's or who-the-fuck-knows-what-else. I highly doubt I would be able to run FO3 or King of the Road if I installed 7 x86 on my machine.[/quote]
I should've worded it better, because my point was mainly "won't install on 64-bit." I included "break" and "10" because I did install Win7 in the first place because of the reasons you're talking about, and I just grouped them on in. That said, I wasn't talking out of my ass with hypotheticals.
[t]https://i.imgur.com/qxFBgqq.png[/t]
[t]https://i.imgur.com/aEDXVjQ.png[/t]
Literally three days ago I tried to install Soldier of Fortune because I wanted to play it, only to be greeted with the latter image because the installer is 16-bit, which is something 64-bit cannot run while 32-bit can (hence the former image). It is [I]entirely[/I] a 64-bit version problem.
[quote] There's no security updates coming in video drivers. It's not an issue.[/QUOTE]
[quote]This change affects 32-bit builds of Windows 7, Windows 8/8.1, Windows 10, Linux, and FreeBSD. That said, Nvidia will continue to dole out critical security fixes, as needed, until January 2019.[/quote]
It is, in fact, an issue.
[QUOTE=gk99;53008060]
Literally three days ago I tried to install Soldier of Fortune because I wanted to play it, only to be greeted with the latter image because the installer is 16-bit, which is something 64-bit cannot run while 32-bit can (hence the former image). It is [I]entirely[/I] a 64-bit version problem.[/quote]
Yeah, and when I try to play King of the Road I'm lucky if I can get it to run once immediately from the installer. Old games break on new systems, who would have thought?! And even if they do run on the newer OS and newer hardware they don't always run right.
KOTR, for example, ties physics tickrate to framerate. This was fine when it came out because the computers of the day would struggle to run it at more than 45-60FPS and at those framerates the physics tickrate works nicely, trucks drive at...intended speeds, we'll say, and all is well. But if you run it on a modern-ish processor(Even something ten years or so old like my AMD tricore)? With a modern GPU? A rig that can hammer out a game that old at four figure framerates? [I]Cue the Benny Hill theme.[/I] Worse still, the physics get buggy at such high tickrates, with changes in road elevation causing damage to your vehicle and even kicking it high into the stratosphere when otherwise it would not do so.
It's frustrating, sure, but it's also an excuse to build an old Pentium 4 or AMD K8 rig running XP Pro SP2. Best way to run those old games is to run them on contemporary hardware, as even when they do decide to clonk into operation on newer stuff weird shit happens. Or optionally, use some third party software changes at the game level to run it, which is what I do with Fallout 3(I run it as an expansion pack for New Vegas with the Tale of Two Wastelands mod), or run it in a VM(I use DOSBox to play SCorched Earth and aside from lacking any form of sound the game runs fine).
Can't play an old game on a new OS? Time to binge watch LGR and save up for a retro PC build.
[quote]It is, in fact, an issue.[/QUOTE]
It is not an issue. Just because they say 'critical security fixes' doesn't mean there actually will be any, and in fact, I can't really think of any sort of way that your video driver can pose a security risk to your computer in the first place. It's not something that interfaces with the network at large and tends to result in a massive BSOD if a gnat farts in its general direction from two states over. The security fixes are going to be aimed at the OS itself because that's where the security holes are.
Iono, I guess if you consider some asshat being able to bluescreen your system remotely by poking your GPU driver with a stick is a security problem then sure. Honestly I don't see that as more than an annoyance. They're going to want your money and that's easier to get by releasing ransomware that encrypts your files and demands money, or by embedding a keylogger in system ram that tries to capture login details and CC info when you shop online, neither of which is something done on the GPU.
[QUOTE=TestECull;53008130]
KOTR, for example, ties physics tickrate to framerate. This was fine when it came out because the computers of the day would struggle to run it at more than 45-60FPS and at those framerates the physics tickrate works nicely, trucks drive at...intended speeds, we'll say, and all is well. But if you run it on a modern-ish processor(Even something ten years or so old like my AMD tricore)? With a modern GPU? A rig that can hammer out a game that old at four figure framerates? [I]Cue the Benny Hill theme.[/I] Worse still, the physics get buggy at such high tickrates, with changes in road elevation causing damage to your vehicle and even kicking it high into the stratosphere when otherwise it would not do so.
It's frustrating, sure, but it's also an excuse to build an old Pentium 4 or AMD K8 rig running XP Pro SP2. Best way to run those old games is to run them on contemporary hardware, as even when they do decide to clonk into operation on newer stuff weird shit happens. Or optionally, use some third party software changes at the game level to run it, which is what I do with Fallout 3(I run it as an expansion pack for New Vegas with the Tale of Two Wastelands mod).
Can't play an old game on a new OS? Time to binge watch LGR and save up for a retro PC build.
[/QUOTE]
There's ways to lock framerates in games tho.....
[QUOTE=TestECull;53008130]
Iono, I guess if you consider some asshat being able to bluescreen your system remotely by poking your GPU driver with a stick is a security problem then sure. Honestly I don't see that as more than an annoyance. They're going to want your money and that's easier to get by releasing ransomware that encrypts your files and demands money, or by embedding a keylogger in system ram that tries to capture login details and CC info when you shop online, neither of which is something done on the GPU.[/QUOTE]
[url]https://nvidia.custhelp.com/app/answers/detail/a_id/4278/~/security-bulletin%3A-multiple-vulnerabilities-in-the-nvidia-windows-gpu-display[/url]
[url]https://www.nvidia.com/en-us/product-security/[/url]
[url]https://www.cvedetails.com/vulnerability-list/vendor_id-5264/Nvidia.html[/url]
It doesn't matter if it's "done on the gpu. Think about how this page is being sent to your monitor. Through your GPU. Your graphics driver runs in kernel mode which means if someone is able to exploit that graphics driver, they have access to everything.
Here's a few fun CVEs
[quote]CVE-2015-5053
The host memory mapping path feature in the NVIDIA GPU graphics driver R346 before 346.87 and R352 before 352.41 for Linux and R352 before 352.46 for GRID vGPU and vSGA does not properly restrict access to third-party device IO memory, which allows attackers to gain privileges, cause a denial of service (resource consumption), or possibly have unspecified other impact via unknown vectors related to the follow_pfn kernel-mode API call.[/quote]
10.0 score. DoS and privilege escalation
[quote] CVE-2006-5379
The accelerated rendering functionality of NVIDIA Binary Graphics Driver (binary blob driver) For Linux v8774 and v8762, and probably on other operating systems, allows local and remote attackers to execute arbitrary code via a large width value in a font glyph, which can be used to overwrite arbitrary memory locations.[/quote]
Remote code execution done through a font. You can pack fonts onto webpages. Visit this webpage, the font is sent to be displayed, code executed.
[quote]CVE-2016-5852
For the NVIDIA Quadro, NVS, and GeForce products, GFE GameStream and NVTray Plugin unquoted service path vulnerabilities are examples of the unquoted service path vulnerability in Windows. A successful exploit of a vulnerable service installation can enable malicious code to execute on the system at the system/user privilege level. The CVE-2016-5852 ID is for the NVTray Plugin unquoted service path[/quote]
More code execution
Security updates exist for a reason.
[QUOTE=Fox Powers;53008135]There's ways to lock framerates in games tho.....[/QUOTE]
ever play sim copter on 2012 hardware?
[QUOTE=Scratch.;53002443]You don't need shadowplay to use NVENC[/QUOTE]
NVENC isn't the whole story. NVENC Is just the H264 encoder. Shadowplay also uses NVFBC and NVIFR to capture the actual footage.
NVFBC stands for NVIDIA Frame Buffer Capture. NVFBC is used to capture the video output directly from the framebuffer when in exclusive fullscreen which is SIGNIFICANTLY less intensive than capturing it through the API like OBS and XSplit have to.
NVIFR stands for NVIDIA In-band Frame Render and is an alternate method to get video output from the framebuffer. It's not as fast as NVFBC but it allows you to capture a window specifically. That's why video output from Shadowplay always matches the window size. Not as fast as NVFBC but still far faster than grabbing the output through the methods OBS and XSplit can use.
So if you want the optimal experience, Nvidia Share (formerly known as Shadowplay) is the way to go. NVENC by itself helps a ton over x264, but OBS and XSplit still have a larger performance impact than Share does because they have additional overhead (API overhead to capture the footage as well as other overhead from their recording process)
[QUOTE=TestECull;53007923]You're aware that 64 bit operating systems have been available to the end user for so long that you can't buy a computer with 32 bit only hardware anymore, right? Even the cheapest, shittiest fucking Walmart Special laptop is fully x64 compatible on a hardware level. And, hell, with modern OS's being so monstrous, you NEED 8 gigs of ram just to get a web browsing machine to function properly. Windows hoovers up damn near three gigs on average and Firefox/Chrome/IE/Edge will happily swallow down a gig and a half if you do anything more complex than have one tab of Amazon and one tab of Facebook open. Throw in Incredimail(Try as I might I can NOT get my mom to drop this for Thunderbird), at least two active anti-malware solutions(Because old people tend to have NFC what they're doing on the internet and will get cryptolocker bullshit at some point), a software firewall(Hopefully in addition to the hardware one in your router), and an allowance for a few toolbars here and there (They're going to get installed on an older person's rig) and even 8gb is starting to feel cramped.
You have to go out of your way to buy hardware that isn't x64 compatible these days and even grandma's email box needs more ram than 32bit can address.[/QUOTE]
I do see 32-bit dinosaurs around quite frequently, with <= 1 GB of RAM, my own machine atm having 2 GB w no swap (yet runs 64-bit linux, because technical reasons).
I know all(most?) new x86 hardware is amd64-compatible, and how the bloat makes it necessary to upgrade.
So I don't disagree for the general case but for more specific applications and for keeping used hardware from becoming e-waste faster than necessary there's still an use for 32-bit.
-snip someone covered it-
[QUOTE=Pw0nageXD;53008164]smartboy[/QUOTE]
Nice :)
[editline]27th December 2017[/editline]
Also I can tell you that nvidia still call it shadowplay internally.
More my problem with it is it's fullscreen detection, which is implemented though the shadowplay server
a lot of my videos now flicker back to my wallpaper because of this
javascript :downs:
[editline]27th December 2017[/editline]
still got that screencap
[t]https://tenryuu.blob.core.windows.net/astrid/2017/12/17-10-23_16-49-57-Windows_PowerShell.png[/t]
Sorry, you need to Log In to post a reply to this thread.