Jump to content

[WIP] Windows Vista Extended Kernel


win32
 Share

Recommended Posts


2 hours ago, winvispixp said:

no

Really? Have you tried it, especially Windows Vista x64 SP2 without any driver and updates (in VirtualBox and VMware), on 5th Intel Core generation or newer, using VT-x and VT-d?

Try install it in both VirtualBox and VMware and then send the screenshot to me through message. I would to know and check if it's successfully entered to desktop, or black screen with or without error message, before or after the welcome screen, or even the worse one, BSOD. And don't forget to reboot the VM multiple times after installing if the first time boot has little or no problems, to verify the bug effect. The screen must be black, with or without errors, before the welcome screen, in many chances.

Edited by Brickedandroid
  • Upvote 1
Link to comment
Share on other sites

59 minutes ago, Brickedandroid said:

Really? Have you tried it, especially Windows Vista x64 SP2 without any driver and updates (in VirtualBox and VMware), on 5th Intel Core generation or newer, using VT-x and VT-d?

Try install it in both VirtualBox and VMware and then send the screenshot to me through message. I would to know and check if it's successfully entered to desktop, or black screen with or without error message, before or after the welcome screen, or even the worse one, BSOD. And don't forget to reboot the VM multiple times after installing if the first time boot has little or no problems, to verify the bug effect. The screen must be black, with or without errors, before the welcome screen, in many chances.

vmware and virtualbox do virtualizations, there is no need to install intel or nvidia or whatever you want driver, only vmware's software (i forgot the name) or guest additions for virtual box; vitualization means it runs on top of your existing os, not directly on your hardware which is why the performance of a vm is way worse
have you never used a vm before? the timing problem has been looked into a billion times already

Edited by winvispixp
  • Upvote 1
Link to comment
Share on other sites

52 minutes ago, winvispixp said:

vmware and virtualbox do virtualizations, there is no need to install intel or nvidia or whatever you want driver, only vmware's software (i forgot the name) or guest additions for virtual box; vitualization means it runs on top of your existing os, not directly on your hardware which is why the performance of a vm is way worse
have you never used a vm before? the timing problem has been looked into a billion times already

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

Edited by Brickedandroid
  • Upvote 1
Link to comment
Share on other sites

1 hour ago, Brickedandroid said:

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

and where are you hoping to get with this assuming that someone sends you screenshots? there are tons of people that don't want to use vms because of the worse performance

  • Upvote 1
Link to comment
Share on other sites

On 11/23/2022 at 11:50 AM, Brickedandroid said:

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.

No, it also has it. It's just happens less frequently. 

  • Upvote 1
Link to comment
Share on other sites

10 minutes ago, Brickedandroid said:

@win32

Don't forget to also port the Windows 8.1's and Windows 10's functions to support Chrome 109 or later,

There is already a topic about that here:

 

10 minutes ago, Brickedandroid said:

because Chrome 108 is the last version for Windows 7

Chrome 109 is the last version for Windows 7, not Chrome 108.

Edited by mina7601
  • Like 1
  • Upvote 1
Link to comment
Share on other sites

  • 2 weeks later...

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.)

Edited by Brickedandroid
Link to comment
Share on other sites

4 hours ago, Brickedandroid said:

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.)

I have added only few “improvements” to @Mov AX, 0xDEAD latest release. You can see changelog on GitHub.

  • Like 1
Link to comment
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
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.


×
×
  • Create New...