Leaderboard

@FantasyAcquiesce Thanks for your info... BUT... The latest version available on the linked site is 3.0.205.0 and yes, min Windows version compatible is Windows Vista (32-bit and 64-bit) - no surprise then that the client wouldn't run under XP... The downloaded standalone installer has a digital SHA1 signature of May 20th 2018 ; even worse, when the installer is extracted/installed, the browser has a buildID of 20150421120931 (i.e. April 21st 2015); in this case, New Moon is just a generic UNBRANDED fork name, not to be confused with @roytam1's unbranded builds... The BlackHawk browser build is based on Pale Moon 25 (platform is Gecko 25.3.0), so extremely outdated security/features-wise ; IMHO, that browser deserves an entry inside digital history books, not installed in one's Vista machine today... (OT: I honestly hope you're well - stay safe )

Perfect! That's exactly what I wanted to hear! Armed with this information, I shall now go install and update Office worry-free c

OK, I will reinstall it and try that. However, I have had a major breakthrough with Windows 8.1, I've finally found an Elan driver that works with it! It's version 15.14.4.1, the latest version I've ever tried. It didn't install at all (although it said that it had) when I tried it normally, but forcing an install in Device Manager from the INF file actually worked, despite a warning from the driver that it wasn't designed for my hardware! The mouse is now an "Elan Input Touchpad". There is no control panel icon in the Windows Control Panel, but it can be accessed from the "Elan" tab on the Mouse Properties. The device is shown there as an "Elan Smart-Pad", which proves that the "Standard PS/2 Mouse" shown in the same place in XP means that the device had not been identified correctly. At least now I have an equivalent working driver in 8.1 to compare with what's happening in XP. Sadly there is of course no chance in hell of that driver actually working in XP.

Yesterday's Microsoft patch resolved the CVE-2020-0938 and CVE-2020-1020 vulnerabilities for supported OSs. For W.7 there is 0Patch. For OS prior to W.7 only the mitigations described by Microsoft + my personal solutions.

In new versions, they broke support for TLS 1.3, if you try to open a site with TLS 1.3 or where 1.2 and 1.3 are used at the same time, the browser will show a certificate error. https://www.howsmyssl.com/ shows the status of BAD. The latest version where there are no these problems is 12.0.1053.0.

fixed in git, will be fixed in next build

Not really. I stopped working on that after my last attempt failed miserably. There's a post with screenshots here on MSFN somewhere. I spent way too many hours on Chromium. It's a far too big project with many parts that I don't really understand and since I don't fully get what they were trying to do and why some things were there that way, some of my implementations were actually wrong when I rewrote them. If you search for my last attempt here on MSFN you'll find out that I managed to get it running but it wasn't able to load any pages and the UI was broken. If you think that every time they add some commit many other things change we're never gonna get it working. That said, the last thing I want right now is to waste many other hours on this code, yelling at my computer for yet another thing that doesn't work. I can only say that I'm not currently working on it and I haven't even opened the solution explorer for months. Dibya isn't working on it and Samuel isn't working on it either. The other guy we shared the code with got stuck at the new vs old multi-threading implementation 'cause once he re-introduced the old multi-threading several things that are NOT documented broke (I.e they are documented, but they expect data in a completely different way and of course it doesn't say anything about it 'cause nobody expects someone to change a trivial modern Windows API to substitute it with some sort of dirty way to check and allocate workload that was used in the former implementation). We haven't heard from him ever since. The last compiled executable works fine on Windows 7 and above but on XP and Vista it doesn't. If we push our very latest code into it and we compile, then it doesn't work on ANY Windows Platform as it fails to load pages (although it does start a glitchy default Window which immediately crashes). This just enlightens the fact that there's something deeply wrong in our code since we broke modern Windows compatibility, but anyway we don't really want to have different routines inside our code for different Windows platforms. In a nutshell: I'm not working on it, don't expect anything from me. I did my part, the code has always been open source and online, so if you wanna help the guy who took the project over from us, ask Dibya and Peter so they can make you talk with him, if he's still working on it of course (I have no idea what that guy is up to since I haven't heard from him for months and he doesn't reply on Skype anymore). I'm sorry to delude you, but I guess that's it...