Release v128.0.2 for Vista+

So the 32 bit build doesn't want to build. I could probably clobber and it would probably be fine, I'm just too tired to wait the hour that would take, so 64 bit only release for now.

Note: If you are upgrading from 127 or earlier, you will want to uninstall any old versions of r3dfox before upgrading to 128+. This will not touch your browser profile or settings. If you do end up with a new profile or no settings, follow these steps. Go to about:profiles, select the previous profile (Usually default-default) as default, and restart the browser.

The portable builds are fully portable, the profile directory is inside the browser folder. It does not touch appdata at all.

Notable bugs:
The 32 bit build (if one existed) is built with --disable-sandbox. With the sandbox enabled under Vista, the browser fails to open multiple processes which breaks the browser. The 64 bit build is fine. Considering Mypal68 globally disables the sandbox, I don't think it's that bad. If this really is a big issue then please pr a fix.

Changes on top of the previous 128.0 build:
Windows Vista support!
dom.private-attribution.submission.enabled set to false (less telemetry)
Aero fog should now work on 10 with Aero properly.

Haven't tested on XP (OCAPI) nor have I extensively stability tested. If you are using 7 RTM, you need to install the VC++ 2019/2022 redistributable, and copy the appropriate files from the r3dfox-7-RTM-fix.7z to the r3dfox installation directory, and it should work.

Please let me know what bugs or issues you encounter with it.

Release v115.13.0esr for Vista+

Edit: For portable mode make a file named pmundprt.mod in r3dfox_esr\browser
The contents of this file does not matter, only that it exists. This file was accidentally not included in the portable release.

The portable builds are fully portable, the profile directory is inside the browser folder. It does not touch appdata at all.

Notable bugs:
The 32 bit build is built with --disable-sandbox. With the sandbox enabled under Vista, the browser fails to open multiple processes which breaks the browser. The 64 bit build is fine. Considering Mypal68 globally disables the sandbox, I don't think it's that bad. If this really is a big issue then please pr a fix.
Most of the r3dfox customizations options do nothing and I have no idea why. So it's hardcoded to be the default. I'm not sure if I can ever fix this under 115 ESR. I figure it's not really worth bothering as most people would want this for userChrome.css themes anyways.

Changes on top of the previous 115.13.0esr build:
32 bit build passes PGO, and yes it was Rust9x. (I use eRust now)
Discord, Snapchat, and Whatsapp should work stock now.
Site specific useragent overrides are back after being removed in 71. general.useragent.override.(site) works in r3dfox.
More privacy respecting default preferences.
I no longer need to hex edit the output, and yes it was Rust9x.
The code is now release 115.13.0 level.
DisplayConfigWindows was added back. (This mitigated some issue on 10 or something idk)

Haven't tested on XP (OCAPI) nor have I extensively stability tested.

Please let me know what bugs or issues you encounter with it.

Release v128.0-2

Note: If you are upgrading from 127 or earlier, you will want to uninstall any old versions of r3dfox before upgrading to 128+. This will not touch your browser profile or settings. If you do end up with a new profile or no settings, follow these steps. Go to about:profiles, select the previous profile (Usually default-default) as default, and restart the browser.

The portable builds are fully portable, the profile directory is inside the browser folder. It does not touch appdata at all.

Changes on top of the previous 128.0 build:
New custom theme with red color scheme and rounded small trapezoid style tabs based off of modified Wavefox. (Can be disabled in settings if you prefer stock)
Discord, Snapchat, and Whatsapp should work stock now.
Site specific useragent overrides are back after being removed in 71. general.useragent.override.(site) works in r3dfox.
Fixed bookmarks folder icon being the wrong icon.
More privacy respecting default preferences.

Haven't tested on XP/Vista (extended kernel) nor have I stability tested. If you are using 7 RTM, you need to install the VC++ 2019/2022 redistributable, and copy the appropriate files from the r3dfox-7-RTM-fix.7z to the r3dfox installation directory, and it should work.

Please let me know what bugs or issues you encounter with it.

Release v128.0-hotfix

So compiling the Rust compiler for AVX2 also makes the output require AVX2, who knew.

Previous description from v128.0:

Note: You will want to uninstall any old versions of r3dfox before upgrading to 128. This will not touch your browser profile or settings. If you do end up with a new profile or no settings, follow these steps. Go to about:profiles, select the previous profile (Usually default-default) as default, and restart the browser.

The portable builds are fully portable, the profile directory is inside the browser folder. It does not touch appdata at all.

Changes on top of the previous b128.0 build:
Browser is now compiled with custom built eRust 1.77.2 instead of 2024-02-04-nightly.
Mozilla made a few changes in the period between b128.0 and now, they don't seem of note.

Haven't tested on XP/Vista (extended kernel) nor have I stability tested. If you are using 7 RTM, you need to install the VC++ 2019/2022 redistributable, and copy the appropriate files from the r3dfox-7-RTM-fix.7z to the r3dfox installation directory, and it should work.

Please let me know what bugs or issues you encounter with it.

Beta b128.0

Note: You will want to uninstall any old versions of r3dfox before upgrading to 128. This will not touch your browser profile or settings. If you do end up with a new profile or no settings, follow these steps. Go to about:profiles, select the previous profile (Usually default-default) as default, and restart the browser.

This is only classified as a beta since Firefox 128 hasn't officially released yet. It's pretty good from what I can tell.

The portable builds are fully portable, the profile directory is inside the browser folder. It does not touch appdata at all.

Changes on top of the previous 127.0.2 build:
This is now built with a 0A00 target and regular Rust. I found a workaround for the issue I was having that stopped it from running on lesser updated versions of 7 and RTM. This simplifies the code significantly and lets me use the newest Cairo instead of needing to downgrade it like I had to do for 127.
Option to enable white caption text. (useful for Windows 10 without Aero)
Download folder and retry icons have been replaced with those from Firefox 68.

Haven't tested on XP/Vista (extended kernel) nor have I stability tested. If you are using 7 RTM, you need to install the VC++ 2019/2022 redistributable, and copy the appropriate files from the r3dfox-7-RTM-fix.7z to the r3dfox installation directory, and it should work.

Please let me know what bugs or issues you encounter with it.

Beta v115.13.0esr for Vista

People have asked for a 115 ESR build, and I figured to offer something over stock I would make it also support Vista.

Currently this is a beta for a few reasons:
1: The 32 bit build is built with --disable-sandbox. With the sandbox enabled it fails to open multiple processes which breaks the browser.
2: The 32 bit build doesn't start PGO. This could be Rust9x, since PGO on the 32 bit build has been funny ever since I started using it but idk.
3: Most of the r3dfox customizations options do nothing and I have no idea why. So it's hardcoded to be the default for now.
4: I have to hex edit out two calls for TryAcquireSRWLock functions, and I have no idea where they get called from to fix in code.
5: I forked this while the code is in a non-release state, 115.13.0 isn't released yet. I could probably revert back to 115.12.0, but I just wasn't thinking about it until typing this right now.

Otherwise, it seems to mostly work, no idea how well or how stable it is. Needs testing.

The portable builds are fully portable, the profile directory is inside the browser folder. It does not touch appdata at all.

Haven't tested on XP (OCAPI) nor have I extensively stability tested.

Please let me know what bugs or issues you encounter with it.

Release v127.0.2

This is a 7+ only release. For stock Vista, please use the previous v126.0.2v release. They will be merged into a single release soon.

I wanted to bring more in the next release, fix some bugs, maybe make a r3dfox theme, etc. However I have been busy working on other projects. I only built this since for once Mozilla actually listened to user feedback and brought back the ability to disable private window separation. Since previous versions of r3dfox disabled this, I set it to be disabled again.

The portable builds are fully portable, the profile directory is inside the browser folder. It does not touch appdata at all.

Changes on top of the previous 127.0.1 build:
Private windows are no longer separated from the main browser windows on the taskbar.
Finally replaced install icon with generic logo.

Haven't tested on XP/Vista (extended kernel) nor have I stability tested. If you are using 7 RTM, you need to install the VC++ 2019/2022 redistributable, and copy the appropriate files from the r3dfox-7-RTM-fix.7z to the r3dfox installation directory, and it should work.

Please let me know what bugs or issues you encounter with it.

Release v127.0.1

This is a 7+ only release. For stock Vista, please use the previous v126.0.2v release. They will be merged into a single release soon.

I wanted to bring more in the next release, fix some bugs, maybe make a r3dfox theme, etc. However I have been busy working on other projects. All this brings are the changes from 127.0.1 and reenabling Gecko Profiler.

Also only the x64 release for now. I am building the x86 release, but I will be delayed in releasing it.

The portable builds are fully portable, the profile directory is inside the browser folder. It does not touch appdata at all.

Changes on top of the previous 127.0 build:
Reenabling Gecko Profiler.

Haven't tested on XP/Vista (extended kernel) nor have I stability tested. If you are using 7 RTM, you need to install the VC++ 2019/2022 redistributable, and copy the appropriate files from the r3dfox-7-RTM-fix.7z to the r3dfox installation directory, and it should work.

Please let me know what bugs or issues you encounter with it.

Release v127.0

This is a 7+ only release. For use on stock Vista, please use the previous v126.0.2v release. They will be merged into a single release soon.

Previous release was stable, and 127.0 is officially out, so I guess that makes this a full release.

The portable builds are fully portable, the profile directory is inside the browser folder. It does not touch appdata at all.

Changes on top of the previous 127.0rc2 build:
GUI option to disable e10s.

Haven't tested on XP/Vista (extended kernel) nor have I stability tested. If you are using 7 RTM, you need to install the VC++ 2019/2022 redistributable, and copy the appropriate files from the r3dfox-7-RTM-fix.7z to the r3dfox installation directory, and it should work.

Please let me know what bugs or issues you encounter with it.

Beta v126.0.2v for Windows Vista

Beta release for Windows Vista without extended kernel. Requires Platform Update, maybe supplement, SHA-2 update, and Visual C++ redistributables. It can work without the SHA-2 update, but it replaces some older update that makes it work and idk how to find it. If it still doesn't work, maybe it needs KB2533623 idk.

It seems to mostly work, no idea how well or how stable it is. Needs testing.

Currently I have to hex edit xul.dll to remove a delay loaded dependency on TryAcquireSRWLockExclusive and TryAcquireSRWLockShared. I have no idea where this comes from, as I have removed all mentions of them from the source code. This is already done on the release here. Please help fix this. (I might just need to build with a target of 600 which will be a pain.)

x86 release is very broken even on 7+, so there is none yet. It's also 126 because I just want to get this out so I can rest, I'm tired.

Changes outside of Vista compatibility:
GUI option to disable e10s.

Haven't tested on XP (extended kernel) nor have I extensively stability tested.

Please let me know what bugs or issues you encounter with it.