Leaderboard

Listviews group header text color is back to dark blue on dark mode. Was good with SAB 3.7.3.

So solid! Hopefully with the new reorganization and Panos Panay out things will get better. Panos is a hardware guy and never should have been in charge of Windows as much as I love Surface. They also got rid of the Bing ads guy that was running Windows for like a month. I guess start menu ads are a holdover from his tenure.

Thanks all, tried both suggestions, unfortunately the devices are still scanned and seen at. chrome://usb-internals

I use driver 368.81. Sorry to hear about your health issue.

From my experience, 382.xx versions and below are the only ones that were written for Windows Vista and 7. Later are just ported 10 drivers. To be 100% sure, try R375 (376.xx) series.

Yes, looks very weird it's still not there, I mean for a fifteen years old totally out-of-support buggy OS.

I'd start with a well-known, 100% proven to be working video driver. Then try another videocard, I had a similar issue, the reason was - one dead VRAM module Korean Hynix. Unfortunately I can't assist in details, I'm still recovering from an eye trauma.

Probably Thorium author assumes you have the latest kernel from March 2023 and didn't bother to adjust to the older version.

Interesting. I may have to go this route on Win 7. As much as I love @roytam1's Serpent, it looks increasingly like the end is near. My hunch (that's all it is) would be no. The author wouldn't expect anyone to run r3dfox on Win 10 since they could just run vanilla Mo. Besides, why? The question reminds me a bit of @Jody Thornton's request for a 64-bit build of MailNews. Sure, it could be done - the program could check the Windows version and then make different OS calls based on the result - but what advantage would it bring?

I did that a bit back, forgot to post back here. Not entirely sure what you mean by that. There is some delay loaded or disabled pre-10 stuff like the share menu or tablet mode for 10. All I did was undo what broke 7. What I did was make Aero work on 7 again, so it should work on r3dfox. It's not something I test, although I don't stray too far from stock. I think the custom settings options would probably break and about menu would be stock, but I guess working well enough. Everything else mentioned should be like stock Firefox. I didn't change too much. https://github.com/Eclipse-Community/r3dfox/tree/release-121

Using Thorium_SSE4_122.0.6261.168_WINXP_x64.zip for XP x64, Vista & 7 (multiboot, so literally the same copy). Will try Thorium_AVX2_123.0.6312.133.zip in Vista 64 & post results in a few. UPDATE: tried AVX2 (this box is 4770k), AVX & even SSE3 flavors on W7, all from https://github.com/Alex313031/Thorium-Win/releases. Each one gives me the "not a valid win32 app" error. AVX2 flavor performs roughly the same on W10: 144, 156, 145 The weird thing is on W10, the XP/legacy version (Thorium_SSE4_122.0.6261.168_WINXP_x64.zip) benches better (196, 200, 204) than the AVX2 version meant for Win10. In Vista extended kernel (Nov. 2022), i get Supermium on Vista extended kernel (Nov. 2022): 199, 203, 200 Thorium (XP SSE4) on Vista extended kernel: 192, 197, 198

Until now, I couldn't observe such crashes here in my Thorium testing installation.

Thanks but I already know that all. I was one of the first to be involved in testing that re-basing when @UCyborg suggested this method for Chrome360 after my observations in terms of its enormous RAM usage on my old Windows XP computer. The good is that Thorium is already well configured inherently when it comes to RAM consumption.

Yeah when I tested 24H2 briefly on my main machine control center was overhauled but borked. Leave it to the world class engineers at Microsoft. I wish they'd get back to the way they were in the 90s and 2000s.

On my system, the 360Chrome 11.0.2031 worked really well. The version 13.5.1030 rebuild 7 worked relatively well but only when the chrome.dll was rebased. The site loading times were much worse than in version 11.0.2031. In contrast, Thorium doesn't need to be re-based by the user and consumes much less RAM than normal Chrome versions. The standard loading behaviour is an other history, unfortunately. However, this browser was never made for my old system, either. But as I already mentioned, I found a convenient way for me to let websites loading much faster. More about this soon!

Thorium actually starts relatively fast compared to other Chrome browsers under Windows XP, even on low-performance hardware like mine. Of course, it has first to be configured well.

You have other sites opened in Supermium, this obviously adds performance penalty. Msfn, github and reddit. Esp. githun and reddit are heavy.

@Dave-H, would you be willing to try out --disable-low-res-tiling? --disable-low-res-tiling reduces cpu usage and saves power https://codereview.chromium.org/196473007/ https://stackoverflow.com/questions/66825943/how-to-reduce-chromedriver-cpu-usage-in-selenium-python

Probably you hit the size limit. Try to delete your old attachments. It helped me, I can embed since then.

With our without HPET, yes, a bit faster start, like Dave wrote. But I'm not on a single core. Those on a single core would've seen a faster startup.

It's very strange, it's not related to CSS, nowhere near it. And the author of Thorium suggests that flag himself. Unfortunately (or fortunately?), I can't link to his site because he hosts Windows cr*cks, pirated loaders on it. But I can make a quote, those interested may find themselves. "--disable-highres-timer[1] ## Disables high-resolution timer on Windows."

That won't disable the API...appropriate setting is at chrome://settings/content/usbDevices Still, I find disabling it pointless...if you're seeing prompts to connect to USB unexpectedly, you should re-evaluate your browsing habits. I would try talking to one of my USB devices through a web browser just because, but I don't know how any of devices work and I'm back at the fact that I hate programming.

Disable the flag #enable-webusb-device-detection!

Crop

Drip

Trap

Clap

Plan

Omg! No wonder Windows 11 is the way it is!!

No they still can't figure out which team fixes compat.

It makes sense, Microsoft removed the system tray from the old taskbar in 24H2 essentially breaking it. I saw your post on Github complaining about that to the EP devs, you probably don't realize that the system tray works in SAB in 24H2 only because Tihiy completely rewrote it from scratch. Explorer Patcher doesn't reimplement anything, it just patches Explorer with it's modifications to things existing in Windows already. It's free software and rewriting the entire system tray is outside the scope of what it's intended to do. StartAllBack is a commercial product that patches explorer with its own proprietary code, that's the difference. It's meant to be a customization tool to bring a classic Windows 7 era UI to Windows 8-11. Start11 is 10 times the size of StartAllBack because it seems to hook more into explorer after it's already running and intercept function calls to do its thing, it runs a service and everything. That's why it's immune to Microsoft because it's not modifying Explorer in memory with a DLL, it's completely proprietary, it's also bug ridden and unstable. SAB consists of a few DLLs with Tihiy's special sauce, the config utility and an updater. It loads with Explorer, not after. Start11 is incredibly bloated, I've even restarted explorer with Start11 and seen it take a second to hook where the regular Windows 11 start menu will pop up and the taskbar will be stock and not their enhanced one. That will never happen with StartAllBack. Edit: I just want to share this comment on Neowin. @Tihiy is indeed a genius and the entire fate of Windows does indeed rest with him.

I find it amazing that Start11 can literally crash all of explorer when configuring its menus but StartAllBack which is one of the most stable pieces of software I've ever seen causes security or performance issues. If Tihiy has to discontinue SAB I will be forced to begrudgingly use Windows 11 stock because Start11 is not a viable alternative in any way. It's amazing that a company as established as Stardock can sell something just so bug ridden and unstable. No wonder there has been a rivalry (it seems), Stardock is this huge company but they can't even come close to matching the quality of the work of one guy. Doing a simple search in the start menu after a few seconds triggers an explorer crash, what a pile of junk that is.

I too (and others) use SAB for the classic taskbar mainly, if it is no longer available.... Not sure we're happy with the really ugly default taskbar (thickness, etc...) Or stay with the 23h2