Skip to content

Updated XP/Vista Release
Compare
Choose a tag to compare
@Alex313031 Alex313031 released this 29 Apr 18:12
· 57 commits to main since this release
M122.0.6261.169
ee56188

As promised, here are SSE2, SSE3, and SSE4.1 builds of Thorium for Windows XP/Vista.

SSE2 builds are not provided for x64, since it doesn't make sense. Every x64 CPU except the very first x64 CPU (The original 1st Gen AMD Opteron from 2003) has SSE3. GCC, Clang, MSVC, Rust, and Chromium all default to SSE3 for x64 targets. Unless you are an exceptionally unique person who is part of the small subset of the population using this software, and an even smaller subset of that population that just so happens to have a server from 2003 with an AMD motherboard, this will be fine. If there is someone out there that actually has this CPU, well, if you file an issue I'll make a special release for you. I cant guarantee that it would even work though, since noone tests compilers or programs for x64 on SSE2.

SSE4.2 is not used as the performance increase is not detectable in my testing, and would exclude alot of people with Core 2 Duos from running it. Fixes #71

There have been some additions and fixes since the last release, both from myself and from Supermium's repo. These include:

  • Installer/Uninstaller .cmd files now use %PROGRAMFILES% instead of hardcoding it to C:\Program Files, for people whos Windows installation is on a drive letter other than "C:\". NOTE: For proper registry entries, you will have to edit the .reg files and use "find and replace" to change instances of C:\ to whatever drive letter yours is. I'm looking into somehow making this something the user doesn't have to manually do. If I can come up with a fix, I will send a PR to Supermium, since this is also an issue with his GUI installer. Partially fixes #75
  • Removed --disable-encryption from the portable .bats, since not everyone wants that and was breaking stuff for some people.
  • PDF rendering in --single-process mode is fixed. See Here
  • Update to .169 minor Chromium revision. See Diff
  • GDI text rendering alignment is fixed This bug caused text to be askew, either too high or too low, or too much to the left. The reason previous releases didn't have this fixed, is that win32ss fixed it in Skia, which is a third_party submodule of Chromium. Because of that, I couldn't see the commits or changes. He shared a patch with me, and I have now created a repo specifically for it, and we will probably use that as a submodule in both here and in the Supermium repo. See the pull request I made for this after we discussed it > win32ss/supermium#511 Fixes #69
  • The classic-omnibox-border flag is mostly complete, after I filed a pull request with Supermium, and then he modified the color to be the authentic grey color (instead of black). See the PR and his commit. Another cool note is that the PR also adds some of Thorium's compiler optimizations to Supermium! He will probably make further changes to the styling to make it even more authentic too. Enable chrome://flags#custom-tab-shapes, chrome://flags#classic-omnibox, chrome://flags#classic-omnibox-border, and chrome://flags#native-ui-style for an almost-authentic classic Chromium style!
  • WebGPU now works on Vista+ (Requires a GPU with DirectX 11 support).
  • Policy templates naming is correct now. Fixes #78
  • New chrome://flags flag: chrome://flags#enable-webbloat-mitigation. Enabling this will cause Thorium to refuse to load Image, Video, or <canvas> HTML Elements that are over 8,000x8,000 pixels in size. The rationale for this is that really large assets cause Chromium to allocate hundreds of megabytes of memory, sometimes 250Mb or more. This could cause out of memory issues on XP-era machines with limited RAM. NOTE: This is different than Supermium's implementation. In Supermium, this is enabled by default, and the flag is disable-webbloat-mitigation to disable it. In Thorium, it is off by default (not changing anything from the normal Chromium behaviour), but setting the flag enables it. I did this because I thought that the majority of users will be on machines with enough RAM (2GB+) to accommodate large web assets like these, and I didn't want a huge influx of GitHub issues like "why is this and that or so and so not loading?". If you have 2GB or less, you can enable this flag. Note that if it is a <canvas> element, it will actually cause the tab to crash, rather than just not loading it. IDK if there is a fix for this.
  • The setup.sh and patch.sh scripts have been separated out into ones for Win7+ and ones for XP+, due to differing patches and differing files between the two, and I didn't want the original scripts to get huge and hard to read due to all the lines of bash. NOTE: If you are building Thorium-Legacy for yourself and are using these scripts, you will need my MSVS artifacts archive with progwrp.lib and progwrp.dll integrated to get a working build. See > https://github.com/Alex313031/Snippets/releases/tag/10.1.22621.3235

NOTE: I noticed that the mini_installer on Vista would copy the files, but not make the shortcuts. Until I can resolve this, the XP and Vista builds will be the same, provided as a .zip with an installer .cmd file inside. It works fine on both OSes.

Assets 9
Loading