Leaderboard

Well, hello dere! Still kicking! Just checking in. Will at a later day see how some of my old faves are doing. Hopefully, y'all still kicking too.

After reviewing your link, Juhn Jac is almost certainly correct: Outlook Live recently started using up-to-date JavaScript that Firefox 52.9 cannot deal with because its JavaScript engine is 5 years old. Most PC users of the world will never encounter this issue because they are running newer versions of Windows that are still being supported by major browsers. If you want to continue running Vista, you must either change your email or change your browser. The most up-to-date JavaScript engine of any browser that supports Windows XP or vanilla Vista belongs to Extreme Explorer 360 version 13, based on Chromium 86. If you prefer Firefox-based browsers, then the MyPal 68 beta is worth a try - but you might not be able to download it from GitHub if Firefox 52.9 is the best browser available (JavaScript again). Such browsers are thoroughly discussed in this subforum: https://msfn.org/board/forum/201-browsers-working-on-older-nt-family-oses/ Another possibility for Vista x64 users is the extended kernel for Windows Vista that is discussed in other threads here, which would enable you to use very recent versions of Firefox that do not officially support Vista.

Nice to read that. I know that you said that the emoji support for the browser interface was getting a little complicated but I think I managed to get the font to work. The font I previously shared had "Microsoft Sans Serif" as the name but in your 360EE registry it said "MS Sans Serif". Well, the font that is requested by the browser in your case is indeed different than the one I shared. I realized that when looking at this thread --> https://www.pcreview.co.uk/threads/ms-sans-serif-font.122939/ I've added an Impact font with the ID of the real MS Sans Serif if you want to test in this folder (named "Impact_fakedMSSansSerif.ttf"). I included as well the Original "MS Sans Serif" font (named "sserifee.fon"). Cheers.

@PRB You might want to try again with Firefox now. I just saw a report that 52.9 and even Opera 36 are now working again. If you can confirm that, it means that Microsoft reverted the JavaScript changes and the issue no longer exists (at least for the time being). On the bright side, a number of XP and Vista users have now heard of MyPal for the first time (and there are other websites where 52.9 no longer works very well).

There have been a few reports that the older MyPal 29.3 (based on Pale Moon 29) is sufficiently modernized to solve the specific issue that @PRBhas pointed out here. It can still be found at https://www.mypal-browser.org/. It would not be surprising if roytam1’s Serpent 52 or New Moon 28 could also cope with this change, but I am unable to test myself.

LOL, I thought someone would immediately say that! I thought it would be ArcticFoxie himself, I'm sure he's of the same opinion!

I would never store any passwords in a browser of Russian or Chinese origin. Therefore 360Chrome is fully portable for me!

@Dave-H Try this font --> https://www.mediafire.com/file/op0i6rdpd0mkou1/SegoeUIEmoji_edited.ttf/file Cheers.

Of course they ain't! Don't let your wishes shield you from reality...

I was intrigued by your report , so I connected an external HDD in which I had archived a copy of NDP462-KB3151800-x86-x64-AllOS-ENU.exe originally downloaded Sep 14th 2016; that off-line installer was dual-signed (SHA1+SHA2) on July 15th 2016; running that installer now, after file extraction, generates the familiar error below: I closed that installation attempt and then went to https://dotnet.microsoft.com/download/dotnet-framework/thank-you/net462-offline-installer Direct link is https://go.microsoft.com/fwlink/?linkid=2099468 The latter fetched file ndp462-kb3151800-x86-x64-allos-enu.exe (in small letters this time ) which is only SHA-2 signed on May 1st 2021; my Vista SP2 32-bit system has SHA-2 support installed, so when I ran that second off-line installer, and after file extraction (takes a few seconds, because it scans ALL your drives to choose the one with maximum FREE disk space), I was, surprisingly, presented with: Now, I didn't click Install to go on with the 4.6.2 installation, because I wasn't yet ready to part with my existing, perfectly working, 4.6.1 setup... Perhaps the 4.6.2 installation would have aborted at a later stage, or perhaps NOT... The thing is the updated .NF462 setup doesn't immediately barf when it detects NT6.0; another kind soul with Vista SP2 in a VM could try that new installer to explore whether it "requires special procedures" to complete the installation... FWIW, since this revised setup targets WS2008SP2, I expect it would require a special minimum set of WS2008SP2 updates to be present in your Vista SP2 image...