Leaderboard

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.ml/basilisk/basilisk52-g4.5.win32-git-20191221-fd382bb-uxp-d6baead6c-xpmod.7z Win64 https://o.rths.ml/basilisk/basilisk52-g4.5.win64-git-20191221-fd382bb-uxp-d6baead6c-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.rths.ml/basilisk/basilisk52-g4.5.win32-git-20191221-fd382bb-uxp-d6baead6c-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.rths.ml/palemoon/palemoon-28.9.0a1.win32-git-20191221-806d807dc-uxp-d6baead6c-xpmod.7z Win64 https://o.rths.ml/palemoon/palemoon-28.9.0a1.win64-git-20191221-806d807dc-uxp-d6baead6c-xpmod.7z Official UXP changes since my last build: - Remove Pale Moon from the Unified XUL Platform repository (4e34c5746) - Remove Pale Moon 7zstub (094e74ff6) - Update metadata in UXP 7z-stub installer (e6a3515a1) - Update 7z-stub README to reflect the current state of its use. (e7d4713e0) - Remove Basilisk from the Unified XUL Platform repository (06494f307) - Issue #1323 - Move XULRunner back to topsrcdir (e2de507e0) - Bug 1317376 - Part 1: Remove unreachable code and remnants from the self-hosted implementation. (e23b013ad) - Bug 1317376 - Part 2: Detect Promise self-resolution when resolving through the Promise resolving fast path. (f589ef816) - Bug 336705 - Part 1: Support creating and resolving Promises without resolve/reject functions. (cb732e5fd) - Bug 1336705 - Part 2: Add self-hosting intrinsics for resolving/rejecting Promises and adding reactions. (1fd726c6b) - Bug 1343481 - Part 1: Remove {JSFunction,JSScript,LazyScript}.isGenerator() method. (9163aaebb) - Bug 1343481 - Part 2: Stop using StarGegerator for async function. (f07d5707c) - Bug 1343481 - Part 3: Add JSOP_AWAIT and rename {yieldIndex,yieldOffset} to {yieldAndAwaitIndex,yieldAndAwaitOffset}. (3a3de55aa) - Bug 1343481 - Part 4: Add Add GeneratorObject.{isAfterYield,isAfterAwait}. (73c873200) - Bug 1343481 - Part 5: Rename AsyncFunction-related names in Promise.cpp to explicitly say Async Function. (4f88fc851) - Bug 1343481 - Part 6: Add native functions wrapper for GetInternalError and GetTypeError. (cba3f6142) - Bug 1343481 - Part 7: Add BytecodeEmitter::emitDotGenerator and make yield/await nodes unary. (79b5eb14b) - Bug 1316098 - Optimize out result object allocation for await/return in async function. (d0d9a4f43) - Bug 1344753 - Update for-of stack depth in ControlFlowGenerator::processWhileOrForInLoop. (f5fa6cfea) - Bug 1317389: Change property attributes for generator and async functions to match ES2015/2017. (f87b1b885) - Bug 1331092 - Part 0: Define NOMINMAX to avoid compile error from min/max macro on windows. (5e1f00240) - Bug 1331092 - Part 1: Add Symbol.asyncIterator. (82f9efff9) - Bug 1331092 - Part 2: Implement Async Generator except yield*. (d5086ac3a) - Bug 1331092 - Part 2: Implement Async Generator except yield*. (8e2f6a759) - Bug 1331092 - Part 6: Support JSOP_TOASYNCGEN in JIT. (bbd1fef78) - Bug 1331092 - Part 7: Implement Async Generator yield*. (ef44324d9) - Bug 1331092 - Part 8: Support JSOP_TOASYNCITER in JIT. (580dfb2af) - Bug 1331092 - Part 9: Implement for-await-of. (5bdfdb678) - Bug 1331092 - Part 11: Await on the innerResult.value when innerResult.done is true in yield*. (55728c964) - Bug 1355399 - Switch property retrieval in Async-from-Sync Iterator prototype methods. (63eee6325) - Bug 1364608 - Stash rval in AsyncIteratorClose. (dd1cbde15) - Bug 1379525 - Part 1: Await on the value before yielding or returning inside async generator. (38c1d558a) - Bug 1379525 - Part 2: Properly handle rejection in async-from-sync iteration. (4a5ed79c6) - Bug 1390082 - Implement AsyncGeneratorQueue with simpler array operations. (e0eee318c) - Bug 1352312 - Enable Async Iteration. (c9bddfca7) - Bug 1454285 - Part 1: Specify the current scope when emitting await and .generator. (c66d25512) - Bug 1454285 - Part 2: Disallow using innermostEmitterScope while the value does not match the bytecode environment. (6c3e42ac6) - Merge pull request #1327 from g4jc/async_iteration (07d0bcbf1) - No Issue - Fix indentation and account for system libevent in ipc/chromium/moz.build (a3e93d08d) - Issue #1328 - Part 1: Change default monospace font to Consolas for all localizations where this would be set to Courier New. (342f94295) - Issue #1328 - Part 2: Change tests that require Courier New explicitly. (0f67e7b22) - Issue #1328 - Part 3: Add fuzz to reftests and fix misc other tests. (eea149e73) - Merge branch 'master' of https://github.com/MoonchildProductions/UXP (11ce27f0d) - Issue #1328 - Follow-up: Increase font size for changed monospace fonts. (8220776c9) - Issue #1322 - Part 1: Remove the DOM Promise guts. (fb96b43b5) - Issue #1322 - Part 2: Remove --enable-sm-promise buildconfig switch. (cdea310f1) - Issue #1322 - Part 3: Remove DOM promise interface gunk (d46126240) - Issue #1322 - Part 4: Fix WebIDL.py parser for line endings and wrong IDL name (c7ae364a8) - Merge pull request #1330 from MoonchildProductions/DOM-promise-removal (3332f584c) - Issue #1316 - Reduce compiler warnings in ICU (368170bdc) - Enable layers acceleration by default on GTK platforms. (ce250e9cc) - Issue #1219 - Align computed DOM styles with mainstream behvior. (d6baead6c) Official Pale-Moon changes since my last build: - Remove Platform Code (846fcb459) - Move browser/ to palemoon/ (93c20bef5) - Overlay Pale Moon 28 (1f08c8017) - Version bump (Start Pale Moon 29) (509cbf622) - Add Comm Build System (75dd33577) - Add platform submodule (e573bfa52) - Add a mach stub (20ea829d0) - Update commit pointer (1afb8b2ec) - Re-create README.md (8c1e4fb00) - Add 7zstub (b2577a078) - Merge branch 'master' of https://github.com/MoonchildProductions/Pale-Moon (d8661ecb1) - Make Pale Moon build in a comm configuration (07a6051d2) - Issue #1697 - Add executable bit to scripts. (980687b89) - Merge pull request #1698 from trav90/buildsystem-work (9e6597608) - Issue #1697 - Correct a couple of paths for Mac build (9d6b4534e) - Merge pull request #1699 from adeshkp/mac-build-split-platform (af8643918) - Update gitignore to account for someone being clever with ntfs junctions or other filesystem links (af431d801) - Update platform commit pointer (806d807dc) Official Basilisk changes since my last build: - Add git stuff (db902e7) - Add Comm Build System (3d5a69a) - Update readme (5a343e9) - Add executable bit to scripts (744b3b2) - Add platform submodule (0e3a8df) - Update readme (c2eb348) - Update readme ONE MORE TIME (ab111e9) - Update gitignore to account for someone being clever with ntfs junctions or other filesystem links (67f840a) - Make Basilisk build in a comm configuration (fd382bb) My changes since my last build: - The front-end(PM/BK/etc.)/back-end(UXP Goanna engine) separation works is not happened in my repo for the time being, but for tracking their changes I put my portions over their repo in my working copy. If the rebranding really happens here, front-end/back-end separation works will happen here and there may be an unified front-end repo for my front-end works.

I think I'd just stated the possibilities, not giving out "Yes" or "No". I'm open my mind for having rebranding, or not, by how people want. As I stated before, whatever rebranding happen or not I'll still build binaries for my use. remember my first PM public build is 2017-09-29 (hey, I kept building PM builds over 2 years! in the past, I built my own firefox 3/4 builds from 2010-04-15 to 2012-04-27, and also firefox 1.x to 2.x builds starting from 2006-03-16)

no you don't really need to update it every week. just update it when you feel you need an update for the browser you use. even I build every week, I don't update my "daily-used" copy every week, even I preliminary tested them in separated position.

1.5.13 installed on v1909 VMs and working without messages at logon. Thank you for making Windows 10 palatable for another 6 months. Just sent you another 20 Euro. Hope it helps make your holidays brighter! -Noel

I think that the branding for the three browsers should reflect the main platforms they run on: Borealis -> Neptune (Windows 2000) New Moon -> Whistler (Windows XP) Serpent -> Longhorn (Vista) Visual design isn't my specialty, but I've come up with these potential logos/icons for Longhorn. They could be refined, but software that runs on a Cyrix 6x86 MX doesn't need the fanciest icons:

i read down through all the updates and fixes for the service pack and I found mention of a usb 1.1 mass storage controller. I tried a flash drive and it didn't work. thats about all I know about that. So your saying I should restart in safe mode, remove everything usb from device manager and then install NUSB. I'll give it a shot.

I personally believe the rebrand should take place, as well as sticking to the 28.x (presently New Moon) builds until 29.x becomes unsupported/surpassed by a potential version 30. When it comes to browser names, using code names from older Microsoft products does make sense (and shares a common theme), but I would prefer more original names.

Mathwiz said: > Anyone who finds the suggested "Whistler" branding for NM 28 objectionable, > should let us know now, while there's still time to change it. Seems pretty innocuous to me, > but you never know what might turn folks off unless you ask! Nothing objectionable, but turning off from completely "unknown" browsers without even taking a short look is quite normal. Therefore, to give clueless users at least a tiny hint about origins and intentions, I'd find it helpful to keep stubs like -fox- and -moon- in some way, and add "X" somewhere as hint if the XP-capability is crucial for a build. Of course, not only for completely clueless newbies, but also helpful for the rest of us to easier remember what's what :-)

Anyone who finds the suggested "Whistler" branding for NM 28 objectionable, should let us know now, while there's still time to change it. Seems pretty innocuous to me, but you never know what might turn folks off unless you ask! For the @roytam1 NM browsers that are usually updated each week, the best way to do what you want would be to wait until the version number changes, then download the last build of the previous version. That would be closest to the eventual release version. OTOH, if you always want the latest, greatest version, @i430VX has an installer that takes the drudgery out of updating your browser! I'm sure it doesn't mean the same thing in Chinese, but in Latin, "Roy" means "king;" so for me, "RoyFox" conjures up an image of a fox with a crown on its head! Then again, that might trigger a "raccoon"-like reaction with some folks.... Edited to add that @caliber suggested a nice "RoyFox" logo a few pages back. No crown but it looks nice to me.

Please update it to the next release, v1.6.8; on Monday, Dec 16th, uBlock0-legacy was updated to v1.16.14.12 and, at that time, uB0-updater v1.6.7 was working OK; but next day apparently, GitHub broke it, yet again, by changing their page source ; methinks this wasn't just pure coincidence, but a deliberate attempt at sabotaging this extension ; in any case, it was yours truly () who reported the breakage to the maintainer, https://github.com/JustOff/ublock0-updater/issues/19 who came up with working version 1.6.8 ; BTW, what keeps your installed version 1.6.7 from updating automatically to 1.6.8 ? Festive regards

Rebranding ect.: I've always had a clear opinion myself that different builds and versions should be easily discernible for users. And easily, without needing expert knowledge. Otherwise confusions are intended and will lead to completely unnecessary probs and wasting much time, without any need. Side note: similar prob by the way for K-Meleon. Before the version upgrade to 76.1, all modern Goanna builds declared themselves as "K-Meleon 76", exactly the same as the much older Gecko builds from 2016, which are also "K-Meleon 76". No way for users to tell apart, except at download time, before unzipping and running it (at least the 7z package has a different name, KM-Goanna, but that will quickly be forgotten.) Although our KM main dev had already suggested the logical next version 77 for those much advanced Goanna builds, before vanishing again. But I was rather lonely with that opinion too, and got attacked for it from several fellow KM fans, when daring to mention it 2-3 times. No idea why it's so hard to grasp that such intentional confusions are causing completely unnecessary probs for others and should be avoided, at least if requiring hardly any effort, only insight. Back to here. To me, this current conflict too just demonstrates all over again that almost all extremely one-sided black/white ideologies are just harmful. And again shows that strictly ideological parties aren't ready to move 1mm, no matter how much it harms others - as long as not forced by external circumstances. No chance if not yet harming themselves too much too, strongly enough, beyond their own limit. Luckily, this point and insight seems to finally be reached now - Yay! :D Tobin has done a GREAT step forward, although it's clear it's not a general change of attitude or end of war, but that doesn't matter. It's still a very positive and acceptable step forward (for now), much more as could be expected, with no strings attached (it seems, and hopefully no trojan horse) And finally there's also a real chance to move a bit forward from the other side too, taking the outstretched helpful hand for the benefit of both, and for less expert users too :-) Regardless that fundamental opinions and attitudes never change, but solving single issues independently is still possible and helps all sides!

I'm sorry LoneCrusader but by invoking the bsd-wip github issue you have lost any credibility among any of us over here. I will take responsibility for what I said on the Pale Moon forums and in my channel. I even take responsibility for what I said in that github issue BUT in THAT CASE I was in the right and there is no denying that from any rational mind. Could a word order change have not evoked such a disproportionate response from them? I have asked that question many times since then. I want to say yes but I know those bsd people are batshit insane. They don't respect intellectual property OR software licenses wanting to treat everything as public domain and/or theirs without cause and are at a level of fanaticism that outshines even my self. So no. You don't get to cite that as a valid argument against me to promote blatant anti-Tobinism. I won't stand for it. You're done. Fortunately for the rest of everyone who isn't you, I am not going to let that impact the start of what I hope will be better times. So to everyone else, nothing has been impacted by LoneCrusader's machinations. I stand by what I have offered and suggested.

I think you'll be very impressed. It's been my exclusive browser at home since mid-October. ALL of these forks (and ALL the original non-fork bases) have a delayed load for the VERY FIRST load after a computer reboot and allowed cpu idle after reboot. I find that this "first load" is fastest with Arctic Fox then any of the others. The SECOND load is never an issue, loads quick and snappy, but the VERY FIRST load is lengthier.

@roytam1 Thanks ! By the way, I update my NM and Basilisk/Serpent every week for the simple reason that it always works flawlessly. Also be informed that ublock origin legacy has been updated to version 1.16.4.12 https://github.com/gorhill/uBlock/releases

Well, it's the little things, the main thing that the job is done. Thanks.

new ArcticFox win32 test build is uploaded: http://o.rths.ml/gpc/files1.rt/arcticfox-27.9.19.win32-20191221.7z - Bug 1134518 - Add test to ensure we don't lose shistory entries when switching a browser's remoteness r=Mossop (f7bd1b4e2) - Bug 1134518 - Use the globalMM for ContentTask's frame script to prevent it from being loaded twice into a docShell swapped to another browser window r=bustage (da4f3899c) - Bug 883609 - Porting tests to new Session Restore backup mechanism;r=ttaubert (f53b11a6f) - Bug 1134518 - Add xpcshell test for shistory caps on clean shutdown and fix existing tests r=Yoric (3ed696a4c) - Bug 1077738: Retain whether history entries are set to persist in session history and restore that. r=smacleod (a0be00dc4) - update (2959bddc8) - Merge pull request #19 from wicknix/master-good (cda043440) - Merge pull request #20 from rmottola/master (ed9f72c2e) - fix duplicated IsWin10OrLater() function (02510748c) - add missing bit of Bug 1134280 - Get rid of Tag() - patch 1 - Is{HTML,XUL,MathML,SVG}Element and IsAnyOf{HTML,XUL,MathML,SVG}Elements, r=smaug (4b86381cc) - Bug 960959 - Use RunState to keep track of the SessionFile's closed status r=yoric (a4cb3aaa3) - remove telemetry initialization part, not needed anyway: removes warning (dd0ef756d) - Bug 1134518 - Send a state object instead of a string to SessionWorker.write() r=Yoric (bd5b96e4d) - Bug 1157235 - Remove unused sessionstore-state-write notification r=Yoric (884843b11) - Bug 1150529 - Remove code for expired telemetry histograms r=Yoric (b86b58e55) - add specific stuff that could hurt mac (156375c79) - clean (904cbaa94) - Bug 1073502 - Restore closed windows even when there are no open windows on startup r=yoric (2c12eea64) - Bug 940777 - Simplify about:blank handling in session restore (r=ttaubert) (5298de7ed) - Bug 1135498 - Get rid of the unused browser.__SS_restore_data property r=smacleod (a87fabb3f) - Bug 923315 - Ensure that sessionstore.js writes don't interfere with browser_upgrade_backup.js r=yoric (31c6a52c0) - Bug 883609 - Porting tests to new Session Restore backup mechanism;r=ttaubert (7c04c1156) - Bug 1107941 - Removing old upgrade backups if too many exist. Max upgrade backups is defined in preferences. Tested with mochi tests. r=Yoric (857fa2844) - Bug 1134518 - Cap shistory entries in the SessionWorker when shutting down r=Yoric (f0a9f43ac) - Bug 1100223 - Make calling loadURI() on pending tabs work as expected by marking the tab as no longer pending and simply waiting for the restoration to finish r=billm (5f4f766b7) - Bug 1152341 - Failure to read one of the session file candidates shouldn't stop us from trying further r=Yoric (ff1bccd2f) - Bug 1034075 - Add more details to SessionFile AsyncShutdown blocker. r=ttaubert (fc0aace02) - Bug 1031298 - Add a histogram for counting unrecoverable sessions. r=yoric (95b377fef) - more stuff to do (044d0dbff) - revert default of showQuitWarning because it exposes a bug which corrupts the profile or session storage (714e4eb78) - Bug 1056443 - Use correct URL in location bar when switching processes (r=ttaubert) (7e6a54793) - Bug 1109875 - When unloading a frameLoader flush all pending state changes by sending a final update message r=billm (4264bb7d1) - Bug 1161928 - Move epoch handling from ContentRestore.jsm to content-sessionStore.js r=billm (9bc20bf8a) - Bug 1145942 - Use the frame message manager to revive crashed tabs upon navigation r=billm (a2ee3704d) - Bug 1161928 - Require an epoch (managed in the parent) included in every message sent by the frame script to get rid of TabState.flush() calls in restoreTab() r=billm (11a126155) - Bug 1169892 - Avoid extra round-trip when a pending tab is reloaded r=billm (569786f54) - Bug 1125411 - OSX: turn CoreLocation provider on, r=cpeterson Also, expose this setting in about:config (fe7fb5620) - Bug 1136956 - Set CoreLocation provider to non-release only in firefox.js. - r=cpeterson (7e971cf02) - update (110be9f3f) - Merge remote-tracking branch 'upstream/devel' into fix-winbuild (11f9fe3b2)

The "branding" should be treaded lightly. I used GreenBrowser + Proxomitron exclusively from 2003/2004 all the way thru 2017/2018. Tabbed browsing using the IE6 engine long before tabbed IE7 showed up (company forced IE at the time). Company would prevent "installs" but I could run "portable" apps without issue (don't tell the IT guy). That worked for me for a VERY long time. But... Proxomitron was "high maintenance". I was fine with all of the "maintenance" - it was the web MY WAY and not the way that "script kiddies" threw it at me. But... It became too much of a hassle to edit and tweak for a couple credit card websites at the time. That led me to abandoning GreenBrowser + Proxomitron. My search led me through Maxthon, SlimBrowser, Vivaldi, Chrome, Chromium, Iron, Opera, Firefox, Flock, Waterfox, Icefox, IceDragon, Avant, Sleipnir, among many others I'm sure that I'm forgetting as I look back. Sleipnir and Chromium lasted the longest as far as my exclusives at the time. I eventually landed on a precursor (?) to New Moon. I forget the name of it but the "branding" was a RACCOON waiving his paw. Sounds "trivial" perhaps, but the RACCOON turned me away from that browser. Despite its functionality meeting ALL of my needs. The "branding" cut my time short with my trial of that browser. My home CPU is an i7 and came with Win 10 LTSB - would never do anything 10 without it being LTSB. But I opted to keep XP x64 instead. My computer can "handle" more resource-hungry web browsers - but it is NOT my "preference". So I ended up still hunting and stumbled into Roytam's builds. Ran v28 for a while, but reverted in favor of v27. Then arrived Arctic Fox Win32 - been my exclusive ever since. Edit: I'll add this. One of my gripes against v28 is because I do *not* 'want' to update each and every week. That borders again on "high maintenance". I would prefer kind of knowing which weekly release is best associated with the "stable" upstream versus the "nightly" upstream. I don't really have a need to update my browser each and every week.

Admittedly, there's zero benefit to me from new branding. At best, we'll get some spiffy new icons, and new artwork in Help / About, but the core functionality of our UXP-derived browsers isn't changing. The difference I see is that this time, @Matt A. Tobin is offering to do a good portion of the necessary work. And I don't see that we're sacrificing anything; if we are, please enlighten me. I'd be much more dubious about this if I though we were losing anything concrete .

I use Win10 at work but use XP x86, XP x64, and 2003 x86 at home. I seem to prefer a build that nobody here talks about so I finally created an account versus just watching and reading (often quite an entertaining read). I use Roytam's ARCTIC FOX build pretty much exclusively at home (a portable Chromium v48 runs my YouTube-to-bigscreen-TV box). I hope that ARCTIC FOX doesn't get lost in all of this. LOVE THE WORK, ROYTAM. Please don't let any of the "back-and-forth" discourage you in any way

Learned a new word today! Although in these parts, we still call it, uh, a still... It's a bit belated, but I wanted to say thanks for that tip! It's finally given me a way to maintain multiple Firefox versions on the same PC, each with its own profile, without a kludge like setting up separate Windows users (and having to log out and back in) to access each version. Just make sure to include the intended FF version in the name of each profile you set up. Very useful when you want to test FF versions ranging from 45 through Quantum to "Firefox Browser" (or whatever the name of the week is). Even on XP, I now have FF 45 SSE, FF 52 ESR, and FF 53 (patched to run with XomPie) all coexisting in relative peace.

I tend to agree. Perhaps @dencorso can move the last few dozen posts about branding to their own thread? Be careful, though; there are a few unrelated posts strewn among them!

@dencorso For me it makes sense to make AT LEAST one separate topic for brandings, names and icons... and you know I think about splitting posts

The largest the logo icon would be anywhere is 256x256 which is the second largest size. At that resolution it doesn't look as chunky as it does in the 512 size. But let's see..

There is a whole loose association of drones out there that all day long and everywhere they can they repeat the mantra of "Old and Insecure" about Pale Moon and allied projects. Some with a little more brain power might use the phrase "Poor imitation" when referring to us and we have indeed made SOME bad decisions over the years and some six years ago a number of rookie mistakes when we declared independence for version 25. There is nothing wrong with that if you learn from them. s*** happens. Least we forget that the moebius codebase for us was a 7 month mistake in that unless we compromised fundamentally the code for other applications aside from the Firefox application code native to that codebase none of it would ever happen. Just porting Pale Moon to moebius would have gone too far in what had to change to make it run and it would have been a massive disaster and might have killed the project out right when said and done. Now I know roytam1 is producing builds of that codebase so you might not know or see that but that is only because the firefox application code matches and is native to it. After 53 stuff went nuts with several refactor storms of fundamental code in how XUL Applications work. That is why UXP was restarted.

Sometimes, the problem of the uBlock0-legacy toolbar button going AWAL after a browser restart, especially on browsers that also support Web Extensions, can be mitigated by setting (in about:config): extensions.ublock0.forceLegacyToolbarButton;true The "LegacyToolbarButton" of "legacy" uB0 might better co-exist in the toolbar with adjacent buttons from other XUL extensions!

It is true. The online installer downloads and launches, and on Win 7 it runs fine. But on XP this happens: The offline installers at the links @Bersaglio posts work fine on XP.

But still write the model of the motherboard, maybe there is an older video card, for example Rageon IGP, they need older drivers, in 14.4 these video cards are no longer supported.

... Apologies are in order ; I was testing previously in my current (dirty) Serpent 52.9.0 profile (and in my dirty NM28 one...); I decided to take a dose of my own medication () and checked your issue on a newly created (fresh) Serpent 52.9.0 profile (latest win32 build, 2019.12.13) and, sure enough, I was able to reproduce! The troubleshooting was easy, as is the fix: Change both Firefox and Gecko compatModes to true (default is false) and reload the page: general.useragent.compatMode.firefox;true general.useragent.compatMode.gecko;true You should be good then! It appears the Adobe site doesn't actually approve of Mozilla/5.0 (Windows NT 6.0; rv:68.9) Goanna/4.4 Basilisk/20191212 which is the default UA (on Vista) of latest St52 build... BTW, @roytam1 , I noticed something that looks bizarre to me, latest Serpent 52.9.0 reports its buildID (20191212) inside the UA, is that normal? Was this changed upstream or by you? I recall it used to report its version number, Basilisk/52.9.0... Sadly, I would expect many more sites to become broken with the current default UA string (no Gecko/Firefox parts) when they see a browser version in the "20 millions" range, that they probably don't know how to handle... I'm tired/lazy now to do a proper bisection of this issue, FWIW a much older build of Serpent 52.9.0 (buildID 20190531001847) reports by default Mozilla/5.0 (Windows NT 6.0; rv:60.9) Goanna/4.2 Basilisk/52.9.0 So please, do kindly investigate this (regression?) ...

I don't have a "Remote Desktop" entry inside WFW's exceptions, only "Remote Assistance", which is not selected (and thus still blocked): Isn't that the norm with Windows 10 ? Every user accessible setting that was fairly easy to locate in previous Windows versions has been now deeply buried/hidden behind a labyrinth of configuration wizards and clicks (which often get relocated anew with major Win10 semi-annual up(-de)grades) ... Have you checked it with Dependency Walker yet? Besides, since it checks for installed Windows Updates, it probably needs Admin privileges, so better run from within an Administrator's account...

... However, works OK on Windows Vista SP2 32-bit: As posted already, the devs themselves claim: It appears the app only checks for the presence (or absence) of a certain M$ update (for WS2008SP2 it's KB4499180); myself, I had already disabled some time ago the "Routing and Remote Access" Windows service... ; also achievable via a GUI setting:

Hi Everyone, I'm Gergely, computer scientist and hardware enthusiast from Budapest, Hungary. I've been using the forum for a while without contributing so i thought it was time I added something to discussion. I hope it will be useful :) Thanks

Yugo over to South America and get some Chile.

Tried it on Vista SP2 32-bit and yes, AERO works nicely ; so does the Task Manager; but every tab crashes when it tries to load ; I've seen this happen when I tried to run Google Chrome 51 (release) under Vista... My wholehearted wishes towards the success of this project (but it'd be a shame if it succeeds on XP but not on Vista... ) EDIT: Checking with dependency walker, it appears there are still missing function calls under Vista SP2; e.g. chrome_child.dll looks for function QueryUnbiasedInterruptTime in Vista's kernel32.dll system file; but that function requires Win7+'s version of kernel32.dll...