FranceBB

Why don't you try OpenOffice instead? The last LibreOffice version compatible with XP is from July 23rd 2017, while OpenOffice is still XP compatible to this very day, in fact: https://www.openoffice.org/product/windows.html Here's the download page: https://www.openoffice.org/download/index.html Of course I didn't just limit myself to trust what they were saying on the website, I'm actually using OpenOffice on XP regularly and here you can see a screenshot with my XP running version 4.1.15 (i.e the latest version released on December 22nd, 2023. You know, between a project who deprecated XP years ago and doesn't really care (LibreOffice) and one who keeps actively supporting XP (OpenOffice) I'll always pick the XP compatible one

It's not a lie, it is based on the original ReactOS implementation and also on Wine D3D for the DirectX10 and 11 implementation, which is totally fine and would be 100% allowed. The problem is that by limiting it to that it wouldn't have achieved much, so it also contains proprietary Microsoft dll which have been patched (hence modified) and backported to allow Windows XP to make use of them by Samuel. He has done an amazing job in doing that and he has been working on this for several years now, however this means that once One Core API is installed, it will replace system libraries and unfortunately MSFN has a longstanding stance against linking modified Microsoft dlls which is why RyanVM was created in the first place. By the way, if you search for posts from 2019 onwards from Dibya, Peter and I you're gonna see that we all know Samuel (heck we were even in the same chat) and we're all great supporters of his work.

One Core API is written by Samuel, we know him very well and he has done an amazing job. Please note that Windows XP + One Core API is way closer to Windows 7 level of compatibility than ReactOS will ever be. Also please note that One Core API is largely based on reversing newer Windows functions, so you won't get far here by linking it (probably a mod will remove the link soon as it's not allowed ).

ReactOS doesn't even have full Windows XP compatibility, let alone Vista and 7 one. Wine, on the other hand, evolved a lot over the last few years and that's the one having up to Windows 7 compatibility

Not to wake an old thread, but has there been any progress on this? One of my XP installations is currently being virtualized on Virtualbox and indeed I'm stuck with AC97 at 44100Hz 16bit PCM stereo 2.0 routed all the way through to Pipewire/Wireplumber on Linux, upmixed to 5.1, upsampled to 48000Hz PCM 24bit and then delivered to my sound card and on to my subwoofer. That... kinda sucks.

Yeah, I'm still going through all the errors in the Event Viewer and the plan is to fix them all one by one once and for all on all my systems (the physical one and the VM). Getting rid of those errors in the Event Viewer does feel good and I reduced them all to just 2 (affecting the system running in the VM) but I'll probably open a separate topic about those as I can't wrap my head around those... I mean they seem to be a bit cryptic.

Thanks for letting us know, I updated too. About this, I've just noticed from the Event Viewer that I still have lots of crypt32 errors due to the Microsoft Certificate Updater running So I'm just gonna uninstall the Microsoft Auto Certificates Updater component given that not only it's no longer useful but it's even "harmful" in the sense that it would be throwing lots of errors for every time it tries to update the root certificates (and fails) in the background, so I invite anyone who still has this component to go "add or remove programs" -> "windows components" and remove it

Guys, chill, I mean it, don't worry about me. I swapped the RAM and I haven't had any bluescreen ever since, so all is well what ends well and yes, it was a problem with the RAM after all, so thanks to everyone who pointed that out. I'm happy with the answer, we can safely close the topic.

Correct. The reference contact person is Weolar and the builds are provided by him to the companies who purchase the extended support afaik. I'm very very very lucky to be one of the people that receives those builds, but of course they're private and I cannot share them, however they do have some bugs. Anyway, they run just fine on Windows XP SP3 x86 without the need to use One Core API.

Not exactly the best solution, but when I wanna download something from YouTube I use JDownloader2 which is running using Java and it's cross platform. It's still updated regularly and it still runs on the latest XP supported version of Java just fine. This is not an accident, but rather a nice coincidence given that JDownloader2 is cross platform and therefore supports all OS capable of running Java, including a wide variety of Linux distro which are running a very old version of Java, which is why it still works perfectly fine on XP at every update. As for the FFMpeg libraries it uses, I'm of course using Reino's fork that he regularly publishes on Doom9 and that have been already mentioned in this thread. As for things I wanna watch on my PC without downloading them, with M108 (the chromium fork), all videos work, including VP9 ones and AV1 ones as they're royalty free codecs whose decoders are included/embedded in chromium however they all run via software decoding due to the nature of the XP compatible versions of chromium. Nonetheless, for anything up to 1920x1080 60p software decoding on a quad core is fine. I don't of course expect it to be playing 4K or 8K footages via software decoding on a puny 4 cores CPU, but realistically most of us probably have a FULL HD 60Hz display anyway, so we're gonna be more than fine for the time being.

I will. Thank you Dixel.

Damn, I'm really sorry to hear that 'cause these RAM sticks (ironically also HyperX) are actually 8 years old and I was emotionally attached to them... I will try running a memory test through it, though, but if you say that it passed it then I don't know how reliable that can be...

Hi there guys, I was doing my usual stuff when suddenly I got the following bluescreen error message: STOP 0x0000008E (0xC0000005, 0xB9D17E94, 0xA7664FF0, 0x00000000) fltmgr.sys - Address B9D17E94 base at B9D11000, DateStamp 480251da I rebooted and it seems to be working fine but I'd like to know what caused this issue. I looked for a MEMORY.DMP file in C:\WINDOWS, however the only one I could find is a 1.9GB one from 30/07/2017 which means that it's not the one of this latest crash. BlueScreenViewer also doesn't report anything at all which leaves me puzzling a bit... I wasn't doing much, I only really had 3 different RDP sessions opened to computers in my local network and that was pretty much it, really...

Well I don't know how things are nowadays, however I remember using Freegate back in the days and their intention were actually not bad: it was a free proxy run by a non profit organization (NED - National Endowment for Democracy) to allow people in censored countries to be able to browse the web freely with a U.S IP Address. I personally used it to watch Hulu (back when Hulu was free).

Thank you @AstroSkipper for the build, I installed it and it works like a charm!

Even better! Thanks!

Interesting! I'm currently still using v2.3.18 which is the last officially supported one, so if the patched 2.5.4 version you're using works reliably well I might use it and ditch v2.3.18. I found the source code and the XP guide (https://openvpn-for-windows-xp.sourceforge.io/), so perhaps this weekend if I have time I'll try to setup the environment and build it, however if you already have a trusted build feel free to send it over.

Same here, including occasional bluescreens caused by the driver.

Yep RDP also works as long as Network Level Authentication is disabled, which is totally fine for an internal network, but I wouldn't dare to use it over the internet (public network) in the wild nowadays... (unless you're asking for troubles, that is). Out of curiosity, are you using RDP without NLA over the internet? O_O I'm personally using Anydesk for remote connections over the internet (public network) and RDP for internal connections between computers in my house (internal network).

Yep, I use Anydesk all the time ever since Team Viewer left us stranded. It has been working reliably well and I'm really glad that it still does.

Ah, I see... Good to know. This also means that the net market share stats for Windows are gonna be completely screwed, nice.

No it doesn't as anyone can request commercial support to Weolar afaik: weolar@miniblink.net I'm not sure whether a private user can buy the commercial support and the versions he provides the companies with or not, but it's definitely worth trying and after all I wouldn't see why he wouldn't. For those looking for his GitHub account, it's here: https://github.com/weolar

This is because the original developer of that version of chrome goes by the name of "Weolar" who is selling official support to companies around the world. Official private builds don't have restrictions like a timebomb. I don't know whether the build got released publicly or if it was leaked by someone, but assuming the first case, I think (but this is speculation) that making one build freely available to the public helps attracting commercial support, but again I'm just speculating here. All I can say is that I've been one of the very lucky people using the official private builds for quite some time (M76, M92, M108) and I reported several bugs which, eventually, got fixed, although I found some regressions in M108 which is the last one I've got (that's right, I haven't received M115 yet). One of the regressions is that if you have the "Save as" to ask you where to save the file that you download instead of saving them automatically to the download folder, it "forgets" the filename, so that it opens the prompt but there's no file name there. That bug was introduced in M92 and it got fixed in later releases but somehow got reintroduced in M108. About M108, it got several releases as the first ones led to a memory leak but that got addressed in later versions of that release (the last being from June 2023 this year). Another issue has to do with the timing and the handling of sampling in the input devices like the microphone that leads to unpleasant artifacts, crackling noises etc. This has been reported by other people (and not just me), however it never got addressed, unfortunately. It affects all version from M76 to M108. One thing you may wanna do is change the user agent, though, 'cause by default it spoofs XP as Windows 10 to the various websites. This is how I created the shortcut on my desktop, though: C:\Programmi\Chrome\chrome.exe --user-agent="Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.5359.125 Safari/537.36"

Thanks for the heads up, looks like I gotta run the update too.

Telegram still works on XP. Sure you'll have to use an older version and you're gonna get an annoying banner begging you to upgrade your OS, but it still works. Older versions of the TeamSpeak client can also be used as long as the server is also relying on an old version.