Brickedandroid
Content Type
Profiles
Forums
Events
Everything posted by Brickedandroid
-
Btw probably it's somewhat similar to the GTA San Andreas's orange atmosphere filter in PS2 version that isn't present in other platforms. Are you looking for an exact culprit file that causes blurry-bluish rendering?
-
This patch is also for Intel iGPU users, especially Intel UHD and Iris. So, just create this and wrap up it into the separate 7z file. The involved files are just d3d9.dll, gdi32.dll, user32.dll, and API-MS-WIN dlls only.
-
No, but Windows Vista's Direct3D 9 runtime has some conflicts with newer Intel HD 4000 drivers! I just want to backport or mod the DirectX 9 runtime file from Windows 7 only. DirectX 10, 11, and OpenGL are remain UNCHANGED!
-
Or try with build 7600
-
Use the 7601.17514 d3d9.dll, don't use the updated version such as extracted from the platform update.
-
It has been changed since Windows 7 build 6936. I tried replacing the d3d9.dll file with build 6910's and it still behaves like Vista's d3d9.dll (BEX64 crash code c0000005), but build 6936's works perfectly just like normal. I tested it myself on Windows 7 build 7000. Driver version: 10.18.10.4885 (December 2017 build), using George King's NTOSKRNL Emu_Extender
-
Please also backport the Windows 7's d3d9.dll for Windows Vista to solve the newer Intel HD Graphics 4000 driver version problem
-
Drivers for an N2840 on Vista x64 with the Extended Kernel
Brickedandroid replied to connor2's topic in Windows Vista
Now I have found myself that the exact culprit of the newer version of Intel HD 4000 driver aero problem is the d3d9.dll file located in System32 and SysWOW64 folder. It would be worked perfectly if using the backported Windows 7's d3d9.dll for Windows Vista, but it also has so many missing functions. Hope @win32 know this immediately. -
Now I have found myself that the exact culprit of the newer version of Intel HD 4000 driver aero problem is the d3d9.dll file located in System32 and SysWOW64 folder. It would be worked perfectly if using the backported Windows 7's d3d9.dll for Windows Vista, but it also has so many missing functions. Hope @win32 know this immediately.
-
@win32 Try backporting the windows 7's d3d9.dll to Windows Vista Extended Kernel. Because finally I have found myself that the exact culprit of the newer version of Intel HD 4000 driver aero problem is the d3d9.dll file located in System32 and SysWOW64 folder.
-
You also can try the newer laptops, but with AMD CPUs and Secure Boot disabled. Intel Haswell or later isn't supported yet for now.
-
But are the MS store apps also compatible with aero/classic themes?
-
And the TSC fix was introduced since 2007. But why Micros*ft didn't implement that s*** in SP1???
-
I don't mean for how successful the HAL wrapper will be. But just for the missing needed functions only, if someday you need to backport that kernel-mode files from newer OS. The rest is your business.
-
Yeah, @win32 with @Mov AX, 0xDEADand @George King must make the patch for both those builds
-
I mean make the patch for hal.dll for build 6002 and 6003
-
Support for both build 6002 and 6003 for the TSC drift fix
-
Would backporting the processr.sys driver file from Windows 7 build 6519 fix the Haswell+ TSC drift bug? (For the kernel-mode missing functions, please have a collaboration with @Mov AX, 0xDEAD's or @George King's NTOSKRNL Emu_Extender instead of adding them yourself to ntoskrnl.exe. Use Dependency Walker to check for the missing functions.)
-
Because sometimes they will be needed for something you don't know yet but you need it if you use Vista as a main OS, and you will don't need to be reported for the missing functions anymore. That's just like "Everything at Once" so the users will not have to wait another few years to enjoy their beloved modern apps or the newer version/updated daily apps. I don't mean to run it. You just have to obtain the MS Store apps and their data files, dynamic link libraries, and other PE-formatted dependency files from the Windows 10 VM/another PC and check for their missing needed functions using Dependency Walker.
-
So you must try more newer modern apps that are released beyond 2019, or apps with version/build newer than 2021, in which they are currently popular and have aesthetic-minimalist UI with rounded corners and eye-catchy effects and animations e.g. Spotify, Dropbox, Netflix, etc., and use Dependency Walker to check for the missing functions. Please try also the Microsoft Store apps on Windows Vista Extended Kernel if possible.
-
There will be some updates and new dll functions soon, as more users reporting the missing functions from the new modern softwares and drivers. But unfortunately the development takes so long time so that you will spend too much time to wait for it. I would contribute for the Vista Extended Kernel, but I want to report the new functions from Windows 7, 8, and 10 at once instead of the missing needed functions from Dependency Walker of the each software only. But I'm rejected because of this way. @win32 I'm so sorry.
-
@win32 Don't forget to also port the Windows 8.1's and Windows 10's functions to support Chrome 109 or later, because Chrome 108 is the last version for Windows 7
-
It's for testing/experiment only, no other purposes. Just install –> take some screenshots –> delete the VM
-
But virtualization emulates everything except processors, unless if you disable VT-X and using Hyper-V (software-based acceleration). And that's equivalent to recompiler and interpreter mode in PlayStation emulation
-
For anyone who has PC/laptop with 5th Intel Core processor or newer, try installing or dual-booting with Windows Vista x64 RTM. Because I think that most likely the Haswell TSC drift bug occurs since Service Pack 1 And I'm sorry for your inconvenience.