ffqq
Content Type
Profiles
Forums
Events
Posts posted by ffqq
-
-
-
On 6/21/2020 at 5:41 AM, win32 said:
I have now fixed the import calls and added K32EmptyWorkingSet. So about 26 more functions to go in kernel32!
OBS Studio 19.2.0 is mostly working now, but there are a few missing functions in MFPlat.dll (Media Foundation Platform), like MFTEnumEx (used to find video/audio decoders) and MFCreateMFByteStreamOnStream. While it picks up on audio, it doesn't record or show video and creates tiny (corrupt) files. Or it may be because it forces a D3D11 renderer and my DX10 native GPU doesn't seem to work very well with DX11 (Cities: Skylines is unplayably glitchy in D3D11 mode on Vista and 7 but fine in D3D9 mode on XP x64).
I think that the media foundation extensions will be fun, as I may even introduce the functions from Windows 8 as opposed to just the ones new to 7. That would mean adding stuff like Direct3D 11-based video APIs. Though adding DX11.1+ features will be pointless if the drivers available for Vista can't use them. And getting WDDM 1.1+ drivers on Vista is going to be one difficult undertaking, but probably easier than porting WDDM 1.0 drivers to XDDM (Windows 2000 Display Driver Model).
And I've found another limitation of LOCAL files. Programs don't like being debugged when redirection is taking place to files within folders; they throw a fault in StackHash_**** when trying to launch them through Dependency Walker. But if the same file is loaded from system32 as opposed to the program directory, with no redirection taking place, the program works (as well as possible) through Dependency Walker. So I thought about .manifest files, which give you the option to redirect only the files specified within them.
Here is an example of the contents of a manifest file used for DLL redirection:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0"> <assemblyIdentity version="1.0.0.0" name="redirector" type="win32" /> <file name="kernel32.dll"> </file> </assembly>
But it appears that manifest files don't seem to help much in that regard. So I guess you will have to replace your system files with mine if you're planning on debugging programs using my files.
Once I get a wide array of programs working stable, I hope that you do one of your excellent videos about the kernel's capabilities. You create some great promotional tools for Vista, and this one will explore some uncharted territory for the OS.
On one last note, this isn't the only new kernel extension project that helps Vista users out:
The tutorial specifically mentions building for x86, but I built it in the Vista x64 build environment in the Windows 7 DDK, so it could help with certain classes of drivers. Will it help for modern GPU drivers? Not really. NVMe and USB 3? Sure.
MFTEnumEx is also required for the Roblox client (RobloxPlayerBeta.exe). The artificial software lock on the launcher (RobloxPlayerLauncher.exe) can easily be bypassed by your OS spoofer, but the client launches just fine (though it gets the MFTEnumEx error) with or without the OS spoofer as far as I've seen. Great work, by the way!
0 -
I'd like my name renamed from "syria!" to "ffqq" please.
0 -
Just now, asdf2345 said:
The 15.100 embedded drivers aren't that bad on my HD 6870, and with the extended kernel you don't need to use the powerprof wrapper
If the embedded drivers support OpenGL which is needed to run most graphical apps or games, you should be good
0 -
8 minutes ago, greenhillmaniac said:
I have a R9 380, precisely the point where AMD drivers stopped working. Had to used a hacked together Embedded version of the drivers. Not ideal.
Never heard of SDI. I'll have to check it out.
Hm, I think you're out of luck on this one, but you can still try Snappy Driver Installer which might get the gpu drivers running.
https://sdi-tool.org/download/
It's 21gb large, DriverPack doesn't work on vista so you have to use SDI
Inform me if SDI installs the drivers correctly, run the windows experience index after installing the gpu drivers, then wait for it to finish the benchmarks. You should get Aero Glass and other Aero effects if it's 3+
EDIT: Yeah, might be the reason. Still, give it a try, might work although it might have to use an engineering sample1 -
5 minutes ago, greenhillmaniac said:
Any chance you'd also take a look at AMD drivers? They stopped working in mid-2015 when they changed driver branches (introduced with the RX 300 series: https://www.guru3d.com/files-details/amd-catalyst-15-15-download.html).
Which AMD gpu do you use? I use the Radeon HD 7000 Series GPU and I got it working using SDI
0 -
Software compatible with Windows Vista Extended Kernel
in Windows Vista
Posted · Edited by ffqq
Chromium 102 (developer build) works on the extended kernel! Extensions (not all of them) work too