Dave-H

If you had a local copy of Office 2024 installed on the machine, its files should still be there, and it should still be in the 'Programs and features' list. 🤔

This thread is now locked until the next Supermium version is released, which might give some answers to resolve this pointless and increasingly personal argument, where neither side can be proved. Thank you for your patience in this matter.

With respect, that's not what @NotHereToPlayGames was saying. What he was saying was that if exactly the same modifications were made to other Chromium browsers as have been made to Supermium, for whatever reasons, then the Twitch login would almost certainly break there too. I'm sure that win32ss is investigating the reason why this is happening.

FWIW, I've just tried it, and the British Gas site breaks in exactly the same way on the latest and greatest version of Microsoft Edge if the experimental features are enabled, so this at least is not a problem peculiar to Supermium!

If that really is the case, then they are completely useless.

So how do you explain the result at https://chromiumchecker.com/? That site would be pretty much discredited if it couldn't detect an old Chromium version masquerading as a newer one!

Surely he had to 'fiddle' with the Chromium code or the browser wouldn't run on XP?!

Quite. Just because Twitch works in a Chromium 110 browser but not in Supermium 126 or 132 doesn't mean that the latter browsers are using even older Chromium versions, despite their names. There could surely be any number of reasons why Twitch doesn't work in Supermium which are nothing whatsoever to do with the underlying Chromium version. I'm sure that the reason is being investigated. The fact that it apparently comes good when the experimental features are enabled must surely be a very big clue as to the cause!

It will be interesting to see if this is addressed in the next Supermium release.

Ah right, I'm still using R6.

I'm well aware that deception is possible, but Supermium 126 appears legit when tested here. It's spoofing version 130 in its default User Agent string, but we all knew that. I don't know about version 132, as I haven't installed it yet. I'm waiting for at least one more update before I do!

It was a silly thing to do in the first place. AFAIK it was because a few users reported that they were having problems with Twitch. These problems went away if the experimental features were enabled. What the developer should probably have done is simply to tell them to switch them on. What he actually did was change the default settings so they were on by default. This was fine until people found problems with other sites, like the British Gas one. Fortunately this has been corrected, but presumably the problems with Twitch are still there with the default settings now, and that does need to be addressed.

Why on earth would the Supermium developer release a version of the browser purporting to be based on Chromium 132, but actually based on an earlier version? That would make no sense at all if it can easily be checked, and he must be well aware that it can be. Surely it's much more likely that the core is indeed Chromium 132 but one or more of the tweaks which have been made to it, especially for compatibility with earlier operating systems, have resulted in the mutually exclusive issues with Twitch and the British Gas site, which now cannot both work properly at the same time.

I abandoned Thorium when it became very clear that there weren't going to be any more versions in the near future, if ever, which would run on XP. A version based on Chromium 122 doesn't really cut it any more. Why that decision seems to have been made I have no idea, but thank goodness that we still have Supermium!

@hidao OK, but here it is anyway if you want it. 360Loader.zip

360Loader.exe was included in the distributions of the 360Chrome browser here. If you have any of the associated zip files, it should be in there. If you haven't got it, I can give you a copy.

@hidao Assuming you actually have a copy of 360Loader.exe, can you try using that to launch Supermium with the INI file you had before? I would be interested to know if it does in fact work. Remember, you will have to change the name of the INI file to match the EXE file's name, e.g. 360Loader.exe will need an INI file called 360Loader.ini.

Just going back to Browsermetrics for a moment, someone here has reported the same issue with Edge, so it looks like it's something that can probably happen with all Chromium-based browsers. A new profile was recommended there too, and apparently fixed it.

Hmmm. Can I just check something? You're not trying to use 360Chrome.exe as the launcher, I hope! That's the executable for the 360Chrome browser. The exe file for the launcher is 360Loader.exe.

Oh dear. I'm sure that @NotHereToPlayGames will be able to say what's wrong. My chrome.exe is in the Program Files\Supermium folder, I don't have the App subfolder. That's just the way I set it up.

Yes thanks, I wasn't aware of that switch when I did it manually. If using the switch works on XP, as you say, I'm just a bit surprised that the normal option in the settings wouldn't work, or at least could have been made to work.

No I'm not. I spent a very long time manually editing the registry to make Supermium my default browser on XP, as the usual mechanism doesn't work on XP. I don't want the registry to be possibly messed up again.

It should be - AppName=Chrome PathToExe=.\App\$AppName$.exe I think that's right. I'm sure that @NotHereToPlayGames will confirm or otherwise! It can't find chrome.exe at the moment.

That's exactly what I did! I had equivalents for Thorium as well, but I've now removed that.

It really does work, I can assure you! Just put the loader exe file in the same folder as chrome.exe, along with its associated INI file where the settings are stored. This is mine for reference. [Setup] AppName=Chrome [FileToRun] PathToExe=.\$AppName$.exe Parameters=--user-data-dir="D:\Program Files\Supermium\User Data" --no-proxy-server /high-dpi-support=1 /force-device-scale-factor=1 --use-angle=d3d9 --ignore-gpu-blocklist [Environment] Profile=.\User Data