Leaderboard

No, this is not acceptable. Don't bring it up again.

Incorrect. When Kaspersky dropped Windows XP from its official system requirements, Vista was also dropped. The last Vista user to report using Kaspersky on February 12 was using 18.0, but it does not necessarily follow that 19.0 was incompatible with XP - in fact the author of this Kaspersky support article clearly thought that 19.0 was compatible with XP provided that the processor supports SSE2: https://support.kaspersky.com/us/common/compatibility/15479 I posted that link as recently as January 24, but unfortunately this thread has doubled in length since then, so repetition is necessary. More unproven assumptions based on analogy with “most AV companies,” by which you must mean Avast, since no other AV vendor has regularly submitted a free version for independent testing. Like I already said, “we will never know whether Kaspersky Free also could’ve achieved a perfect score.” One can only assume.

Happy Birthday to Malwarebytes 3.5.1 which is 5 years old today. 🎂 Malwarebytes Premium was first certified by AV Test (Magdeburg, Germany) in October 2018, although its Protection score (4 out of a possible 6) was the lowest of any product in the test. Avast Free scored 5.5 for Protection on that occasion. AVG Internet Security scored the same as Avast Free, which suggests to me that there is no advantage in using paid versions of Avast/AVG products. Of course most products in that test had already stopped supporting XP, including Malwarebytes (although it was still a 3.5 version when testing began in September). An interesting question is whether Kaspersky Internet Security 19.0 was compatible with XP. I don’t know, although I did see reports that it worked on Vista. Unlike Avast, Kaspersky never submitted their free version for testing by independent labs, so we will never know whether Kaspersky Free also could’ve achieved a perfect score.

... Well, according to below support article, last reviewed on Aug 13, 2019, min WinOS version targeting KAV19 is Windows 7 Starter SP0 : https://support.kaspersky.com/KAV/2019/en-US/43520.htm It's totally unknown to me whether KAV19 could be installed on Vista SP2 (let alone on XP SP3) 32-bit, provided all the rest software/hardware requirements were met (and there were several ) ; still, I have a very faint recollection of someone posting back then in the Vista subforums, claiming to be running KAF19 (Kaspersky Antivirus Free 19) under Vista (but NOT XP!), but am too tired now to search for that post, sorry ...

I am not quite sure I understand the question nor what prompted it to be asked. I'll offer some thoughts up as "rules of thumb" and allow others to chime in from that. 1) If you have more than 2 or 3 posts back-to-back with nobody else chiming in, then consider the possibility that you are "talking to yourself". 2) Always remember that you are writing to a human being that does the reading, you're not talking to your keyboard or your computer monitor. 3) Remember that this is a discussion forum and not a "blog". A blog (in my view) is somebody "talking to himself" with an occassional reply. 4) Read before hitting the submit button and ask yourself, "Am I being informative or am I being spiteful?" (ie, don't submit something with the agenda of causing an online "flame war") 5) Remember that you don't have to have the last word in order to have the last word. Readers can read and know when the discussion is over but people just keep replying for the sake of having the "last word". 6) Remember that you don't always have to be "right". You can present your point and let the reader decide. 7) Excessive underlines, bold, and italics ALL OVER THE PLACE in a post comes across (at times, not always) as AGGRESSIVE, often even RUDE, and can be DISTRACTING and CONFUSING (at times, not always).

Perhaps you are not aware this is a forum called: Browsers working on Older NT-Family OSes Linkedin works better than in chrome (more like in a cage, so to speak) in the latest librewolf in linuxmint, or (freeranging on your data) in its own shinny app in android. Be aware, though, that that has no bearings with what is being discussed here.

You surely are up to date with your fine knowledge of cybersecurity. Keep it up, because if that was indeed true 6 years ago, imagine what is today out there. Lions and Tigers and Bears, Oh my!

Smallville didn't seem so expensive, or is that Metropolis? jaclaz

This works at least in the case of https://www.gwr.com/ // ==UserScript== // @name Inject Object.hasOwn Polyfill // @version 0.0.1 // @match *://*/* // @run-at document-start // @grant none // ==/UserScript== if (!Object.hasOwn) { Object.defineProperty(Object, "hasOwn", { value: function (object, property) { if (object == null) { throw new TypeError("Cannot convert undefined or null to object") } return Object.prototype.hasOwnProperty.call(Object(object), property) }, configurable: true, enumerable: false, writable: true }) } Source: https://github.com/tc39/proposal-accessible-object-hasownproperty/blob/main/polyfill.js Another read: https://stackoverflow.com/questions/69561596/object-hasown-vs-object-prototype-hasownproperty

It's not an obsession. It was an attempt to correlate a fine-line parallel in a friendly manner. In your view, I failed. But agreed, an international forum has to decide for itself which country laws pertain to forum content. MSFN does not allow direct links to these projects so I follow MSFN's lead in that regard. We are allowed to disagree with each other, you do know that, don't you? Moving on, I was attempting some middle ground but your reply clearly did not see it that way. We are not all always going to agree with each other, plain and simple. I do continue to have a vested interest in just how will Chrome continue on Win7, so I won't be far away, this is a valid and useful thread.

New build of BOC/UXP for XP! Test binary: MailNews Win32 https://o.rthost.win/boc-uxp/mailnews.win32-20230506-5b6a0056-uxp-725b27a0f-xpmod.7z BNavigator Win32 https://o.rthost.win/boc-uxp/bnavigator.win32-20230506-5b6a0056-uxp-725b27a0f-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/boc-uxp/tree/custom Changes: - [Mail] Issue MoonchildProductions/UXP#1451 - Support hunspell as shared library (98335aaa) - [Navigator] Issue MoonchildProductions/UXP#1451 - Support hunspell as shared library (5b6a0056) * 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-20230506-id-656ea98-uxp-725b27a0f-xpmod.7z IceApe-UXP(suite) https://o.rthost.win/hbl-uxp/iceape.win32-20230506-id-656ea98-ia-93af9a0-uxp-725b27a0f-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/icedove-uxp/tree/winbuild https://github.com/roytam1/iceape-uxp/tree/winbuild Changes: - [IceDove] Issue MoonchildProductions/UXP#1451 - Support hunspell as shared library (b2d9022) - [IceApe] Issue MoonchildProductions/UXP#1451 - Support hunspell as shared library (5bce618) for UXP changes please see above.

Not this thread but on the other one, I wonder if a "poll" would be helpful? I'm thinking more along the lines of removing any bias and sticking with undeniable hard-core data. If the "poll" voted by all MSFN Members following the thread has Kaspersky in the top 3 or 5 or so, then we should use real data to assist MSFN Members to use it or not. I'd be willing to run the top 3 or 5 or so and do "quantitative analysis" (in a VM only!) for hard-core data, which consumes more RAM, which scans a 20 MB reference .zip file the fastest, which slows the install of an Office Suite the slowest, which effects PC Startup Time the most, numbers like that are important to me.

Your profile shows that you are running Windows 8.1 this week, in which case the good news is that Malwarebytes still supports Windows 7 and above, i.e. you are not restricted to using 5-year-old version 3.5.1. Not only that, but Malwarebytes 4.x versions have scored better in independent tests! I never realized that you were a fan of Malwarebytes. As recently as January 16 you stated, “I’ve never used anything else accept avast.” Then you puzzled me by stating on March 9 that “panda is definitely the better choice...and has been my go to antivirus for the past year now”!? Looks like no one has posted in the Windows 8 forum since April 19, so perhaps you could try to liven things up over there? 🤔

Sorry for the off-topic, but I hope you continue being humorous like this, because reading this part made me laugh almost the entire day.

D.Draker would agree with that, and it was not my intention to pressure you into testing Kaspersky 19 - only to point out a gap in our knowledge.

@mina7601. I can move and re-size my windows taskbar. Maybe it's some utility I installed but I could have sworn you can do this with OEM Windows 11. EDIT, oh so I see it's changed in Windows 22H2 build. But there are registry hacks that can modify the taskbar: https://www.alphr.com/move-taskbar-windows-11/

Does that also mean you will stop providing FFmpeg builds for XP? On the other hand, if that PC is powerful enough, you can run XP in a virtual machine.

We are definitely a dying bread. There are more than three of us. I think what a lot of visitors forget is that XP today is a lot like 98 x-number of years ago. By that I mean that 7 and 10 folks don't visit 98 threads and remind them that they run an insecure OS - but they will to an XP thread. Makes no sense to me.

I'm a real XP user But of the 64bit version. I never tried the POSReady updates since I think they are meant for the 32 bit version.

lol. I'm on Season 6 on Hulu. A lot of Justice League references but no Batman yet. Which is odd because there would be no Justice League without Batman.

No clue why my name was brought up. No clue whatsoever. A rib-jab, perhaps? So I shall only add this, as I have also stated in the past - a web browser's "padlock" in the address bar is a "false sense of security", plain and simple. ESPECIALLY for the XP crowd! Regardless if you jumped through hoops to "update" certificates or not. XP can not handle modern SSL technology and you can't "hack" XP to do so. That "padlock" can be FAKED at the browser level to totally IGNORE "secure or not" at the Operating System level - the browser itself can put whatever padlock it so chooses (I have witnessed this in Chrome forks, but I suspect FAKES [can] exist in Firefox forks also). A "padlock" at the browser level indicates nothing at the Operating System level - no matter what OS you are on. A "padlock" at the browser level indicates nothing at the DNS level - Catsxp demonstrates that one really well, a lot of DNS traffic if-and-only-if you use its built-in DoH "security feature". I shall remind all that 360Chrome on XP was never intended to "extend" the life of XP - it was only intended to function as a stop-gap for XP users to skip directly over Vista and 7 and jump straight to 10, not 11 or 12, but 10. I've stated that in the past and I still believe that - 360Chrome is a stop-gap, nothing more, nothing less. My preferred browser-of-choice (and as also stated, browser selection is always always ALWAYS a matter of personal CHOICE) nowadays is Marmaduke Ungoogled Chromium v112, nothing newer, nothing older - on Win 10. Hope that will be enough to clear the mud.

Based on my recent research I did for many different security programs, Kaspersky 18.0 was the last XP-compatible version. Starting with Kaspersky 19.0, the system requirements changed, and Windows Vista was listed as a minimum requirement. But KIS 18 was tested by AV-TEST, and I assume KFA and KIS 18 are based on the same scan engine as most AV companies usually do. Therefore, the scan results can be used to get an idea. Here is a test of KIS 18: https://www.av-test.org/en/antivirus/home-windows/windows-7/february-2018/kaspersky-lab-internet-security-18.0-180557/ Cheers, AstroSkipper PS: I totally forgot. Also happy birthday to MBAM 3.5.1!

See: https://github.com/yt-dlp/yt-dlp#related-scripts I know, but I put the link here anyway for others to test. Indeed. I'm amazed he still manages to cope with the hundreds of duplicate issues.

Haha, I can only focus with background music or anything really. I also understand the whole caffiene thing, I can drink a lot of it without issues. But at a point it becomes the opposite and I start bouncing off the walls. December 2022, I drank a Mountain Dew and a Mountain Dew Amp in the same hour, which totals to 200mg+ of caffeine. I ended up bouncing on an exercise ball laughing because it was fun. I also at the same time was tired so I felt like I hadn't slept for weeks but couldn't sleep.

A temporary workaround: disabling javascript.options.ion stops the crash.

If define is defined now, that's excellent.

That's brilliant, thank you so much!

Although this thread is actually only targeting the Windows XP operating system, I have nevertheless added the necessary system requirements to my articles in which I present security programs, in order to let our fans of Windows Vista in particular know whether the program in question is compatible with this operating system or not. Cheers, AstroSkipper

I don't know, it does exist on GitHub, but I'm not familiar with npm and whether compiling it would give an injectable version.

lol, a bad habit. I generally jump straight to making a site "readable" and I can do that most of the time just by blocking scripts or letting a few in without letting all in. I wonder of Object.hasOwn() can be injected the same way we inject structuredClone?

IMHO, there is no need to close this thread. And one thing is clear. If this thread should be closed, it will still not be deleted. You can access the information collected here at any time, but then you can no longer add anything new. Just as it has always been here on MSFN. Anyway! This thread contains a lot of important information, a source of knowledge. I use it for my research regularly.

Just writing in to let everyone know I’m not going to be as active here as I was in the past. I know it’s not on-topic but since this thread is more than likely going to be closed and deleted anyway, I thought this would be a good opportunity to speak up without drawing too much attention to myself. I’ve had a nice time talking to users here but haven’t had much to contribute other than words of encouragement. It seems this forum prizes and values those who actually know how to program/code, and I definitely don’t fall into that category. I had been a lurker for years but joined in 2021 to comment on the Feodor/Tobin situation with Mypal. Since then I don’t think I’ve had much of value to add to the discourse, and the way I see it this is a forum better left to far smarter individuals. I certainly don’t want to annoy the moderators, who have better things to do with their time than read my drivel. Indeed, it is a difficult task to keep things on-topic, and as I fell in love with this site because of all of the valuable information it provides, the last thing I would ever want to do is sully those waters with posts that are less than useful. So much has changed, but this is still my go-to site when I want to learn about what’s happening on the tech enthusiast front. I am glad I got to know what it feels like to post and to be met with varying degrees of kindness, and responses from people who know far more than I will ever, ever know about this sort of thing. Of course, I may return in the future, if I have something of value or interest to share. For now, I’ll go back to lurking, just as I was doing for so many years beforehand. To those who have been nice to me, I appreciate it more than you will ever know. To everyone who is making an effort to develop/maintain software that keeps old operating systems useful, thank you, from the bottom of my heart. To the moderators, thank you for striving to maintain law and order here. May you do your best to hold up MSFN’s legendary reputation. Take care, everyone…I wish you all peace.

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20230506-3219d2d-uxp-725b27a0f-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20230506-3219d2d-uxp-725b27a0f-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-20230506-3219d2d-uxp-725b27a0f-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.6a1.win32-git-20230506-d849524bd-uxp-725b27a0f-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20230506-d849524bd-uxp-725b27a0f-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20230506-d849524bd-uxp-725b27a0f-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win64-git-20230506-d849524bd-uxp-725b27a0f-xpmod.7z Official UXP changes picked since my last build: - Remove unmaintained WebGL conformance test suite. (733451d1b) - Revert "Issue #61 - Place Skia in libxul" (260f8e154) - Issue #61 - Follow-up: Fix gkmedias.dll link bustage related to Skia. (6e2f70a70) - Issue #61 - Follow-up: Fix xul.dll link bustage related to Skia. (4584069f2) - No issue - Correct handling of async (arrow) functions declared inside constructors (ffe6d48af) - No issue - [MailNews] Fix build bustage due to recent MIME API changes (2048f4df5) - Issue #1451 - Split hunspell library out of xul. (cbbc15ad8) - Issue #1451 - Fix hunspell build bustage in FreeBSD. (d75c6c181) - Issue #1691 - Part 1: Provide a way of associating a private value with a script or module. (1a6b3a822) - Issue #1691 - Part 2: Implement call import and import meta in the parser. https://bugzilla.mozilla.org/show_bug.cgi?id=1427610 https://bugzilla.mozilla.org/show_bug.cgi?id=1484948 (a8ab41b4c) - Issue #1691 - Part 3: Finish implementing import meta. https://bugzilla.mozilla.org/show_bug.cgi?id=1427610 (3f4985ce6) - Issue #1691 - Part 4: Finish implementing call import. https://bugzilla.mozilla.org/show_bug.cgi?id=1499140 (7a6dab0b3) - Issue #1691 - Part 5: Don't pre-create module metadata object when compiling. https://bugzilla.mozilla.org/show_bug.cgi?id=1489477 (c965fbdd1) - Issue #1691 - Part 5b: Stop modules from entraining the top-level JSScript. https://bugzilla.mozilla.org/show_bug.cgi?id=1489477 (5c09a3b3c) - Issue #1691 - Part 6a: Support private values which contain pointers to cycle-collected C++ objects https://bugzilla.mozilla.org/show_bug.cgi?id=1342012 (1b811bd71) - Issue #1691 - Part 6b: Initial browser support for dynamic import from module scripts. https://bugzilla.mozilla.org/show_bug.cgi?id=1342012 Factor out script fetch options from script load request classes. https://bugzilla.mozilla.org/show_bug.cgi?id=1480720 Remove support for version parameter from script loader. https://bugzilla.mozilla.org/show_bug.cgi?id=1428745 (86e0057ea) - Issue #1691 - Part 6c: Fix a few issues with the earlier commits. Need PNK_CALL_IMPORT and PNK_IMPORT_META in the node children list or it will abort. When porting ScriptFetchOptions support, I had 2 constructors, I picked the wrong one. Missed adding the preference javascript.options.dynamicImport to all.js. (9a19e9d16) - Issue #1691 - Part 6d: Optimize handling of internally-created Promise objects. https://bugzilla.mozilla.org/show_bug.cgi?id=1358879 The patch uses a different test: PROMISE_FLAG_DEFAULT_REJECT_FUNCTION which doesn't exist in our codebase. It was added in this bug, which appears to be partly complete: https://bugzilla.mozilla.org/show_bug.cgi?id=1313049 (c3daecc21) - Issue #1691 - Part 6e: Fix problems due to divergent codebases. This gets basic dynamic import working. Fix a problem in Part 5b where Mozilla used toGCThing() and we don't. Fix a problem in Part 4 where runtime() returns nullptr in our codebase since it runs on JS Helper thread. We need to get the runtime via runtimeFromAnyThread() instead. (e7d0b58e5) - Issue #1691 - Part 7a: Add a JS API to get the private value for the calling script or module. https://bugzilla.mozilla.org/show_bug.cgi?id=1342012 (62be54216) - Issue #1691 - Part 7b: Make load request element optional. https://bugzilla.mozilla.org/show_bug.cgi?id=1342012 (ba01d99e3) - Issue #1691 - Part 7c: Refactor ModuleScript into ClassicScript class and LoadedScript base class so we can represent all scripts that can perform dynamic import. https://bugzilla.mozilla.org/show_bug.cgi?id=1342012 (41eda05e5) - Issue #1691 - Part 7d: Allow dynamic import in cases where there's no referencing script or module. Support dynamic import from classic scripts by creating ClassicScript objects and associating them with the compiled. https://bugzilla.mozilla.org/show_bug.cgi?id=1342012 This patch is incomplete, some code in ScriptLoader::EvaluateScript() could not be applied for missing dependencies. Part 7e will apply the missing dependencies and finish the patch. (d5d7bb5e4) - Issue #1691 - Part 7e: Dependencies for required to finish part 7d. https://bugzilla.mozilla.org/show_bug.cgi?id=1331662 Reimplement EvaluateString using the ExecutionContext class. https://bugzilla.mozilla.org/show_bug.cgi?id=1316078 Extract redudant code into StartOffThreadParseTask. Use an ExclusiveContext instead of a JSContext in XDR functions. Add a script decoder as a valid off-main-thread parse-task. https://bugzilla.mozilla.org/show_bug.cgi?id=900784 Add nsJSUtils functions for encoding and decoding the bytecode. https://bugzilla.mozilla.org/show_bug.cgi?id=1316081 Add XDRIncrementalEncoder to replace delazified LazyScript in the encoded XDR buffer. Add an XDRIncrementalEncoder instance on the ScriptSource. Expose a new JSAPI to incrementally encode bytecode when it is generated. https://bugzilla.mozilla.org/show_bug.cgi?id=1334091 XDR function use the sourceObject instead of the enclosingScript as argument. (993476283) - Issue #1691 - Part 7f: Split up compile and execute so we can use ClassicScript. https://bugzilla.mozilla.org/show_bug.cgi?id=1342012 Refactor nsJSUtils::ExecutionContext to separate compilation and execution steps and allow extraction of compiled JSScript. https://bugzilla.mozilla.org/show_bug.cgi?id=1366773 Move buffer argument from JS::StartIncrementalEncoding to JS::FinishIncrementalEncoding. (c69a47c39) - Issue #1691 - Part 8: Fix --enable-debug builds and continue dynamic module import changes. https://bugzilla.mozilla.org/show_bug.cgi?id=1342012 Support import from timeout handlers by associating the initiating script with the compiled JSScript. Fix error message that covers all import() failures that don't throw a JS exception. https://bugzilla.mozilla.org/show_bug.cgi?id=1331662 Partial - Replace nsJSUtils::EvaluateString calls by ExecutionContext scopes. Left EvaluateString() in nsXBLProtoImplField.cpp until ExecutionContext errors can be fixed. (1109559a5) - Issue #1691 - Part 9: Make import() work when the active script is in another document. https://bugzilla.mozilla.org/show_bug.cgi?id=1342012 Associate event handler with active script when they are compiled. (be916ef7c) - Issue #1691 - Part 10: Add and use method to annotate CC crashes with a class name. https://bugzilla.mozilla.org/show_bug.cgi?id=1277260 Make PtrInfo into a class and mark it final. Also fix an erroneous debug assert because mBaseURL not set in one code path. (7e056a6f7) - Issue #1691 - Part 11: Fix incorrect reference counting in ModuleScript class. (edb82ec9f) - Issue #1691 - Part 12: Fix return value in ExecScript() and debug assert in ParseTask. https://bugzilla.mozilla.org/show_bug.cgi?id=1331662 Replace nsJSUtils::EvaluateString calls by ExecutionContext scopes. ExecutionContext: The mRetValue is not used even though it is checked in various asserts. This is how it is in the Mozilla code even years later, only the passed in value is used. ParseTask: JoinDecode() and JoinCompile() run the same code but the type is different causing a debug assert when it checks the type Script vs ScriptDecode. (a892a7590) - Issue #1691 - Part 13: Remove MUST_MATCH_TOKEN* macros in Parser. https://bugzilla.mozilla.org/show_bug.cgi?id=1501928 This was helpful in debugging one of the crashes, the macros made debugging a nightmare. (bc895eba9) - Issue #1691 - Part 14: Fix a debug assert and memory leak. PNK_IMPORT_META and PNK_CALL_IMPORT are binary nodes... They function similar to list nodes, so they worked there, but debug mode asserts because of the wrong type. https://bugzilla.mozilla.org/show_bug.cgi?id=1342012 Fixed a memory leak due to missing code in SourceScriptObject::finalize(). Thanks FranklinDM! (79ea755b7) - Issue #1691 - Part 15: Make |new import()| a syntax error. https://bugzilla.mozilla.org/show_bug.cgi?id=1508672 (f2b179156) - Issue #1691 - Part 16: Dynamically imported modules can throw any value as an exception. https://bugzilla.mozilla.org/show_bug.cgi?id=1508672 (1ac1e90b6) - Bug 1432272 - Make Fetch API use the global's base URL instead of the entry document's base URL (62e2fbc4e) - Issue #2218 - Part 1: Add nsExpirationTracker::NotifyEndTransaction(Locked) callbacks for subclasses to know when an aging iteration is complete (fa787f4a6) - Issue #2218 - Part 2: Make SurfaceCache free ImageSurfaceCache objects outside of the lock (93644fd33) - Issue #2073 - Follow-up: Use internal Move instead of std::move for consistency (b7f217e5a) - Issue #2213 - Follow-up: Fix derieved Generator prototypes after previous change (a27e8bf98) - Issue #2173 - Follow-up: Use common ancestor of PNK_(OPT)DOT in ASTSerializer::expression (e31a058ce) - Issue #1894 - Follow-up: Fix return value ordering in IonMonkey nullish coalescing (aece6260f) - Issue #1285 - Follow-up: Correctly handle follow-up compilations of RegExp with named capturing groups (0a74a5758) - Issue #2221 - Enable link-time optimization for Spidermonkey by default if building it shared. (b592711bb) - Issue #1691 - Follow-up: Fix CallSelfHostedFunction deprot introduced by Part 4. (45b34592b) - Issue #1862 - Follow-up: Replace deprecated Harfbuzz functions with current ones. (51426d105) - Issue #1691 - Follow-up: use error message with no arguments for bad import statements (73a99c155) - Issue #2142 - Fold BytecodeEmitter::checkTypeSet into BytecodeEmitter::emitCheck (014ebe8ae) - Issue #2142 - Extend newSuperCall for JSOP_SPREADSUPERCALL (6f56a494e) - Issue #2142 - Change InitPropertyOperation to accept a PropertyName directy and use DefineDataProperty (627d0da7d) - Issue #2142 - Add predicate functions count_if and any_of to ListNode iterator (3b9b111b2) - Issue #2142 - Ensure 'await' is always a restricted identifier when parsing modules (faed047e3) - Issue #2142 - Reduce calls to FindReservedWord when checking for forbidden identifiers during parsing (6abb54ff1) - Issue #2142 - Add internal option for fields, but always true (afa7bddc9) - Issue #2142 - Implement syntax for public/private fields and computed field names (51db22ff2) - Issue #2142 - Improve TokenPos handling in BCE (ab7721e4d) - Issue #2142 - Add PropertyEmitter, ObjectEmitter, ClassEmitter, LexicalScopeEmitter, DefaultEmitter (1b89be6d0) - Issue #2142 - Add FunctionEmitter, FunctionScriptEmitter, and FunctionParamsEmitter with current methods (e6335ded8) - Issue #2142 - Handle fields in derived classes (235ca7794) - Issue #2142 - Factor out PropertyName parsing from Parser::propertyName() (014953c53) - Issue #2142 - Implement ASI for fields (447261cf8) - Issue #2142 - Use JSOP_INITPROP for field initializers (849ab4417) - Issue #2142 - Restrict contents of direct eval in fields (8c6750014) - Issue #2142 - Fix several scoping issues in field initializers (bcb6203e4) - Issue #2142 - Pass through arguments in synthesized constructors for derived classes (1031b1fc4) - Issue #2142 - Emit field keys in correct order (f374ab472) - Issue #2142 - Don't treat PNK_NAME specially emitAssignmentOrInit (f0b06f5ad) - Issue #2142 - Set anonymous function name in field initializer (c20611496) - Issue #2142 - Optimize .initializers scoping and emitter (e0b5528c2) - Issue #2142 - Support SuperProperty in field initializers (b187006a7) - Issue #2142 - Parse and process static class fields (c3b19191f) - Issue #2142 - Track isFieldInitializer on JSScript instead of Scope (22a9d46ef) - Issue #2142 - Implement class static block (1fac189ae) - Issue #2142 - Remove the temporary fields option (ba9647a12) - Issue #2097 - Implement logical assignment operators (10951a169) - Issue #2097 - Handle Logical Assignment in Ion CFG (a7d8cecdb) - Issue #1691 - Follow-up: Fix videojs and potentially other problems. When rewriting the ExecutionContext code in ScriptLoader I accidentally removed some required code. (a1f787fc8) - Issue #2225 - Implement Element.replaceChildren (ae50e9e01) - Issue #1656 - remove vim control lines from js/src (e6ff567de) - Issue #1656 - Remove more vim control lines. (d388e478a) - Issue #1656 - Remove more vim control lines. (c9b8a576d) - Issue #1656 - Remove more vim control lines. (2f117eeca) - Issue #1656 - Remove more vim control lines. (a39fd9e75) - Issue #1656 - Remove more vim control lines. (f1759b33f) - No Issue - Do not parse or return body for XHRs with HEAD/CONNECT method or content-length=0 (84eadbe3c) - Issue #1691 - Follow-up: Ship dynamic module imports enabled by default. (5b7f259ab) Official Pale-Moon changes picked since my last build: - [Pale-Moon] Issue MoonchildProductions/UXP#1451 - Support hunspell as shared library (2be4e3e69) Official Basilisk changes picked since my last build: - [Basilisk] Issue MoonchildProductions/UXP#1451 - Support hunspell as shared library (61874576e) My changes since my last build: - partly import changes from tenfourfox: #651: M1761233 M1687303 M1633019 M1797336 M1799748 M1801102 (fb91afbb4) (ba3e46b17) - follow-up Issue #1691 - Part 6b, fix code that codepath is removed by upstream but remaining here (80d11ebc3) - Issue #2142 - follow-up rev 51db22ff, removing `static` keyword from upstream force-push rev aa6d42e5fc..63a00fdd25 (fa52ac972)

what is the reason? @Tripredacus I respect that but I don't know the reason ...

Do not post a link to that website and do not mention the types of things that are on that website. Even mentioning the names will cause those terms to be indexed by search engines and leading to here. So don't do it, use a generic term. I edited some posts to remove the specific terms and replace them with warez.

Technically, no, you cannot! It does have a link to GitHub for a something called a "warez" as some sort of "warez". But it does not HOST whatever a "warez" is - GitHub is doing the hosting. Semantics, I guess. MSFN does not blanket-ban GitHub links, regardless of the wide array of content, legal or otherwise, hosted via GitHub. At any rate, I still advise the poster to learn from my mistake and remove the link to Thorium's main website.

*I think I have read in the past that this browser was officially supported by Google, right now I can't find information to confirm it

Ah well, if Euronosta is not impressed that says something. jaclaz

It's called signature.

I claim to space the compute boards by 20mm, so here's a 8mm thin liquid cooler for the Lga2011. The preferred coolant would be the less flammable phytane, but only farnesane is mass-produced by Amyris and could also be obtained from Ocotea caparrapi resin chemicalforums I compute with Dowtherm A here, also called Therminol VP-1 and more, because it's better characterized. Melting Flash Boiling Capacity Density Capacity Conductivity Viscosity Coolant point point point J/kg/K kg/m3 MJ/m3/K W/m/K mPa*s ----------------------------------------------------------------------------------------- Farnesane <-79°C +109°C +242°C ~1900 ~750 1.43 0.13 few Phytane <-79°C +160°C? +296°C ~1900 ~765 ~1.45 ~0.13 few Dowtherm A +12°C +110°C +257°C 1658 1036 1.72 0.13 2.1 ----------------------------------------------------------------------------------------- To evacuate <=150W from the Lga2011, 8.7cm3/s unfrozen Dowtherm A enter at +35°C and exit at +45°C, or mean +40°C. With Re=1800, marginally laminar 1.2m/s in D=3mm waste only <<800Pa. 44 biface channels 35mm long and 5mm tall offer 1.5dm2 exchange area. In the laminar flow, heat crosses 0.3mm width /2/3 = 50µm, so 0.13W/m/K drop 3.7K to conduct 150W. The Re<100 laminar 8.7cm3/s flow peaks at 0.20m/s at the channels' center. The 18Mm/s/m2 curvature of the parabolic distribution lets 2.1mPa*s induce 37kPa/m gradient and waste only 1.3kPa over 35mm length. Cu-Cr, Cu-Zr or CuCr1Zr aged for yield >= 310MPa conduct >310W/m/K so the 44 fins 0.5mm wide and 35mm long drop 1.0K over mean 5mm/3 height. The 35mm*35mm base drops 0.6K over 1.5mm thickness. This design keeps the Cpu's top at +45°C (plus the paste's drop), huge margin. It can cool a 205W Lga3647 too, be thinner, have fewer thicker channels. A prototype can etch chemically the elements, or mill them if glued or soldered on a holder. Series production would stamp them. They can then be coated with a filler, Sn or other, and the stack soldered together with pressure, with here undisplayed end pieces for the mounting screws and the pipes. The base is finally milled flat. Marc Schaefer, aka Enthalpy aka Pointertovoid

Some proposals are illustrated here. If it works, a Ddr4 Dimm connector shall pass 2*36 Pci-e lanes to the backplane. It's 142mm wide, so a backplane >1.15m tall hosts columns of 8 compute boards. The compute boads and its rails are thankfully taller. Narrow sockets exist for Bga2011. I considered only the square ones. Multichannel Dram needs dense routing while plugging in a connector a thin board: video cards combine both. If needed, make the board thinner locally. 2 Nvm-e per socket fit easily. The Qpi suffices for a Raid-5 among 4 sockets on one compute board, reading 10-20GB/s for any core successively. Very far from the golden rule, but virtual memory make sense again. Boards with fewer Cpu sockets can join more Nvm-e on Raid. One desktop power supply can feed a socket over a video card cable. A banal supply feeds one socket, a gamer's supply feeds two. Recycled ones are dirt-cheap. Connectors less ridiculous would save room. +12V/0V bars of 2mm*8mm copper feeding 4*150W drop only 6mV each for low ground noise. Connect the supplies' ground at their compute boards. Taylor-made shorter So-dimm were a bad idea. They gain only 50mm over a 1m board. Dram packages are soldered so one must buy them new. Searching better is necessary; in 1Q2023, I found 6usd for 8Gb or 4Gb Ddr4, 13usd for 16Gb, 52usd for twin-die 32Gb: digikey - mouser 4*16b+8b wide with Ecc take 5 packages *4 channels, or 120usd and only 16GB per Cpu socket. Recycled So-dimm cost 50usd for 16GB or 88usd for 32GB. More expensive and powerful Cpu sockets wouldn't get more Dram capacity, Dram speed, network speed. I dislike a compute board 2m long to carry 8*Lga2011, so Dram chips are soldered at the front and back of the compute boards, with the mentioned drawbacks. So are Nvm-e packages, at the rear too if thin enough. Maybe Nvm-e packages assemble several chips, then individual packaging saves height. 12V could provide 1200W and the rails carry them, but I prefer to connect desktop power supplies in series for 24Vdc or 48Vdc. Use a different connector model. But are the converter components cheap? I didn't recheck the diameter of the coolant pipes. The coolant pipes could also run over the socket's "Independent Loading Mechanism", one at each side. The pipes could carry the power too, good excuse for better connectors. 4*Lga2011 as drawn would use So-dimm. Please imagine the 8*Lga2011. Marc Schaefer, aka Enthalpy aka Pointertovoid

There's an enablement patch for x86/32 bit 22H2, kb5015684. I got it here months ago and it's running good so far: https://www.reddit.com/r/Windows10/comments/w7rint/featureupdate_22h2_enablement_package_download/

Today's update: - KB2416447 replaced by KB2572067 (.NET 1.1) - KB2572073 added (.NET 2.0)

UPDATE - KB2478658 replaced by KB2539631 (.NET Framework 2.0) - .NET Framework 3.5 and switchless installers removed I had to remove them as they apparently are against the rules of this board. I'm sorry You can still very easily make switchless installers using Silent .NET Maker. Just remember to add "z" before "2" in the newer updates (ex. KB2539631 should be changed to KBz2539631).

In the first post I described an easy way how to download all updates and switchless installers in just a few clicks. It should be much easier to do now comparing to manually downloading each update one by one

2KDNF11SP1.exe is a switchless installer for .NET 1.1 (+updates) only. Did you use the other one for .NET 2.0 too? How does your HFSVCPACK folder look like?

whoops ... my bad! .. my bad!! I reran hfslip and installed with .nets in HFSVCPACK when I open control panel on the install, to check install/unistall programs, .net 1.1 shows up as uninstallable, but .net2.0 doesn't. does that mean that .net2.0 didn't install? is there a quick way to tell? I don't want to uninstall it, just know it's installed. sorry for my error ... tried to edit out the pic above but couldn't

just ran HFSLIP -- I ran it with Bristols' list plus a few ancient ones of my own, where I can't see where ms replaced them. hfslip built the iso and didn't return any error flags (does it have any?). Then I remembered that I forgot to add the .NET files, so I put your two files in /HF and ran it again. when hfslip got to 2KDNF11SP1.exe (MD5 = 81eee1c8fdd87abb7332431d4e9d349e *2KDNF11SP1.exe, size is 11,648,346 bytes) it stopped hfslip, and produced a red(X) message in case the image doesn't upload, the title is "2KDNF11SP1.EXE" and the message is "/Q is not a valid switch, Type 2KDNF11SP1.exe -h for help." I clicked [ok]. hfslip resumed processing and built the iso. I haven't tried to build a system from it yet. Thought this might be of help. highest regards ...

By the way, there is also another advantage of using 976576 instead of 982524. 976576 can be processed by Silent .NET Maker synthesized while 982524 cannot