Dave-H

I'm getting a green padlock with the proxy in use, unlike with a direct connection, but the site seems to work fine with either configuration, including downloading files.

I'm using - Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36 This matches the string used by Thorium.

I'm not seeing any verification. This is what I'm seeing - The certificate appears to be faulty, but everything still seems to work.

This is in Windows XP. No sign of any problem at all.

Strange, as I said, it works fine for me with 360Chrome 13.5.2036.0. And I've changed the UA string from the default too, which I think was speculated might be part of the problem.

Thanks. That's good to know. Did you mean "db" files, or was that a typo? Outlook Express mailbox files are 'dbx' files.

The Sourceforge site seems to work fine here, in 360Chrome, Supermium, and Thorium. At least the homepage looks fine. What are you actually trying to do there?

The Sourceforge site seems to work fine here, in 360Chrome, Supermium, and Thorium. At least the homepage looks fine. What are you actually trying to do there?

Good to have it confirmed that OE Classic does still work with Hotmail (and presumably Outlook) accounts on XP! I won't be using it because my entire e-mail history going back nearly 30 years is in my Eudora e-mail client, so I don't want to change unless I have to. Am I right in assuming that, like the original Outlook Express, OE Classic does store the mailboxes and messages locally in dbx and eml format?

A friend told me last night that he is still successfully using OE Classic with Hotmail on XP, so presumably OE Classic does include OAuth2 support, probably with a 'borrowed' token.

My understanding is that an e-mail client has to be registered with an e-mail provider for OAuth2 to work with that provider's servers. The client is issued with a token which has to be used. The proxy I'm using is actually using a token which was issued to Mozilla Thunderbird, and the Microsoft servers therefore think that it is Thunderbird. I gather that the mechanism for getting a token from Microsoft is quite complex, so 'borrowing' someone else's is a lot easier than going through the hoops to get one of your own!

Microsoft are enforcing mandatory OAuth2 authorisation on their e-mail systems. Basic password logins will no longer work, even with 'app specific' passwords. I'm surprised that the mechanism for that is even still there, I suspect that it won't be for long. Gmail will go the same way soon, I'm afraid, as will all the other major mass e-mail providers eventually, I suspect. The writing is on the wall now for any e-mail client which doesn't support OAuth2, I'm afraid. I use a proxy to work around the problem, but that's no help on Windows XP, where the proxy will not work.

@user57 This '64 bit' conversation is completely off-topic for this thread. Please start a new thread with an appropriate title, and I will move the relevant posts into it. Thank you.

Yes, they said it would happen on September 16th, it actually happened a week later, yesterday. I'm using an OAuth2 proxy to maintain access to my Hotmail account using Aurora (the successor to Eudora) and it works fine. Unfortunately, it won't work on XP, so I'm now having to boot into Windows 10 to access my Hotmail account, unless I use webmail of course.

There is no problem including paid software in this thread. Any software which still works on Windows XP now is worth mentioning. I would ask though that if software is not freeware that it should be mentioned in the relevant post.

FWIW my Windows temporary folder is also marked as read only, so I don't think that's your problem. If your temporary folder really was unwritable you'd be having a lot more issues, as many programs need to write to it all the time, including Windows itself.

Should do, yes. I have drives on my multi-boot system which I keep on FAT32 for compatibility with Windows 98!

Is the C: drive NTFS formatted? If it's FAT32, that's the reason. The security tab only appears on NTFS drives.

This is off-topic of course as we're talking about browsers on later operating systems, but could it be a certificate issue? Not working on 114, 119, or 115 because it's too new, and not working on 125 or 128 because it's too old?! For 122, 123, and 124 'just right' like Goldilocks' porridge!

FWIW, the Yandex site doesn't work with the latest Microsoft Edge in Windows 10 either! I can only get it to work in Firefox 130.

@bennybenny This thread is 13 years old.

The installer still doesn't seem to work in XP, but the portable version does.

I think that might be a bit of a big ask, why don't you ask him yourself?

Supermium works fine here, I'm still gobsmacked that there is a browser based on Chromium 126 which works on Windows XP! It's missing a few things which I've got very attached to with 360Chrome, such as double-clicking to close tabs, and automatically opening bookmarks in new tabs. There is a 'Chrome Plus' add-on for Chromium with gives those facilities, and I'm using it on Supermium on Windows 10, but of course it won't work on XP. Thorium has the double click to close tabs built into it, and I'm going to try and persuade win32ss to add it to Supermium as well. If he does, I will probably go over to using Supermium as my default browser on XP. It's disappointing that Thorium Legacy is now four Chromium versions behind Supermium, and there seems to be no sign of any update coming. Also, the font problem on forums.digitalspy.com on XP has now been fixed in Supermium, but it's still no good in Thorium.

@sazkion Thread is now unlocked again.