Leaderboard

Some months ago I complained about the poor performance of Hotmail after their last update became final. They gave me an URL to access the older version, which works much better with XP compatible browsers. It also solves the problem with Chrome 49. https://outlook.live.com/owa/?path=/fb

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.cf/basilisk/basilisk52-g4.2.win32-git-20190518-c72afc3c8-xpmod.7z Win64 https://o.rths.cf/basilisk/basilisk52-g4.2.win64-git-20190518-c72afc3c8-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom NM28XP build: Win32 https://o.rths.cf/palemoon/palemoon-28.6.0a1.win32-git-20190518-c72afc3c8-xpmod.7z Win64 https://o.rths.cf/palemoon/palemoon-28.6.0a1.win64-git-20190518-c72afc3c8-xpmod.7z Official repo changes since my last build: - When using XRENDER, create Xlib-based offscreen image surfaces. (996887f40) - Issue #1084 - Add null check for URL Bar in the writePlaceholder() method (8b7d91e51) - [PALEMOON] buildHelpMenu() is executed by the shared help menu but not all windows have the AppMenu (f857efc35) - Update sync clear history function to use new clear() API call. (a53ab3f34) - Merge pull request #1086 from zootboy/master (70c5719dc) - Remove deprecated appending of #-moz-resolution from Pale Moon and left over from nsMediaFragmentURIParser.h (c7dc667e6) - Merge pull request #1060 from Ionic/bugfix/scrolling-regression (413ba3bad) - Rip broken telemetry out of the app AUS. (1595ee7da) - Fix scroll bar orientation on MacOS (06f7a03ff) - Map IntersectionObserver rect to the correct viewport. (34d5483ac) - Merge branch 'master' of https://github.com/MoonchildProductions/UXP (f932fb94d) - Implement String.prototype.trimStart and trimEnd. (354c6dcee) - Add nullcheck. (c72afc3c8)

Yes, I tried the final version of .NET 4.8 on Vista just now, and while it could be installed, it unfortunately displays the same behavior as 4.8 Preview: This means that .NET 4.7.2 is the final version that can be used on Windows Vista without these issues, seemingly I did just that, and here are some of the files I got: I then modified the .MSI file with Orca like @artomberus did, and received the same error message when attempting to run the program after installing it... However, this limitation is pretty easy to circumvent using @blackwingcat's PEMaker tool: After modifying and recompiling the .exe file using this tool, that eliminated the "not a valid win32 application" error but sadly, my success was short-lived: So it looks like Paint .NET is a no-go on Vista As far as SP1 goes, .NET Framework 4.7.2 does "require" this, but there is no mention of the Platform Update "requirement" on Microsoft's .NET OS compatibility chart here. Bearing this in mind, the software likely calls for functions introduced in Windows 7's Platform Update, which would explain why it doesn't work in Vista even with .NET Framework 4.7.2 installed... Sadly, no. Downloading the installer and attempting to run it does not work, and extracting it provides no .MSI installer to use/modify, nor are there any available elsewhere on the web, from what I've found:

Thank you very much indeed @Nojus2001 and @Dave-H!

@Radish, Very glad the comment helped. I think a similar situation was part of the solution to the old MU/WU problem where it took hours to display the available updates each month. I'm hoping that @dencorso will chime in to remind us of what the full solution for that problem was found to be. For the IE updates I choose to install, first off I usually wait a month or two after ANY update is released before I even think about installing it. Then, unless it has been flagged either here or at Woody's that the update has a problem, if it is specified for IE11 then I install it. But I NEVER use IE on purpose. I've never installed or used MS Edge. and unless it becomes required for some other part of the OS to function, such as MU/WU, I don't intend to. If that changes, I'll probably treat Edge like I'm currently treating IE. I'll keep it fully updated and never purposely use it. If you choose to use certain software products (such as MS Office products or a particular VPN) you might need additional MS updates, even if they are not specified for those products' use, because of what might be going on in the background, like you discovered trying to play certain videos with Firefox. Cheers and Regards

New New Moon 27 Build! 32bit https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190518-4a37a0ce8-xpmod.7z 32bit SSE https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190518-4a37a0ce8-xpmod-sse.7z 32bit noSSE https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190518-4a37a0ce8-xpmod-ia32.7z 64bit https://o.rths.cf/palemoon/palemoon-27.9.6.win64-git-20190518-4a37a0ce8-xpmod.7z source repo: https://github.com/roytam1/palemoon27 repo changes since my last build: - import change from rmottola/Arctic-Fox: - Bug 1144802 part 1. Add a JSOP_GIMPLICITTHIS which acts like JSOP_IMPLICITTHIS when the script hasPollutedGlobalScope and JSOP_UNDEFINED otherwise. (7b0f4bf1f) - Bug 1144802 part 2. Add JIT and interpreter fast paths for JSOP_GIMPLICITTHIS when the script doesn't have a polluted scope. (7ed943ea9) - Bug 1144802 part 3. Output JSOP_GIMPLICITTHIS whenever we have a JSOP_GETNAME in call context and don't know for a fact that we need an implicit this. (5b77362cc) - Bug 1144802 part 4. Stop returning true from ByteCodeEmitter::needsImplicitThis based on the compileAndGo flag. (3961fb79d) - Bug 1144802 part 5. Flag eval scripts as having a polluted scopechain when inside a with scope. (59c83ceb0) - Bug 1144802 part 6. Remove the scopechain walk in BytecodeEmitter::needsImplicitThis, since consumers should now set hasPollutedGlobalScope as needed. (9df2cdacd) - Bug 1144802 part 7. Remove the scopechain walk in the FunctionBox constructor, since consumers should now set hasPollutedGlobalScope as needed. (4c271aff8) - Bug 1144802 part 8. Drop the scopechain member from GlobalSharedContext, since it's not needed anymore. (dc58199c2) - Bug 1336791 - Allow readelf to print types without parentheses. (Fix FreeBSD) (cef15d006) - pointer style (95722a23a) - Bug 974418 - Fix a TSan race involving the double-elements flag on template objects. (e5eb524b6) - pointer style fix and cleanup (2c44d9120) - Bug 1143802 - Forward jit level information to profiler frontend. (3eefdde2b) - pointer style (8c639a731) - Bug 1143860 - Add column number to PCToLineNumber. (7cdb37ad9) - Bug 1143860 - Deduplicate tracked optimizations when streaming the profile. (2c13cb5fe) - Bug 1145440 - Ship constant names for tracked strategy and outcomes in the profile JSON instead of slightly longer form strings. (3b8cfa5b5) - Bug 1142669 part 6 - Don't inline scripts that are known to inline a lot of code. (73bcdf96d) (38409ecc5) - import changes from tenfourfox: - #551: update certs, pins, TLDs (bc5094b91) (without pins) - #551: one last certbump (cb1e62033) (32174fa57) - import change from rmottola/Arctic-Fox: - Bug 1130439 - Trigger compacting GCs after the user becomes inactive (aa5936222) - Bug 1139429 - Fix ICU configuration for SunOS/OpenSolaris. (a0e4467b4) - Bug 1143521 - Remove IsPoisonedPtr stuff (341899b88) - Bug 1142351 - Part 1: Collect telemetry about deprecated flag argument for String.prototype.{search,match,replace}. (3ad712689) (partly) - Bug 1142351 - Part 2: Warn about deprecated flag argument for String.prototype (66c280d79) - Bug 1083498 - Remove SpiderMonkey's nonstandard behavior for destructuring for..in loops in JS1.7. (428b6a0d1) (4a37a0ce8)

@Blados, @artomberus The best approach on (manually) updating a (manual) install of .NET FW 4.6.1/4.6.2/4.7.0/4.7.1/4.7.2 on Vista SP2 is to have access to a Windows 7 machine, where the exact .NET FW version is manually installed; you should then let WU check for .NET FW related updates and selectively hide upgrades to a higher version, if it's not what you have on the Vista machine (e.g. I understand that on Win7, MS will offer to upgrade you to 4.7.2 (4.8 maybe?) if you've got a previous version installed). Install only the patches offered for the .NET FW version you're interested in, then head to Control Panel => Installed Updates (for .NET FW) and write down the KB numbers of these patches. Track them down in MUC and then proceed to manually install on the Vista machine! My sister has a Win7SP1 x64 laptop, where I "froze" .NET FW to v4.6.1 and, to make a long story short, that was how I was updating my own 4.6.1 install on Vista!

I noticed clicking on the thread title from the index page (https://msfn.org/board/) takes me to the last post. Obviously, the selection of threads is limited to specific one per each sub-forum.

Pale Moon 27 and up don't run on Windows XP, but you've been running FF 52, so I can't think of any reason New Moon 28 won't work for you. Try i430vx's installer: https://msfn.org/board/topic/177125-my-build-of-new-moon-temp-name-aka-pale-moon-fork-targetting-xp/?do=findComment&comment=1163175

Neither could I , but here is some more test material: ShadowSocks is an application very popular in China, because it can be used to connect to specialised servers outside of the GFW and thus circumvent regime implemented censorship ; the windows binary is built on .NET Framework 4.x.x; the last executable that could be launched under Vista SP2 with 4.6.1 (Final) installed is v3.3.4 all the way back from Oct 2016 ; any more recent version will throw an error: Unlike ShareX, Shadowsocks.exe does not come with a *.config file we can patch, you do have to have 4.6.2+ installed to make it launch! In their Wiki it's noted (in Chinese) that .NET FW 4.6.2 is the minimum version required, along with latest Visual C++ 2015 Redistributable; also in their wiki they suggest So I think shadowsocks should be a perfect "test-bed" application for correctly functioning .NET FW 4.6.2/4.7.2[4.8.0?] under Vista SP2... People here with Vista SP2 VMs, the challenge is open!