Chrome on Windows 8.1

[mjd79]

20 minutes ago, D.Draker said:

 talented "Chinese student" already ported the cutting edge and UNCHANGED (as far as I can see from my brief usage) Ungoogled to Vista

Unfortunately, as you probably already saw in the relevant topic, it will not support Vista. I checked the version for 7 SP1 on 7 SP0 out of curiosity, the browser takes a suspiciously long time to start and I get a STATUS_BREAKPOINT error on every tab. I, unfortunately, do not have the skills or a sufficiently powerful computer to be able to compile his browser with the design that helped him maintain Vista compatibility, but perhaps there is a suitable person on the forum.

On 7 SP0 it is probably possible to solve this problem, I checked much older compilations of the Chinese student, and its run without this problem.

Edited April 6 by mjd79

[D.Draker]

11 hours ago, mjd79 said:

Unfortunately, as you probably already saw in the relevant topic, it will not support Vista. I checked the version for 7 SP1 on 7 SP0 out of curiosity, the browser takes a suspiciously long time to start and I get a STATUS_BREAKPOINT error on every tab. I, unfortunately, do not have the skills or a sufficiently powerful computer to be able to compile his browser with the design that helped him maintain Vista compatibility, but perhaps there is a suitable person on the forum.

On 7 SP0 it is probably possible to solve this problem, I checked much older compilations of the Chinese student, and its run without this problem.

Yes, I saw, but with the already ported version 136 we could do just fine for about two years, as you see, Thorium and Supermium only started to completely fail after two years from the initial version 111 (which in my humble opinion they are based on). My PC also sucks by the modern day standards, its CPU is very similar to the severely outdated CPU used by NotHereToPlayGames.

Edited April 6 by D.Draker
136

[mjd79]

@D.Draker, I already know what break ungoogled Chromium 135 and Chromium 137 by Chinese stundent on 7 SP0. It's ADVAPI32.dll, I temporarily used the whole library from Supermium, but in a day I'll check which specific function is responsible for it.

On Vista x64 SP2 it should be possible to run these browsers with an extended kernel redirected locally, as long as the “ntext.dll” file created a few years ago by win32ss is enough to replace ntdll.dll.

Edited April 7 by mjd79
Edit about possible Vista SP2 x64 support

[D.Draker]

10 hours ago, mjd79 said:

@D.Draker, I already know what break ungoogled Chromium 135 Chinese stundent on 7 SP0.

My trust in you has no bounds, I had no doubts you would find.

[D.Draker]

In NTDLL NtOpenKeyEx needs to replaced with just NtOpenKey, it's even safer this way, why would they need the extended variant!?!

[D.Draker]

For lower OS in SHELL32

SHGetPropertyStoreForWindow replace with SHGetStockIconInfo

[D.Draker]

11 hours ago, D.Draker said:

In NTDLL NtOpenKeyEx needs to replaced with just NtOpenKey, it's even safer this way, why would they need the extended variant!?!

If it fails, don't give up, try NtCreateKey.

https://learn.microsoft.com/en-us/windows-hardware/drivers/ddi/wdm/nf-wdm-zwcreatekey

[mjd79]

13 hours ago, D.Draker said:

In NTDLL NtOpenKeyEx needs to replaced with just NtOpenKey, it's even safer this way, why would they need the extended variant!?!

NtOpenKey without the "Ex" appended was enough. shell32 you mentioned and most other libraries I redirected locally from the extended kernel of March 9, 2023 (rev2). It is not possible according to what I have determined for now to redirect bcrypt.dll and ntdll.dll, kernel32.dll, which is a wrapper for Chromium 110 and 111 support does not work, probably due to lack of platform updates, however, there is also kernel33.dll in the files, which is the original kernel last modified by win32ss in December, 2022, and it works with ungoogled 135 and Chromium 137 without problems. My Vista update level is end of April 2017, no post-eol updates.

Edited April 7 by mjd79

[D.Draker]

22 hours ago, mjd79 said:

also kernel33.dll in the files, which is the original kernel last modified by win32ss in December, 2022

So the last (real) kernel release was in 2022, I knew something fishy was going on, thanks for the warning!

[mjd79]

I already know what is messing up Chromium 127+ It is the kernel32.dll and kernelbase.dll version checking. I rewrote it to return a false value for them indicating Win 10, and here is the result:

The latest versions also use IsWindowArranged from user32, which is absent in 8.1 - possible to be replaced by, for example, IsWindowVisible.

Now it remains for me to write my own version of UpdateProcThreadAttribute.

Edited May 15 by mjd79

[mjd79]

Sandbox working 

[mjd79]

https://github.com/ToprakBZK/Modern-Chrome-134-For-Windows-7-and-8.1/releases

Be warned, should anyone come across it, it's Blaukovitch's crack LOL My goal for more than a year was to become independent of his solutions when creating my own mods, but unlike that kid, I succeeded....

Edited May 21 by mjd79