Leaderboard
Popular Content
Showing content with the highest reputation on 08/14/2024 in all areas
-
I think Aero-styled buttons were available at 2.x.x versions only . I noticed they replaced the perfectly good Vista buttons starting from 3.x.x. with the ugly Win 10 buttons. It is strange about m4a though , I can play them fine .4 points
-
Those aren't 'retro' , those are FLAT , 'modern' type , Win10 style . And on your pic. with Windows 7 is just an older version. I too have Win7 installed for testing purposes and they look EXACTLY the same with this version . Why did you assume that someone wanted to lie to you ? It's not the right attitude at all. Try an older version and you will get those Vista style buttons . The main point is Aero working and everything looks like it supposed to be. And don't be hostile, people are here to help , not to argue.4 points
-
vulkan-1.dll is still used to load software-backed Vulkan implementation for running WebGL content. Inside the GPU process: Getting rid of vulkan-1.dll will produce errors and break WebGL. Screenshots are from Supermium, but I doubt Thorium is any different in that regard. So Vulkan components that come with these browsers are functional on XP, but that doesn't change anything regarding the ability to use GPU for it since no XP drivers provide the working implementation AFAIK. Deleting DLL doesn't break the browser here, but generally such interventions appear pointless to me. Why look for even more trouble? Experience of running these browsers on archaic operating systems already seems a lot like experience of living a life with mutilated genitals as it is.3 points
-
Yep! That's why I modified my null hypothesis H0 some days ago. I tend to assume that my computer is such certain hardware.3 points
-
It depends on the user's behavioural patterns, one would need to extensively use youtube or instagram to notice, twitter maybe, which I think you don't.3 points
-
I tried it on my Windows XP Pro SP3 + POSReady installation months ago. It didn't do anything interesting, so I removed it a short time later. I should mention that RAM consumption of Thorium is not the problem on my computer. And just for clarification, this flag actually can't be a solution for my issue, as Thorium works fine without it on my Windows XP Pro SP3 + POSReady installation. But I'll give it a try anyway. Just to be sure.3 points
-
That is the UI that looks the same on Windows 7 , so I assume that is exactly what developers wanted. Still that doesnt explain why Aero is NOT working in your case , I'm guessing you installed a ton of newish updates , ain't that right ? If you desperately need that precise version , you can try Application Verifier and set it to lie about Windows version , the instructions are one the page with KernelEx. It worked for win32 and many others (aero theme in browsers worked) That's my advice. Or revert Vista to smth like 2017.3 points
-
3 points
-
Both partitions were created by me in 2004. Since then, there has been no reinstallation due to a perfectly functioning imaging system. I correct all errors myself. The registry of both have been modified, cleaned and fixed by myself. The main difference between them is that I had to stop the updating of Windows XP with the last update in 2014 in one of them, and in the other, I applied the POSReady hack and performed updating until 2019. PS: I never had an infection, which had to be removed by an antimalware programme, in both Windows XP installations. And don't forget there is an undetermined probability of type II error for accepting the null hypothesis H0.2 points
-
I tend to assume that my computer is such certain hardware. The reason for my assumption is that everything works in my Windows XP Pro SP3 without POSReady partition. I have never had such problems. Firefox, New Moon and also Mypal 68 work perfectly there. This partition is configured in exactly the same way as the one with Windows XP Pro SP3 + POSReady updates. Actually, my issue can only be due to a missing patch or update. And the only updates missing there are the POSReady ones.2 points
-
After all my measures, and I performed many of them, I have to confirm my last null hypothesis H0. Thorium behaves unstably on my Windows XP Pro SP3 without POSReady. Sometimes, the browser opens and lasts for a few seconds or minutes, very often the browser closes during startup. There is no recognisable pattern. I also tried different combinations of command line flags. No success. The internal site chrome://metrics-internals/ doesn't provide any information on my old machine. The good thing about the story is that my Windows XP Pro SP3 without POSReady installation is now absolutely error-free and updated.2 points
-
Here you can see what Chrome thinks of your device. Go to: chrome://metrics-internals/ Click on "variations" Look at the "Low End Device" param.2 points
-
In that case, go to chrome://net-internals/ Tell me what you see in: Attribution Reporting is currently "insert here" in this browser.2 points
-
2 points
-
2 points
-
Another user was aggressive in a post that was removed. You're good! Also the 7+ TT dev I believe develops Windhawk now.1 point
-
1 point
-
1 point
-
Eureka! THAT explains it all. The *two* (and only two) members that shout from rooftops to delete vulkan files also do not enable WebGL. I didn't used to enable WebGL, not even for my uploaded releases here at MSFN. But I do enable WebGL nowadays. Partly because each and every "bug report" for my uploaded releases were dang near ALWAYS tied to the end-user needing WebGL. Partly because the "security risk" associated with WebGL is "much ado about nothing".1 point
-
They are required in XP x64. I will NEVER convince you otherwise. NOT my fight! I can only tell you what I have witnessed in Thorium and in 360Chrome and in Supermium and in Ungoogled. ALL OF THEM !!! XP x64 only. This is YOUR fight, not MINE. Please contact the DEVELOPER if you wish to dive deeper. Granted, my ONLY issue "when I take your advice" and remove these, the ONLY issue is FIRST LAUNCH after a reboot or coming out of hibernate. Without these, in XP x64, Thorium crashes on first launch after reboot, 360Chrome crashes on first launch after reboot, Supermium crashes on first launch after reboot, Ungoogled crashes on first launch after reboot. Again, please contact the DEVELOPER, they are there for a REASON and you ASSUME that just because Chrome-based works for YOU on YOUR system WITHOUT these, "then it must work for everyone". I can only tell you what I have witnessed. In Thorium. In 360Chrome. In Supermium. In Ungoogled. ON MY SYSTEM. In XP x64 only. Contact the developer. Ask him/her WHY these vulkan files are NEEDED for first launch after reboot or hibernate. I REALLY DON'T CARE. You are just trying to prove your "advice" correct. Your advice DOES NOT WORK in XP x64. First launch after reboot or hibernate. MY computer. Go out and buy a Dell XPS 8700, install XP x64. Or contact the developer. This "I get the last word" or "I'm always right" is kind of UNCALLED FOR.1 point
-
Listen, BOTH you and I are no "dummines" when it comes to computers. We BOTH know our way around computers! Firefox is a telemetry nightmare. Firefox forces the user to go through extreme firewall rules due to its "loopback" quote-unquote "feature". MOST users are CLUELESS when it comes to FIREWALL RULES SETUP (I do NOT include you in this subset of "users"). MOST users when faced with a "firewall poppup" upon launch of Firefox just click the STUPID dialog where the firewall asks "is this a WEB BROWSER" or the firewall just ASSUMES "yes, this is FIREFOX, so I'll just use default "web browser" rules. No offense to these "users", but this really is the STUPIDEST thing I have ever witnessed over the years - "just let Firefox make ANY connection it wants to, I'll accept the default firewall rules, I trust Firefox". THIS TRUST IS MISPLACED! Firefox really is the biggest telemetry nightmare I have ever come across! AND THAT INCLUDES A CHINESE/RUSSIAN REPACK OF 360CHROME !!! This "loopback" (1 byte several times each and every second) was referred to as a *BUG* in the days of Windows 2000, it's just "accepted" as 'normal behavior' by Firefox users today that DO NOT CARE (nor KNOW HOW to monitor these "loopback connections"). A CPU cycle is a CPU cycle. Make it perform a task and that means other tasks are delayed. I am NOT a Chrome/Chromium "fanboy". This world is full of "lesser of two EVILS". All OT regarding Thorium, of course. But let's be perfectly honest, if THORIUM (or 360Chrome!) made the HUNDREDS (literally!) of telemetry connections that FIREFOX does (esp FIRST LAUNCH), none of us would turn a blind eye !!! YET ALL FIREFOX USERS TURN A BLIND EYE REGARDING FIREFOX TELEMETRY CONNECTIONS !!! Firefox users "today" really are VERY different from those that used it in the 90s. Tout privacy and security but clueless that they have "sold their soul". "Do as I say, don't do as I do." But I digress...1 point
-
yes, smaller icon spacing "XSS" would be great if that were implemented. 7++ Task Bar Tweaker, the programmer does not support Windows 11 24H2! (the updates have been coming for some time, via Windows update) I have already written to him twice about this, he says it is a beta version, which is not true.1 point
-
Another bug I found with 3.8.3 With Firefox I get a list of open windows, very nice, but the list is way too small to read the text. With Notepad, I get a preview of the windows which I don't need as I still don't know what I need. I would like to have the text list for all apps. Is there a setting?1 point
-
That would be great to get even smaller spacing. XXS. I've used 7++ Task Bar Tweaker since many years. Now SAB replaced all other functionallity except one: I'm not able to reorder tabs withing a group. e.g. I have 10 Firefox windows and want to reorder them, how can I do it? Any one more function I'm missing but its not important. I have the new context menus everywhere except the taskbar. With SAB I can only use classic context menu everywhere or not at all. Great work with SABs. Thanks. One question. When I use the "new font for classic UI" option, which font is used and where is is used? I can see the desktop icons font changes.1 point
-
Hi, It's about the task bar, the icon spacing is set to XS in my SAB. The icon spacing is still too big for me. Is there a way to reduce it even further in the registry?1 point
-
I reinstall my XP at least three times per year! I know EXACTLY the state of my XP. What I'm hearing you say (if I recall correctly) is that you do NOT install this often. So no offense, but I really do not believe for one second that you can "remember" what you did to the registry 5 years ago, let alone 20. I *DO* think that something you did in your registry 20 years ago is *WHY* your POSReady is not behaving the same as your non-POSReady as far as Thorium is concerned. How many "default" browsers did you install and uninstall in those 20 years? Did they have MALFORMED registry entries such as the Thorium .reg file? (I do not use the Thorium .reg file, I have no clue if this claim of inaccuracy is correct or not.)1 point
-
YES! My only conclusion is that these are not "100%" VULKAN files. The UPSTREAM Chromium programmers seem to be using "something" contained within these SO-CALLED "vulkan" files for some other purpose. And forgive the directness, but I lose confidence in those that tell me I do not need these files. I am not a "dumb" computer user, I know my way around computers. I'm no "genius", but I know my way around computers. I need these "vulkan" files on my XP x64.1 point
-
Google's definition of "Low end" is very laxed, I tried to run Thorium on an ancient 775 socket computer, it still says: low end - no.1 point
-
I have. Regardless of what you and D.Draker think on this matter, I CANNOT LAUNCH 360CHROME ON XP x64 "when I follow your advice" regarding VULKAN FILES.1 point
-
1 point
-
I wouldn't quite say it that way. I think it was also you (do not remember!) that was suggesting I axe "vulkan" .dll's. THAT suggestion KILLED my Chromium-based on MY computer. So yeah, I started "listening" a tad differently. "Is what it is"1 point
-
Nah they ain't that smart I guess. They're known for doing senseless decisions from time to time.1 point
-
it is better to report "archive name" instead of build ID since build ID is not always updating itself in every build.1 point
-
cleaned up and rebased pm27 history repo is here: https://github.com/roytam1/palemoon271 point
-
yeah, I'm preparing a Tycho-history repo for a clean history (like my palemoon*-history repos) will have a look after history repo is ready. yes, they ported upstream(mozilla-esr) changes into their repo, and I cherry-picked non-PowerPC exclusive patches into my repo, and M*** are actually bugzilla.mozilla.org bug numbers.1 point
-
New Palemoon 27 Build! * This build is on par with official 27.9.4 build. 32bit https://o.rthost.cf/palemoon/palemoon-27.9.1a1.win32-git-20180714-4038e3c24-xpmod.7z 32bit SSE https://o.rthost.cf/palemoon/palemoon-27.9.1a1.win32-git-20180714-4038e3c24-xpmod-sse.7z 32bit noSSE https://o.rthost.cf/palemoon/palemoon-27.9.1a1.win32-git-20180714-4038e3c24-xpmod-ia32.7z 64bit https://o.rthost.cf/palemoon/palemoon-27.9.1a1.win64-git-20180714-4038e3c24-xpmod.7z source patch against official palemoon: https://o.rthost.cf/palemoon/sources_patches_20180602.7z Official repo changes since my last build: - Make nsAtomicFileOutputStream::DoOpen() fail if the file is read-only. (9ced22633) - Update mozharness reqs. (9cb81d2cc) - Update requirements.txt (4038e3c24) My changes since my last build: - Port TenFourFox changes: + Ported changes: bug1385395, bug1375599, bug1381157, M1395138_M1400003_M12611751 point
-
TenFourFox AdBlock list is a very small(i.e. limited) one by blocking hosts, people can enable it by their choice.1 point
-
New Palemoon 27 Build! * This build is on par with official 27.9.4 build. 32bit https://o.rthost.cf/palemoon/palemoon-27.9.1a1.win32-git-20180707-54887c52d-xpmod.7z 32bit SSE https://o.rthost.cf/palemoon/palemoon-27.9.1a1.win32-git-20180707-54887c52d-xpmod-sse.7z 32bit noSSE https://o.rthost.cf/palemoon/palemoon-27.9.1a1.win32-git-20180707-54887c52d-xpmod-ia32.7z 64bit https://o.rthost.cf/palemoon/palemoon-27.9.1a1.win64-git-20180707-54887c52d-xpmod.7z source patch against official palemoon: https://o.rthost.cf/palemoon/sources_patches_20180602.7z Official repo changes since my last build: - Check redirect status code before forwarding to NPAPI. (4a7f5bc0b) - Confirm launch of executables other than .exe on Windows. (93403cdeb) - Confirm launch of executables other than .exe on Windows. (d8e715cff) - Reject some invalid qcms transforms. (f929ffa0e) - Update dimensions early in ClearTarget. (1abb23fdf) - Perform some sanity checks on nsMozIconURI. (e50a11dfe) - Ensure the right anonymous element is focused when calling input.focus() (8b999f2be) - Fix typo (RefPtr -> nsRefPtr) (54887c52d)1 point
-
a related post about it is here: https://msfn.org/board/topic/177570-slowness-when-accessingposting-forum-post1 point
-
1 point
-
1 point
-
replace pm26.win2000 files with this: http://o.rthost.cf/gpc/files1.rt/pm26xp-no-manifest.7z1 point