Firefox and Chromium running on Windows 7 by e3kskoy7wqk.

[mjd79]

The patcher included by e3kskoy7wqk, along with the diff files for each compilation (a total of 5 apply_patches.bat files), require a bit more correction than the author claims. At “REPO_PATH=E:\win7dep\chromium\src” change the path to yours, of course, but besides that, you also need to replace “!REPO_PATH!” with “%REPO_PATH%” in two places. In addition, it is required to add clang_use_chrome_plugins = false to args.gn.

Edited April 14 by mjd79

[mjd79]

Unfortunately, Chrome Sync still does not work after adding Google API keys, you still need OAuth2 keys. As a not being a Chromium developer, you can only use the default keys, which can be added with the --oauth2-client-id and --oauth2-client-secret flags. There is a simple solution for this, so that you won't have to add flag it to shortcuts or in the registry (in case you set it as default browser)

void ChromeMainDelegate::PreSandboxStartup() {
  base::CommandLine& command_line = *base::CommandLine::ForCurrentProcess();
  std::string process_type =
      command_line.GetSwitchValueASCII(switches::kProcessType);

  if (!command_line->HasSwitch("oauth2-client-id")) {
    command_line->AppendSwitchASCII("oauth2-client-id", "77185425430.apps.googleusercontent.com");
  }

  if (!command_line->HasSwitch("oauth2-client-secret")) {
    command_line->AppendSwitchASCII("oauth2-client-secret", "OTJgUOQcT7lO7GsGZq2G4IlT");
  }

With this code, replace the PreSandboxStartup() function in the chrome_main_delegate.cc file. 

Edit: in testing/variations/fieldtrial_testing_config.json there are flags about TabStripComboButton and disabling MV2 support. They override the default values declared in the corresponding files, hence you need to remove them from this json.

Edited June 2 by mjd79

[Klemper]

On 4/16/2025 at 7:30 PM, mjd79 said:

Unfortunately, Chrome Sync still does not work after adding Google API keys,

So! It's basically Ungoogled, right? No more need to apply patches @NotHereToPlayGames asked you to apply for him several posts before?

[Klemper]

@mjd79have your ever tried --memory-pressure-off            ?

[mjd79]

9 hours ago, Klemper said:

So! It's basically Ungoogled, right? No more need to apply patches @NotHereToPlayGames asked you to apply for him several posts before?

No, any pure Chromium lacks API keys and OAuth2, I remind you that I only applied e3kskoy7wqk patches to the completely original Chromium.
I have not tried this flag, I will check it under Win7, on which, of course, my rebuilts work. I will now look for the cause of the crash on 7 SP0.

BTW I tried to restore at least partially the old look, unfortunately Chromium 135 has the old code completely removed. The only thing I can do is to restore the default color scheme of the omnibox, reduce the height of the elements on it, restore the old icons. In the "3 dots" settings menu I will try to change the font to non-bold, remove the icons and reduce it to the size it was before CR23.

I was also able to restore the flag that disables Chrome Labs.

Edited April 17 by mjd79

[mjd79]

Temporary deleted

02.05.2025:

I'm revisiting this topic back, now I 99% know what I need to do to get it running on Windows 7 SP0. EventSetInformation seems to be able to be overridden by TraceSetInformation to the extent of making the browser work, hence I will have to make it so that EventSetInformation is loaded dynamically, and TraceSetInformation is used if it fails. I probably also already know how to use YY-Thunks, which will allow us to run this on Vista. 

Edited May 2 by mjd79

[Klemper]

On 4/18/2025 at 6:24 PM, mjd79 said:

I probably also already know how to use YY-Thunks, which will allow us to run this on Vista. 

Looking forward to it!

EventSetInformation is a Win8 telemetry function. Can block it completely.

https://learn.microsoft.com/en-us/windows/win32/api/evntprov/nf-evntprov-eventsetinformation

 

[mjd79]

8 hours ago, Klemper said:

Looking forward to it!

EventSetInformation is a Win8 telemetry function. Can block it completely.

https://learn.microsoft.com/en-us/windows/win32/api/evntprov/nf-evntprov-eventsetinformation

 

Unfortunately, it is not known where it sits, but any attempts to neutralize it have failed. For what it's worth, it's interesting to note that the browser works after replacing it with TraceSetInformation. STATUS_BREAKPOINT without this feature starts at version 133.0.6876.1 from e3kskoy7wqk. I did a thorough search of the entire repository downloaded locally (including all 3rd party components) in 133.0.6876.1 and 6861.0, the use of this function in the code files has not changed at all. My suspicions fall on the dxc generated by mcgen during compilation, but I have no idea what to do about it next.

I am currently working on moving patches to version 120.0.6099.338 - one of the longer supported LTS versions. And one thing puzzles me - how the author moved the original commits from 2023 removing support for Win 7 (only that reversed, for that I already have a script) for all of his versions. All the diffs/commits after merging into one file are more than 35 thousand lines of code, and there are about 100 of them. And for most of the files, lines have changed in the meantime, where some code needs to be removed or added, in the case of some, for example, 50 lines. Did he correct it manually? I find it hard to believe... more than 650 files are being changed. I tried manually correcting the hunk, but quickly gave up. I even tried to create scripts that search for given passages in the original files and, based on that, determine new lines to put in the hunki, but that too succeeded for a small number of files.

Edited May 13 by mjd79

[ED_Sln]

Firefox 139.0

https://github.com/e3kskoy7wqk/Firefox-for-windows-7/releases/tag/139.0