Dave-H

On Windows 10 I think the profile should be at C:\Users\<username>\AppData\Roaming\Supermium\User Data.

If by 'standalone' you mean a portable version, yes there is. If you are going to continue using Supermium, please continue this in the Supermium thread.

That is the most recent version according to the repository on GitHub. It was released back in February though, so it's now nine months old. I would recommend switching to Supermium, which is now on version 138.

The 'dog account' (Jaguarek62) posted on October 29th in another thread on a completely different subject, so it is still active. No forum rules have been explicitly broken here yet, and I trust people will be aware and careful about this.

28.08.2025 it says for me. Thanks!

Supermium's password manager is working fine for me, and always has done. It is backed up to the cloud by Google Sync, so it's synchronised with my other Supermium installations on other machines, (I know, I know, but it works for me, and I don't use it for any really sensitive passwords like online banking!) I back up my whole machine locally regularly as well, of course.

Just copy 360Loader.exe and 360Loader.ini into the Thorium program folder (they can actually go anywhere, but I find that neatest and saves any complications with paths). IIRC (I don't have it installed any more) Thorium uses Thorium.exe as its executable, not Chrome.exe, so you will have to change the line in the ini file to be AppName=Thorium. That's actually what I've always done too, it makes it a lot easier to change the command line switches. Your shortcut will now have to point to 360Loader.exe of course.

That's not how you do it. Right-click on the Thorium shortcut, and select 'properties' from the menu. In the properties box which pops up, you need to add the switch to the command line in the 'target' box. Add a space after what's there, and then add (copy and paste from Mathwiz's post will be easiest) the --user-agent switch.

A general personal opinion on the actions of an anonymous large group of people many years ago is fine as far as I'm concerned, as long as it's not based on something like racism of course. That is my final word on this, and it should be yours too. Thank you.

Well, I really don't know, but presumably win32ss does! Surely the current ESR version has to be patched until it's superseded, if it's vulnerable, or there's no point in having it. That is 132 as far as I'm aware.

Thanks. IIRC does the system indicate that PAE is enabled if Data Execution Prevention is enabled, or am I mis-remembering? Of course that isn't actually doing anything with the RAM availability, as you say.

We may be talking about different things here regarding PAE. Standard PAE is enabled on my machine, and always has been. Until recently though, I had not experimented with 'PAE patches' to extend the amount of RAM available on my 32-bit system. I do now have one of those available as an option on boot, and it is possible that my access to the 3TB disk will fail if I use that, if I go over 2TB on the disk. I haven't actually tried that, but certainly with the standard PAE configuration, I went over 2TB on my tests without any apparent problems.

I'm pretty sure that when I did my tests, I went well over 2TB on my 3TB disk, with PAE enabled as it always has been, and there were no issues.

I don't see why it would be, they are different exploits. I'm sure win32ss knows what needs patching and what doesn't.

New security patched release. Supermium 132.0.6834.226 R5.01 "The only substantial change in this release is a patch for vulnerabilities CVE-2025-8010 (CVE-2025-8011 is not applicable to M132) and CVE-2025-6558."