Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


win32

[WIP] Windows Vista Extended Kernel

Recommended Posts

9 minutes ago, burd said:

https://imgur.com/a/1guYVNq

can you view it now?

So there seems to be something wrong with my custom osloader.efi. Unfortunately there is no EFI hardware here for me to test it with, so any corrections will take awhile.

Does my ntkrnlmp.exe work with the regular winload.efi and nointegritychecks = 1 (yes) in the boot entry?

Though this could also be used in theory, but I need to test it:

https://github.com/Mattiwatti/EfiGuard

Edited by win32

Share this post


Link to post
Share on other sites

6 minutes ago, win32 said:

So there seems to be something wrong with my custom osloader.efi. Unfortunately there is no EFI hardware here for me to test it with, so any corrections will take awhile.

Does my ntkrnlmp.exe work with the regular winload.efi and nointegritychecks = 1 (yes) in the boot entry?

Though this could also be used in theory, but I need to test it:

https://github.com/Mattiwatti/EfiGuard

it doesn't work even with winload.efi same error

Share this post


Link to post
Share on other sites
6 hours ago, asdf2345 said:

Don't know if I'm temporarily more lucky, but Vista appears more stable now.

Thought I replied to this, it still crashes quite a bunch.

Share this post


Link to post
Share on other sites
15 minutes ago, asdf2345 said:

Thought I replied to this, it still crashes quite a bunch.

So none of the instability was induced by a OS version bias. Now I just need an ntoskrnl version to tie to the dumps that you have posted previously and hopefully I can look into those.

Share this post


Link to post
Share on other sites
5 minutes ago, win32 said:

So none of the instability was induced by a OS version bias. Now I just need an ntoskrnl version to tie to the dumps that you have posted previously and hopefully I can look into those.

Most are from RTM SP2, but I'm pretty sure I posted some dumps from the 2017 EOS point, and the 2020 EOS point.

I'll try to get some more with the custom kernel tomorrow.

 

  • Upvote 1

Share this post


Link to post
Share on other sites

Will this custom kernel allow the installation of newer Windows 7 drivers on Vista?

Share this post


Link to post
Share on other sites
5 hours ago, greenhillmaniac said:

Will this custom kernel allow the installation of newer Windows 7 drivers on Vista?

Yes. Hoping there are no issues that may arise once the appropriate functions are added.

  • Like 1

Share this post


Link to post
Share on other sites
45 minutes ago, win32 said:

Yes. Hoping there are no issues that may arise once the appropriate functions are added.

I can't wait! This and a fix or maybe an improvement for Haswell+ CPUs should drive vista to a completely new level of usability on modern hardware.

Edited by tamarindojuice

Share this post


Link to post
Share on other sites
7 minutes ago, tamarindojuice said:

This and a fix or maybe an improvement for Haswell+ CPUs should drive vista to a completely new level of usability on modern hardware.

Well, it appears that MS got around to improving Haswell, though there are still some issues.

I haven't been able to test it due to issues with Windows Update on my Kaby Lake though.

Now I'm thinking; do I rebase the extended kernel on the September 2020 versions of files, thus abandoning the April 2017 versions? Or do I still work on LoadLibraryExW from build 6519 since that is flawless, while this one is not (mind you, the UAC permission issues may lie elsewhere).

 

  • Like 1

Share this post


Link to post
Share on other sites
51 minutes ago, win32 said:

Well, it appears that MS got around to improving Haswell, though there are still some issues.

I haven't been able to test it due to issues with Windows Update on my Kaby Lake though.

Now I'm thinking; do I rebase the extended kernel on the September 2020 versions of files, thus abandoning the April 2017 versions? Or do I still work on LoadLibraryExW from build 6519 since that is flawless, while this one is not (mind you, the UAC permission issues may lie elsewhere).

 

The issues still exist , the stability is just a bit better , it would have a 65% successful boot compared to 50% of before august

Share this post


Link to post
Share on other sites
1 hour ago, tamarindojuice said:

I can't wait! This and a fix or maybe an improvement for Haswell+ CPUs should drive vista to a completely new level of usability on modern hardware.

Well, with the extended kernel, up to AMD 15.100 drivers work without any modification (Well, you would need to modify the .inf, but other than that, nothing is needed). The AMD 15.6 CCC is missing some powerprof.dll functions, but works anyways. Maybe with the new ntoskrnl, I could try the 16.2.1 drivers, or those modded 16.101 drivers.

I think someone would need to mod 372.70 drivers to work better with Vista, because I think the issue is not missing functions. @win32 seems to be the best person to attempt such a thing, unless @blackwingcat decides to try and fix them, but that's highly unlikely.

I think I'd rather see the Oct 2nd Steam tricked into running the Windows 7 CEF without issue, or Discord working on Vista before I see the Haswell+ or Ryzen issues fixed.

Since Chromium 73 stable and newer don't work on Vista, I think you'd need to modify a older copy of Discord, which Discord still hosts.

https://dl.discordapp.net/apps/win/0.0.305/DiscordSetup.exe

This is the last(?) copy of Discord that has a Chromium 69 CEF, and should be the easiest to get working on Vista. If you bypass the shortcut, and run Discord directly, it'll update to the latest version of 305, and run.

Edit: There might be a Chromium 72 Discord Development build, but I'm not sifting through thousands of versions of Discord Development.

Edited by asdf2345
  • Like 1

Share this post


Link to post
Share on other sites
1 hour ago, win32 said:

Well, it appears that MS got around to improving Haswell, though there are still some issues.

Now I'm thinking; do I rebase the extended kernel on the September 2020 versions of files, thus abandoning the April 2017 versions? Or do I still work on LoadLibraryExW from build 6519 since that is flawless, while this one is not (mind you, the UAC permission issues may lie elsewhere).

I would keep the things in the path they are going now, since the bugs are still existing on Server 2008 updates side and everything to this point is going well as it is.

Just my thought. 

Share this post


Link to post
Share on other sites
32 minutes ago, asdf2345 said:

Since Chromium 73 stable and newer don't work on Vista, I think you'd need to modify a older copy of Discord, which Discord still hosts.

We don't need to go back that far for Electron apps. Visual Studio Code 1.46 works and it's based on Chromium 78. If Discord and Steam were x64 native, they'd probably work.

We need to get into ntdll (both x86 and x64) for later Chromiums to work. And now that ntoskrnl modification is starting, ntdll modification should be coming soon.

And yes, based on recent comments, the current path will be maintained.

 

Edited by win32
  • Like 1

Share this post


Link to post
Share on other sites
5 minutes ago, win32 said:

We don't need to go back that far for Electron apps. Visual Studio Code 1.46 works and it's based on Chromium 78. If Discord and Steam were x64 native, they'd probably work.

We need to get into ntdll (both x86 and x64) for later Chromiums to work. And now that ntoskrnl modification is starting, ntdll modification should be coming soon.

And yes, based on recent comments, the current path will be maintained.

 

I think it would have been easier for you to get those older versions of Chromium x86 working.

Steam mostly works, we just need to trick it into loading the Windows 7 x64 CEF.

Share this post


Link to post
Share on other sites
3 hours ago, asdf2345 said:

I think someone would need to mod 372.70 drivers to work better with Vista, because I think the issue is not missing functions. @win32 seems to be the best person to attempt such a thing, unless @blackwingcat decides to try and fix them, but that's highly unlikely.

I just remembered someone else that might be able to help with this, @Dibya.

Mainly thinking about this post

@Dibya might be able to fix the 372.70 drivers, and maybe even port much newer AMD drivers to Vista.

Also, @Dibya might be able to help with the extended kernel

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...