Leaderboard

Vista guru WinClient5270 stated December 27

The usual one is here - https://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html You have to accept the licence agreement as usual, but annoyingly you now also have to log in to Oracle as well, which means you have to register with them. It's not a big issue to do that though, and I've never had spam from them or anything like that. There may well be other places you can get the file if you don't want to do that. HTH.

eset re-released last working version for xp and the new isnt compatible anymore new 12.1.34 certificate date is different, i installed the old with a 120 days promo key and works good just use a little bit more memory ram https://support.eset.com/en/download-and-install-eset-offline-or-install-older-versions-of-eset-products

you may need to exchange their position instead.

FWIW, Java 8 Update 241 seems to be now out, I was just prompted to update to it on Windows 10.

Hi, I am a registered user of Aero Glass. I use this for Windows 8.1. I would like to share an idea I had for Aero Glass: Integrating Aero Glass parameters into theme system. Here's all you would need: 1) Windows variable expansion We need Aero Glass to support expansion of environment variables. Maybe some whitelist or sanitization would be required. I.e. Aero Glass doesn't like it when I set CustomThemeAtlas to %ResourceDir%\Atlas\whatever.png. I must instead always write the full path as follows: C:\Windows\Resources\Atlas\whatever.png 2) Registry keys that Aero Glass uses read from the msstyles file or a corresponding file (the real magic!) Any msstyles for 8.1+ which is made with Aero Glass in mind usually ships with a .reg file. It would be great if Aero Glass were updated with one feature. There are two possible routes I can think of going: Reading Aero Glass config keys from the theme file. I.e. [AeroGlassStyles] CustomThemeAtlas=Something TextGlowMode=Something However, this might present one issue which I can think of: Windows might sanitize the .theme file in some cases. I recall setting aerolite.msstyles and coming back to aerolite.msstyles.msstyles. If this will truly prove to be an issue, we check which msstyles file is defined in the theme and look for an existing .aeroglass file or something inside the same directory. I came up with this idea originally and considered executing some assumed .reg file, but that's a bit more dangerous. A non-registry file in some custom format specifically for Aero Glass would probably be a better bet. Let me know what you think. Aero Glass is already very handy, but I feel like this would make it way better. -Dmitri Edit: As for users who wish not to have their Aero Glass reg settings tampered with by .theme or .msstyles, you can simply add a DWORD in the usual place called DisallowThemeConfig or something. By default, it would be 0, but users who prefer to have their existing settings preserved can always add this registry key and set it to 1. This will not be an issue at all since the user who had custom Aero Glass preferences uses regedit, regardless.

GitHub relies way too much on the UA, and none of our browsers provides GitHub with a suitable UA out of the box (or .7z). Well, Serpent 52 does, but only in "native" move (not in FF-compatible mode). So Iset an SSUAO with Serpent 52's native UA string, Mozilla/5.0 (Windows NT 6.1; rv:52.0) Goanna/4.4 Basilisk/52.9.0, for github.com (to be consistent and safe, I also set the same SSUAO for githubassets.com and githubusercontent.com, although I don't think those are strictly necessary). Note that FF 60.9 also works, but the MCP's latest browsers now default to FF 68.9, which doesn't work (unless you're running a Quantum browser). It's nonsense like this that makes me somewhat sympathetic to what Google is proposing to do with user agents. Web sites should base their functionality on the capabilities of the browser, not its version or what OS it's running on. I've been wondering the same thing. My first thought was that the vulnerability probably affects versions based on FF 49, when the JS engine was rewritten, or later; if so, then FF 45, NM 27, ArcticFox, etc. wouldn't be vulnerable. But as you say, the javascript.options.ion pref does exist in those older browser versions, so I'm not all that confident about that assessment.

Update: I just downloaded Microsoft/Rovi EPG data for over-the-air channels extending to 6 PM January 14.

Hi everyone. I'm the author of Chromium XP (version 76.0.3771.0). I couldn't register here when I started but FranceBB suggested I try again tonight so now I'm available on here. You can also find posts by me on the Tao Kaizen forum. My post history on there -> https://browser.taokaizen.com/forum/search.php?author_id=848&sr=posts