search

win32ss / supermium

Chromium fork for Windows XP/2003 and up
https://win32subsystem.live/supermium/
BSD 3-Clause "New" or "Revised" License
2.46k stars 85 forks source link

Windows XP startup errors (CTRL+C) #900

Closed eikoni closed 2 months ago

eikoni commented 2 months ago

On Windows XP SP3 (real machine) CTRL+C errors (total 3) when launching chrome.exe version 126. No effect with VC_redist.x86 reinstall.

Image1

Chrome 124 version works wells with Win7-to-XP API Adapter patch (progwrp.dll) version : 1.2.0.5064. https://github.com/IDA-RE-things

Any ideas ? Thanks

Half-Modern commented 2 months ago

System specs (CPU, RAM etc.)?

eikoni commented 2 months ago

Memory 3.5 GB CPU 1.90 GHZ Image1

IDA-RE-things commented 2 months ago

@eikoni , My actual alternate DLL's supports latest v126. So you can try it, and may be problems will go away.

eikoni commented 2 months ago

Sorry, but where i can find the working progwrp.dll ? Thanks

IDA-RE-things commented 2 months ago

If you are about my alternative, its in Releases section as usual. And all questions about it please there in issues. https://github.com/IDA-RE-things/Chrome-xp-api-adapter/releases

eikoni commented 2 months ago

Issue solved. Thanks for the great work.

Half-Modern commented 2 months ago

But shouldn't it be fixed in the main browser without 3rd party extension? 🤔

IDA-RE-things commented 2 months ago

I think not. 1. What do you mean ander "main browser" ? If the problem inside main browser (Chrome.dll, LibGLES etc), -- componets w/source code, developed by teams around the world, then yes, --- it should be fixed there.

But I'm sorry, you trying to "pit us against each other" with the repository owner again. If everything will be fixed in the "main browser" (I think you mean here the browser distributive w/all of the dll's around), then why would there be a need for a "third-party extension" as you called it? (In fact set of alternate proprietary DLL's w/o source code, same, as it is in main distrib). You are thus saying that my work should die and not be used by anyone?. Are you want this ? Why another developer should not do anythis to improve browser (ending result) ? And then have at least a number of grateful users for his work. So , I should bug-reprots for browser (its fine), but not develop anything for it for another people (its bad)? Or what ?

What do you mean about this?

In normal Open-Source projects, this situation is unlikely. Because any person can join the project, make their contribution, it will be indicated in co-authors or contributors, and the contribution will be made to the source code. What should we do here? There is no source code of that components, and the owner of the repo wants to be alone-genius. He does not need co -authors, contributors or team for his private components.

Therefore, we now have what we have.

Half-Modern commented 2 months ago

If there's a bug/error in the original version (Supermium), then it should be fixed in the original version as well. That's why he opened that issue tracker, but he shouldn't have closed it because using a THIRD-PARTY library fixed his problem, because the issue STILL exists in Supermium itself. Third party modifications were made to provide functionality and additional stuff won't be provided by the original version. Your progwrp replacement shouldn't be meant to fix errors, because those should be fixed in the ORIGINAL browser. If it's meant to provide new functionality and performance improvements, then it has a purpose (but fixing any errors must be done in Supermium itself, since it's in ACTIVE development).