Leaderboard

After moving the profile from 51 to 52 ESR two settings were missing: media.gmp-eme-adobe.enabled = true media.gmp-eme-adobe.visible = true After adding these two everything seems to be working, for now.

he will be missed. He helped so many people around the world during his lifetime, and he will always be remembered

Oh no, not again. Sigh :( Could it be bandwith-related? But guess doesn't matter if it's only the domain name, not the hosting server... no clue of such stuff. But I still keep suspecting that the original browser names in your zip packages are problematic! Whether that contributes to those domain probs or not, but sooner or later you'll have to rename them anyway, so the sooner the better. Am glad that KM-Goanna already has a unique name, although Dorian welcomed your builds very much. But who except a few insiders know this?

Is something up with o.rths.cf today? I keep getting either a 503 error or a redirect to a "Girls and their Webcam" page

Don't give up so easily; the problem is simply that @roytam1's version numbers have gotten ahead of what the language packs support. At one time @VistaLover posted instructions for fixing a language pack to work with a newer version: Or if that's too much, you could simply download @roytam1's last version 28.7 build of New Moon at https://rtfreesoft.blogspot.com/2019/08/weekly-browser-binaries-20190817.html & install the language pack in that version. (You aren't required to always use the very latest NM version!)

Ya know... I would probably be saying the same thing right now... but I kept at it. When I installed Avast, the default method... it installed everything it had. Bad move on their part, because it kept rendering my network unusable. I called their Premium Tech Support... and they basically told me XP is dead and I had better upgrade my OS. I told them I like XP, and I pay 30 people to use those 64bit windoze on 30 or so machines. I prefer XP. And so, if you want to use Avast on Windows XP, don't call the tech support. What I did was select the custom Install option, and unselected everything. Then the installation went like it should have. There was a small problem getting new virus definitions, but I eventually got them. All in one night. They really are making it hard for us XP users. I will say that I picked up 10 machine licenses for Avast for 34.98 I think. That's all Paypal is showing I paid. Malwarebytes... would have cost $400 for 10 machines. They do not appear to have a phone number you can call, in the event you need to talk to someone in the company. Avast does. I called it even though I was using the Free product. (Sure they were $1/hour Filipinos, but they seem to have been trained.)

my 45esr build has same mechanism as nm27 does. related rev: https://github.com/roytam1/mozilla45esr/commit/18929e06248829cb89bdef39b2b61e6ae2895e16

OT really, but Chrome required SSE2 long before that (see this 5-year-old post).

Actually, I never said that; what I said was: i.e. I couldn't be sure off the top of my head whether VP9 support is present in Fx 48; I had to search about this, Implement VP9 video decoder in Firefox suggests VP9 codec support landed in Fx 28, ergo is indeed present in Firefox 48 . In any case, I've instructed you how to tell the video codec used in the clip reproduced in youtube's HTML5 embedded player; based on your report (and my search), VP8+VP9 ones should be OK; h264 (avc1) wouldn't play How one's own clips have been originally encoded and packaged (in what media container...) prior to uploading them to youtube is kind of a moot point, because once the original encodes reach yt's servers, they are being re-encoded (re-coded and/or trans-coded) to several different formats/resolutions, to be able to meet yt's dynamic streaming requirements; you can easily check this fact by using one of the several "youtube downloading" apps (e.g. the CLI youtube-dl) and see how your originally uploaded video (in a defined resolution, bitrate, container, etc) is now available in several "qualities". Google have recently (Aug 9th 2019) removed their very useful youtube/HTML5 test page, http://web.archive.org/web/20190805082454/https://www.youtube.com/html5 which was invaluable in troubleshooting HTML5 video playback in browsers (they've replaced it with https://www.youtube.com/supported_browsers and I suppose the reasoning behind the original's removal is that Google now only support latest versions of Firefox, Google Chrome, Edge, Opera - all these browsers had been, since long ago, passing the tests extant in that previous page with flying colours; of course, they don't care about older unsupported versions of browsers on unsupported OSes... ). As I said, the procedure outlined in the first post of this thread was tailored, tried, and known to successfully work in Firefox ESR 52, the last released for XP (but with an SSE2 capable processor); Fx 48.0.2 is not Fx ESR 52.9.1, so there might be other factors why the procedure doesn't yield the expected result in your case (???...) Perhaps some of the documented about:config prefs need to be modified for Fx 48? Some other(s) missing? ... Hard to tell; it would help if other SSE-only XP users could test and report back (to rule out it just isn't you..); @looking4awayout, would you possibly care to oblige, please...? Firefox 48 was at a peculiar spot with regards to Adobe Primetime CDM; Adobe had signaled Mozilla that their closed-source module wouldn't be able to be used on XP for its original purpose, i.e. decrypt DRM content, and that they (Adobe) would only continue its development targeting Vista onwards... The module itself had some unresolved bugs on XP machines that Adobe weren't inclined to fix; Mozilla OTOH did not have at the time a concrete plan what to do with it; they swayed between leaving it visible and enabled on XP (and Vista OEM) for MP4 decoding purposes, not downloading it by default on XP, hiding it completely on XP (just like they did with WidevineCDM) etc... So, as to what extent was/is AP CDM supposed to work in Fx 48, I can't honestly be sure... The module was at one stage upgraded from version 15 to 17 (16 was only an interim update for 64-bit Firefox), and then EOL'ed in favour of WidevineCDM; v17 had lesser bugs on XP, Mozilla decided to keep it alive a bit longer, until Fx 51; Fx 52 did not come with official support, nor would it download it by default; finally, the underlying support code was completely removed from the codebase in Firefox 53.0. Pending reports from other SSE-only users, I'd speculate that your failure is caused by the CDM's inferred dependency on a SSE2 CPU; while the browser itself may be fine with just SSE, the module might be needing SSE2 instruction set to function properly... I tried to find documentation to sustain my claim, but, sadly, Adobe have now removed almost everything related to the CDM ("help.adobe.com/en_US/primetime/drm/HTML5_CDM" now redirects to a recent page ); I stumbled upon a blog article by some Russian guy, https://weekly-geekly.github.io/articles/373803/index.html it's quite long, but inside it there's this part ... which I interpreted to mean: "set this pref to false, unless you have an SSE2 CPU and the Adobe Primetime CDM installed" ; so my bet is on Primetime requiring SSE2... It's quite a long shot, but perhaps you might try the previous version of the module, version 15, accessed via https://cdmdownload.adobe.com/firefox/win/x86/primetime_gmp_win_x86_gmc_30527.1.zip (if it doesn't need SSE2, then you might have a chance...) You are not left without other options ; several members here on SSE-only processors use @roytam1's Firefox ESR 45.x.x fork (but I'm not sure whether he has modded it for h264 support under XP) and New Moon 27-SSE; the latter does indeed come with h264+aac support, courtesy of custom LAV files you have to download separately and place inside NM27's main folder - just be sure to download the SSE-only flavour of the LAV .dlls (and I'm sure you know already, but security-wise, official Firefox ESR 45.9.0 is more secure than Firefox 48.0.2 ). Hope I've helped a little...

This assumption couldn't be more wrong... Youtube (i.e. Google) employ a variety of streaming methodologies and combinations of video+audio codecs, there's not a one-size-fits-all philosophy here... The older VP8 video codec is natively supported in Firefox, so is the newer VP9, but I'm unsure about its support in Fx 48 that you're using ; Firefox also supports natively the very widely used h264 (AVC1) video codec, but only on Vista SP2 (with platform update supplement); h264 support in Firefox implies Windows Media Foundation (WMF) framework, an OS feature absent in XP; the use of Adobe Primetime CDM in Firefox under XP is meant exactly to mitigate this missing OS feature, since the CDM comes with its own h264 decoder, which the browser can then use to decode unencrypted MP4 video... Right-clicking the Youtube embedded HTML5 player and then choosing "Stats for nerds" will tell you what codecs are being used in the streamed video; Additionally, MPEG-DASH streaming in Youtube (notably the high resolutions) requires the browser to support Media Sourse Extensions (MSE), but not all Youtube videos use that, some use the older "progressive download" type of streams; OTOH, live Youtube streams (may) use AppleHLS streams; so no, if one clip plays, it's not a given all the rest would also play... @vipejc is correct; YouTube have completely killed their Flash embedded player; I suspect those "older" clips that do play are in the older VP8 codec, supported natively in Firefox... If you head to about:addons/plugins (and even about:plugins), can you spot an entry for the Adobe Primetime CDM? if yes, is it always enabled? If there isn't an entry for it, something's gone awry in its proper installation... Any reason why not using Firefox ESR 52.9.1 (on which the procedure is known to work)?

As time went on, especially with the advent of Web 2.0 (although the roots go back into the late 90s) things became "cookie cutter" in terms of design. Especially with the web, where webmasters no longer will host large portions of functionality on their own servers, and will thus rely on the speeds of other websites to load the scripts needed to show theirs. This was never recommended but you'd be hard pressed to find a website that doesn't do this. And then websites will use pre-made packages for things, which contain way more bloat than needed. I have javascript disabled by default on most of my browsers for general web use... do you know that there are websites that will not show any text or pictures if javascript is disabled? The pre-made packages is also a problem with web development. As pointed out in the article, a simple program may also include a driver for an Xbox 360 controller. A developer may find one thing and just stick it into their program, even if they only need 1% of the entire package. It wouldn't be an issue if this bloat was not being noticed. It is noticed because programs are behaving badly. And the general run-of-the-mill machine has not maintained the rapid climb of memory and cpu speeds. The low-end devices make up the majority of any given retail market, yet the programs are made to run best on high-end systems. Manufacturers are also making mistakes. Notebooks shipping with 5400RPM HDDs... and I can tell you that standards of BIOS/UEFI are not being followed by the companies responsible for that. Its all bad and has been an issue for quite a while now, and often it seems like I am just old man yells at cloud.

He was a amazing man , Of course a good friend . It is honor for me that i once worked with him in some project and learned many thing from him. He was pioneer in patching OSes beyond their limit . He was always straight forward which is rare in today's engineer . I cannot say anything , i am crying . Heck even i am so late , as i was offline for long . We will definitely miss him. RIP

... It looks as though the BETA channel has lagged behind the stable release one... https://desktop.telegram.org/changelog#beta-version By visiting their official GitHub repository, https://github.com/telegramdesktop/tdesktop/releases the latest stable release posted there is at version 1.8.11 (updated a mere two hours ago...) That same version can be obtained by visiting the main site: https://desktop.telegram.org/ At least on their GitHub repo, https://github.com/telegramdesktop/tdesktop#supported-systems suggests Windows XP as being still supported Though not a Telegram user, I decided to conduct some tests here, on Vista SP2 32-bit; I fetched the "portable" 1.8.10 package from GitHub, it had no issues launching: As you see, I, too, was greeted by the red header with the warning, but the behaviour of the app itself contradicts that warning, as it's automatically downloading (in the background) the update to the newer version; once I click UPDATE TELEGRAM, the app is restarted to latest version 1.8.11: Are you saying this is no longer possible under XP? In any case, if I choose to hide the red header here (by clicking the white X), this option is honoured and it isn't displayed anymore in future relaunches of the app... Generally speaking, when still running XP or Vista, it's a dead certainty that currently working software will cease to function sometime in the near (or, hopefully, not so near) future; this will soon-ish become also true for Windows 7, though I suspect the deprecation of this very popular Win OS will come much slower compared to Vista and, to a lesser extent, XP... OT: I have British and Greek friends in the UK with whom I communicate frequently ; I was under the impression DAB broadcasts used as high a bitrate as 192kbps, but employing the less efficient audio codec MP2... Anyhow, FM analog broadcast in the UK is slated for the ax... WRT Capital London: On occasion, I also like to listen to this commercial radio station (although I shouldn't really be listening from overseas... ); their public online stream is indeed abysmal, only HE-AACv1@48kbps (adequate, I guess, for mobile devices and poor laptop speakers); there's a higher quality - non public - stream of theirs at http://media-ice.musicradio.com:80/CapitalMP3 This is in high contrast to BBC Radio streams which, if inside the UK, are offered as AAC LC@320kbps Cheers

I am glad that he had found friends here. I never really knew the extent of all of his Win9x work. My current desktop can still boot into Win9x because of him, although, I haven't in a while. I would like to try to provide some closure for others so I'll give a timeline of what happened. You may or may not have known that my father had heart issues. He had a mild heart attack in his 40s. August 19th: Goes in for angiogram, gets fast tracked for triple bypass surgery. He left me a message midday about it and I called him that evening. We discussed the options they gave him and he seemed settled on the bypass surgery. August 21st: Has the surgery. Gets out of surgery, doctor tells me take he handled it well. August 24th: First time I was able to contact him on the phone after the surgery. He seemed well but certainly worn-down after the surgery. August 25th: Had a heart attack (cardiac event). Survived, but apparently it was not a good situation. I was able to talk to him that evening (I think, it could have been the next day). Got the impression that his diabetes and insulin resistance played a major role in the incident. August 28th: Last night I get to talk to him. I made plans to come down to see him on the 30th. August 29th: Situation escalates, possible infection/sepsis. August 30th-September 2nd: He is heavily sedated for the pain. But things seem stable. Not good, but stable. I return home and hope for the best. September 3-7th: Situation goes back and forth, fluid buildup leads to treatment for infection. Ultimately, the infection is treatable but the sepsis is not. September 9th: Palliative care nurse contacts me and I go back down that afternoon. Situation is getting worse. September 10th: Responsiveness to questions during sedation vacation is lost except to pain stimulus. September 11th: Taken off of life support. Passes at 1:28pm. I hope that helps. I think it has helped me to write it out. I forgot I had the message from him in my voicemail about going to the hospital. My own personal take on it is that complications from diabetes played a major role in his inability to recover but I am not a doctor and it's just my own mind trying to justify the situation.

Thanks for providing the screenshots. From what we can see, the FX5200 successfully accelerates the browser in hardware, but does not accelerate WebGL, due to the driver version used. The situation is bleaker with the Radeon 9550, where the hardware acceleration does not work at all. I'm not surprised about the result, because those two graphics cards are too old to receive any benefit for the patch. For a Geforce FX, a 5600 is a better option since at least you have full hardware acceleration minus WebGL, which is not strictly essential. Concerning this, there might be a way to trick Firefox into enabling full hardware acceleration, which is done by spoofing the driver version. You have to create a batch file that lets you decide the driver version and eventually, the VID and PID of your graphics card, in order to let Firefox think it's using another driver version, or even another graphics card. You can find more info about that on Google. Unfortunately YMMV with that, as the spoofer might work with some cards (for example, it does on my old 6800GT and my current X1950 Pro, as I use driver versions that are officially blacklisted by Mozilla, but they are the fastest ones for the respective cards), but it might not work with others, or even cause the browser to crash altogether. About Youtube, as I said, you do not want to use the HTML5 player with those graphics cards, as it is already too taxing for the CPU, let alone for those poor cards, which do not have any kind of support for that feature. There is a way for you to watch YouTube in browser much like you do with a modern computer. First, you have to download this extension, Greasemonkey: https://legacycollector.org/firefox-addons/748/greasemonkey-3.9.xpi Then, you must download this script called ViewTube: http://sebaro.pro/viewtube/ Once you have downloaded it, installed and enabled it, you will have to configure VLC first, in order stream Youtube videos most likely at 360p or 480p (I used to watch videos at 480p and they ran fine on the 6800GT, I actually do not remember if I used 480p with the FX5600 though), then you have to enable the VLC plugin in Firefox, and in Viewtube, you need to set the option from the Viewtube list to "Low Definition MP4", then in the Auto dropdown menu, you must choose VLC, then click on the HD button and choose LD, and select the MD option and voila, you will be able to watch YouTube videos in browser even with a very old graphics card. YT 2 Player does the same thing: https://legacycollector.org/firefox-addons/550044/yt2p-1.2.1-signed.xpi The difference between Viewtube and YT 2 Player is that unlike the former, the latter just automatically opens VLC whenever you click on a Youtube link. But first you have to configure the add-on in order to point it to the location of your VLC installation. Remember to periodically update your Youtube.lua file, or else videos will not be played.

Actually the very last version of Google Chrome to work on Intel Pentium 3s / AMD Athlon XP-K7 Semprons is version 34.0.1847.137. I'm using this version of Chrome 34 on an old XP SP3 computer (Intel Celeron 1.1Ghz with 512Mb of RAM) Chrome 35 and above require Intel Pentium 4 with SSE2 & AMD K8 (X2) CPUs or better.