Dave-H

Yes indeed! He's done the same edit that I did to the file and bundled a copy of pwrp_k32.dll in the zip file with it.

Thanks, everyone. Yes, that modification makes the file work fine on XP.

The error I'm actually getting on XP is - "Entry Point Not Found : The procedure entry point InitializeCriticalSectionEx could not be located in the dynamic link library KERNEL32.dll."

Thanks, that's interesting! That's good. As you said earlier, presumably I can just make any changes I need on the 64-bit Windows 10 version, and then copy the generated file to the 32-bit Windows XP version.

Of course I've now found that it doesn't work on Windows XP!

Going back to a previous discussion, people might be interested to know that the latest release of Supermium includes an editor for the UA string and Client Hints, which may be useful. It's a standalone program, not built into the browser. https://github.com/win32ss/supermium/releases/download/v144-4/supermium_uao.zip

Thanks. I will have a look and see if I can see what the problem is. I'm assuming that at least the syntax is correct, but as I say, I'm not an expert in this!

I've now had a chance to try this script, having been away from home for the last few days, and it loads in my OrangeMonkey extension fine but doesn't actually seem to do anything on Facebook other than add a 'previous' and 'next' button at the bottom right of the page. The buttons don't seem to do anything, and there is no apparent change in the behaviour of the page. I can't see anything obviously wrong with the code, but I know nothing about writing scripts!

Thanks! I can't try that out at the moment as I'm away from home for a few days, but I will certainly try it out on my desktop machine when I get back home!

I've never had any issues with YouTube either. I don't use Discord. Facebook and Instagram are the main problem, the tab always crashes after doing any prolonged scrolling on either of them. If I look at the Windows Task Manager, I can see the available RAM disappearing before my eyes! 😯

My main bugbear with Supermium on XP is that tabs often fall over with out-of-memory errors on sites like Instagram and Facebook. I gather this is because 32-bit processes can each only access a maximum of 4GB of RAM (sometimes even less depending on the system configuration). My understanding is that nothing can be done to work around this, even patching XP to access all of my 16GB of RAM makes no difference because the RAM limit for each process still exists. It means I can potentially open a lot more tabs, but each tab will still crash if it goes over the RAM usage limit. That's the main reason I would never use a 32-bit browser from choice.

Now that would be a bit of a giveaway, as there has never been a 32-bit version of Windows 11 of course! I suppose you could legitimately be running a 32-bit browser on Windows 11, but why would anyone do that?

Well I guess the '32' gives away that it isn't official Google Chrome in that case but a fork which still provides 32-bit versions. I think the old-school UA string has always said 'x64' in recent times, 360Chrome was/is the same. The discrepancy doesn't seem to be causing any problems with Cloudflare-protected sites as yet, at least none of the ones which I use. It's not pretending to be a higher version of Chromium now at least, which it used to with earlier versions. Does Cloudflare even look at the old legacy UA string now?

What do you reckon? The only spoofing I can obviously see is that Supermium 144 is saying I'm on Windows 10 when I'm actually on XP. Not sure what 'platform version 19.0.0' means.

I've never had captchas on any of the banking sites I use either. They mainly rely on sending a login code, either by SMS text to your mobile or by e-mail.