Problem with the newer version of Intel HD Graphics 4000 driver on Windows Vista Extended Kernel

[K4sum1]

So I went to 7000, and had both the weird font and pixelated blur issues on both AMD and Intel, however OGL, DX9, and DX11 work perfectly fine on heaven in my testing.

Also the SSD I mentioned in the previous post is fine, apparently 6801 can corrupt partitions.

[com.android.systemui]

So I went and tested 6801 first as it's different, and found Intel drivers are black screen and AMD drivers are code 43.

Please also try with build 6936, 6941 (x86), 6956 (x86), and the builds between 7000 and 7600.
Don't forget to use NTOSKRNL Emu_Extender.
If testing the 32-bit builds are more complicated, please try the x64 builds first.

[com.android.systemui]

So I went to 7000, and had both the weird font and pixelated blur issues on both AMD and Intel, however OGL, DX9, and DX11 work perfectly fine on heaven in my testing.

Can you open the Intel HD Graphics control panel, play mp4 videos on Windows Media Player (especially 1080p videos), and play Chess Titans?

[blueclouds8666]

Back when I was friendly with win32 and co I heard from one or more of them that 7, when paired with a WDDM 1.1 driver and a capable card, uses DirectX 11 for Aero. I think they would know their shit. Could test with the AMD driver and deleting the DX11 dll on 7.

At the uncertainty of making a new thread or not, i'll be replying you here:

I have analyzed DWM's function calls and it does seem rendering is entirely comprised of D3D10.1 calls (namely D3D10CreateDevice1 for initialization, ID3D10Buffer::Map, ID3D10RenderTargetView::Release, ID3D10Texture2D::Release, ID3D10ShaderResourceView::Release for rendering & other related tasks). While i have observed a very few D3D11 calls, they seem to be used exclusively for checks, only done at the beginning and not used ever again after this initial phase of the compositing engine. I am also not aware of any kind of interoperability between DX10 and 11 that allows running ID3D10 functions inside a D3D11 context. (Likely) There is no 9Ex fallback mode on Win7, as it is probably not even needed. Direct3D10.1 can run on feature level 9_1 hardware providing the renderer code was programmed accordingly (not using hardware features not available in feature level 9_1), which this is the case, so it can run on the same hardware as Vista, providing the driver vendor wasn't lazy enough to forget to implement D3D10.1 on their WDDM drivers for their legacy GPUs (if i'm not mistaken, GeForce 5 FX WDDM drivers never implemented D3D10 so there is that (there is a chance those can only run aero under vista, unless something escapes my knowledge)(further research needed), intel probably neglected some of their older GPUs as well).

Vista also uses exclusively 9Ex. Tests with RivaTuner further confirm my findings (attached images).
Read the latest blog post at my website for all the technical details:
http://neonfloppy.sytes.net/blog/2022-12-25/

[com.android.systemui]

At the uncertainty of making a new thread or not, i'll be replying you here:

I have analyzed DWM's function calls and it does seem rendering is entirely comprised of D3D10.1 calls (namely D3D10CreateDevice1 for initialization, ID3D10Buffer::Map, ID3D10RenderTargetView::Release, ID3D10Texture2D::Release, ID3D10ShaderResourceView::Release for rendering & other related tasks). While i have observed a very few D3D11 calls, they seem to be used exclusively for checks, only done at the beginning and not used ever again after this initial phase of the compositing engine. I am also not aware of any kind of interoperability between DX10 and 11 that allows running ID3D10 functions inside a D3D11 context. (Likely) There is no 9Ex fallback mode on Win7, as it is probably not even needed. Direct3D10.1 can run on feature level 9_1 hardware providing the renderer code was programmed accordingly (not using hardware features not available in feature level 9_1), which this is the case, so it can run on the same hardware as Vista, providing the driver vendor wasn't lazy enough to forget to implement D3D10.1 on their WDDM drivers for their legacy GPUs (if i'm not mistaken, GeForce 5 FX WDDM drivers never implemented D3D10 so there is that (there is a chance those can only run aero under vista, unless something escapes my knowledge)(further research needed), intel probably neglected some of their older GPUs as well).

Vista also uses exclusively 9Ex. Tests with RivaTuner further confirm my findings (attached images).
Read the latest blog post at my website for all the technical details:
http://neonfloppy.sytes.net/blog/2022-12-25/

During Windows 7 development, since what build was DWM migrated to DirectX 10?

[K4sum1]

So I went to 7000, and had both the weird font and pixelated blur issues on both AMD and Intel, however OGL, DX9, and DX11 work perfectly fine on heaven in my testing.

Can you open the Intel HD Graphics control panel, play mp4 videos on Windows Media Player (especially 1080p videos), and play Chess Titans?

[K4sum1]

Tried 6910, same behavior as 6801.

[K4sum1]

6936 is the same as well.

[com.android.systemui]

So I went to 7000, and had both the weird font and pixelated blur issues on both AMD and Intel, however OGL, DX9, and DX11 work perfectly fine on heaven in my testing.

Can you open the Intel HD Graphics control panel, play mp4 videos on Windows Media Player (especially 1080p videos), and play Chess Titans?

DSC_0333.JPG
DSC_0335.JPG

Do you use NTOSKRNL Emu_Extender?

[K4sum1]

Yes, I use the same version shipped in this pack
https://board.eclipse.cx/viewtopic.php?p=3294#p3294

[com.android.systemui]

Mine is Mobile, version 10.18.10.4885, December 2017 build.

[K4sum1]

Hmm, I got my build from Intel's site, try the ntoskrn8.sys I used and the latest driver from Intel.

[com.android.systemui]

But, how about the AMD driver that you're installed on the Windows Vista machine that breaks DX11? What is the exact driver version and build? Do you also use George King's NTOSKRNL Emu_Extender there?

[K4sum1]

Anything after 17.10.1 breaks DX11, for my testing I used 18.3.1 since I had it on my USB still, but any release after 17.10.1 should be the same. I use the same George King NTOSKRNL emu for all.

[com.android.systemui]

Intel HD Graphics 4000 driver version 10.18.10.5161 build August 2020 works almost perfectly fine for me too. However, the 1080p videos are still crashing with problem signature BEX, code c0000005.

[com.android.systemui]

So, the bottom line is: DirectX 9 won't work at all on Windows Vista, nor even at least working so messy with glitches or artifacts, but keeps returning BEX64 related errors.

[com.android.systemui]

Maybe the culprit is the d3d9.dll file located in System32 and SysWOW64 folder. It would be worked perfectly if we use the backported Windows 7's d3d9.dll for Windows Vista, but it also has so many missing functions. Hope win32 in MSFN know this immediately.

[K4sum1]

Could try build 7000 d3d9, or maybe a slightly earlier build's d3d9 just to test with?

[com.android.systemui]

Could try build 7000 d3d9, or maybe a slightly earlier build's d3d9 just to test with?

No, it has quite a lot of missing functions when checked on Windows Vista Extended Kernel using Dependency Walker.
May win32 in MSFN would know this immediately and try to backport it.

[com.android.systemui]

Here are the following missing dependent functions (in gdi32.dll) that are needed for the Windows 7 Build 6519 d3d9.dll file

Edit: Windows 7 build 6519's d3d9.dll behaves the same like Vista's d3d9.dll

[K4sum1]

Seeing as how those are a bunch of 2 functions, you could probably remove the 2 and see if it works

[com.android.systemui]

Seeing as how those are a bunch of 2 functions, you could probably remove the 2 and see if it works

How do I remove them? Should I use CFF Explorer? Have you tried if it is still working even you removed some missing dependency functions?

[K4sum1]

I'll try it later. Use CFF Explorer to remove the 2.

[com.android.systemui]

I tried removing them, and I got this error when trying to play Chess Titans:

So, all I have to do is only add the missing functions to gdi32.dll and user32.dll files.

[legacyfan]

if it would help any I have a collection of all the Intel HD graphics 4000 drivers ever made (from xp-10) that I'm wIlling to offer if it would help with the problem https://www.mediafire.com/folder/7cn502z2o2hbo/Intel Drivers (HD 3000-4000)

[com.android.systemui]

Windows 7's Aero DWM actually also still relies on D3D9 (for older graphic cards only).