Eclipse Community

hiw did you get this to work? I can never get anything except the 4000 driver from msfn to work properly

legacyfan wrote: *

01 Jun 2023, 15:54

hiw did you get this to work? I can never get anything except the 4000 driver from msfn to work properly

I'm using WineD3D to replace the d3d9.dll file in System32 and SysWOW64 folder. Also I renamed or moved out the igdumdim64.dll and igdumdim32.dll files.

If your iGPU supports Vulkan (particularly the 7th gen or later Intel Core CPUs), please use DXVK instead.

GTA San Andreas also works successfully on WineD3D. But if the Visual FX Quality is too high, the game will become very slow and unplayable, especially when in Red County. And the intro's FMV only plays the audio but still can be skipped. Unlike when using the native D3D9 which the game keep runs smoothly even with highest graphics quality on the same hardware and also can play the intro's FMV videos perfectly. Hope the DXVK's D3D9 will improve the performance so much and become faster and better graphics quality than the native D3D9. (BTW I'm using SkyGFX to make the GTA San Andreas on PC graphics looks like in PS2.)

Windows 8.1's D3D9.dll is also faulty on latest Intel UHD 620 driver! (Crashes with problem signature BEX, code c0000005)
Maybe that driver with the new Intel logo is only designed for Windows 10 or higher.

Uh the D3D9.dll probably just straight up doesn't work. Also this is not a DirectX error, it's a user32.dll issue.

This might be helpful and informative, but don't focus on PCSX2. Instead, just learn the DirectX-related things from it.
https://github.com/blueclouds8666/pcsx2_XP/issues/2

com.android.systemui wrote: *

07 Jun 2023, 03:32

Windows 8.1's D3D9.dll is also faulty on latest Intel UHD 620 driver! (Crashes with problem signature BEX, code c0000005)
Maybe that driver with the new Intel logo is only designed for Windows 10 or higher.

There might be some missing hidden functions that are not shown blatantly in Dependency Walker or Export Table tester, or there might be some differences or changes with the unnamed functions or ordinal-based functions. So that's why Windows Vista's d3d9.dll won't support the newer Intel HD 4000 drivers, and Windows 8.1's d3d9.dll also won't support the Intel UHD 620 drivers with new Intel logo on the control panel. As well with the Intel HD 530 driver won't support Windows 7 unless with Service Pack 1 installed.

We need IDA Pro to investigate those further.

Native D3D9 is also the best choice because it fully works for all programs and games, with noticeably fast and good performance, and basically supports all GPUs.

any further finds on this problem? as im interested in trying new games thru this method

I've kinda lost interest in Vista, so I probably won't be looking into this for a long while.

Sorry, for the current solution, just go buy the new laptop with 12th gen or newer Intel CPU with E cores and using discrete GPU (GeForce or AMD Radeon). And only install the discrete GPU driver on Windows Vista Extended Kernel (the integrated graphics device remains without driver, otherwise it will cause problems with DirectX 9 when initialized, and might have negative impacts to the discrete GPU, because DirectX 9 still plays most major roles in Windows Vista despite also has DirectX 10 and 11 versions, and ironically, the newer Intel Graphics drivers only support DirectX 10 and newer, OpenGL, and Vulkan if not installed in Windows 7 or newer).

The TSC clock drift that causing black screen after boot and service start problems from the 4th gen through 11th gen in Windows Vista has been addressed since 12th gen.

For the AMD CPUs, any AMD CPU can run Windows Vista, but most of them occassionally will occur the random BSODs after some hours of usage (unresolved sudden mysterious 'internal injury'). And AMD's Vega iGPUs are fully supported.

I spotted this on the extended kernel website.
https://www.win32subsystem.live/extended-kernel/downloads/graphics/intel/IntelHD_9.17.10.4459_Vista.7z

This seems to be the last driver for the HD 3000 (also works on 4000) and the driver .sys was modified to work with Vista. Still old control panel but may be worth a shot.