UCyborg

I know dev tools are provided as-is... But I still find references to Firefox amusing. I also didn't know Firefox codebase at any point included ASCII art anywhere. While browsers struggle to run id Tech 4, ala DOOM 3, classic DOOM is not a problem, even for UXP browsers (OK, maybe a little bit...). http://browser-doom.io/ But I'm not sure if ZDoom engine would run well if ported to web browser environment. This one doesn't just feature shareware (demo) versions of those games, lets you upload data files of full versions.

I can get by with 1 GB of RAM on an almost 10 years old smartphone just fine with few tabs of normal websites. Of course I don't expect it to run heavy web apps and there are some cumbersome, unbearable sites like https://www.mimovrste.com/, but most others are a breeze (I don't count most social media). The trick is not using full blown web browser, but a browser utilizing WebView like Via. I'm not aware of any non Chromium implementation of WebView on Android, but it's how to keep resource usage down. Not sure how recent versions of Via are, should still be OK, though at some point the user reviews were worse... In any case, NOTHING on either my phone or computer updates automatically. Most browsers on a desktop will lean towards larger RAM usage though. You could keep it simple if you really wanted and especially if you still use one of those old machines that survived capacitor plague, but if you have the RAM, it's there to be used. Unused RAM is wasted RAM, you know? BTW... https://www.tomshardware.com/tech-industry/modern-web-bloat-means-some-entry-level-phones-cant-run-simple-web-pages-and-load-times-are-high-for-pcs-some-sites-run-worse-than-pubg Funny it mentions Quora, I never had problems with Quora, even on that old smartphone, except with nags for registering. Am I supposed to do anything special? May take a bit to load, but afterwards it's mostly fine. That said, modern web is riddled with analytics and other garbage, which must be blocked to keep things somewhat sane.

And I'm not sure you can even reliably tell by the numbers in Task Manager/Process Hacker/System Informer when exactly it happens. Somehow it took me until now to realize how important this can be in some of my usage patterns. I've been actually using 64-bit build at work for years now, though I don't remember ever getting to even 2 GB there. Same with most other software in general (at home also), I lean towards x64 build when available. But it's easy to accumulate with a web browser and kept it at 32-bit to save a little bit of RAM, which upgrade I kept putting off for over a decade to the point it's hard to come by it (DDR2), let alone a decent one, but got an extra stick last year, which is really out of place near the old ones, they run at an odd frequency and timings because of that. People change, expectations change.

64-bit version is definitely much more stable, although unloading larger amount of tabs can take minutes and result in a big spike in RAM consumption while the browser is unusable. Got to total 5,6 GB / 6 GB RAM utilization, 3,6 GB of those occupied by Pale Moon. Unloaded all other tabs except the one with MSFN, browser settled to little over 600 MB afterwards, there was a spike to about 7,2 GB while it was frozen according to Event Viewer (resource exhaustion event), auto-scrolling was again smooth afterwards. What I noticed while testing, browser in 64-bit flavor had an easier time pumping event loop (less occurrences of its window being marked as not responding) and sitting in the middle of comments section on YouTube didn't load the CPU as much, it could actually downclock, 32-bit version would usually just sit at constant 100% on one core. I just avoided most of GitHub except wiki pages due to problems with ghost windows they cause internally.

Probably depends on what you do/expect. Found this writeup a while back: https://dudemanguy.github.io/blog/posts/2022-06-10-wayland-xorg/wayland-xorg.html While I can sort of get by with Linux, I'm just not at home there.

It's nothing new, I'm just venting. Symptoms are apparent on much newer hardware as well, browse long enough on heavy enough sites and it slows down and you have to restart if you want it to go faster again. Add lower RAM amount into the mix and it may eventually get stuck in the loop. Maybe the latter only happens in 32-bit builds. It's probably even worse idea to run 32-bit builds on modern Windows, process address space probably gets fragmented enough from extensions as-is, then there are extra system DLLs and some 3rd party software's DLLs may end up in there. I seem to remember people in the Fx52 era writing 64-bit build was more stable. Should probably switch at this point, at least on desktop where I can. Running 32-bit Pale Moon is an old habit that persisted even after adding more RAM, though 32-bit build could actually be a bit more responsive compared to 64-bit.

Had a bit longer browsing session with Pale Moon recently, it's absurd how things slow down to crawl. Even tab switching is considerably delayed. Click, wait 3 seconds, repeat later. Had another session before that on a poor laptop with 2 GB of RAM, System Informer showed about 700 MB private bytes for palemoon.exe, still had about 500 MB free physical memory. And it just got stuck in a loop, had to end palemoon.exe. Sometimes I can't help but think using such browser is self-torture. Other times I think maybe I should do myself a favor and buy something modern with decent amount of RAM and just daily drive Firefox, then it can leak as much as it wants.

They have other things to worry about, you probably wouldn't want to live there. How much does it even take to run Win10? My old heap of junk runs it, I'm sure it's worthless on the market.

Be very patient, it may take years.

I think this board is more on the retro side at this point. As far as I can tell, there's just one fuse, the yellow thingy near the power connector, it just cuts the power from the board if it blows so nothing would light up in this case. Yeah, it's what I actually had in mind when I said I measured the new capacitors. I just wanted to see if I could get the router going for a while, so just bought random ones I could get locally. Could always get more reputable ones from one of those big distributors like DigiKey or Farnell, but unless confirmed they were really the biggest problem to get the device going, it didn't seem worth buying them and have them shipped from who knows where. Actually, it only occurred to me at the later point that if everything else was OK, probing capacitor through-holes when the capacitor is not inside, multimeter should have picked up on resistance, at least I think it's logical they shouldn't behave like if you just bridged the holes with solder, so no (read very low) resistance and just "beeep". The multimeter I got is one of those smart ones, for basic measurement parameters like voltage, resistance, continuity, you don't have to select the mode. So in that regard, only one pair of holes changed between having the old capacitor in and removing it, going from no resistance to resistance. I think this leaves only one another simpler component, the two diodes near the power connector. I suspect removing them wouldn't reveal anything new. When measured in circuit, there is a larger difference in resistance, depending on which lead you put each probe, and I read that's expected from a diode.

In the end I did it, old capacitors out, new capacitors in. The clumsy one just needs a lot of time. Desoldering pump seems to work well, unless you fail to heat the right area well, which must have been my problem. But it was only partial solution at best. The one capacitor where the power goes in must have really been kaput, at least that area doesn't measure 0L on the multimeter anymore. But where second and the last one from where power goes in are connected, with new ones in place, they still read 0L. I did measure new ones before connecting them and they're fine. Something else must still be shorted. I guess this is where easy fixes end. Behavior with more decent power supply remains the same, the power is cut shortly after powering up due to short circuit.

OK, it worked for that guy somehow, so should have worded a bit differently. I think I just got a black window back then. Still, better try this: https://storage.googleapis.com/chromium-browser-continuous/index.html?prefix=Win/291943/ Just remember to disable GPU blocklist on chrome://flags page. Though TBH I'm not sure if canvas accel works specifically, hard to test in reality such an outdated browser, but period correct WebGL stuff seems to work. None of that slow 100% CPU sucking SwiftShader nonsense. The hint comes from https://superuser.com/questions/958238/how-to-enable-webgl-on-chrome-on-xp. I like the last comment from the guy who asked: Interesting, but I have updated to Win10, so I can't test. I think Chrome no longer supports XP anyways.

Implying WineD3D actually works, much less works well (tried the suggested hack years ago, didn't get anywhere). Bogging down Pentium 4 with translating D3D to OpenGL, it's a great idea!

Chrome 49 requires D3D9Ex for HW accel, which is Vista+.

Oh, one more thing, the method with which I was somehow successful with that one hole was melting solder on it and using solder pump. But just couldn't reproduce the success on other holes.

I think if I could have just skipped desoldering part, I might have got somewhere already. You think those smears could look worse than they really are? I'm ashamed to photograph it, it does look horrible. There is actually a *bigger one below where antenna connector is mounted from the factory, just much less dark. BTW, last year I still saw this model of router on sale directly from Linksys, sure pricey for the capabilities, but this year, they might have actually stopped producing it. Edit: [*]not bigger than mine, just rather big one.

I got even less far with 40W one. I got almost nowhere in hours. What chances are there that I haven't destroyed it now if it wasn't destroyed by that voltage shock after the power outage already? Sad to say, but some of us are clumsy beyond help. Should I have used a chisel tip? That looked even more difficult use due to it being bigger and those holes are so small.

I officially gave up on this. I'm simply incapable of using these tools, no amount of YouTube videos and reading about techniques help me, not 60W iron, not desoldering wig, not the pump, nothing. All I managed to do this evening was free one hole and left a bunch of smears on the board. Well the other day I got one capacitor out (with legs still stuck in the holes). When I measured them in circuit (capacitance - I know it's not accurate that way), all but one showed 0L on meter, which is overload. The other one showed 100 higher value than should be (but again, in-circuit, sooo...). I think it's best if I just forget about it and throw the router in the trash. I guess some of us just weren't meant to be able to do self-repairs. Some may say recapping is not that hard, but for some of us, it is very hard, downright impossible.

I would check autoplay settings in the browser first. It could also be an extension, which you could try ruling out by disabling them one by one. If you have any for YouTube specifically, go through their settings first as there are extensions that offer to disable autoplay on YouTube. Normally, it should autoplay by default.

Post on win32's Patreon suggests it could. Nah, I'm waiting for win32. I would expect something along the lines of the build at https://storage.googleapis.com/chromium-browser-continuous/index.html?prefix=Win/291943/ quality/stability wise.

I wonder why we have the entire Android subforum. @chermany4ever Thank you for detailed response, it means a lot! My mood can vary wildly and I'm a bit down in recent times. Sometimes I want to do something new on my own and even what's supposed to be easy relatively speaking turns out to be challenging for me. It's depressing. I suspected the trends you mentioned were the ones you had in mind initially. I tried to imply at the later point running Chromium-based browser might still be trendy, even if not running it on legacy systems specifically. I still have Supermium on XP x64 installation, only deleted it and Thorium from Win11. I might still try out the upcoming Supermium build on XP to see how it'll be able to use the GPU.

OK, that would block standalone SVG files. I was curious how that like button on those forums would behave, eg. would the image be invisible, but still clickable. BTW, an open issue for CSS layers: https://repo.palemoon.org/MoonchildProductions/UXP/issues/2486 There is a server-side polyfill for this feature: https://www.oddbird.net/2022/06/21/cascade-layers-polyfill/ But UXP browsers aren't listed in any compatibility table web developers are looking at.

Unable to confirm any of these do anything to prevent SVGs from being rendered. https://upload.wikimedia.org/wikipedia/commons/b/bd/Test.svg No change on those two forums that use them that have them as part of HTML. Checked both official Pale Moon and Serpent 52.

It seems legacy Thorium has some stuff from Supermium that modern Thorium lacks, I noticed modern Thorium doesn't have the option to disable rendering of custom title bar on Windows 10+. No idea TBH, I was just curious about what people actually do on their computers and @chermany4ever brought up rebelling against trends. Nothing reasonates with me, not a big fan of anything or anyone. Existential crisis sucks. Maybe that's one of the reasons some people start drinking or taking drugs.

But in the end, death is the only just thing in this world. Every corrupt scum will eventually succumb to it. I just got rid of both Supermium and Thorium on my system. How's that for resisting trends?