<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - swr: GPU Caps Viewer crashes with any 3D demo" href="https://bugs.freedesktop.org/show_bug.cgi?id=102564#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - swr: GPU Caps Viewer crashes with any 3D demo" href="https://bugs.freedesktop.org/show_bug.cgi?id=102564">bug 102564</a> from <a class="email" href="mailto:liviuprodea@yahoo.com" title="Alex Granni <liviuprodea@yahoo.com>"> Alex Granni</a> <pre>Sorry, I didn't mention that GPU Caps Viewer is 32-bit even if running on 64-bit Windows so it goes in \windows\syswow64 on a 64-bit Windows. The way I get it to use Mesa is by copying or rather create symlinks to Mesa DLLs in the folder where GPU Caps Viewer resides; there is no DLL hijacking mitigation in place. I create symlinks instead of copying to save storage and to update Mesa from a centralized location, but you can do it as you want. Also I have an advice for you. Dropping Mesa3D DLLs in system32 is short lived. Only Windows 7 still allows this. Starting with Windows 8, Microsoft enlisted TrustedInstaller to have ownership over system files. Changing permissions of system files is bad idea if not impossible in Normal boot mode. However there is a way to apply Mesa3D system-wide even on Windows 8 and 10 in Normal mode, by hijacking the OpenGL ICD of the main GPU. Windows stores the filenames of all OpenGL ICDs in registry in Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control under various keys which contain values named OpenGLDriverName for 64-bit ICDs and OpenGLDriverNameWow for 32-bit ICDs. The data of these values point to the OpenGL ICDs filenames.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>