All Activity

That’s exactly what I expected. What’s the point of AnyTech365 having friendly staff if the customer is still left in the dark? 👀

I'm running 22.03.05. There is a more recent version 23, but it appears that isn't XP compatible, as if you try to install it on XP, you actually get 22.03.05 instead. I had no reply from the direct Panda support people responding to the report forms I sent them, which didn't surprise me at all! Nothing from the people at AnyTech365 either, which did slightly surprise me as they seemed to be pretty good. They had said that they would let me know about ongoing support for XP.

Interestingly, and as if this company had read this post, the following happened: SASDEFINITIONS.EXE 345.6 MB 07.02.2026, but then SASDEFINITIONS.EXE 229.4 MB 15.05.2026 Unfortunately, the virus definition file SASDEFINITIONS.EXE was inflated again in July 2026: SASDEFINITIONS.EXE 305.8 MB 26.07.2026 Very strange what on earth they’re up to there. My guess is that the definition files and their installer are compiled extremely sloppily.

Which version are you currently running? 22.03.05? And do they still offer a more recent one for paid customers? And what about their support? Have you got any reply that Panda Dome is working again on Windows XP? 🤔

OK, me again! I hope I'm not jinxing it, but Panda Dome seems to be working properly again now for me on XP. I hadn't had a stop and restart of the main service for a few days, so yesterday I removed my shortcut files exclusion. All still seems to be working fine. Can you confirm this @Tangy? Whether they have fixed it as a result of our reports or whether they realised the problem themselves, I do not know. I just hope now that it keeps on working! It does look as if XP support is still a thing for Panda Dome, at least for now! Cheers, Dave.

StartAllBack 3.9.24

Also, it appears that the "View members flags" settings has no affect. Flags are displayed for me regardless of this setting.

we getting off-topic again but can you explain why ? that guy might wrote a other video where is said the oposite but the questions he answers to are asking it wrong (for example he is being asked for a short instruction list somewhere in the code - why it would be only made there ? people are seeing this problem quite often) 64 bit app´s result in bigger file sized because for example the offsets are bigger, there are things coming together (to avoid this they used the trick list, for example they didnt use always the full 64 bits or even 32 bit instructions) often x64 app´s in elder compiliers use a 32 bit instruction set instead of a 64 bit instruction set (shown in regedit_64.jpg) they are aware of this problem, bigger instructions means more demand, in the regedit (64 bit) case they use a 32 bit instruction set so in theory it is not even a x64 bit application, but it is bigger in size even tho some tricks where used then there is also useally the 4 GB question that is also a longer story in fact there are no 4 GB moves, or 4 megabytes moves, or 100 mbit/s these things are made via a assembly command and these are in common 32 bit or 64 bit (16 and 8 are only used if the data dont is smaller then 32 bit or 16 bit then 8 bit is used) now comes the good part about that, the cpu for example the TLB can see the incoming commands then there is actually no speed loss for example there was the a older question in quad-pumped questions in the LGA 775 socket question instead of pumping just 32 bit it quad pumps the 32 bit *4 aka 128 bit or more the cpu´s gone longly away from just a clockrate + the 32 wires 32 bit is not limited for 4 GB of RAM either (for the 32 bit move question it also would make no difference in speed or memsize) in a programming language it normally looks like this like memmove(offset1,offset2, 5 megabyte) https://www.geeksforgeeks.org/cpp/memmove-in-cc/ but that is always being translated into 32 bit moves maybe 64 moves (but these are not faster, the reason i tryed to explain buffering and such) , here are the norms for passing 4 GB of ram in 32 bit PSE (page size extension) and PAE (physical address extension) and paging/segments these exits since AMD athlon (1999) and for intel pentium 2 (1998?) https://msfn.org/board/uploads/monthly_2024_10/page_size_method_PSE.jpg.21624fe4f9fa5ef04f8f49d5bf6f8d52.jpg shortly said - these so called "virtual offsets (VA)" in 32 bit are not physical ones physical ones are made via paging why 4 gb isnt used for a 32 bit application then ? the reason goes rather back that in that time you barly needed more then 2 GB ram in only 1 application then you could see that microsoft didnt use the extra segments to its full potential - rather they used maybe a few kilobytes of it the next reason is the compiler, the compiler normally just knows the 32 bit offset it dont know how to generate a memflow over segments (the memmove command for example cant do that) so all the applications are compiled to have it with the 4 gb limit - but more would be possible there is no "continuous flow" question for the "32 bit move question" - 32 bit are a very small amount lets say we want to move 1024 (1 kb) that would make 32 times the 32 bit moves and for that reason if the compiler (or better said the compiled code) at some point would reach the 4 GB ram - but since its a very small piece of 32 bits the cpu could not even reconize the difference it then would just say ds:00000000 (0002:00000000) instead of ds:ffffffff (0001:ffffffff) but again a normal compiler do not know this method! also something you can test the speed if 32 bit and 64 bit are slower or faster is the heic encoder i wrote just turn off the hardware acceleration (then normal instructions are used) i can compile a 64 bit version if you want but it makes no difference the hardware acceleration use the hardware speed registers (MMX,SSE, AVX) and these can move 512 bit 256 bit 128 bit (depending on what your cpu can do) also they can interact - makes them a lot faster so in sence of speed you also dont find yourself in a better position for x64 https://msfn.org/board/topic/185879-winxp-hevcheifheic-image-encoderdecoder there is also a elder method called the ramdisc, but the ramdisc has to remap the virtual address space (it can use more then 4 gb of ram, but when it whats to see a other piece of that it has to make the pagein/remap) for a normal compiler you just set it from 32 bit to 64 bit but 64 bit applications give an error to 32 bit operating systems - so i think 32 bit has the advantage in that question you can run a 32 bit compiled app also on 64 bit - its like no problem - its not slower - often even a little faster and smaller

Well, I hate as much as anyone to be a PITA , but, again, a member's country flag has gone AWAL ; things look more ominous now, because, unlike on the previous time, there's no sign anywhere of a member's country of origin in the form of even a tooltip (see the screenshot in my previous post); going to my MSFN account settings, https://msfn.org/board/settings/ I no longer see any setting related to "my country and/or my country's flag" ; is this now completely gone?

Long ago I reported Steam game list didn't display correctly. After it got fixed on some version I can't recall, here it goes again with the same glitch, that happens (with different affected elements) on wishlist and games list. Working on 2026-06-28 build, not working in latest 2026-07-18 build (note I haven't been online since early July and didn't update NewMoon so don't know which version had the regression). Wishlist with messed up menus over games on list (this is the more visually impacting; on game list it affects other elements, such as triple dots):

Not that it matters much right now, but many applications no longer support 32-bit. Windows XP with One-Core-API can still run a lot of modern software, but in the long run, only the x64 version will have the minimum capabilities needed for everyday use.

Good news! Looks like Mozilla is doing the community's work, and we thank them for it, because they extended ESR 115 support AGAIN till March 2027! https://support.mozilla.org/sr/kb/firefox-users-windows-7-8-and-81-moving-extended-support Looks like someone was right when he said that if they knew that Firefox was going to support 7 and 8.1 until 2026+ , they would've continued to support it on the main branch until like end of 2024..

I have no clue what you are talking about. Could you please explain a bit more detailed what you wanted to say? And what does the abbreviation SRP mean? And which gui do you refer to? 🤔🤔🤔

for test my Gui for SRP - stock securuty WinXP https://ru.files.fm/u/wmgmdj6fw4

@GH0st So, here is a workaround. Create a SSUAO for cloudflare.com, i.e. general.useragent.override.cloudflare.com with the following user agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0 Test it and report here! And if that doesn’t help, try disabling uBO completely, i.e. the extension in the Add-ons Manager, if you’re using it. An uBO set too aggressively made it impossible for me to complete the CF challenges.

Ok. Forget about this version! It still can be started under Windows XP but it no longer works properly. I reverted back to the last good one I could find. And that is Malware Hunter 1.210.0.841 (Dec 29, 2025). I will edit my article accordingly. And BTW, I said tests could be done by the users but I’ve never seen any like that.

The links are still available on Adlice servers after editing to suit the users’ needs. I do not use COMODO Internet Security but COMODO Antivirus. This works fine with no impact on CPU. And my CPU is a single-core P4. I wouldn't recommend the complete suite COMODO Internet Security, either. You must always focus on the pearls and throw the by-catch overboard.

I would like for you to replace the links for RogueKiller last XP compatible versions from generic web-site links to archived links with v15 and portable v16 on 32bit and 64bit. It's a shame that Panda is placing XP on guillotine right now, but to be honest, XP had a good run, 25 years of anti-malware support from various programmes. I am still using Avast on XP VMs and i feel relatively secure with COMODO Firewall Pro from 2007 version, and i have no complaints. I do not recommend the last version of COMODO Internet Security however, because it choked my old Celeron to the core when i tested 4 years ago...

This time on time :-) - the latest update is online: 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 20260725 build - added latest IceApe 52 20260725 build - added latest IceDove 52 20260725 build - added latest MailNews 52 20260725 build - added latest New Moon 28 20260725 builds - added latest Serpent 52 20260725 builds - added latest Serpent 55 20260725 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

Don’t be misled! Quoting from old, already closed and resolved at the time issues serves no purpose and is misleading. I’ve opened a new issue on GitHub today: https://github.com/Feodor2/Mypal68/issues/723 One thing is clear. If you use a browser that doesn’t support Cloudflare’s security nonsense, you won’t get very far in these days, and it’ll be useless. Indeed, Cloudflare = Cauldron Filthcare.

thanks

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-20260725-94e741a46-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk55-win64-git-20260725-94e741a46-xpmod.7z repo: https://github.com/roytam1/basilisk55 Repo changes: - ported from UXP: Issue #1803 - Convert std::*<T>::value/::type to _v and _t suffixes. (1dd094e9) (200256195) - ported from UXP: Issue #3061 - Remove network tickler. (3312ebb2) (5cb455841) - ported from UXP: Issue #3144 - Implement CSSStyleSheet replaceSync (05467e9d) (de7f8267f) - import from UXP: [js] Guard against OOB string sizes in internal Printf (90952505) (604ade209) - import from UXP: [gfx] Add bounds checks and limit reverse scanning of ligature data. (07271921) (6c05b903c) - import from UXP: [gfx] Hold a strong ref during GetFontAt lookup. (0b8fd38f) (a3d9936ff) - import from UXP: [DOM] Make parser update form owner properly (0cd2c3ac) (443fd3272) - import from UXP: [js] Initialize BaselineFrame return value slot in OnLeaveBaselineFrame. (a809f575) (df19befd2) - import from UXP: [js] Clamp length of regexp captures array for dollar substitution. (f8982ebd) (94e741a46)

New build of BOC/UXP for XP! Test binary: MailNews Win32 https://o.rthost.win/boc-uxp/mailnews.win32-20260725-40a79c75-uxp-30427c0213-xpmod.7z BNavigator Win32 https://o.rthost.win/boc-uxp/bnavigator.win32-20260725-40a79c75-uxp-30427c0213-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-20260725-id-656ea98-uxp-30427c0213-xpmod.7z IceApe-UXP(suite) https://o.rthost.win/hbl-uxp/iceape.win32-20260725-id-656ea98-ia-c642e3c-uxp-30427c0213-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/icedove-uxp/tree/winbuild https://github.com/roytam1/iceape-uxp/tree/winbuild

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20260725-3219d2d-uxp-30427c0213-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20260725-3219d2d-uxp-30427c0213-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-20260725-3219d2d-uxp-30427c0213-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-20260725-d849524bd-uxp-30427c0213-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260725-d849524bd-uxp-30427c0213-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260725-d849524bd-uxp-30427c0213-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20260725-d849524bd-uxp-30427c0213-xpmod.7z Win7+ x64 AVX2 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20260725-d849524bd-uxp-30427c0213-w7plus-avx2.7z Official UXP changes picked since my last build: - Issue #1803 - Convert std::*<T>::value/::type to _v and _t suffixes. (1dd094e90b) - Issue #3061 - Remove network tickler. (3312ebb226) - No issue - Exclude some files from the preprocessor that don't have directives in them. (4b77043d11) - Issue #3144 - Implement CSSStyleSheet replaceSync (05467e9db6) - [js] Guard against OOB string sizes in internal Printf (90952505ec) - [gfx] Add bounds checks and limit reverse scanning of ligature data. (07271921c9) - [gfx] Hold a strong ref during GetFontAt lookup. (0b8fd38fb3) - [DOM] Make parser update form owner properly (0cd2c3acf7) - [js] Initialize BaselineFrame return value slot in OnLeaveBaselineFrame. (a809f575d1) - [js] Clamp length of regexp captures array for dollar substitution. (f8982ebd3f) No official Pale-Moon changes picked since my last build. No official Basilisk changes picked since my last build. My changes picked since my last build: - devtools: restore preprocessor usage (30427c0213) 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.