[WIP] Windows Vista Extended Kernel

[D.Draker]

@win32, hi. Could you try the new Opera ? Looks like Opera went kaput. Nothing happens, no error, doesn't even start the process.

No missing API. Maybe it's just me ? I had only tested on a PC with the bloody 6003 update, so maybe it's the case.

Looks like 100% match with the latest news regarding dropping win 7. 

But - Chrome 109 works weirdly fine. Here's the link. Unpack and don't forget to delete the "launcher" crap.

It's just out of curiosity because I had ditched Opera and switched to the Ugoogled.

https://get.opera.com/ftp/pub/opera-developer/94.0.4597.0/win/Opera_Developer_94.0.4597.0_Setup_x64.exe

[D.Draker]

I had found the problem yesterday. They had removed the Skia renderer from "older OS", starting recently, which was forced by my flags, hence no ability to launch.

Just so you know, later chrome will now depend only on software rendering completely, which sucks, honestly. They even disabled RawDraw !

Compare.

1 - The image is from the newest Opera.

2 - This link is how it should look with Skia on the earlier ones. 

https://msfn.org/board/topic/184046-future-of-chrome-on-windows-7/?do=findComment&comment=1229006

 

 

[Jakob99]

@win32 I was wondering if any of the following will be added to x86 user32.dll: DisplayConfigGetDeviceInfo, GetDisplayConfigBufferSizes, and QueryDisplayConfig

These break DX11 with the newly modded AMD Radeon graphics drivers as AMD 17.10.2 introduced new functions within atidxx32.dll. The drivers work for the most part (we get Aero Glass and what not), but not DX11.

[win32]

22 hours ago, Jakob99 said:

I was wondering if any of the following will be added to x86 user32.dll: DisplayConfigGetDeviceInfo, GetDisplayConfigBufferSizes, and QueryDisplayConfig

These break DX11 with the newly modded AMD Radeon graphics drivers as AMD 17.10.2 introduced new functions within atidxx32.dll. The drivers work for the most part (we get Aero Glass and what not), but not DX11.

If I can confirm that the wrappers will allow me to add the functions without breaking applications, then those functions will return.

But have you tried 64 bit DX11 applications and games? If those don't work then it must be something else.

[Jakob99]

On 11/13/2022 at 10:57 AM, win32 said:

If I can confirm that the wrappers will allow me to add the functions without breaking applications, then those functions will return.

But have you tried 64 bit DX11 applications and games? If those don't work then it must be something else.

I haven't yet. Hopefully those functions can return.

[Jakob99]

On 11/13/2022 at 10:57 AM, win32 said:

If I can confirm that the wrappers will allow me to add the functions without breaking applications, then those functions will return.

But have you tried 64 bit DX11 applications and games? If those don't work then it must be something else.

Sorry for double post, but two DirectX11 games that work with Vista do not work with 18.3.4 AMD installed.

[D.Draker]

On 11/12/2022 at 6:21 PM, Jakob99 said:

atidxx32.dll

 

On 11/12/2022 at 6:21 PM, Jakob99 said:

@win32 I was wondering if any of the following will be added to x86 user32.dll: DisplayConfigGetDeviceInfo, GetDisplayConfigBufferSizes, and QueryDisplayConfig

These break DX11 with the newly modded AMD Radeon graphics drivers as AMD 17.10.2 introduced new functions within atidxx32.dll. The drivers work for the most part (we get Aero Glass and what not), but not DX11.

Directx11 should have an independent file, at least it's the case with Nvidia. Aero will work if everything's ok with the DX9 file. So yeah , he might be right. 

[SigmaTel71]

18 hours ago, D.Draker said:

Aero will work if everything's ok with the DX9 file. So yeah , he might be right. 

IIRC, in Windows Vista, Aero relies on DirectX 10 when possible.

[D.Draker]

4 hours ago, SigmaTel71 said:

IIRC, in Windows Vista, Aero relies on DirectX 10 when possible.

In short, no. Longer explanation, look at the nvidia drivers (same goes for ATi). nvwgf2um.dll nvwgf2umx.dll are 32/64 DX10/11 drivers,

you can safely delete them, reboot and still have aero, because aero works off nvd3dum.dll and nvd3dumx.dll

(which are 32 and 64 bit drivers for D3D9). 

You know, this is very funny, if I ever relied on that kind of "sources trust-me-bro", I would make zero drivers for Vista.

Also, looks like you weren't paying attention because the OP wrote, DX11 doesn't work, but aero does.

And DX10 is in one file with 11, so it is not loaded at all. DX11 is pretty much DX10 with stuff added upon.

EDIT: *hint* you can see in the .dll's description yourself what are they for exactly.

Edited November 17, 2022 by D.Draker

[Brickedandroid]

@win32

Mine is Intel HD Graphics 4000. And I'm currently using the Windows 7 version of Intel HD Graphics 4000 driver (which has blue and white control panel window color) with NTOSKRNL Emu_Extender and some modifications. I have installed it through Device Manager driver update. And it turns out that it has worked partially. OpenGL and DX11 work perfectly without glitches, also the driver has no problem at all in Device Manager, but DX9 causes BEX64 related crashes. And until now I still cannot enjoy the Aero theme and play videos using Windows Media Player (because they need DX9 to work properly.)

Edited November 18, 2022 by Brickedandroid

[Brickedandroid]

And if I am trying to show the information center from Options and Support menu, the control panel crashes with code 0xc0000096 (STATUS_PRIVILEGED_INSTRUCTION)

[Sergiaws]

 

I'm having a strange issue with the new extended kernel version. Anything related with chromium, electron or node.js is not working. As an example, here's what happens if I write node or npm install jquery in the cmd

https://ibb.co/p4nrgqz

Here's a Brave browser log too.

debug.log

[Sergiaws]

 

I finally noticed what's wrong. These strange issues happens when you spoof globally. Tried global spoofing to see what was wrong with VSCode /VSCodium (v. 1.73) that version is not working at least for me. As far as I know, they dropped Windows 7.

[win32]

On 11/19/2022 at 2:07 PM, Sergiaws said:

I finally noticed what's wrong. These strange issues happens when you spoof globally. Tried global spoofing to see what was wrong with VSCode /VSCodium (v. 1.73) that version is not working at least for me. As far as I know, they dropped Windows 7.

You can't run anything Chromium if it's version spoofed to NT 6.2 or greater for now, because of the use of features that aren't implemented right now like job objects.

[Brickedandroid]

Does the TSC drift bug on Haswell or later also still have effect if installed inside virtual machine?