UCyborg

Must be one of the game's graphics settings that NVIDIA driver doesn't like. You could try playing with various graphics settings to find out which setting at which value causes it. You can backup your current config file to be able to easily revert to working configuration, its path relative to installation folder is main\players\<your profile name>\config.cfg.

The biggest thing (obstacle) about driver programming to my knowledge is knowing how the hardware you're writing a driver for actually works. I guess if Linux kernel has a driver for particular piece of hardware, hints could be looked up in its source code.

This was on VMware virtual machine, I don't have Win9x compatible hardware. I could give it a spin on a VirtualBox since it differs in practical execution speed, it's faster. Nope, we aren't, I ran setup.exe from original DVD. Linkage to DirectDraw would have to be investigated, even CoD1, which renders using OpenGL, has it for some reason, maybe it just checks some aspect of the environment it runs in. If I remember correctly, forcing the game to run in windowed mode via SwiftShader helped a bit with the mouse problem, forgot to mention that.

Block JavaScript from adobedtm.com and see if there's anything missing.

You can tell by inspecting the program's executable or its dependent DLLs whether they import GDI32.dll or not. Process Hacker comes with PE Viewer. Some programs are packed so their import table looks weird when inspected and I'm not sure whether all DLLs are shown or not. Also, OpenGL applications need certain functions from GDI32.dll. Though even if a lot of functions are used, which is probably a good indicator GDI is supported and that the program can do interesting things with it, it might just be present as the fallback. .NET programs call methods from System.Drawing namespace, which encapsulates basic GDI+ functionality. Seems System.Drawing.ni.dll is loaded by the process when used. Aye, it's pretty widespread and updated programs that use it are out there (KeePass. 7-Zip, HD Tune...). This should be re-targeted to lower .NET Framework version. Are there even any noticeable differences between different .NET versions? I suspect invoking GDI from .NET isn't very expensive.

No glitches with 368.81 driver in Unigine Heaven on XP x64 here, the GPU is fine. Though this particular case isn't the main point, just that the older drivers (and software in general) can have bugs that newer don't (and vice versa, though the goal is to eliminate issues with newer releases).

GDI is at least partially hardware accelerated. On Windows 7, WDDM 1.1 driver is required and DWM must be active for acceleration to work (so no acceleration with basic and classic themes). Vista is an oddball here, where GDI is 100% on the CPU.

I didn't detect any perceptible performance difference between 368.81 and 344.11 on my GTX 750 Ti. That problem with Serpent browser hanging after PC out of stand by...isn't actually specific to it...seems can effect any D3D app that was running at the time...and it happens with 344.11 as well. And the DOOM 3 memory problem, which might not necessarily be a problem, it has something to do with reading through 1 GB worth of archives containing textures. When handles to those files are closed, shown memory usage goes down. Running Unigine Heaven 4.0 with 344.11 driver has shown visual artifacts, at least in D3D9 mode, I haven't tried OpenGL mode. Seems I'm not missing anything crucial for my use cases by keeping 368.81 on XP.

I never said anything else about 368.81 besides the problem regarding monitor detection, which I brought up because that's something that could've been looked into if they were to be modded. I haven't actually used any other version with GTX 750 Ti on XP x64. I encountered 2 other problems that could be related to graphics driver, but can't say for certain if they are (Serpent browser freezing after resuming from standby/sleep and DOOM 3 consuming a lot more memory on XP than on newer OS). There's another known issue with said 64-bit version of the driver and multi-monitor setups, known to occur with GTX 9xx series cards, which someone patched.

+set r_rendererPreference dx7 may be added to the shortcut's Target field to select D3D7 mode. This particular setting is stored in user's config.cfg file, so it doesn't have to remain in the shortcut for it to be effective on subsequent launches, assuming it launched successfully and had the chance to create the said file.

A thread with the workaround for your Windows version: The meaning of symbols: http://glass8.eu/guide

So what's the point of Chinese Flash? If authoring tools are no longer developed, it doesn't run any more content than international Flash. What else is there, security fixes? And what does Win8+ ActiveX version offer over the regular version?

Something else worth mentioning, newer XP drivers have some regressions when it comes to proper monitor detection, see this thread on VOGONS for details.

The version as written on the desktop doesn't tell the exact build you're using, check in Settings app->System->About->OS build. If the second number is over 752, it won't work, unless you also transplant certain system from an older build on your system. So if you're over build 18362.752 and don't feel like messing with system files (there is a procedure in another thread), you can stop reading here. In some cases, you have to download symbol files manually for it to work properly. It's automatic process for donators, but otherwise, check the rest of this forum for the exact procedure. You can also post your debug.log file here, which might give clues what goes wrong.

Wake up and smell the reality. The state of open-source nouveau driver oughta tell you something.

Location of mms.cfg on Google Chrome: %LOCALAPPDATA%\Google\Chrome\User Data\<Profile>\Pepper Data\Shockwave Flash\System\mms.cfg

Check the link, it points to the current page of this thread.

The positive infinity, according to IEEE_754-1985 would be 00|00|00|00|00|00|F0|7F

Some sites are invoking Flash content with an emulator. I don't know about Supernova, but Ruffle is laggy and only works on Chrome. Maybe it would be possible to write a user script for such sites to invoke the real Flash Player on user's system, kinda like how ViewTube can play videos on some sites using a browser plugin. Seems these emerging Flash emulators are just adding to infinite list of Chrome exclusive crap. Nice, didn't think of that. I set mine to year 2060 a while back, doubt I'll care by then. If I wanted to be thorough, I'd just NOP that block out and move the rest of the code up, so it would look like the check was never there and it would save few processor cycles.

https://www.computerworld.com/article/2534312/the--640k--quote-won-t-go-away----but-did-gates-really-say-it-.html

Try Tab Groups extension from Classic Add-ons Archive, which supports similar functionality. After you do CTRL + SHIFT + Tab, click Tab Groups to open its main UI.

No, just more difficult.

Yeah, just WMP11, more specifically, the drivers that come with it. I had to do this to get MTP working. I kinda forgot whether working drivers for ADB are actually needed as well if Android Debugging is enabled at the same time, but I use homebrew INF file for that (and Fastboot) so it's always picked up correctly via compatible ID, rather than device-specific IDs, which are more like software-that-runs-on-the-device-specific, which may not be constant, TWRP recovery that I have for instance uses different device IDs than the main OS. Either way, under the hood, only official MS driver files are ever used, as can be seen in Device Manager on the device's Driver tab. Well, the newest one I have is 6 years old Sony Xperia E3. Maybe I could borrow a newer Samsung Galaxy S8 from a family member to try on XP. It probably still runs Android 7 though. Not sure why it wouldn't work either way. MTP is MTP. Or was the protocol changed at any point?

Source code is a collection of 1 or more original files containing the program code that usually come with the project files for specific IDE (Integrated Development Environment) or makefiles (that could be "real" makefiles or just the kind (eg. CMake) that describes how to generate "real" makefiles or project files for specific environment), which the IDE or the program that reads the makefile use to know about code files that have to be run through the compiler to produce object files from each code file and finally invokes the linker to link the resulting object files into a final executable. No one is actually modifying the source code for closed-source software, just the resulting binaries.

IDA Hex Rays just generates pseudo C code from disassembled code, that's no way near the actual source code, it can't be just pulled from compiled binary, it doesn't work that way.