IntMD

(Thread inspired by Dr. Flay's thread: https://forum.vivaldi.net/topic/38561/windows-7-old-games-failing-to-run) Ever since Games Explorer was introduced in Windows Vista, it has caused problems for users with limited access to the internet. Most affected users would have already disabled it by editing GameUX's registry settings or by unregistering the dll (GameUX.dll), but last month Microsoft has taken the domain the Games Explorer system used to phone for game-related metadata and updates out of commission (specifically: "https://games.metaservices.microsoft.com/games/SGamesWebService.asmx"), thus the problem will also show for users which have permanent connection to the internet. Symptoms related to this problem: Game fails to open, but their processes can be seen in the taskmgr The rundll32.exe process related to gameux.dll spikes up to >50% of CPU usage Running a second copy of the game or renaming the game executable works around it Any old game that has been added by Games Explorer itself is affected to this problem, since Windows is using the rundll32.exe process to check the game updates before launching the game. Note that you can't remove said games from Games Explorer itself, only hide it. Even changing the options within the Games Explorer to never check online for game updates and news won't fix this problem. The fix which tackles the problem at its core is to use these registry files provided by user UCyborg (Make sure to read the whole post!): The second fix (or rather a workaround) which is more simpler, but doesn't remove the problem at its core (less recommended than the first one): All you have to do is to open regedit, go to this key: HKEY_CLASSES_ROOT\Local Settings\Software\Microsoft\Windows\GameUX\ServiceLocation Changing the server address in the "Games" value to either '127.0.0.1', 'localhost' or '0.0.0.0' ought to fix it.

Quoting what I said on OP's similar thread about the problem. This has fixed OP's problem, so it should fix yours.

https://forums.geforce.com/default/topic/783386/geforce-drivers/geforce-960-970-980-windows-xp-drivers/post/5918551/#5918551 This apparently might fix this problem with the multimonitor. Fits the error you have- PAGE_FAULT_IN_NONPAGED_AREA. Make sure that you have the 368.81 GeForce Game Ready driver installed using this guide: https://mattpilz.com/windows-xp-drivers-nvidia-geforce-gtx-970-980-980-ti-titan-x/

Rechecked the v0.43b of the app on Win7 Enterprise 7601.24441 and the Amazon/Paypal problem has been fixed. On the first run from the 200 hosts only one had a failed handshake (www.discover.com). Checking the site on both Chrome and IE show that the Root CA is DigiCert High Assurance EV Root CA. Running the app the second time makes said handshake succeed with a valid result.

Just have rechecked the recently released v0.42b of the app on Windows 7 Enterprise build 7601.24441, and from the (updated) 200 hosts two of them had the ALERT result: Amazon and PayPal. Both of them shared the VeriSign Class 3 Public Primary CA - G5 Root CA with the thumbprint being "4EB6D578499B1CCF5F581EAD56BE3D9B6744A5E5". Can someone recheck this version of the app to see if the same alert results will also be detected, just to be sure it's not a false alarm or something? Many thanks. Picrel below showing the results with the ALERT ones on the top.

That's weird, since on build 7601.24441.amd64fre.win7sp1_ldr.190418-1735 all of the handshakes have succeeded, along with the tinyurl root CA being valid (COMODO ECC Certification Authority). Using version 0.39b of the tool and my schannel.dll file version is 6.1.7601.24441

https://docs.microsoft.com/en-us/previous-versions//jj126201(v=vs.85) https://community.osr.com/discussion/257498 Apparently the HID over the I2C interface thing isn't supported in Windows 7, so that might not be surprising that the touchpad doesn't work. Least it could work is Windows 8, so I'm afraid that OP won't get the touchpad working.

Here's the driver that my acquaintance (OP) used. To clarify once again he used the setup.exe in Elan_19.4.4.3WHQL (not the one in the x64 subfolder) , thus he got the mentioned Intel miniport driver installed with the Code 12 problem. The executable linked in the following quote is an inno-setup-type self-extracting archive, so you can extract it by using UniExtract2

Also 2023 when it comes to the extended ''paid'' updates for Professional and Enterprise. I hope that when they'll be released somebody might leak them, of course assuming that the update packages will not be tampered. (by verifying the signature/sum)

Come to think of it, if OpenGL applications are fully accelerated whilst DirectX ones aren't with 372.70, maybe we can workaround by using WineD3D for DirectX apps. It's sloppy but it's better than nothing :/

None of those issues mentioned didn't happen for me. I recommend to install the SHA-2 updates before the monthly update though.

What's rude with informing an user to test the drivers by themselves if they work and posting in a correct subforum(since you yourself have made the inf file)? You kind of remind me of this guy in this very own forum making a thread in the vista subsection about somebody to make an unattended setup program for a pre-release version of Windows. Even though I don't want to jump into the conclusions you might be the guy that made the thread mentioned in first place, given these set of circumstances (that might or might not be inaccurate): nationality (Turkey) kind of similar typing style getting passively aggresive when somebody doubts your "project" Something makes me think that you're trolling

Here are the GetVersion.exe results for WinXP SP3 build 2600.xpsp_sp3_qfe.180912-0606 (with POSReady patch) <tt>GetVersion: 0x0A280105 GetVersionExA (OSVERSIONINFOA*): dwOSVersionInfoSize 0x00000094 dwMajorVersion 0x00000005 dwMinorVersion 0x00000001 dwBuildNumber 0x00000A28 dwPlatformId 0x00000002 szCSDVersion[128] "Service Pack 3" [53 65 72 76 ...] return TRUE GetVersionExA (OSVERSIONINFOEXA*): dwOSVersionInfoSize 0x0000009C dwMajorVersion 0x00000005 dwMinorVersion 0x00000001 dwBuildNumber 0x00000A28 dwPlatformId 0x00000002 szCSDVersion[128] "Service Pack 3" [53 65 72 76 ...] wServicePackMajor 0x0003 wServicePackMinor 0x0000 wSuiteMask 0x0100 wProductType 0x01 wReserved 0x00 return TRUE GetVersionExW (OSVERSIONINFOW*): dwOSVersionInfoSize 0x00000114 dwMajorVersion 0x00000005 dwMinorVersion 0x00000001 dwBuildNumber 0x00000A28 dwPlatformId 0x00000002 szCSDVersion[128] "Service Pack 3" [53 00 65 00 ...] return TRUE GetVersionExW (OSVERSIONINFOEXW*): dwOSVersionInfoSize 0x0000011C dwMajorVersion 0x00000005 dwMinorVersion 0x00000001 dwBuildNumber 0x00000A28 dwPlatformId 0x00000002 szCSDVersion[128] "Service Pack 3" [53 00 65 00 ...] wServicePackMajor 0x0003 wServicePackMinor 0x0000 wSuiteMask 0x0100 wProductType 0x01 wReserved 0x00 return TRUE gv=0x0A280105 gvex=5,1,A28,2,Service Pack 3,3,0,100,1,0</tt>

The only thunderbird fork i know of that isn't quantum-based is binaryoutcast's 'interlink mail & news'. Roytam makes XP-compatible builds of it (along with the browser suite (Borealis)), so you're in luck.

The difference is that Google doesn't even try to straightup put a lie that it's a browser that keeps privacy in mind and doesn't collect data unlike Slimjet, that and whether to pick up a small-name company (FlashPoint) sharing sensitive info to multiple companies and a big-name company (Google) to collect the data and keeps it to itself, i'd pick the latter. It's much worse when it comes to privacy than Chrome, especially when it's advertised as a browser trying to not collect your data. Advanced Chrome would be more reliable, even if it's also by a small name company though. Their site providdes a git difference between their fork and normal Chrome.

I wouldn't recommend Slimjet, especially since it's basically a spyware bomb. Take a read on this

You might be better off using wined3d to translate >=DX10 calls to OpenGL. This way it's a nice workaround for DX10/DX11 only games on XP.

IIRC roytam1's Basilisk fork (I dunno how's the case with PM28) allows you to use the Discord voicechat feature.

Just remove the folder containing New Moon's program files and replace it with the newer version. Since roytam's builds aren't portable the configuration files are in AppData, so you don't have to start it again.

Sorry for bumping, but is there any progress (even the smallest) on this project? It has been 2 months since the last post and it would be sad if this project was abandoned.