An absolute disaster: illegible writing, illegible settings menu, accent color that hides the writing...

[drimisone]

Mr @Catsxp please :


since the problem is very complex and if sadly it is impossible to fix, I think the ultimate solution to save Catsxp and Chromium on Windows 7 OS is
Vxkex: Windows 7 API Extensions:

https://github.com/i486/VxKex

Some accuse Microsoft of deleting the original vxkex repository on GitHub, but Mr @i486 is in contact with the real original developer of Vxkex and he publishes an exact copy of the authentic vxkex, so I think the ultimate solution would be a collaboration between Mr @Catsxp and Mr @i486 who will take care of forwarding the specific technical requests of Mr @Catsxp to the original developer of Vxkex in order to continue supporting Catsxp and Chromium on windows 7, months ago, before discovering Chromium-for-windows-7, by curiosity I installed vxkex and I installed chromium for windows 10 os and it did not work on my windows 7 os , so I think please there should be a mutual technical collaboration between Mr @Catsxp and the developer of vxkex to maintain the dream of Catsxp and Chromium on windows 7 os please, thanks!

[drimisone]

Update !!!!!!!!!!!!!!

Mr @Catsxp, I have great good amazing news !!!!!!!!!

After i tested many chromium 136 and chromium 132 versions, the great Mr @e3kskoy7wqk has achieved the sensational, titanic exceptional amazing technical feat of determining the origin of the Chromium 136 display problems, i.e., the Windows SDK version upgrade !

Since generous compassionate hero Mr @Ctasxp refuses to abandon millions of users who use Windows 7 os, so we hope please a fruitful collaboration on github between great Mr @Catsxp and his compatriot great Mr @e3kskoy7wqk to help Mr E3kskoy7wqk to confirm the origin of this bug and to fix this problem, since Catsxp browser is based on Chromium and Catsxp browser continues supporting Windows 7 os, thank you!


here what Mr @e3kskoy7wqk says about the origin of the bug:

"@trimechee Thank you so much for your testing! We can stop further testing at this point. It's now almost certain that the explanation in #47 (comment) holds true - this issue may caused by the Windows SDK version upgrade.

I'll now attempt to revert the Windows SDK back to version 10.0.22621.2428, then rebuild and verify whether the issue disappears."

https://github.com/e3kskoy7wqk/Chromium ... 2868673675

[drimisone]

Mr @Catsxp : to recapitulate the origin of the bug of chromium 136 32 bits for windows 7 os 32 bits :

chromium 136.0.7080.0 has no dipslay issues
vs.
chromium 136.0.7081.0 has display issues


* there is SDK version upgrade between chromium 136.0.7080.0 and chromium 136.0.7081.0 :

Commit fca8e87
https://github.com/chromium/chromium/co ... 4cd530b23e


also, let's note:

Chromium 132.0.6780.0 (32 bits) doesn't have display issues=there is no problems
vs.
Chromium 132.0.6787.1 (32-bit) has display issues=there is display issues


*possible fix:
revert the Windows SDK back to version 10.0.22621.2428, then rebuild and verify whether the issue disappears

[catsxp]

try copy [135.5.4.3] d3dcompiler_47.dll to [137.5.5.4 beta-2]
Replace the file and see if it works properly
Understand the relevant information, after upgrading the d3dcompiler_47.dll file, it will call functions that are not available in the Win7 system
Causing several anomalies

[drimisone]

Aieee Bad News!!!!!!!!

Mr. @gz83, one of the developers of Thorium-legacy browser commented this:

"I just did a quick read and didn't read the context carefully, I think reverting the windows sdk update is not the best option, it can only be used as a short-term workaround.

But regardless of what happened, I applaud the attempt to provide support for the old system."

https://github.com/e3kskoy7wqk/Chromium ... 2868741561


****
Please Mr @Catsxp, Is there another way to fix these display issues in Chromium 136 please?
users of windows 7 os would be very grateful, please, Mr. @Catsxp if you can you assist or give new ideas and solutions to Mr. @e3kskoy7wqk to fix this problem, since our beloved Catsxp Browser is also based on Chromium and we need vital capital expert advice of Mr @Catsxp on how to fix this urgent issue affecting Chromium 136 please!

[catsxp]

Aieee Bad News!!!!!!!!

Mr. @gz83, one of the developers of Thorium-legacy browser commented this:

"I just did a quick read and didn't read the context carefully, I think reverting the windows sdk update is not the best option, it can only be used as a short-term workaround.

But regardless of what happened, I applaud the attempt to provide support for the old system."

https://github.com/e3kskoy7wqk/Chromium ... 2868741561


****
Please Mr @Catsxp, Is there another way to fix these display issues in Chromium 136 please?
users of windows 7 os would be very grateful, please, Mr. @Catsxp if you can you assist or give new ideas and solutions to Mr. @e3kskoy7wqk to fix this problem, since our beloved Catsxp Browser is also based on Chromium and we need vital capital expert advice of Mr @Catsxp on how to fix this urgent issue affecting Chromium 136 please!

try copy [135.5.4.3] d3dcompiler_47.dll to [137.5.5.4 beta-2]

[catsxp]

Why not try this simple and efficient solution of patching Win7?
It's a terrible idea to be compatible with Win7 that's not in a fully charged state

[drimisone]

Thank you very much Mr. @catsxp for your great generous advice which is so helpful to the entire community!

I will immediately inform Mr. @e3kskoy7wqk of this brilliant idea

[drimisone]

Mr @Catsxp, thanks for your advice to patch windows 7 os!

Sadly, windows update no longer works in my windows 7 os starter edition,

and i already try to download and install these updates:

KB2533623 (Adds several kernel32 functions)
KB2670838 (Platform update, needed for some games and drivers)
KB4019990 (Installed with .NET 4.8, adds native compatibility for D3DCompiler_47)


but sadly, I got error message:

"The installer encountered an error: 0x8......:
The specified service does not exist as an installed service."

I also got the same error message when I tried to install the other two updates...


and even if we install these updates patch, the error persist remain on windows 7 32 bits, because yesterday a user said this:

"Yeah, 136.0.7103.96 x86 is affected. The issue starts with 7083.1. 7077.0 works.

I have a Turkish (not English) Windows 7, maybe this causes it? What Windows language are you running on? I already have KB4019990 and KB3080149 installed."

https://github.com/e3kskoy7wqk/Chromium ... 2866233734

I previously said that I'm ready to reinstall vxkex. Mr. @Catsxp, do you think Catsxp 32-bit for Windows 7 will work without issues if I install vxkex?

vxkex has an official list of supported softwares, including Chromium, but vxkex doesn't officially support the Catsxp browser, and Chromium didn't work with vxkex when I tried it a few months ago. Perhaps, great Mr. @Catsxp could try forking vxkex to add official support for Catsxp?

https://github.com/i486/VxKex?tab=readme-ov-file#faq

[drimisone]

Mr @Catsxp, if you have any patches to suggest to me for my Windows 7 OS starter edition 32 bits to fix this bug, of course I am ready to install them, please if it doesn't tire you, send me Windows patch and I will try to install them, thank you