Jump to content

All Activity

This stream auto-updates

  1. Today
  2. So far, no matter how many browsers I tried, only CatsXP has them partially disabled, it just sends empty strings, just like in @Dixel's hack, but the API works, Possibly Brave, too. @NotHereToPlayGames, you mentioned you use brave 134, could you check? Thanks
  3. Wasn't Haswell (2013) not supposed to work with 7? And what is the purpose of AVX being integrated in Chrome?
  4. Good browser, version 137 for legacy OS released, leaving Thorium 15 versions behind. https://github.com/e3kskoy7wqk/Chromium-for-windows-7/releases/tag/137.0.7106.1
  5. Yesterday
  6. try the 2025 v16e one from https://www.win2k.org/wlu/wluen.htm
  7. As a workaround for now, you can terminate dwm.exe
  8. I think my windows 8.1 pc died anyways sadly, so this might just be it for that system anyways. it just powers up but nothing more, keyboard isnt even doing stuff already. I will probably let it rest for a few weeks and then try again
  9. Unfortunately still doesn't work... Another thing I tried is this problem exists when I run Windows 98 Setup, press Continue and after the 1st loading progress bar, I hit cancel so I got back to DOS. I tried doing stuff like "mem /c /p" a few times and when I left it around 30 seconds, it stops responding to any keyboard/touchpad events.
  10. Light mode tooltip bug in the latest version (clock area tooltip not affected by this), manifests when energy saver is on
  11. I finally got to what's messing up the Chromium 110-126 sandbox on Windows 8.1, and it's the UpdateProcThreadAttribute feature. When I redirected it in the original kernel32.dll to the pwrp_k32.dll included in Supermium 132 R2, the sandbox started working. Just find a 100% sure solution to the RAM and virtual memory usage problems, and you will be able to use any Chromium-based browser (except Edge) up to version 126. I still don't know what is causing the problem with Chromium 127 and newer preventing the browser from running. And fixing the sandbox in version 126 is just a milestone. It is 17 versions higher than 109, but it is also 9 versions older than the latest official Google Chrome.... If anyone knows how to debug, I would greatly appreciate your help. All I know is that the problem is definitely in chrome.dll. 126 also worked on 8.0, but the sandbox after the repair still does not work, the browser starts up, but with the error SBOX_FATAL_CLOSEHANDLES, and does not display any page, of course.
  12. Thanks, I will try to compile myself with support, maybe also an AVX2 version for my Haswell Win7 PC.
  13. I still have this issue on 3.9.7 unfortunately
  14. I use the Restore Session at least twice a week (Serpent RAM leaks)! It really is "hit or miss" in newer versions of Serpent 52. Whereas it *ALWAYS* works in 2023-07-31. There's also really *nothing* in newer versions that I technically need (it is used as an email/text-message reader 24/7/365 but it is not used to browser the internet for news, videos, streaming, etc). I try the latest-and-greatest every three weeks, pretty much like clockwork, *hoping* it is going to be fixed, but alas, IT NEVER IS. It really is "hit or miss" on my hardware, no clue "why" exactly.
  15. AFAIK this driver is only for mobile chips listed here http://web.archive.org/web/20190904143021/https://downloadcenter.intel.com/download/22876
  16. You still haven't used the latest version? Restore session has never been broken here (that I would notice) and I do use it from time to time. Sometimes it just take a bit longer to load/show that button/option at the bottom of the start page or in "History" menu. --------------------------- As for that CSS nesting for those icons - I do read the news and if it is about dumpster fire that is Windows NT 6.x, so be it.
  17. Hey, i was installing driver for my pc i5 4570 (haswell gt2), but it encounted error code 39, can anyone help me to fix?
  18. The topic is about Win 8.1, but since there is no separate one for 8.0 I am posting the information here, it also works after very similar modifications (even GetSystemTimes is not missing, although this 8.0 is RTM without any updates, and 8.1 I use updated to the end of 2017)
  19. Just fyi: Unfortunately this is the current behavior of StartAllBack and the developer isn't interested or willing to fix this :(
  20. I have not combed through the changelogs of Serpent, Basilisk, Pale Moon, New Moon, etc to see when/if layout.css.nesting.enabled flag is added/present. As far as my daily-use Serpent v52.9.0 (2023-07-31), I can report that the flag is not present. For my useage, there are other things "broken" if I upgrade to newer (ie, Restore Session feature is very-much-so "hit or miss" in newer) so I intentionally use 2023-07-31.
  21. Agreed. My intended point was more along the lines that these "experimental" flags effect both css and js.
  22. But then again, might too be problematic. https://www.reddit.com/r/graphicscard/comments/nw289k/any_graphics_card_that_supports_win_10_ltsb_2015/
  23. Any GPU path you choose these days will be bad, but I agree, RX6000 over RTX3000 has much nicer colours. For me, 8.1 and 10 are equally evil, maybe try 2015 LBSB, LSGT or whatever it's called, then.
  24. ... I'm well aware , so that's why you weren't quoted ...
  25. Last week
  26. Most of us don't. If you have some time, probably make a list of the garbage files? like I did here. https://msfn.org/board/topic/186741-firefox-and-chromium-running-on-windows-7-by-e3kskskoy7wqk/page/2/#findComment-1278902
  27. I don't need it, I've already replaced them with empty files, I just posted about it informatively. https://github.com/e3kskoy7wqk/Firefox-for-windows-7 includes a working crashreporter, if anyone want a 100% complete browser (and actually with unnecessary additions).
  28. Also seems like a piece of junk. Replace with an empty file with the same extension. (from TXT file)
  1. Load more activity
×
×
  • Create New...