UCyborg

Probably contains word it doesn't like, for example you can't mention the notorious config boot configuration file that was used pre-Vista, but it's far from the only word. I recently couldn't post normally in Thorium forum until I reworded what I was trying to say. This forum really went down the toilet, didn't it?

For the last time, he uses Pentium 4 based on Northwood architecture clocked at 2,80 GHz. I had Northwood based Celeron clocked at 2 GHz back in the day. All rather boring, in contrast, the final Pentiums 4 were 64-bit. I tried booting XP with just one core (set it in advanced options in msconfig on BOO.INI tab). At first, it almost seemed Supermium may be usable with easier sites. At the end, I barely managed to close the browser as it made everything unresponsive. Nope, this is totally unusable.

No. Maybe if you can root the phone and the kernel's USB gadget still supports USB Mass Storage mode and is configurable through files, you could access FAT32/exFAT SD card that way, if you have it. Of course, you don't get to configure that through menus. Not sure about internal storage, as this is usually just a folder on an ext4 formatted partition. There's supposed to be VFAT emulation taking place, but I'm whether this means it could just be exposed to the PC through USB is another question, I never tried and can't say I have a clue what file (if it exists) would correspond to a block device representing internal storage. As @windows2 said, you'll definitely need WMP11. Judging by Samsung Galaxy A15 I'm testing, you might have to convince Windows to configure it as MTP device. Out-of-the-box, it was detected as a camera. This is is the content of one of the folders listed through phone shell's ls command: And this is how the folder appears in Explorer: Besides default layout being centered towards working with cameras, eg. Date Taken and Picture Size columns, Camera Tasks on the left, no full path is shown in Address bar and folder names are truncated. Not good. Likewise, its appearance in My Computer and its properties: Anyway, head to Device Manager to find "the camera", open its Properties, then on Details tab, select Hardware Ids and note the first ID. You will need the part after USB\. Open Registry Editor (regedit.exe) and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB, there you should find the key that corresponds to the ID noted earlier, inside that key, you should find another key (folder, if you like), if you select it, you should notice CompatibleIDs value on the right. You have to open that value and insert the following line at the beginning: USB\MS_COMP_MTP To be able to do that, you'll probably have to temporarily grant Administrators group (or your user) permissions to the key/folder containing CompatibleIDs, so right-click it->Permissions...->Add...->type Administrators->OK->tick Full Control->OK. After you're done modifying CompatibleIDs, you can remove the permissions. Now you just have to go back to Device Manager, open "the camera" and trigger driver update, so Driver tab->Update Driver...then just accept the defaults to let the wizard configure it properly. Final result:

uBlock Origin Chrome Font Super Enhancer (only on browsers that aren't Edge and only on Windows) KeePassXC-Browser Improve YouTube! Return YouTube Dislike Auto Copy IP Domain Country Flag JPEG XL Viewer Lazy Tabs Navigational sounds Stylus TamperMonkey Not sure I have a favorite Chromium-based browser, I most often lean towards Edge on Windows and Vivaldi on Linux. Interesting, didn't know that can be done browser-side. Not an extension I'd use specifically since I do use what is called "Perfect EQ" preset system-wide. https://www.ziyadnazem.com/post/956431457/the-perfect-eq-settings-unmasking-the-eq Exact values from: https://github.com/JackHack96/EasyEffects-Presets/blob/master/Perfect EQ.json

Nothing using GPU on Chromium works on XP. Waste of good hardware.

My problem with Windows XP x64 updating is probably not related to Legacy Update specifically. The Automatic Updates service just gets stuck in a loop on "PT: Synchronizing extended update info" step (WindowsUpdate.log). According to this, the only slightly outdated component was Internet Explorer 8, so I installed the cumulative update for it, 64-bit version of course. Also tried cleaning up the logs and DataStore.edb database in C:\Windows\SoftwareDistribution, that way it took a while to reconstruct, but then got stuck as usual. This installation was hardly used much, I doubt resetting update components would do anything. Automatic updates were turned off from the beginning. Back in the old days we solved these sorts of problems with format C: /Q Was it anything like Edge on this video out-of-the-box? It only shows YouTube loading, though. Maybe a bit faster on yours since XP fits in smaller amount of RAM? Thorium in general appears glitchier than Supermium, on XP at least. I got it to crash on Google Drive with fresh profile. Crash doesn't occur using Supermium. Regarding Chrome XP API adapter, some difference in size seems negligible to me, the browser would work better if it was more feature complete. Still takes 10 seconds to start after cold boot here. I find slower initial start of any program to be an old pattern. Maybe more pronounced with Chromium since it's a big program. PS.: One finer detail, the path to Windows Update log file was omitted above because forum doesn't let us post normally, so I'm mentioning it here subsequently that the log is located directly in Windows folder.

I think they need to update system requirements. https://support.google.com/chrome/a/answer/7100626?hl=en No one runs Windows 10 on a Pentium 4, no one runs Chrome on a Pentium 4. A Raspberry Pi 5 offers much more enjoyable browsing experience than any old, loud and clunky computer from over 2 decades ago or so.

I got nowhere. All it did in 6 hours was heat up the room and increase the cost of electricity bill for the current month.

Never mind, still happens. I only ever deleted D3DCompiler_47.dll as this one is normally not loadable on XP. https://en.wikipedia.org/wiki/Vulkan Maybe runtime library (vulkan-1.dll) is a hard dependency, even though there aren't any Vulkan drivers on XP. There's more discussion among Linux folks for getting Vulkan working in Chromium, I think I only tried once (unsuccessfully) on Edge on Win10, though it's possible that couldn't work due to Microsoft alone as last time I checked, they prevented ANGLE backend flag from doing anything. Presumably Vulkan is mostly interesting in combination with WebGPU (for new graphics web apps) on non-Windows systems, maybe as an alternative backend on Windows. No idea if it's supposed to effect webpage compositing in general. Anyway, I'll see if Legacy Update gets me anywhere on XP. So far, it looks just as bad as I remember, if not worse. Checking for updates for over 50 minutes already...

Huh, I wonder if IDA-RE-Things lurks here, he put changes related to keyed events I described in a new version. So far, I didn't get the problem with USB with his DLL. One time, GPU process crashed, at least with 5044 I uploaded above, but it's more difficult to reproduce. Another bigger issue, which I haven't checked yet if it also occurs with Supermium, the tab just crashes here after navigating to Google Drive main page (requires login). Doesn't matter if I use win32's DLL or IDA-RE-Things' version. I also wonder if anyone gets the problem with browser being unusable after Windows XP coming out of standby. Same problem with 360Chrome, the window content simply doesn't render, it's a see-through to desktop, have to restart the browser.

I was trying 32-bit version, 64-bit obviously couldn't possibly load 32-bit DLL. The thing is programmed to call undocumented API NtCreateKeyedEvent with an object name \KernelObjects\SRW_WakingEvent, which fails unless the calling application is run with administrative rights, as KernelObjects namespace is restricted. Why would I run a buggy web browser on a buggy insecure OS with unrestricted access to everything?! I live by the principle_of_least_privilege. I modified the DLL to use BaseNamedObjects instead. Also changed DesiredAccess parameter of both NtCreateKeyedEvent and NtOpenKeyedEvent calls from 0x2000000 to 0xF0003. Don't know what former is supposed to mean, but the latter has been documented to translate to KEYEDEVENT_ALL_ACCESS, which sounds about right. Browser was unusable crash fest with the original. chrome-xp-api-adapter_x86.b5044.zip There was an error on launch that said: The application failed to initialize properly (0x80000003). Click on OK to terminate the application. That was with DLL build 5041, in the latest version 5043, he put a block on XP x64 and most other OS...an error saying it's not supported. Not supported my a**, I removed the block. Can both XP x64 and XP x86 users here check the modified the DLL above and see how it works? If it's broken, should be apparent right away as new versions are about new synch code using keyed events, kinda important. Edit: Well, non-NT 5.x systems are still blocked, not sure how much mess is in there that it would be needed to prevent the user from getting crappy (non-working) experience...I could throw the check out entirely. But now it's really late here, so time to sleep.

Yeah, people here really don't have a wide vocabulary, maybe try asking at Emulation and virtualization section on FreeBSD forums. Even ElevenForum would be better for Win11 specifics.

All I get with this "Chrome-xp-api-adapter" is this: So that's completely and utterly useless.

I meant I don't know what ads are they talking about with uBO active. I don't have to configure anything, reset uBO to factory defaults, still nothing of that kind. But who knows, with people here running on ancient worn out hardware (who knows if those capacitors still work?) with God knows how many OS tweaks which they think they're good, but they're actually bad coupled with who knows which browser build about which you never know is stable or not because roytam1's world is a permanent beta testing program etc. etc. So I don't know about ads, but there are couple scripts that are loaded that can be omitted without impairing the most basic functions: ! Those clickety things with links to other pages/videos that may appear on some videos ||www.youtube.com/*/annotations_module.js$script ! Sounds like a remnant for supporting obsolete browsers ||www.youtube.com/*/custom-elements-es5-adapter.js$script ! If you don't care for the end screen with links to other videos ||www.youtube.com/*/endscreen.js$script ! Polyfill for obsolete browsers ||www.youtube.com/*/intersection-observer.min.js$script ! I guess that's a miniplayer that could continue playing video on the lower-right corner eg. if you go back from video to search results ||www.youtube.com/*/miniplayer.js$script ! ??? ||www.youtube.com/*/network.js$script ||www.youtube.com/*/offline.js$script ||www.youtube.com/*/remote.js$script ||www.youtube.com/*/scheduler.js$script ||www.youtube.com/*/spf.js$script ||www.youtube.com/*/web-animations-next-lite.min.js$script ||www.youtube.com/*/www-tampering.js$script

This must be one of the reasons I'm still on Pale Moon most of the time. Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: firefox.exe (10540) consumed 2574610432 bytes, firefox.exe (3720) consumed 1298313216 bytes, and firefox.exe (11168) consumed 513085440 bytes. All my ancient XUL extensions still work, including ColorfulTabs (love ColorfulTabs! only updated it few years back by myself to remove the bug related to Australis UI detection) and Navigation Sounds. There's Extra Sounds for Firefox, but there's a catch other than those sounds being hardcoded, extension being active means there's always one AudioContext active, which means Windows resolution timer is permanently stuck on 1 ms as long as the browser runs even with zero multimedia stuff active on web pages, which is bad . Latest uBO would be nice, but eh, we still get by with the old one. Speaking of uBO, I would laugh so hard if Mozilla dropped Manifest V2. Yesterday after my PC came out of sleep, one of the firefox.exe renderer processes was stuck in a loop, constantly consuming over 40%...even worse when Pale Moon gets stuck on crappy JavaScript on some crappy pages, which is usually constrained on one core, so that's 25% in my case on a quad core.

@66cats IDK, call it a hybrid then. Yeah, I tried Debian ISO once on my laptop, the one ISO as it was meant to be, so no proprietary blobs. Got warning right away that firmware should be downloaded for Wi-Fi adapter, so didn't get anywhere. I'm mostly in "whatever, as long as it works" camp today. Source code availability is nice, but eh... Used to be more of a tinkerer, but these days, screw it. It's all such nonsense in the grand scheme of things, systemd vs non-systemd, PulseAudio or no PulseAudio, Blink vs Gecko, XUL vs WebExt etc etc. It's all f***in' politics and I hate politics, I just want a working computer. Is that too much to ask?? Well, I guess got it more or less so not much to complain about from my side. Regarding this forum post editor, it's been months since it last glitched out on me, but when it did, and that must have been couple forum software updates ago, you would click Submit Reply and it seemed it didn't do anything, even though it actually did so if you clicked the button again and refresh the page, you realized you just double posted.

I've no idea what people are talking about when they're talking about ads on YouTube. Regarding uBO's blacklist, non-issue as far as I'm concerned. If I want ABP's lists, then I'll use ABP. Don't see the point in feeding uBO with a list that contains crapload of ABP specific filters. If something useful is in there, it can be implemented in uBO's lists.

How does that invalidate the open-source components? There are distros out there that do not include binary blobs. Supermium's source code is here, it simply depends on closed-source Win7+ API emulator. Apparently Windows XP is so bad they have to emulate Windows 7+ (APIs) to make it run on XP. And even then it's far cry from the old XP compatible Chrome versions, which were higher quality releases with none of the bugs or deficiencies you see these days.

It's on the list of bad lists. https://github.com/uBlockOrigin/uAssets/blob/master/filters/badlists.txt https://github.com/uBlockOrigin/uAssets/commit/e5ee8b11958091aed01321a56e5340ccc99243be

With 1 GB page file, I can get to 3,8 GB of total RAM utilization before crashing. 2,86 GB page file gets me to 5 GB. Until the limits are reached, it's stable in that regard. But all these Chromium browsers can eventually destabilize Windows' USB functionality, despite any browser functions related to USB aren't even working on XP past last 360Chrome versions. At least I had these issues with 360Chrome and they still seem to appear in Thorium, someone else reported related browser crashes related to the former. A device may stay stuck in Device Manager as it was still plugged in after being unplugged, then there's no power on that USB port, it snaps out of it when you close the browser. And yeah, this was never meant to run on early XP era machines. That would be on the other level than getting around OS limitations I think.

It's called responsive design. There is no "mobile" or "desktop" version, there is only one version I think. MSFN (board index page) loads in 1.6s to 1.8s in x64 SSE3 build on my XP x64 according to DevTools. Didn't time it on 10 or 11, but it's probably very close to those figures. Serpent (x86 or x64) takes 3.3s to 3.5s.

It was a needlessly ranty part and didn't take into account process address space fragmentation... although TBH, I still find it strange, Chromium being multi-process, how do you not have consistently free contiguous 256 MB of space in that one process. https://github.com/win32ss/supermium/issues/507 On the other hand, we live in the age of abundant computing resources, so sometimes these issues do struck as "first world problems".

I noticed random tab hanging with Supermium as well. Slightly off-topic, it's just that I used Supermium slightly more often on XP than Thorium so far. But it could be due to small fixed 1 GB page file since XP is installed on a small 20 GB partition...I think warning about possibly failed memory allocation requests may only show the first time. Those that have these types of problems should check if their page file setting is set to auto. No, you're not smarter than Windows if you think you know appropriate size or worse, think you don't need it at all. If you don't have decently (over)sized page file and settings prevent Windows from resizing it, chances for memory allocation requests randomly failing decrease dramatically.

Play Store says Firefox 125.3.0 works on Android 5.0+. Or you can buy a new phone 'cause I don't see anyone porting Chrome to older Androids. The history repeats itself. "You will be upgraded!"

The point of that setting (the one on normal Settings page, not page with flags) is to prevent the web pages to be able to do anything with WebUSB. https://intel.github.io/zephyr.js/webusb/ You'd have to implement another flag or setting in any other shape if you wanted to turn the backend off.