Dave-H

I did try using the files from Server 2003 before, but the result was exactly the same. I actually think that the GPT driver is working fine, the disk is being recognized as a GPT disk correctly. I'm seeing this in the System Event Log when I mount the 3TB disk. The fact that it looks correct in Device Manager would seem to bear this out, too. I think the problem is not that the GPT disk isn't being recognized, it's the fact that it's over 2TB which is the issue. Windows XP is just not recognizing it as being a valid disk because of its size. I have a spare 250GB disk, so I will try formatting that as a GPT disk, and see if that works correctly with XP using the Paragon GPT driver. If it does, I think that will prove that it's the disk size which is the problem, not its format.

Thanks for replying in the right thread @VistaLover! I've just tried this again, this time downloading the CRX file using the Get CRX extension as you did. I used the release version rather than the beta though. Still the same result, everything seems to install OK, the scripts all imported OK and show no errors, but the Violentmonkey icon remains stubbornly grey, and the scripts don't actually do anything. As you can see, I keep getting 'Violentmonkey was restarted. Please reload the tab to run userscripts'. Reloading the tab does not change this. I'm using 360Chrome 13.5.2036.0. Orangemonkey 1.09 still works, but I get constant nags popping up saying it's about to be unsupported, which it is of course! The new version, Orangemonkey Pro, does not work with Chromium 86 of course!

@Cixert Sorry for the delay, but I have now successfully uninstalled my original Paragon GPT loader driver (which came with HFS+ v10.5.0.95) and replaced it with the version which came with Partition Manager 15 Pro v10.1.25.779. I hope this is your recommended version. The version of GPT_Loader.sys is now 8.0.1.0. Unfortunately, it has made no difference to the original problem. The 3TB disk, in its eSATA connected enclosure, still appears correctly in Device Manager, but does not appear in Disk Management. Populating the volumes in Device Manager says that the disk format is unknown/unreadable. I have confirmed this time that things are exactly the same if the enclosure it connected via USB instead of eSATA, which I think has exonerated the eSATA interface card or its driver from being the problem. I didn't think that it was, because everything works fine in Windows 10 of course, but good to have it confirmed. So, I'm still stuck.

Off-topic, but I can't get violentmonkey to work in 360Chrome 13.5. It apparently installs fine, but does not actually work. The installed scripts do nothing.

@hivan42 Please do not bump threads with empty posts. You are much more likely to get a response if you add more content.

OK. I've found a copy of v10.1.25.779. My next worry is, how do I replace the version I already have installed with the older one? I suspect that the installer won't let me do it, and I'm very worried that if I uninstall the present version I then won't be able to boot, I'll just get an 'inaccessible boot device' BSOD. How can I avoid that?

Interesting. I can't remember all the versions I tried in my tests, but from what you say, I should at least try to find a copy of v10.1.25.779. I can't imagine that all the problems I had would go away with that version, but you never know!

When I did my tests, I was using version 10.5.0.95 of the Paragon driver, which I still have installed on XP. I can't comment on FAT32 partitions, as my 3TB disk was formatted with a single NTFS partition. It appeared to work in XP, but the problem was that when I switched between XP and 10 on my multi-boot machine, the drive showed horrendous errors in chkdsk. This might of course be OK in a single boot system, but for me, it was unusable. A further complication for me was that the 3TB disk is in an enclosure connected via an add-in eSATA card, not connected directly to the motherboard. However I never got it working correctly when I did try connecting it directly either.

Thanks!

@Robotron2001 Threads merged. If you don't get the response you want from a question, please do not just start another thread on the same topic. Try adding more information, this will bump the thread and hopefully attract the attention of someone who can help you.

Yes, I was sad when Malwarebytes finally dropped pattern updates for 3.5.1, although to be fair they did keep them going for a number of years longer than I thought they would. I was a bit annoyed though, like everyone else, when they suddenly stopped them with no notice at all! I'm still using it, but obviously as time goes on, using it with an out of date pattern will become more and more risky.

@Erizur Please do not post links to other places which will potentially take discussions away from here. Also, please be aware of forum rule 2e.

Remember that Supermium 126 is supposedly an ESR version.

Supermium 126 is an ESR version, so should be fine for quite a while yet.

FYI, rloew passed away five years ago. He was one of the most valued people on this forum.

We don't allow members to delete their accounts themselves because doing that would probably destroy all the forum content associated with the account (as being banned does, of course). This would probably make a nonsense of any threads which the user had contributed to, and we would potentially lose useful information from the forum.

Download the setup file (I assume you want 32 bit) from here - https://github.com/win32ss/supermium/releases/download/v126-r5/supermium_126_32_setup.exe That should set everything up properly, it did for me. The only thing you can't do on XP (and presumably Vista too) is use the built-in facility to make it the default browser. This is off-topic of course here in the Thorium thread BTW, if you need further help with setting up Supermium, please post in the Supermium thread.

Welcome to MSFN! Did you use the supplied installer for Supermium? That should certainly have generated the necessary shortcut to run it. I started with Supermium, but on XP x86 its RAM use was excessive, and tabs would sometimes crash as the memory was exhausted. Then I tried Thorium, and that seemed to be better with RAM. Unfortunately, Supermium then moved on, and Thorium didn't, which meant that I was missing things that I wanted on Thorium which were there on Supermium, so I went back to Supermium. The memory usage problem hasn't gone away, but I am living with it! It only affects memory hungry sites like Instagram and Facebook.

My main reason for going to 126 was that my understanding is that it's an ESR version, which will hopefully not actually need to be updated due to site compatibility issues until sometime next year. I will only update it if a new facility that I really want is added, or a really major serious security flaw is patched.

Yes I am, but it's still very useful for everyone here to be aware of new releases, so thank you @mina7601.

Thanks for the heads-up, but I don't think I'll bother to update this time. I can't see any changes which are important to me.

What a shame, but I'm glad you found it anyway!

The earliest Supermicro CD that I have is from July 2014, and that has version 15.5 of the Intel Ethernet driver on it. I may have had an earlier one from the first 32 bit Supermicro board that I had, but I guess I didn't keep it when I updated. As Supermicro only make server boards as far as I know, I would doubt that any of their installation media has Windows 98 drivers.

What are you trying to do? What is the motherboard, and which operating system?

I came to the same conclusion, which is why I advised @CIACIACIACIACIACIA to post here to get other people's opinions. What the problem on their system is I can't even speculate on I'm afraid.