ED_Sln

Perhaps the issue is that FF 39 does not support TLS 1.3, so websites that use this protocol cannot be opened. FF 2 has an encryption engine update, so websites with TLS 1.3 can be opened there. To enable the browser to use system certificates, find (or create) the security.enterprise_roots.enabled parameter in about:config and set it to true.

If you mean this: https://github.com/win32ss/supermium/issues/1596 This has been fixed in 138 R6. The problem was in the instructions; if the processor did not support SSE4.2, this bug could occur.

I tested the new Chromium on Win XP. It runs faster than Supermium. But there are a few things to note. The RAM consumption bug when C++ is installed can be resolved by adding the corrected_api_sets.zip folder from Supermium. In XP x64, there is enormous virtual memory consumption, and I haven't found a solution. WebGL is completely disabled, even the software version, which means that websites that require it do not work. Manifest v2 is available but disabled by default. You need to add the parameter --disable-features=ExtensionManifestV2Unsupported,ExtensionManifestV2Disabled to the shortcut. To disable the notification that the OS is not supported, add --test-type to the shortcut. The browser requires a CPU with SSE3. Browser crash during import fixed in version 144.

There is a second link to mini_installer.exe, which is a browser.

@EliraFriesnan The developer replied: https://github.com/e3kskoy7wqk/Chromium-for-windows-7/issues/70 The browser he linked to runs even on XP, but it is x64.

I created Isuue. Now we just have to wait for the developer's response.

Was telemetry added to Vista? Write KB, I'll check what these updates are. Maybe there's something important there. Because I installed all the updates that are available.

No, there shouldn't be any problems with that processor. I thought that maybe you have a processor without SSE3 and that's why it won't start. Then you need to write to the developer. Even though he no longer supports Vista, he may be able to tell you what the problem is.

What kind of processor do you have?

Supermium 138 opened without errors.

Yes, I'm talking about them. Well, then I don't know what else might be needed. I have all the updates installed, as well as all versions of C++ and Net 4.6.2. Does version 136 give the same error?

You need to download chrome.packed-vista.7z and run it with the --no-sandbox parameter. Everything is written there. If this is done, then some updates may be missing, especially the Platform Update.

Yes, and versions ESR 128.14.1 and 140.5.0 have already been released.

Does anyone know what happened? The repository on GitHub is archived, and the website is down.

It also works, but after launching it sets the timer to 2 ms, after launching the browser it switches to 1 ms, and after closing the program it remains at 1 ms.

I'm not sure if that's it. It mentions an ACPI timer, but this thread is about HPET, which doesn't depend on the processor frequency and is measured in milliseconds rather than megahertz.

No, you cannot set a different value. As far as I know, these values are hard-coded into the OS kernel, and you cannot set a value lower than 1 ms.

If it starts using more memory than it has and the OS has to constantly dump the excess into a swap file, then yes, this can cause it to run unstable. Increasing the available memory should fix this, because each tab will be able to use 2 GB of RAM.

This manifests itself in the fact that the time on the computer starts to rush. This occurs when working with relatively new versions of Chrome-based browsers, such as 360, Chromium 87, and Supermium. They constantly switch the timer mode from 1 to 16 ms, which causes the time to run ahead. This program switches the timer to continuous operation in 1 ms mode, so the time is correct.

I use this: https://yadi.sk/d/KpTGDPITsNWn7w the program itself is in the Timer_Fix folder. Brief description: Timer_Fix program with source code written in Visual Studio 6.0. The program has no interface; after launch, it will set the system timer to a period of 1 ms and leave it unchanged. The program will remain in the processes until the OS is rebooted. For convenience, it is best to place this program in “Startup” and completely forget about the problem of time passing. No issues have been found with using this method.

The SysWOW64 folder contains 32-bit files. Including the ntoskrnl.exe file.

If it were possible to fix it in the registry, they would have done so instead of creating a program. No, in XP, you cannot set a timer without third-party programs.

Or install fix128. It will install the kernel from Server 2008 R2, and the OS will see and use all available memory, i.e. 16 GB. However, not all drivers are compatible with the current PAE mode, so you need to check.

https://web.archive.org/web/20160609092058/http://download.microsoft.com/download/a/a/c/aac39226-8825-44ce-90e3-bf8203e74006/dotnetfx.exe This is SP1 only, without Framework 1.1.

I've collected various USB3 drivers that I found on different forums. They work differently on different motherboards and with different ACPI, so before installing it is better to make a backup of the OS, because it happens that the OS stops booting. The first one to try is AMD+Intel, it does not add any additional layers to the system, for example ntoskrn8.sys. If it doesn't work, then try the others one by one. https://www.upload.ee/files/18148104/USB3.7z.html