Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 10/21/2024 in all areas

  1. Yes, you do, there were several reports of different brightness levels in CatsXP (no modifications, just running only on kernel-ex), ported Chrome 115 (mine), default version of Brave and even Ungoogled! Supermium is brighter than all of those above, also has thicker, blurry fonts. I talk about all fonts (including the UI). The winners are Ungoogled and Brave.
    2 points
  2. How then you'd explain it works (like it supposed to) in a normal Chrome 115? Unfortunately, I can't test both of 121 version, because I only have a self-ported v115 at my disposal. But then again, in older tests 115 vs 115, Supermium was also brighter.
    2 points
  3. Thanks, tried that, the white text is still too white, besides it has no affect on the Supermium UI. I have 16GB, no lagging was observed.
    2 points
  4. Missed my post again, I wonder if folks these days read before posting. It's rather insulting to assume I didn't try all available drivers before troubling win32. I mean, it's me we are talking about, not a random github fella. "I tried other drivers, all the same." https://msfn.org/board/topic/185045-supermium/?do=findComment&comment=1259724
    2 points
  5. Disagreed. Any comparison is only valid within the same Chromium version.
    2 points
  6. I'm sorry , I don't know for sure , maybe Nero ? I remember I had a laptop which came with Nero 8 preinstalled , it was so long ago , I think it had something like that in it's Wave Editor. MPC-HC/MPC-BE is not for me , thanks , I don't like the controls.
    2 points
  7. Thanks , I see , but the buttons are still ugly . I mean not much difference between these and the buttons I have . I think I'll just throw VLC away and start using another player . Thanks for the help , everyone .
    2 points
  8. All of that seems far too complicated. Not because it's "not easy", I don't mind "not easy". But because most people aren't going to sift through a read SEVEN pages long and add over a HUNDRED rules just to browse YouTube! I've never had to do ANY of that and I'm on YouTube 8-12hrs per day here at work. ZERO ads. ZERO banners. ( I do not get the cited banner even with all extensions disabled!) With nothing more than the already-included filter lists that come with uBO (well, with AdNauseum based on uBO). No added "my filters", no hunting down lists from "list sites", no hurdles to jump, no hoops to jump through. I don't even have to use any of the "annoyances" filters.
    1 point
  9. If you call tricks what you get with 8+, keep' em. (https://msfn.org/board/topic/174160-guide-disable-data-collection-in-windows-10/#comments, https://msfn.org/board/topic/174208-windows-10-deeper-impressions/#comments, etc. etc. etc.) PS: besides, look at the title of the thread you are in.
    1 point
  10. This means W7 minimum + Firefox ESR (up to march 2025).
    1 point
  11. Version is not important. NONE will work in 360Chrome. NONE will work in Supermium. NONE will work in Thorium. NONE will work in Ungoogled Chromium. YOU MUST USE OFFICIAL CHROME OR OFFICIAL FIREFOX if you want Netflix to work with WINDOWS! There is no way around it because Netflix links a "browser" .sig file with your browser's Widevine .sig file. What you are trying to do is bybass the "browser" .sig file - this cannot be done in WINDOWS. It can, however, be done in LINUX. Only OFFICIAL CHROME and OFFICIAL FIREFOX have the MONEY to PAY for the .sig file! 360Chrome, Supermium, Thorium, and Ungoogled Chromium do not have the MONEY to PAY for the .sig file.
    1 point
  12. Nope, Last version is 4.10.2830.0 (catched from Kodi ). Earlier versions will no more work.
    1 point
  13. Personally, I would tend to agree to this: Mypal 68 ≈ Firefox (≥ 68). In many ways, Mypal 68 behaves like a normal Firefox browser, but not in all. The JavaScript engine, for example, is comparable to that of higher versions. Mypal 68 is a Quantum browser, which has made it quite difficult to enable the use of UC.JS scripts, for example. The download package MYPAL_68_CB_requirements.7z from my first post is not available anywhere. It is very specific, and stops working in Firefox 72+ due to some code changes. I put together the configuration files myself to make it really work. In higher Firefox versions, the script functionality seems to be much easier to activate. BTW, one file of my package spits out an error in the Browser Console, which I fixed in the meanwhile.
    1 point
  14. I never did that before. How do you go back to an earlier point in a project?
    1 point
  15. FYI, I have tested this, and it doesn't work for me in Mypal 68. Neither the implementation for loading of scripts nor the one for loading of specially adapted bootstrapped extensions from xiaoxiaoflood's project userChromeJS works in Mypal 68.14.4b. The whole project seems to be related to more recent versions of Firefox. Here is a quotation from the GitHub page: The specially adapted bootstrapped extension Download Manager (S3), for example, targets Firefox 125.0a1 and higher.
    1 point
  16. @feodor2 I noticed this issue when creating a custom button for calling up the cookie manager. For reproducing this issue, call up chrome://browser/content/preferences/siteDataSettings.xul, delete a site cookie of your choice, close it, open the site whose cookie you deleted and call up chrome://browser/content/preferences/siteDataSettings.xul again. You will then notice its cookie is not listed although it is there. And when now restarting the browser, the call up of this internal chrome site leads to an empty, broken and non-functional interface. Here is a screenshot of this issue including the TypeError message Uncaught TypeError: this._getQuotaUsagePromise is null SiteDataManager.jsm:255:5 getSites resource:///modules/SiteDataManager.jsm:255 init chrome://browser/content/preferences/siteDataSettings.js:127 onload chrome://browser/content/preferences/siteDataSettings.xul:1 in the Browser Console: Only by calling up the about:preferences page will it work again. BTW, when doing so in an UXP browser as, for example, New Moon 28 or Serpent 52 by calling up chrome://browser/content/preferences/cookies.xul, there is no such problem.
    1 point
  17. I only tested such an extension for the UXP browsers called MTube. But I didn't like it. The extension uTube was and is much better. At the moment, I am totally fine with the VORAPIS V3 extension for Mypal 68.
    1 point
  18. Your contributions are great in my book. Keep on doing them.
    1 point
  19. A very wise decision, why give them an extra opportunity to disparage you. I think I should rephrase what I was trying to say before. I think people might want to read the Github thread to be aware of what's happening - but only those who a) have something useful to add that hasn't already been brought up and, b) can restrain themselves enough to remain polite should go over there to add their thoughts. They can of course also do it here, but the Github issue is more of a place of record. I myself might have met a) in the early stages but b) was pretty doubtful. At this point, a) is also doubtful. @XP2003 Yes, I've seen it. Gotta "love" that one guy actually demanding jail time for @feodor2... I'm reminded of a quote from an R. K. Narayan book about Indian mythology, where he describes asuras (demons) as "strong-minded, intelligent, and capable of offering arguments to establish that they are righteous, and all others are evil-minded". He then adds "They succeed - but, [...], only for a while; sooner or later they are overcome." Let's hope for that. (It's not my style to compare people to demons, but the comparison comes to mind when someone is so incredibly insistent to enforce the letter of the law at the expense of the spirit of it, for very questionable reasons and with clearly damaging cansequences.)
    1 point
  20. Nor should you...you haven't done anything wrong in this or any other case, and your health and well-being should always come first. Thank you for all of your great work over the years! Rest assured--it is never in vain, and never taken for granted!
    1 point
  21. actually impossible. https://hackaday.com/2018/09/27/can-you-take-back-open-source-code/ (P.S.: I'm not going to jump in this mud fight)
    1 point
  22. as I stated before, I don't compile point-releases. dev branch are compiled but (mostly) not uploaded since there is still some bugs that preventing for daily use. and I compile it as verification to see if those changes are working on windows.
    1 point
  23. New regular/weekly KM-Goanna release: https://o.rthost.win/kmeleon/KM76.4.4-Goanna-20210828.7z Changelog: Out-of-tree changes: * update Goanna3 to git 520d6b706...be0dbe88f: - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1185997 - Split referrer tests to avoid intermittent timeouts. r=RyanVM (976fb981a) - Bug 1175736 - Add iframe referrer attribute tests. r=ckerschb, r=baku (f22da1340) - Bug 1184781 - additional referrer tests - redirect. r=christophkerschbaumer (49f1aaea0) - Bug 1186544 - A better test suite for StructuredCloneAlgorithm, r=smaug (d94f76a45) - Bug 1167690 - Part 5: Add tests for plugin audio channel integration; r=baku (26931ea9d) - Bug 1144631 - Make FTP with auth prompts work in e10s. r=billm/dragana (e69f9f5e0) - Bug 1179255 - (fatal) Assertion failure: aRequest == mCancelable, at netwerk/protocol/websocket/WebSocketChannel.cpp:2766, r=mcmanus (e1e3d6799) - Bug 1024056 - Simple ASCII lexical analyzer. r=nfroyd (dc67ec784) (ac77268e0) - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1189369, part 1 - Remove trailing whitespace from some nsNavHistory* files. r=mak (317dd5937) - Bug 1074416 - Don't AddRef or Release nav history result observers during CC traversal. r=smaug (2ce1e8cc6) - Bug 1189369, part 2 - Don't implicitly convert nsMaybeWeakPtr to an nsCOMPtr. r=mak (c4c3261e5) - Bug 1189369, part 3 - Inline nsMaybeWeakPtr_base. r=mak (efdb4fd76) - Bug 1189369, part 4 - Get rid of some old style QIs from nsMaybeWeakPtrArray. r=mak (fa534f76c) - Bug 1189369, part 5 - Use the nice cycle collector macro template for nsNavHistoryResult. r=mak (f1fafbdc9) - Bug 1189369, part 6 - Inline AppendWeakElement and RemoveWeakElement. r=mak (514efe9f8) - Bug 1189369, part 7 - Use nicer nsTArray functions in nsMaybeWeakPtrArray. r=mak (38384b1a1) - Bug 1189369, part 8 - Clean up some minor style issues in nsMaybeWeakPtr.h. r=mak (3f37712f9) - Bug 1189369, part 9 - Use early return in nsMaybeWeakPtr<T>::GetValue(). r=mak (5606a69c5) - Bug 1180498 - Tolerate a different major libGL.so on NetBSD as well r=jgilbert (4f7c00f01) - pointer style (44d4789bd) - Bug 1182428 - Refactor bytecode compilation r=luke (790c13aa2) - Bug 1163851 - Pass the correct |InHandling| argument when parsing the initializer in a LexicalDeclaration in a for-in loop. r=efaust (e6b891d53) - reapply Bug 1163851 - Remove the remaining two tests of |pc->parsingForInit| (c59d57225) - Bug 1180498 - Tolerate a different major libGL.so on NetBSD as well r=jgilbert (9463d2aea) - Bug 1189282 - Refactor parser BindData class r=efaust (4dd897771) - Bug 1179063 - Hook up the static scope chain in the Parser and replace SharedContext walking with scope walking. (r=efaust) (70b8fdd1e) (5cdc3234f) - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1186724 - Make BytecodeEmitter::emit2 take a uint8_t instead of a jsbtyecode; r=arai (0520b800d) - Bug 1179063 - Simplify enclosingStaticScope and rename to innermostStaticScope in BCE. (r=efaust) (9b80db494) - Bug 1179063 - Cleanup: remove useless pn_index. (r=me) (8c0599c32) - Bug 1155618 - Fix some more places we don't report OOM properly r=jandem (4c45f314a) - Bug 1165486 - Debug function to dump static scope chain of scripts. (r=efaust) (3de10d2bf) - Bug 1191177 - Kill UpvarCookie. (r=efaust) (373fe90f3) - Bug 1191177 - Kill staticLevel. (r=efaust) (a8734595e) (be0dbe88f) * Notice: the changelog above may not always applicable to XULRunner code which K-Meleon uses. A goanna3 source tree that has kmeleon adaption patch applied is available here: https://github.com/roytam1/palemoon27/tree/kmeleon76
    1 point
  24. New NewMoon 27 Build! 32bit https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20210828-be0dbe88f-xpmod.7z 32bit SSE https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20210828-be0dbe88f-xpmod-sse.7z 32bit noSSE https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20210828-be0dbe88f-xpmod-ia32.7z 64bit https://o.rthost.win/palemoon/palemoon-27.10.0.win64-git-20210828-be0dbe88f-xpmod.7z source repo: https://github.com/roytam1/palemoon27 repo changes since my last build: - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1185997 - Split referrer tests to avoid intermittent timeouts. r=RyanVM (976fb981a) - Bug 1175736 - Add iframe referrer attribute tests. r=ckerschb, r=baku (f22da1340) - Bug 1184781 - additional referrer tests - redirect. r=christophkerschbaumer (49f1aaea0) - Bug 1186544 - A better test suite for StructuredCloneAlgorithm, r=smaug (d94f76a45) - Bug 1167690 - Part 5: Add tests for plugin audio channel integration; r=baku (26931ea9d) - Bug 1144631 - Make FTP with auth prompts work in e10s. r=billm/dragana (e69f9f5e0) - Bug 1179255 - (fatal) Assertion failure: aRequest == mCancelable, at netwerk/protocol/websocket/WebSocketChannel.cpp:2766, r=mcmanus (e1e3d6799) - Bug 1024056 - Simple ASCII lexical analyzer. r=nfroyd (dc67ec784) (ac77268e0) - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1189369, part 1 - Remove trailing whitespace from some nsNavHistory* files. r=mak (317dd5937) - Bug 1074416 - Don't AddRef or Release nav history result observers during CC traversal. r=smaug (2ce1e8cc6) - Bug 1189369, part 2 - Don't implicitly convert nsMaybeWeakPtr to an nsCOMPtr. r=mak (c4c3261e5) - Bug 1189369, part 3 - Inline nsMaybeWeakPtr_base. r=mak (efdb4fd76) - Bug 1189369, part 4 - Get rid of some old style QIs from nsMaybeWeakPtrArray. r=mak (fa534f76c) - Bug 1189369, part 5 - Use the nice cycle collector macro template for nsNavHistoryResult. r=mak (f1fafbdc9) - Bug 1189369, part 6 - Inline AppendWeakElement and RemoveWeakElement. r=mak (514efe9f8) - Bug 1189369, part 7 - Use nicer nsTArray functions in nsMaybeWeakPtrArray. r=mak (38384b1a1) - Bug 1189369, part 8 - Clean up some minor style issues in nsMaybeWeakPtr.h. r=mak (3f37712f9) - Bug 1189369, part 9 - Use early return in nsMaybeWeakPtr<T>::GetValue(). r=mak (5606a69c5) - Bug 1180498 - Tolerate a different major libGL.so on NetBSD as well r=jgilbert (4f7c00f01) - pointer style (44d4789bd) - Bug 1182428 - Refactor bytecode compilation r=luke (790c13aa2) - Bug 1163851 - Pass the correct |InHandling| argument when parsing the initializer in a LexicalDeclaration in a for-in loop. r=efaust (e6b891d53) - reapply Bug 1163851 - Remove the remaining two tests of |pc->parsingForInit| (c59d57225) - Bug 1180498 - Tolerate a different major libGL.so on NetBSD as well r=jgilbert (9463d2aea) - Bug 1189282 - Refactor parser BindData class r=efaust (4dd897771) - Bug 1179063 - Hook up the static scope chain in the Parser and replace SharedContext walking with scope walking. (r=efaust) (70b8fdd1e) (5cdc3234f) - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1186724 - Make BytecodeEmitter::emit2 take a uint8_t instead of a jsbtyecode; r=arai (0520b800d) - Bug 1179063 - Simplify enclosingStaticScope and rename to innermostStaticScope in BCE. (r=efaust) (9b80db494) - Bug 1179063 - Cleanup: remove useless pn_index. (r=me) (8c0599c32) - Bug 1155618 - Fix some more places we don't report OOM properly r=jandem (4c45f314a) - Bug 1165486 - Debug function to dump static scope chain of scripts. (r=efaust) (3de10d2bf) - Bug 1191177 - Kill UpvarCookie. (r=efaust) (373fe90f3) - Bug 1191177 - Kill staticLevel. (r=efaust) (a8734595e) (be0dbe88f)
    1 point
  25. I'm not @feodor2's spokesperson, but since you're asking me, the source for the latest Centaury release (0.17.0) looks to be at https://github.com/Feodor2/Mypal/archive/b9d3b502ef4786aa77d30e9ace63494422fa00a4.zip Sorry, too busy atm to properly write up the steps to get there, but I can say that I was able to figure it out without ever asking @feodor2 (or anyone else) about it.
    1 point
  26. Because they can't. Unless they rewrite whole engine without using any mozilla code to get rid of MPL2 license. I do pre-release (there is no point-release) and people should be able to find exact git commit revision that I use to build from my snapshot notes.
    1 point
  27. This is XP (which I love, as y'all know)... so, no, there'll not be many "newcomers", in fact, and most "outgoers" are long gone, already. Whoever ventures here from scratch now needs to be very interested, ultra very motivated, and patient, to be able to get anything working (or be a leach who deserves to writher in the sun while starving!) so, no: if one needs spoon feeding, anything earlier than 1x ( ) is not for them. Let roytam1 worry with meaningful things, not that. As people at old Aston Martin used to say to those who insisted their cars ought to display some indication of what it was in the front: "if one looks at the rearview-mirror and doesn't recognize instantly it's an Aston Martin, they don't deserve to know it!".
    1 point
  28. Installed just for you to see the option ! Yep , I was right ! Nero has "pitch tuning" option right in the Wave Editor !
    1 point
  29. I might just use MPC-HC/MPC-BE if not for the absence of pitch changer. Is there any player that has a pitch changer other than VLC? EDIT : Winamp's interface does not look good to me, so I won't prefer it
    1 point
  30. I have the same result on Win 7 N SP1 (European version , for those who are wondering) . And this is on a clean install without patches and with kb3125574-v4 installed , the result is the same , I'm sorry , I can't make that high quality pictures , like @Dixel made . I'm maybe mistaken , but you wrote that too about Win 7.
    1 point
  31. And what I'm trying to say , Aero buttons are still absent even in 2.2.8 (not to mention 3.x.x.) and even with the hex edit. (do you want me to repeat again?) Yes , I agree with Dixel , they somewhat look better after hexing , some curves are added , they don't look as flat as before , but nowhere near the previous ones , that you (and most of us) wanted to see . So hexing is NOT the ultimate solution , it's better to roll-back to earlier versions , 2.2.6 something. I don't quite understand how "testing again using a maximised window" will help with the aero look in the butoons . I'm just starting to think you don't understand English well enough , or have a poor LCD display and simply can't see the obviuos difference , excuse me if I'm wrong (in advance) , but it's pretty obvious and shown well enough at Dixel's picture with the patched 3.3.x and NOT patched 2.2.x . Also , his upper frame looks prettier than the one that you provided , I mean the shape , not the colour , since it is his own customized colour. In case you don't agree or understand again , please refrain from asking me 'cause I simply can't tell you anything new apart from what I've already said , please ask other members if they see the obvious differnce at the Dixel's picture .
    1 point
  32. 1 - You mean the first picture in this topic where aero is totally absent ? I can't reproduce it no matter how hard I try , Ive tested on an a clean install , without any mods. I mean , yeah , I can find a newer version where the buttons will be flat , but the aero is always working with all versions ! Known or had it youself ? If it is easily reproduced , could you show us a pic. ? I'm curious. Thanks. 2 - The screen of the user named @Dixel clearly shows that aero is working and it is transparent , in both versions, patched and unpatched , don't you see ?
    1 point
  33. Dixel , please show us the full comparison of something older , like 2.x.x and anything higher than 3.x.x. Thanks
    1 point
  34. Have you tried any games that use "MonoBleedingEdge" ? There are plenty of them now , even though the main executable doesn't have anything against Vista , that dreaded "mono" won't load . The error "can't load mono" , that's it . Adding files isn't helping.
    1 point
  35. Honestly , I think Chrome is not needed when we have 360 , Chrome has sooo much telemetry alone, even without added Chinese prying eyes , I see no reason to use it without removing it first . I mean , let's say I found some time to sit and edit it , then I'll better add some more time to remove it from 360 and be with a much faster and convenient browser. It's not that I like it, it's just I'm choosing between these evils. I don't like anything modern at all. Besides , Chinese working for Google , aren't they ?
    1 point
×
×
  • Create New...