Dave-H

@LoneCrusader OK, I substituted the USBPORT.SYS file (I used the one in Dibya's patch) and everything seems to be fine with the USB connection now, working normally. Thanks for the tip!

Thanks. I will try to find the version of USBPORT.SYS I need, and report back! Is there any reason to think that daniel_k's patch is any more likely to solve the browser problem than the one I'm using?

Of course, I have now found an issue! When I connected my mobile phone to the system by USB, and tried to transfer some files to it, it didn't work. It went through the motions, but wouldn't actually copy any files. Eventually I had to kill the transfer. I tried again with the normal memory configuration, and it worked fine. So it looks as if the USB problems much mentioned here are happening with the patch I'm using.

Thanks. That is, of course, the $64,000 question. Is that patch actually providing 16GB of RAM on my system, or is it just appearing to, with some or all of the extra RAM not actually accessible? All of my system analysers (and I have lots of them!) say that I now have 16GB of RAM, but how can I test that this is actually properly usable?

I've been having problems with my installation of Supermium on 32-bit XP, where tabs crash with an 'out of memory' error. This happens particularly on Facebook. You can see the RAM being eaten on the Task Manager as I scroll the Facebook newsfeed, until eventually it falls over. I read up here about ways to get 32 bit XP to see more RAM, and eventually I found this patch. It seemed very simple to implement (and undo!) compared with some of the other possible solutions being discussed here, so I thought I would give it a try. I wasn't very confident, expecting a BSOD at worst, and other issues even if that didn't happen. To my amazement, at least on my system, it seems to have worked perfectly! The system now reports 16GB of RAM available, which is great. Unfortunately, it hasn't fixed the browser crashing problem. If I scroll Facebook now, Task Manager still shows the RAM being eaten, but when there's still apparently loads still left, the browser tab still crashes with the same 'out of memory' error. I suspect that this isn't a problem peculiar to Supermium, it would probably happen with any recent Chromium-based browser. So, anyone any idea why this is still happening? It is simply because it's a 32-bit browser, so perhaps can't access more than a limited amount of RAM, regardless of how much is available? If so, is this an insurmountable problem? Any suggestions gratefully received! Cheers, Dave.

I get a warning from the Malwarebytes Browser Guard extension on that site, but it works fine if I override it. Supermium 132.0.6834.224 on XP.

Is nothing sacred?!

New version now released, Supermium 132.0.6834.224 R4. This release of Supermium includes various changes and improvements, including: (#1412) - Option to disable autoplay introduced in chrome://flags, #disable-autoplay (#1403) - --force-dark-mode option introduced to deal with possible issues with white flashes in dark mode. However, some flashes may still appear due to caching of previous page views (#1445) - chrome://version uses Supermium branding (#1441, #1433, #1398, #1400) - Small changes to default metrics, particularly affecting v109 and CR23 tab styles (#1438) - New tab button fixed in place (and the tab close button should no longer overlap favicons) (#1411) - Download link now appears by default in chrome://downloads, as opposed to referrer link (issue unassigned) - #disable-gpu-driver-bug-workaroundsnow available in chrome://flags Some small mitigations have also been introduced for crashes in portable configurations on Windows 7.

Thanks!

Thanks, yes, I did access it through the Wayback Machine. This is what I'm seeing if I try to access it normally - As you can see, it's not a browser block or security software block, it's a block by the ISP at source, which I've very rarely seen!

OK, but I can't override the block. As I said, those who can access it, proceed with caution!

Be aware that hardwarefetish.com is blocked by my ISP as a malware/phishing site. Proceed with great caution if you visit it!

As I feared, the most recent version of DiskGenius, 6.0.0.1631, no longer works on XP, even the portable version. "The procedure entry point inet_ntop could not be located in the dynamic link library WS2_32.dll" The last working version (portable only, the installer does not work on XP) is 5.6.1.1580.

The separate installer for Windows 10 and 11 was introduced to apparently mitigate some hard to pin down issues which only appeared on those operating systems. https://github.com/win32ss/supermium/releases/tag/win10_11-test-v1 What the differences actually are, I don't know, but the separate installer has remained on all subsequent releases. I've never used it on Windows 10, because I've had no problems with the standard version.

@Karla Sleutel Did you use the special Windows 10/11 version of the Supermium installer? If so, try using the standard version. It works perfectly for me on Windows 10, so will probably be OK on 11 too. Whatever Windows 11 Security is flagging may not actually be there in that version, which is why I'm not seeing a problem and there haven't been loads of reports on GitHub about it, although Malwarebytes is my main security program anyway. I still think it's a false positive anyway.

Everything seems to be fine here on Windows 10. It's almost certainly a false positive, but until win32ss comments on the report, we don't know.

Thanks. This is off-topic here of course, but the driver I'm using for the M4000 on XP is version 368.91. Are any of the ones you've referred to later than that?

I can use either GPU with Windows XP, I have drivers for both. There are no Windows 10 drivers for the X600, and of course no Windows 98 drivers for the M4000! I tend to keep using the X600 on XP, as it causes boot complications if I set the M4000 to be the primary card in the BIOS. It works fine, and as I said, I've had no video performance problems with it.

My XP graphics card is pretty ancient now, an ATI X600. I keep it for compatibility with Windows 98! I've been using the #ignore-gpu-blocklist flag for a long time on XP already.

Early tests on IG with the new 32-bit version on XP look promising, but as far as I know the issue I reported has never been flagged on GitHub anyway! I was thinking of doing so. I will try later with the 64-bit version on Windows 10. Twitch and TikTok I don't use, I'm afraid.

A new update of Supermium 132.0.6834.222 R3 has been released. Changelog - This exceptional release of Supermium includes various enhancements over Supermium 132 R3, including: (#1372) - some tweaks to the look-and-feel of v109 Tabs. Tab-specific compact UI options are separated from #compact-ui, now in #compact-tab-ui. (#1370) - a new feature named #open-bookmark-option allows users to open bookmarks in new tabs, either in the foreground or background. This replaces the equivalent Chrome++ functionality that is currently unstable with Supermium. (#1382) - drag-and-drop fully restored on NT 5.x. (#1368) - CR23: tab separator duplication disabled by default, other metrics modified including tab gaps (#1367) - Widevine patch updated for version 4.10.2891.0 Glad that drag and drop has been restored to the XP version, you couldn't even re-order the extension icons on the previous version! The feature to always open bookmarks in a new tab is one I've lobbied for for ages, so I'm really pleased with that too. It means that I don't have to use Chrome++ on Windows 10 any more, and I now have that facility on XP (Chrome++ doesn't work on XP). If it all works as it should, I'm really delighted with this!

The query on GitHub has been updated. It seems the problem went away with a new clean profile.

Does anyone else use Supermium with Instagram? The reason I ask is because recent versions for me seem to have trouble with the overlays which should come up if you click on the link in a post to view the comments. What often happens for me is that the screen darkens down, but the overlay does not appear. The only way I can view the whole list of comments is to open the link in a new tab, which I shouldn't have to do. The equivalent overlay on Facebook works fine. I'm pretty sure this isn't being cause by any of my extensions. I did suspect uBlock, but I've switched it off on IG and the problem is still happening.

Strange, I have no problems with YouTube at all, even on 32-bit XP.

The British Gas site still has the same issues. I haven't tried the other two. At least the 'experimental features' are disabled by default now!