Leaderboard

Calm down folks!

Thanks @Tangy. I would be interested to know your results. Just an update, I spoke again today to Panda's technical support people at AnyTech365. Again, really friendly and helpful people, who knew exactly what I was talking about. They are thinking, as many here do, that Panda have actually withdrawn support for XP. They agree that doing this by just breaking the legacy version of Panda Dome, is not a good way of doing this, especially for paying customers, and they are trying to find out whether this really is the case or whether this has been done accidentally and will be fixed, if indeed it's possible to do that. There has certainly been no change made to the system requirements on Panda's website, and the article trumpeting its XP compatibility claims to have been updated on July 1st. They have given me a number to ring for Watchguard, Panda's parent company, so I will try giving them a ring tomorrow to see what they say about this.

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20260620-3219d2d-uxp-f718564719-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20260620-3219d2d-uxp-f718564719-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20260620-3219d2d-uxp-f718564719-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260620-d849524bd-uxp-f718564719-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260620-d849524bd-uxp-f718564719-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260620-d849524bd-uxp-f718564719-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20260620-d849524bd-uxp-f718564719-xpmod.7z Win7+ x64 AVX2 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20260620-d849524bd-uxp-f718564719-w7plus-avx2.7z Official UXP changes picked since my last build: - Issue #2306 - Re-introduce pref for WeakRef API spec. (8eac1db64b) - Issue #2306 - Enable full weakref by default in platform. (0bd0d0a296) - Issue #3122 - Exclude local resources from <base> CSP checks. (692606e89c) - Bug 2029066 - Remove Sinking of Live instructions. (2712943075) - Bug 2029765 - avoid refcount over-release in nssTokenObjectCache error path [@ nssToken_Destroy]. (13d8737677) - [network] Make keep-alive pref Atomic. (f20e0799a0) - [DOM] Reject too large mLength in MutableBlobStorage::WriteRunnable. (b60661dfe1) - Bug 2023478 - improve handling of escape sequences in pk11uri_ParseAttributes. (7ae6442d99) - Bug 2033848 - Use non-default response ID for GTK file picker accept button. r=stransky (81babad165) - [DOM] Zero-initialize ThreadSharedFloatArrayBufferList. (5ab14e5932) - No issue - Use ImmGCPtr for module meta data visits. (0bdcc65c4c) - [parser] Better align with spec definition of adding nodes. (a50e1d7ae5) - [DOM] Avoid over-optimizing some getter/function calls. (a83b6f74bb) - [gfx] Check more offsets during CFF subsetting. (9a457cbfd9) - [network] Make HttpBaseChannel::mLoadFlags atomic. (100f6aaf5b) No official Pale-Moon changes picked since my last build. No official Basilisk changes picked since my last build. Update Notice: - You may delete file named icudt*.dat and icu63.dll inside program folder when updating from old releases. * Notice: From now on, UXP rev will point to `custom` branch of my UXP repo instead of MCP UXP repo, while "official UXP changes" shows only `tracking` branch changes.

I got a response from Watchguard technical support. "At this time, we have not received any official communication indicating that Windows XP support for Panda Dome has been discontinued. Based on the information currently available, Windows XP continues to be listed as a supported operating system for the legacy Panda Dome version referenced on the Panda website. Based on the information you have provided, this issue appears to be related to **Panda Dome**, which is a consumer (home) product. While we understand your concerns regarding the recent crashes of **PSANHost.exe** on Windows XP, we are unable to investigate or provide support for Panda Dome through WatchGuard Technical Support." So it appears that they only deal with professional business customers at Watchguard support, and they can't help private domestic customers. I would have to use the domestic support channels for Panda support, which I've already done, of course! The guys at AnyTech365 have promised to let me know if they hear anything about the status of XP support from Panda, so all I can do is wait.

Assuming you haven't already uninstalled Panda, could you try excluding from scanning the folders I detailed in my earlier post? I would just be interested to know if this helps the problem on your system. I'm still getting occasional stops and starts of the main Panda service, and I'm trying to find out exactly what is triggering them. Again, not a fix, just a better understanding of where the mechanism is now failing. Incidentally, Panda's online support forms are pretty useless, as once you've submitted one, you are supposed to be able to add new information to it by clicking on the link in the e-mail it sends you. Unfortunately, this doesn't work. When you submit the revised form, you just get an error message that the e-mail and customer number don't match any current user! I've had to submit two further forms from scratch to give them more information.

Back again. I'm cautiously confident that I've found another workaround for the problem with Panda Dome, and this one appears to have stuck. I was puzzled as to why the crashes, although sometimes apparently at random, could be triggered at will, at least on my machine. One thing which nearly always triggered an immediate crash, even if the system had been running for some time without any, was to click the Windows 'Start' button. This led me to think that there was some issue with Windows Explorer which was triggering the crash. One other clue was that one of the first things I noticed was that if I clicked Start, even if it didn't crash, the user-added shortcuts were a blank box, only populating after several seconds. I tried excluding Explorer from scanning, but that made no difference. I then tried excluding my whole system drive from scanning. Hey presto, no more crashes! So, by a process of elimination, I eventually narrowed it down to the folders which were triggering the crashes when they were scanned. I now have three folders excluded from scanning – Documents and Settings\[Username]\Start Menu Documents and Settings\[Username]\SendTo Documents and Settings\[Username]\Recent So far this has stopped the regular crashes, and Panda has updated without them coming back again. This is pure speculation, but what I suspect happened here is that Panda rolled out an update which broke compatibility with the Windows XP Explorer, which is quite different from that on later versions of Windows, of course. When Panda tried to scan those folders, like the 'Recent' folder being scanned when 'Documents' is clicked on the Start Menu, this triggered a crash. This is of course only a workaround, not a fix, and the problem could come back at any time, but at least on my system it seems to have fixed it for now. There is a security issue with excluding system folders from scanning, of course, but as the folders concerned only contain shortcuts, I would think it's pretty minimal. If anyone else still has a malfunctioning installation of Panda Dome installed, I would be interested to know if this works for them.

FFmpeg update. XP: static shared libfdk-aac VISTAx86: static shared libfdk-aac The following static links will always match the latest uploaded XP archives: https://files.videohelp.com/u/69760/ffmpeg-win32-XP-static-latest.7z https://files.videohelp.com/u/69760/ffmpeg-win32-XP-shared-latest.7z

Regarding panda forum reporting, to be able to uninstall panda you have to be able to stop the antivirus running. right clicking task bar icon does not always respond. after a few reboots my task bar icon informed me that my computer was not protected, a tiny red circle with the x. then it was easy to uninstall from add/remove. I also used their generic uninstaller which removed everything from my pc. I did a clean install but unfortunately the song remained the same. 5 minutes later it crashed. I have not got the foggiest how to go about it.

Yes indeed, in fact, the first test I did was to replace that entire folder with one from an ISO image I made a few days before the fault appeared. It made absolutely no difference, it still carried on crashing, so I discounted the contents of that folder as having anything to do with the problem. I next looked for any other recently updated files in the Panda installation, and that led me to the cache folder in the Panda program files folder.

OK, an update. I rang the local UK number for Panda's technical support. It's operated by a company called AnyTech365. They took ages to answer the phone, but just as I was thinking about giving up, the call was answered by a very nice and very helpful guy, who sounded completely English! He wasn't aware of the problem, and I had the usual lecture about the risks of still using XP, but when I pointed out that Panda make a big thing of still supporting XP, he was quite conciliatory about it! Amazingly, when I said I'd already reported the problem via a web form, when I gave him the case number, he actually found my report from last Friday on his system! It's open and pending response apparently. I told him that I had, since the report, discovered that the files in the cache folder are apparently related to the problem, and he has added that information to the report. So, a rather better experience than I thought it would be! All I can do now is wait and see what comes back, but if nothing does, at least I now know there's a real person I can talk to if I need to.

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20260627-3219d2d-uxp-98f21468a1-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20260627-3219d2d-uxp-98f21468a1-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20260627-3219d2d-uxp-98f21468a1-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260627-d849524bd-uxp-98f21468a1-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260627-d849524bd-uxp-98f21468a1-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260627-d849524bd-uxp-98f21468a1-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20260627-d849524bd-uxp-98f21468a1-xpmod.7z Win7+ x64 AVX2 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20260627-d849524bd-uxp-98f21468a1-w7plus-avx2.7z Official UXP changes picked since my last build: - Fresh import of libpng 1.6.58 (b61274cd5d) - Apply (hopefully for the last time before 2.0.x) APNG support code. (882bf4b345) - [devtools] Consistently show filepicker on first save action from StyleEditor. (6316f240c7) - Bug 2029403 - avoid PORT_Strdup in ssl_DecodeResumptionToken. (c95367158a) - Bug 2030366 - avoid race with module unloading in NSSTrustDomain_FindTokensByURI. (43317d3eba) - Bug 2030564 - add defensive input validation to sftk_compute_ANSI_X9_63_kdf. (346619a8ea) - [DOM] Clean up WebGL transform feedback validation. (a4a23b4318) - Issue #3122 - Put base paths in the json viewer client deps. (09108384c7) No official Pale-Moon changes picked since my last build. No official Basilisk changes picked since my last build. Update Notice: - You may delete file named icudt*.dat and icu63.dll inside program folder when updating from old releases. * Notice: From now on, UXP rev will point to `custom` branch of my UXP repo instead of MCP UXP repo, while "official UXP changes" shows only `tracking` branch changes.

Long story short, I have revived Comodo Antivirus 12.0.0.6818 (CAV) as part of the Comodo Internet Security suite (CIS) since it was no longer working out of the box. It's one of the last working antimalware programmes with real-time protection, HIPS, VirusScope, secure containmenr, online definition updates, even incremental definition updates, and the possibility of offline updating. This is now my new antimalware programme. And Vir.IT of course. All free of charge.

As I already said, it is no longer time to be picky when it comes to real-time protection under Windows XP. And of course, I read such reports about IOBit Malware Fighter. I personally never liked the IOBit company. Their products have never really been any good. And in the case of IOBit Malware Fighter, I can see why. The positives: Easy to install. A clearly structured, very tidy and modern interface. Good usability. Lots of features not usually found in freeware. Excellent uninstallation speed. The negatives: No daily updates as advertised. Today, it’s still installing the version from 9 July. Not really integrated efficiently into Windows XP. When the protection is activated, performance plummets. Version 13 is constantly being promoted, and you’re told to download it, even though it’s not compatible with Windows XP. No self-protection. The scan speed is so poor that I’m lost for words... The scanning speed is the absolute worst I have ever experienced. Smart Scan was cancelled after 123,226 files!!! and 120 minutes!!! with only 5% progress!!! This is no Smart Scan. I then uninstalled it completely. The uninstallation was done in seconds. That just goes to show how poorly the programme was integrated into Windows XP. It was practically just a superficial add-on. And it can even be shut down completely with just two clicks. That’s a goldmine for malware. My conclusion: Looks great on the outside, but a flop on the inside. P.S.: And that’s the good thing about my ancient P4 computer. It mercilessly exposes the weaknesses of software.

@j7n are adamant on NOT using an extension-based adblocker (e.g. uBO) in the browser, because they harbour the conviction that such an extension would considerably impede their browser's performance ; in the past, both myself and other members here have suggested to them the installation and use of uBO, but they still think that their old ways of dealing with ads (blocking "known" ad-serving domains in their HOSTS file) is still sufficient/effective in the web-ecosystem of 2025+ ... Is this on a UXP-based browser (the object of these megathreads) ? Because if you're talking about recent Chromium/Firefox, these now come with built-in ways of dealing with (some of the) unwanted content ...

For the time being I am trying to avoid going back to a full build which may contain many libraries that nobody uses. It will expand as fixes and requests are added to it. Here is a build for you to test with added support for https. The next release can include it in all builds. https://files.videohelp.com/u/69760/ffmpeg-8.2-2237-b4b30ff8fd-win32-shared-xpmod-P4.7z

Thank you once more for these new releases ; however, I have to report that the latest ffplay.exe compiles for Vista x86, BOTH the static+shared binaries, are completely broken under Vista SP2 x86 (with ALL MS updates until EoS, and then some ); whatever media file you throw at FFplay.exe (e.g., via drag-n-drop) results in the app instantly crashing; below, an instance of a plain MP4 file containing h264 video + aac audio: Your previous VISTA release works as expected with that same MP4 file: FWIW, your latest FFplay.exe static compile for WINXP doesn't suffer from this issue and plays the MP4 file without any problem: You'll probably need a Vista SP2 x86 VM to troubleshoot this, as I have no clue as to what might have gone wrong; perhaps an updated third-party lib has in the interim (n8.2-dev-1568...n8.2-dev-2232) removed support for NT 6.0? We know it's not caused by upstream (FFmpeg source code), because your n8.2-dev-2232 compile for XP works OK; in addition, when I probe the MP4 file with latest FFmpeg for VISTA, it doesn't crash: ffmpeg version N-125505-gc57660fb18-WINVISTA Copyright (c) 2000-2026 the FFmpeg developers built with gcc 16.1.0 (Rev5, Built by MSYS2 project) configuration: --disable-autodetect --enable-amf --enable-bzlib --enable-d3d11va --enable-dxva2 --enable-iconv --enable-lzma --enable-zlib --enable-sdl2 --enable-gmp --enable-libmp3lame --enable-libopus --enable-libvorbis --enable-libx264 --enable-libx265 --enable-libdav1d --disable-debug --enable-libfdk-aac --enable-fontconfig --enable-libass --enable-libbluray --enable-libfreetype --enable-libmysofa --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-amrwbenc --enable-libwebp --enable-libxml2 --enable-libzimg --enable-libshine --enable-avisynth --enable-libxvid --enable-libopenmpt --enable-libsrt --enable-libzmq --enable-libgsm --enable-chromaprint --enable-frei0r --enable-libaribb24 --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libflite --enable-libfribidi --enable-libgme --enable-libilbc --enable-libmodplug --enable-librubberband --enable-libzvbi --enable-openal --enable-libcodec2 --enable-ladspa --enable-libuavs3d --enable-libjxl --enable-libxeve --enable-libxevd --enable-libharfbuzz --enable-liblc3 --enable-libaribcaption --enable-lcms2 --enable-libdvdread --enable-libdvdnav --enable-liboapv --enable-libqrencode --enable-libquirc --enable-opengl --enable-gnutls --enable-gpl --enable-version3 libavutil 61. 2.100 / 61. 2.100 libavcodec 63. 5.100 / 63. 5.100 libavformat 63. 3.100 / 63. 3.100 libavdevice 63. 2.100 / 63. 2.100 libavfilter 12. 2.100 / 12. 2.100 libswscale 10. 2.100 / 10. 2.100 libswresample 7. 2.100 / 7. 2.100 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'Mastermind_Se8Ep12[2494504515559].mp4': Metadata: major_brand : isom minor_version : 512 compatible_brands: isomiso2avc1mp41 encoder : Lavf62.13.101 Duration: 00:25:41.93, start: 0.000000, bitrate: 968 kb/s Stream #0:0[0x1](und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p(progressive), 768x432 [SAR 1:1 DAR 16:9], 837 kb/s, 25 fps, 25 tbr, 90k tbn (default) Metadata: handler_name : VideoHandler Stream #0:1[0x2](eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 125 kb/s (default) Metadata: handler_name : SoundHandler At least one output file must be specified Hopefully you'll be able to get to the bottom of this, as I do use FFplay.exe myself under Vista SP2 (32-bit) ; thanks for all your hard efforts already!

You’re welcome! It’s rare for me to be this blunt. But what I went through last night was hell. My entire partition was at risk. The BSOD had wiped out various files. Fortunately, most of them were related to Panda. It was a miracle that I was even able to boot the partition at all. And the fact that Panda could be uninstalled despite the damage was another one. Incidentally, the whole drama started straight after the nightly automatic update that Panda had carried out yet again. I’m a bit reluctant to make recommendations these days, but I can tell you what I did a few days ago, in a moment of foresight. It’s really just a coincidence, but take a look at number 7 on the list you posted. That’s what I recently installed: VirIT eXplorer Lite. Here’s my post: https://msfn.org/board/topic/184730-antimalware-firewall-and-other-security-programs-for-windows-xp-working-in-2023-and-hopefully-beyond/page/101/#findComment-1288687 This antimalware programme is very nice. It is fully compatible with Windows XP, even in the latest version!!! The Lite version is free of charge. If you want to have more protection, you have to buy a license for the Pro version. The programme interface isn’t modern; it’s got a bit of a retro feel to it. That’s what programmes looked like in the 1990s: extremely colourful, with lots of bright colours and plenty of colourful buttons. Personally, I think it’s brilliant. It reminds me of those days. VirIT eXplorer Lite requires very little RAM and CPU power. The virus definitions are downloaded locally to the computer and are therefore available offline. That’s the only reason why the programme folder takes up just over 500 MB. And support is available and active. The intrusion detection shield, called VirIT Lite Monitor, had flagged processhacker.exe as malicious and issued a warning every time the computer started up. I then uploaded the file to VirIT or, to be more precise, to C.R.A.M., along with a message. A day later, the warning had disappeared, as they’d complied with my request to whitelist it. I’m completely satisfied with VirIT eXplorer Lite at the moment. Another reassuring point is that this is a programme developed in Europe – specifically in Italy. I will soon be writing a detailed article about VirIT eXplorer Lite/Pro. Old screenshot of my VirIT Lite Monitor with false positive: New screenshot with Process Hacker 2 whitelisted by C.R.A.M.: Cheers, AstroSkipper

For experimenting with Avast, you should avoid the last XP-compatible version. As far as I can remember, is a previous version associated with fewer problems. I have to look in my archive for the exact version number. As far as I can remember, there were repeated reports on the Avast forums that avast! Free Antivirus 18.5.2342 runs much better than the latest XP-compatible avast! Free Antivirus 18.8.4084.0.

All Panda Dome installers come with offline installer version 15.14.5.0. Therefore, this information is unfortunately of no use. I asked you for the programme version. The most recent is 22.03.05 but I currently use 21.01.00. And it doesn't matter whether you actively click the update button or not, the update is automatically done every day and there is no option to disable it.

The file version of the installer file is meaningless, unfortunately. It isn't the version of Panda Dome that it will install. It's probably just the version of the packaging process used. As far as I can see, the only way to find out what Panda version it is, without actually installing it, is to extract it with 7-Zip and look in the extracted \Program Files\Panda Security\Panda Cloud Antivirus\ folder. There you should find a file called version.ini, which, if you open it, will list the Panda version and build number.

Well, I guess of those here still using XP, very few use Panda Dome, even though it's one of the vanishingly few security programs which is still supposed to work on XP. I found one instance on the virtually dead Panda forum reporting the same problem (with no response). https://support.pandasecurity.com/forum/viewtopic.php?t=12151&sid=a73549f228b82be2dde1657a770a28e4 My installation is still crashing all the time. It stops if I clear the recent files in the cache folder but starts again as soon as the folder repopulates.

Not to get anyone's hopes up, but I may have found a fix, or at least a workaround. In the Panda program files folder, there is a subfolder called 'cache'. I looked at that and thought, 'clearing out caches is often a good idea'. After first backing it up, of course, I deleted all the files in it. The program then ran on a reboot, with no crashes. All the instabilities seemed to have gone away. The only thing that happened was that Panda started prompting me to OK the running of a lot of program files, so maybe that's where that data was stored before. After OKing all the prompts, things were still good, but surprisingly the cache folder still didn't seem to have anything in it. The folder originally contained a .mngr file, a .util file, a .code file, and several sets of .act and .sig files, which were in pairs with the same filename. The first three files were dated from the date of the program's installation; of the other pairs, one was from back in February, and the others were all from July 3rd this year. I put all the files back, except the recent ones, which I was suspicious of, and everything is still fine. So, was there a corrupted file or files in there?

That's only for XP users, though. We discovered earlier that if you download and install the latest version from Panda on Windows 10, say, you get that version. If you install it on XP, however, it automatically downloads and installs an earlier version (22.03.05). I assume that is the latest (and probably last) version for XP. The build date for that version is 12/08/2025, which I think you thought was December because you didn't realise the date was in European format, so it's August 12th, not December 8th, even older than you thought! The current version is 23.01.00.0000, whose build date is 29/06/2026, so very recent. Nothing back from Panda support as yet. I have disabled the real-time scanning, which has stopped Panda interfering with the rest of my system, but the service is still crashing. In my case I can only tell this by looking at the Windows System Event Log. The service is automatically restarted after 30 seconds.

If you need a solution for Windows XP, you can try my QJS build - it's certainly not super fast, but it's lightweight and native to XP. https://postimg.cc/9D5NQkZ2 https://postimg.cc/HcVt20XF https://www.mediafire.com/file/b2yx0shb0ncfp2c/qjs.zip/file

Please take the new version from codebergs

ah something went wrong and uploaded old one, all files are replaced and please redownload.

Not only Serpent, all are from last week.

Oh man...plz stop this kind of personal war...we all are very special individuals, please respect each other and his/her opinion and behavior! I find out this myself every f*cking day...and still have problems to come together with other people... ------------------------------------------- Thank you, I hope to be here again regularly. ------------------------------------------- Sorry, had some vacation at the Baltic Sea - so the latest update is online just now: The mirror of latest ArcticFox 44, BNavigator 0.9, Firefox 28/45ESR, IceApe 52, IceDove 52, K-Meleon 1.5.x/74/76, MailNews 52, New Moon 26.5/27/28, RetroZilla, RZ browser and Serpent 52/55 builds by @roytam1 has been updated -> soggi.org - tools. changelog: - added latest BNavigator 0.9 20260620 build - added latest IceApe 52 20260620 build - added latest IceDove 52 20260620 build - added latest MailNews 52 20260620 build - added latest New Moon 28 20260620 builds - added latest Serpent 52 20260620 builds - added latest Serpent 55 20260620 builds To don't lose track of things I want to update too someday... todo: - add various flash player versions - add FlashFix for WinXP - add VLC 2.2.8 (WinXP non-SSE2) done! - add polyfill addons Kind regards soggi

New build of post-deprecated Serpent/moebius for XP! * Notice: This repo will not be built on regular schedule, and changes are experimental as usual. ** Current moebius patch level should be on par with 52.9, but some security patches can not be applied/ported due to source milestone differences between versions. Test binary: Win32 https://o.rthost.win/basilisk/basilisk55-win32-git-20260620-962fb7e60-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk55-win64-git-20260620-962fb7e60-xpmod.7z repo: https://github.com/roytam1/basilisk55 Repo changes: - ported from UXP: Issue #2306 - Re-introduce pref for WeakRef API spec. (8eac1db6) (938e5c744) - import from UXP: Issue #2306 - Enable full weakref by default in platform. (0bd0d0a2) (74824f24b) - import from UXP: Issue #3122 - Exclude local resources from <base> CSP checks. (692606e8) (6fc95b735) - ported from UXP: Bug 2029066 - Remove Sinking of Live instructions. (27129430) (e89f0a52f) - import from UXP: Bug 2029765 - avoid refcount over-release in nssTokenObjectCache error path [@ nssToken_Destroy]. (13d87376) (73b5f11e4) - import from UXP: [network] Make keep-alive pref Atomic. (f20e0799) (0d6196afd) - ported from UXP: [DOM] Reject too large mLength in MutableBlobStorage::WriteRunnable. (b60661df) (94d348ce4) - import from UXP: Bug 2023478 - improve handling of escape sequences in pk11uri_ParseAttributes. (7ae6442d) (f277da265) - import from UXP: Bug 2033848 - Use non-default response ID for GTK file picker accept button. r=stransky (81babad1) (1f1e28073) - import from UXP: [DOM] Zero-initialize ThreadSharedFloatArrayBufferList. (5ab14e59) (91d2413a4) - import from UXP: No issue - Use ImmGCPtr for module meta data visits. (0bdcc65c) (456bea8af) - import from UXP: [parser] Better align with spec definition of adding nodes. (a50e1d7a) (1f0c79b3a) - import from UXP: [DOM] Avoid over-optimizing some getter/function calls. (a83b6f74) (94850d8a2) - import from UXP: [gfx] Check more offsets during CFF subsetting. (9a457cbf) (acffb7115) - import from UXP: [network] Make HttpBaseChannel::mLoadFlags atomic. (100f6aaf) (962fb7e60)

New build of BOC/UXP for XP! Test binary: MailNews Win32 https://o.rthost.win/boc-uxp/mailnews.win32-20260620-40a79c75-uxp-f718564719-xpmod.7z BNavigator Win32 https://o.rthost.win/boc-uxp/bnavigator.win32-20260620-40a79c75-uxp-f718564719-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/boc-uxp/tree/custom * Notice: the profile prefix (i.e. parent folder names) are also changed since 2020-08-15 build, you may rename their names before using new binaries when updating from builds before 2020-08-15. -- New build of HBL-UXP for XP! Test binary: IceDove-UXP(mail) https://o.rthost.win/hbl-uxp/icedove.win32-20260620-id-656ea98-uxp-f718564719-xpmod.7z IceApe-UXP(suite) https://o.rthost.win/hbl-uxp/iceape.win32-20260620-id-656ea98-ia-c642e3c-uxp-f718564719-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/icedove-uxp/tree/winbuild https://github.com/roytam1/iceape-uxp/tree/winbuild

@AstroSkipper I think I'll spend the weekend doing a thorough debugging session on Windows XP because I initially tested the extension on Windows 7. Unfortunately, I can't completely avoid using BAT files, but I'll try to optimize the process.

It’s clear and obvious that Panda stopped supporting Windows XP for programme updates quite some time ago. The latest version is 22.03.05, nearly one year ago, and that was a long time ago. But to then go and break even that version via the automatic update – that’s a no-go. And in doing so put the user’s partition at risk.

New Moon, Serpent or Mypal are a nightmare without uBO. And the forum editor is a nightmare, anyways. I already again reported that some weeks ago. There have been many such reports in the past.

Custom Install of IOBit Malware Fighter 11.4.0 (easy to install ) Latest Database Version 2608 ( 2026 - 7 - 9 ) Fingerprint : 898269 I ran a smart scan Objects scanned 107.446 Threats Detected 0 as expected Time Elapsed : 20.02 minutes Very light and smooth

@VistaLover Thank you for reporting the problem. I will investigate and make new builds.

Somehow, I have a sixth sense. The PSANHost.exe process just crashed after running without errors for three days. Here is the error message and the contents of the PSANHost.exe.mdmp dump file extracted with WinDbg: As I said, you shouldn't get your hopes up too soon. This time, it also has to do with the DLL file PSANModProcMon.dll. Maybe try turning off Process Monitor . I'm glad there's no Panda Dome on my primary Windows XP partition at the moment.

I've now tried as a test removing the cache folder completely from my Panda installation. Rather unexpectedly, the program has not recreated it. It's been running for ages now like that with no crashes, but it's not updating, presumably because it has nowhere to put the files! Doing a manual update from the option in the settings does nothing. I guess I could leave it like that, but of course, like the version of Malwarebytes I used on XP for years, it will eventually become useless for protection because of no updates. I tried Avast on my system a few years ago and never got it to work on my desktop system. Even the supposedly compatible version for XP would not run, its core service obstinately refused to start, reason unknown. I even worked with Avast's technical support people about it, and even they couldn't determine what the problem was. I tried a test install on my netbook under XP, and that worked perfectly, so what the problem was with the desktop remains a mystery.

You have to download the last XP-compatible version 11.4.0. Here is the original website with this version: https://web.archive.org/web/20240830175125/https://www.iobit.com/de/malware-fighter.php Download link: https://www.filepuma.com/de/download/iobit_malware_fighter_free_11.4.0.1360-40845/download/ Please test this version to find out how it works and whether it still receives definition updates or not!

Here are a few words about my plan C. More than 3 years ago, my good old friend @D.Draker had recommended the anti-malware programme Vir.IT eXplorer. I still had it on my internal list, but as there were no further tests or information available, I couldn’t report on it. At that time, it also seemed to have some temporary issues with VB100 certification, but these had long since been resolved. I was also worried that support for Windows XP had long since been discontinued, as it is no longer listed as an OS on the website. So I downloaded the very latest version 9.5.981.0 and was delighted to discover that the programme is still compatible with Windows XP. For some days, I have been testing Vir.IT eXplorer Lite. More on this coming soon.

No one can spoil Windows XP for me . I’m currently working on Plan C. First I need to free up some space on my hard drives so I can back up my main Windows XP partition as an image. And then it’s down to the nitty-gritty.

Thanks but I am not interested in workarounds. Either the forum editor is able to process code syntax in the dedicated code block or it is simply unusuable and crap.

It's no longer even possible to enter simple, harmless DOS code in the forum editor. Not in the text area, not as a code block, and not as a quote. No longer a forum for coders who want to post their code, or must.

AstroSkipper ... thanks for the link. I probably would not have found it anytime soon.

https://codeberg.org/Theodor2/Mypal68/releases You do not need to have an account there. BTW, Codeberg is much better than GitHub.

Thank you very much for the new release! It works great here under Windows XP Professional SP3. Especially GitHub is running again now, and incredibly fast on my old P4 machine. Everything that worked in Mypal 78.0.2 seems to work in Mypal 78.0.3 as well. In particular, the Alice0775 script loader, all 37 of my own UC.JS scripts, and the installed extensions. Brilliant! I’ll carry on testing, but I’m already thrilled. Can you provide in short what you changed in this release compared to the previous one? And here a quick reminder: The issue #96 on GitHub is still open. Is there anything else to add? I assume it has already been fixed but I might be wrong, too.

I tried to play a music video which I downloaded from YouTube with the H264 codec in the mp4 format. A standard format, so to speak. It was downloaded with my ytBATCH for Windows XP and processed with ffmpeg 7.1 to embed subtitle, metadata and a thumbnail. It can be played with all players, even with ffplay except your recent version 8.2. ffplay immediately closes when trying to play this video. Why did you scale down to basic? Your previous releases have really been fine. In my opinion, the only thing which can happen is that scaling down results in problems playing some kind of videos. BTW, I asked you in a previous post whether you also could add ffplay to your static releases. Is that possible for you?

No idea. When I run this version on Windows 7 (with all Server 2008 R2 ESU updates), I get: qjs -h QuickJS version 2026-06-04 usage: qjs [options] [file [args]] -h --help list options -e --eval EXPR evaluate EXPR -i --interactive go to interactive mode -m --module load as ES6 module (default=autodetect) --script load as ES6 script (default=autodetect) --strict force strict mode -I --include file include an additional file --std make 'std' and 'os' available to the loaded script -T --trace trace memory allocation -d --dump dump the memory usage stats --memory-limit n limit the memory usage to 'n' bytes (SI suffixes allowed) --stack-size n limit the stack size to 'n' bytes (SI suffixes allowed) --no-unhandled-rejection ignore unhandled promise rejections -s strip all the debug info --strip-source strip the source code -q --quit just instantiate the interpreter and quit On Windows 7, I use Node 20.19.2 from here as js interpreter. Much faster. Node 20 is not supported by yt-dlp any more since this commit, but in my build I reverted that change. [debug] Command-line config: ['-v', '--js-runtimes', 'node'] [debug] Encodings: locale cp1252, fs utf-8, pref cp1252, out cp1252 (No VT), error cp1252 (No VT), screen cp1252 (No VT) [debug] yt-dlp version nicolaasjan/yt-dlp@2026.06.22.040728 (win7_exe*) [debug] Python 3.14.6 (CPython AMD64 64bit) - Windows-7-6.1.7601-SP1 (OpenSSL 3.6.3 9 Jun 2026) [debug] exe versions: ffmpeg 8.1.2-WIN7 (fdk,setts), ffprobe 8.1.2-WIN7, phantomjs 2.5.0 [debug] Optional libraries: Cryptodome-3.23.0, brotli-1.2.0, certifi-2026.06.17, curl_cffi-0.15.0, mutagen-1.47.0, requests-2.34.2, sqlite3-3.50.4, urllib3-2.7.0, websockets-16.0, yt_dlp_ejs-0.8.0 [debug] JS runtimes: node-20.19.2 [debug] Proxy map: {} [debug] Request Handlers: urllib, requests, websockets, curl_cffi [debug] Plugin directories: none [debug] Loaded 1739 extractors

<redacted>, you egomaniac! It gets old reading your high sense of self-worth. And I know for a fact that many others on the forum think the same. I simply stated that not all of us have a MODERN DEVICE to fall back on. I could care less if you have the oldest XP computer, no one else cares either. Carry on, wayward son.

Unfortunately NO. You would have to contact the owner of the server hosting the web site. Maybe if you get THOUSANDS of users of that web site to protest, you could get the owner to remove it. But I do assure you, the owner implemented it for a reason. All SERVER-SIDE reasons.

Of course, you can resolve relative path issues in such Lua scripts by using hard-coded, absolute paths, but that’s not exactly the pinnacle of programming. If you copy my youtube.lua(c) script into the lua\playlists subfolder of VLC, it automatically recognises yt-dlp.exe and hidecon.exe without the user having to set any absolute paths. This is how it should work in the youtube_search.lua script as well. When looking into your log, you can clearly see that the script doesn't add any path to the yt-dlp.exe file: lua: [yt-ext] cmd: yt-dlp.exe "ytsearch10:Adele" -J --flat-playlist --no-warnings --encoding utf-8 lua: [yt-ext] bat cmd: yt-dlp.exe "ytsearch10:Adele" -J --flat-playlist --no-warnings --encoding utf-8 Of course, this only works if the BAT file or the CMD file is run from VLC’s programme folder.