Leaderboard

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 http://o.rthost.win/basilisk/basilisk55-win32-git-20230701-7ec514b57-xpmod.7z Win64 http://o.rthost.win/basilisk/basilisk55-win64-git-20230701-7ec514b57-xpmod.7z repo: https://github.com/roytam1/basilisk55 Repo changes: - ported from UXP: Issue #1956 - Allow building with newer MSVC versions. (d8f486f26) - import from UXP: No issue - Set the default for incremental cycle collector to be off. (c4d665a0) (8060b71a4) - import from UXP: Issue #1691 - Follow-up: Print leaking class name and remove crash reporter dependency (fe7244c0) (a540c3c0f) - import from UXP: No issue - Update SQLite lib to 3.42.0 (86584523) (006009e73) - ported from UXP: Issue #251 - Move MOZ_AV1 back to ac configure for everyone to use. (20b2c264) (f7c8a895e) - ported from UXP: - Issue #1769 - Part 1: Add vendored libjxl and highway sources. (7983f5d8) - Issue #1769 - Part 1 Follow-up: Tidy up moz.build for highway and libjxl (00a5d640) - Issue #1769 - Part 1 Follow-up: Use standard [[deprecated]] for JXL_DEPRECATED. (40f27cd3) - Issue #1769 - Follow-up: Fix typo in MOZ_ARG_ENABLE_BOOL (4d78f53d) - Issue #1769: Update symbols for libxul linkage (1ef390db) - PR #2050 follow-up: add symbols to build shared on Windows. (514ed142) - Issue #2061 Follow-up: Export jxl/version.h. (b1811451) - Issue #2061 Follow-up: Fix moz.build to compile on all platforms. (743d1f66) - Issue #2061 - Follow-up: Silence compiler warnings for libjxl (84dc161d) - Issue #2061 - Follow-up: Silence compiler warnings for libjxl (MSVC) (80c20628) (3c3852c26) - ported from UXP: - Issue #1769 - Part 2: Implement JPEG-XL decoder and about:config and MIME plumbing. (51ea0e4f) - Issue #1769 - Part 3: Cleanup nsJXLDecoder. (2df55850) - Issue #1769 - Part 2 Follow-up: Do not use namespace parent::child {} for defining nested namespaces. (134c5e94) - Issue #1769: Ensure MIME type is known in URIloader for jxl (f860413e) (c03ea8fbf) - ported from UXP: Issue #1769 - Follow-up: Default-enable JPEG-XL images if built (7f87cc12) (d6c6b4ac3) - import from UXP: - Issue #2033 - Temporary fix of R<->B channel swap. (77ca4ae9) - fix whitespace. (8b4b6f8e) (e867d8e24) - import from UXP: Issue #2040 - Pre-multiply the alpha values in our JXL decode buffer. (9b4c0ef4) (b3702ccfe) - import from UXP: Issue #2041 - Add animation support for JPEG-XL. (042b8f37) (3023bbd11) - import from UXP: Issue #2048 - Add progressive decoding for JPEG-XL. (0bd6f003) (964d065e3) - import from UXP: Issue #2041 Follow-up - Remove opacity check from original patch. (54e07351) (0f35b7c78) - import from UXP: Issue #2041 follow-up - fix macro condition (8f091628) (789eb8d8b) - import from UXP: Issue #2057 - Use gfxPackedPixel + WritePixels instead of WriteBuffer. (42543c12) (c5bc7b4c0) - import from UXP: Issue #1382 - Fix invalid assert for decoder type if JXL is not built on debug builds (06d2df29) (7ec514b57)

Well, I really don't know whether it counts or not, but the BBC wrote an article 7 days ago about the increasing number of accidental phone calls to the police now that Android has released a new feature in which if you press the power button 5 times it will send an emergency alert to your emergency contacts and will also call the police for you. https://www.bbc.com/news/technology-65962942 The article has a picture at the very beginning which depicts a police station with operators monitoring incoming calls and on the computer you can clearly see the Windows XP start button with the classic Luna theme: Of course, although the article was released as little as 7 days ago, we don't know whether the picture used is a stock photo or if it's a recent one and they're still using XP to run legacy stable software, this is why I said "I don't know if it counts" at the very beginning.

Old story. Besides, it wasn't the antivirus, but a "product" called "Avast Secure Browser" which is a chromium fork and as such it doesn't work on XP. That, of course, used to track everything and give data to third party for analysis as long as you opted in to share your info, however Avast wasn't aware that the third party was also reselling the data instead of using it for research and to make transactions safer (yes, in theory it was born as a browser on which you were supposed to make transactions like logging in to your bank account or use credit cards / debit cards on etc so that it was totally sandboxed etc etc etc). When the story came out, Avast dropped the contract with the third party. Since you're concerned about the antivirus itself, that program only shares data about the threats you find if you choose to send them up for analysis. It also shares a very limited amount of data, which can be increased if you opt in to the optional data sharing, but it's gonna be limited to how many threats you face every month, what your subscription is like and what OS you are running on what hardware etc so that they have some statistics that can be useful to make a better antivirus. For instance, think about polymorphic viruses. They're viruses whose code changes frequently so that - in theory - they will be able to do some damage before they're included in the virus definitions and detected. Avast of course has heuristics, so it might see that although a program isn't in the virus definition, such a program isn't signed and is behaving in a peculiar way, perhaps by accessing resources etc. It's a point based system and if the score adds up to a certain threshold, Avast detects it and blocks the program, thus asking you confirmation. Although this might lead to some false positives, it can also detect polymorphic viruses and, once you catch one of those viruses which is temporarily blocked, you can send it in for analysis and they will immediately add it to the virus signature database which every user will receive through the streaming updates immediately. All this is, again, if you "opt in", with the word "opt in" being the keyword here. Exactly. I remember talking about this a while ago, thank you for confirming.

I just tested Spybot - Search & Destroy version 1.6.2 @AstroSkipper Unfortunately up to version 2 it is not possible to update the database. Until 1.6.2 you had to update the entire program. Sorry.

New build of BOC/UXP for XP! Test binary: MailNews Win32 https://o.rthost.win/boc-uxp/mailnews.win32-20230701-ef491d91-uxp-4fae28f05-xpmod.7z BNavigator Win32 https://o.rthost.win/boc-uxp/bnavigator.win32-20230701-ef491d91-uxp-4fae28f05-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-20230701-id-656ea98-uxp-4fae28f05-xpmod.7z IceApe-UXP(suite) https://o.rthost.win/hbl-uxp/iceape.win32-20230701-id-656ea98-ia-93af9a0-uxp-4fae28f05-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/icedove-uxp/tree/winbuild https://github.com/roytam1/iceape-uxp/tree/winbuild for UXP changes please see above.

That seems to be the NORM to me. McAfee. Norton. Avast. Avira. Kaspersky. Panda. They all have "uninstall/removal TOOLS" that you have to download because the Operating System's normal "uninstall" routines don't do the job.

This thread is typically too "defensive" to want to participate. But the only thought I have is this - what antivirus product out there does NOT have a service running 24/7 and what antivirus product out there does NOT "collect data" from its users? My perception has always been that they *ALL DO*. The line in the consumer-sand is generally NOT that data is collected, but rather that the data is then SOLD to other companies.

OT since ESET is no longer an option for XP - but since you are so knowledgeable about such matters, I have to ask: Is Bratislava another “KGB nest”? 🤔

Yes i installed all updates even in windows update

did you install kb4474419 and kb4493730 on top of the official vista updates?

go to C:\Program Files\Windows Sidebar and create a new folder called sidebar.exe.local put ole32.dll there and make sure you merge DLLredirectionenabler.reg every file can be found at the same location as ex kernel

I'm very glad to hear it!

AvastClear does not need any installation. It is portable. So there is no need of uninstallation, either. But in my case, it didn't work, unfortunately. AvastClear is more of a joke. A company provides a special tool for uninstalling their products, but it fails, either. Very poor!

Hello, @AstroSkipper, you're always very helpful, thanks for the warning! Just like the others already pointed out that issue, even on Dell forum: "I'm trying to uninstall avast antivirus for the past 6 hours" https://www.dell.com/community/Virus-Spyware/Can-t-uninstall-avast-antivirus/td-p/6103780 They suugest to use "AvastClear.exe", but no one tells how to uninstall that tool itself after that!

Manually installed it

I do not like it much either, there are still plenty of 32bit Windows, I have even see several 32 bit Win10 laptops that were not up-gradable to 64 bit because of UEFI BIOS. So in the end I think there are more 32bit windows than Linux desktops. Even if all AMD/Intel CPUs have been 64bit since the early 2000s... Also I always saw the duality or architectures as a free sanitizer, you would be surprised on how many subtle bugs can be found by just building and testing in both 64bit and 32bit. There were a lot of buggy 32 bit programs that were hard to port to 64bit and now I see random programs that have a ton of warning simply when you build them for 32bit and some of them cannot even work. Bad coding habits still exist but have just migrated from :"I assume my CPU is 32bit so int == void* and stuff" to "I know my CPU is 64bit so uint64_t == void* and stuff". Windows 10 will be supported until 2025 (and possibly beyond), so dropping 32bit support is very strange because it is still maintained by Microsoft.

Yesterday they changed the system requirements of 116 Nightly to Windows 10+ Before that, all 116 builds had the minimum requirement of Windows 7. However, I could still install the latest nightly (on 8.1) without any issues. The installer isn't blocked either (yet)

@AstroSkipper Not necessarily applying to this particular product (Vir.it), but being well known or popular is not always a proxi for anything but being well known or popular, and definitely not for quality or convenience. As an example, take DMDE (which I actually personally recommend[1]) as a program for data recovery, try finding it searching for a data recovery program, you will find that Recuva, Easeus and Wondershare are far more well known and popular, yet they - in the best case (if/when they work at all) - offer a fraction of the capabilities of DMDE. jaclaz [1] but that D.Draker cannot use because the programmer is Russian

This is a political opinion that should not fit in this forum. I cannot imagine that situation and I am not going to express my political opinion here. Sorry.

Only to understand how these highly sophisticated soviet/ex-DDR communist agents operate: 1) they wait until you go visit your Bavarian friends 2) they break into your house (not necessarily a fortress house) 3) they rely on autorun to infect your PC 4) when (if) you wisely disabled autorun they go away muttering the equivalent (in Russian or German) of "D@mn, we can't do anything, autorun is disabled". jaclaz