Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 02/15/2024 in all areas

  1. As @VistaLover already pointed out, this is a thread about @roytam1's browsers and only about extensions targeting these browsers. @nicolaasjan indeed used the <Offtopic> tag but you didn't. That kind of offtopic from you causes such misunderstandings in the end. Windows 11, Chrome browsers and their webextensions are definitely not the topic here.
    3 points
  2. The processor is exactly what affects this. I have tested Supermium on many different computers, from a very low-end Atom to an i7, but the problems with freezing or inability to start have only occurred on a single-core processor. On one system it doesn't start at all, on another it starts, but every action causes the CPU to load at 100% for a long time. The developer is aware of this problem, maybe in future updates it will be solved.
    2 points
  3. @SEDANEH No, the lack of an IDE connector doesn't matter. You'll need to learn to use the methods we showed you, or you can use the ISO that dietmar made for you. We're willing to help you, just ask.
    2 points
  4. As most following these threads probably know already , all the XP/Vista compatible 360EE variants (v11/12/13/13.5) are NOT compatible with MV3 Chrome extensions (which require at least Chromium 88) and, in the same vein, are NOT compatible with the "new" Chrome Web Store (CWS) ... Since sometime on Feb 13th, 2024 (depending on your location), "old CWS" URIs for extensions/themes/etc., of the format: https://chrome.google.com/webstore/detail/* now auto-redirect to the "new CWS" URIs for the same extensions/themes/etc., of the format: https://chromewebstore.google.com/detail/* This isn't a first occurrence, the same thing used to take place during the autumn of 2023, when the eventual migration to the new CWS was announced beforehand: https://support.google.com/chrome/thread/231812199 https://blog.google/products/chrome/google-chrome-web-store-redesign/ https://9to5google.com/2023/11/20/google-chrome-web-store-redesign-preview/ In late December 2023, this auto-redirection (old -> new CWS) in non-supported Chrome versions stopped taking place, but in the loaded old CWS appeared a top info-banner indicating that: The user could disregard/remove this banner and continue as usual ... Well, Jan 31st 2024 came and went, but the "status quo" remained in place until Feb 13th, when the auto-redirection to the new CWS resumed ... Google staff seem to have a perverse sense of "humour" , because after the auto-redirection has been completed, in non-supported Chrome versions, a new in-page banner is being displayed, stating: However, clicking on the "Visit legacy store" area (JS-controlled button) will only start a vicious circle , resulting in that same "new CWS" page ... Issues with the "new CWS": The older the 360EE version you have, the more page rendering issues you'll get ; below, a screengrab with 360EEv11 (Ch69-based): Apart from the overlapping fonts, all "carousels" in the page are absent/non-functioning, because they require JS+CSS code not supported there ; these rendering issues are less/absent on higher versions of 360EE (v12+) ... But the main issue is that you can't install/download extensions from the "new CWS", because the "Add to Chrome" button is greyed out ... Mitigations This third party userscript, when installed (requires a userscript manager, e.g. Violentmonkey, Tampermonkey, etc.), will make the "Add to Chrome" button active again, however its functionality will now be limited, in that it will only enable a .crx file download to disk, not proper installation (as was the case with the "old CWS"); after saving to disk, the user has to drag-n-drop the saved file onto the "chrome://extensions/" internal tab, for the installation to proceed... The problem with that userscript is that the "name" of the downloaded extension always comes up as "undefined" (the "version" comes up correctly), so some renaming is in order after the download (perhaps one savvy person here could fix the script in that regard? ) ... Another solution I've been using is based on this extension ; the problem is that the latest version, 1.51, compatible with the "new CWS", is of the MV3-type, thus incompatible with 360EE (and Kafan MiniBrowser); here's an MV2 custom patch that will install and function as expected under Ch<88: https://www.mediafire.com/file/on5h2vit08a1xk6/1.51-mgdjkephahlgejakcnbooghhocmoppai-MV2.crx/file BTW, this is an "anonymous" upload that will expire after 2 wks of inactivity ; once installed, use the context menu on a "new CWS" tab to fetch a .CRX file to disk... Caveats of the two solutions above is that the "new CWS" won't label incompatibilities with Ch<88, so the .CRX you end up saving to disk may well be an MV3-type extension, incompatible with your "legacy" Chrome browser ; I probe the CRX files with 7-zip, opening their manifest.json files with an editor and checking for the "manifest_version" value (to be 2, that is...). A third option that might die any day now is the following: Make a bookmark of below URI: https://chrome.google.com/webstore/old/ Once loaded, it'll auto-redirect to: https://chrome.google.com/webstore/category/extensions which is STILL the "old CWS"; as long as your browsing remains confined inside that very one tab, you can access extension-URIs in the old format, e.g. by clicking on suggestions or searching in the old-store's searchbar (and make sure the search result is opened in the same tab): The back and forward nav buttons are allowed, but be sure not to click the reload one (will get you to the new CWS) ; since this is the "old CWS", it won't offer (to your "legacy" browser) MV3-type extensions in the suggestions/search results ... Of course, as time moves on, the MV2-type extensions now found inside the "new CWS" will be eventually all migrated to MV3 or purged completely, thus these workarounds will become moot... Save your MV2-type indispensable Chrome extensions while you can... PS: I'm dead certain evil Google will make sure your Ch<88 will become less effective in browsing the web over time, but I feel it'll still be good for the next two years, at least - here's hoping (of course, browsers based on much newer Chrome versions have recently surfaced that can launch under XP/Vista, granted with several issues so far, but this analysis was targeting mainly 360EE/KMB users) ...
    2 points
  5. No, no, no, I never said that, and don't even plan to do that at all. In fact, I actually find using old OSes like XP or Vista (and even 2000, if we are to go to the mimimum of Older NT-Family OSes) very fun. Please, don't assume stuff I don't plan to say. Also, I don't disrespect your own reasons for not wanting to use something, so please, kindly respect my own reasons for not wanting to use something. Thanks What are you here talking about? My statement doesn't mention you at all. It was just a reply to @VistaLover. Grammatically, it's simply a conditional clause type I. That means it expresses a fulfilable wish or condition. Furthermore, it was formulated without any reference to a certain person, which apparently escaped your attention for whatever reason. First read, then think, and only then post would be much wiser! And please, stop such kind of interpretions! Thanks!
    2 points
  6. BTW, is it not rather the case that the legacy version of Adblock Plus is much older than the legacy version of uBlock Origin? I had a look at GitHub. The last version there is 2.9.1 from June 2017. Same version in the CAA. And its repository has been archived by the owner on Jan 26, 2024 https://github.com/adblockplus/adblockplus-legacy/tags. It is now read-only. I can't find any more recent version right away. And Adblock Latitude in version 5.0.9 is from May 2022 which I tried a very short time in the past. Very resource-hungry and not recommendable. So far as New Moon or other UXP browsers are concerned, Adblock Plus and its forks are not really an interesting alternative to uBlock Origin. And even the last webextension of Adblock Plus for Serpent in version 3.12 is from May 2022. Same problem with the webextension Adblocker Ultimate. The version 3.7.12, which is the last compatible version with Serpent, is from Oktober 2021.
    2 points
  7. That's indeed very funny. If something from 2021/2022 is old, then it's better not to use Windows XP or Windows Vista. They are much, much older.
    2 points
  8. Found! Generic bluetooth 5.0 is what he wants. "I can't even find Windows XP or 7 drivers for generic bluetooth 5.0 dongles on ebay." https://msfn.org/board/topic/185881-seeking-bluetooth-30-ud-300m-usb-drivers-for-windows-98seme/?do=findComment&comment=1259897
    2 points
  9. @win32, btw , you wrote you don't have that file when you install the driver , right ? So I installed 456.71 on a spare Win 7 PC with GTX780Ti, just to look what files are created, so here I made an export : 456.71 filename full.txt nvDevTools.dll nvDevToolsR.dll nvdisps.dll nvdispsr.dll nvgames.dll nvgamesr.dll nvlicensings.dll nvLicensingSR.dll nvmccss.dll nvmccssr.dll nvmobls.dll nvmoblsr.dll nvsmartmax.dll nvsmartmax64.dll nvsmartmaxapp.exe nvsmartmaxapp64.exe nvsvs.dll nvsvsr.dll nvui.dll nvuir.dll nvvitvs.dll nvvitvsr.dll nvwss.dll nvwssr.dll nvxdapix.dll nvxdbat.dll nvxdplcy.dll In reality , one can delete everything except these : nvdisps.dll nvdispsr.dll nvgames.dll nvgamesr.dll nvsmartmax.dll nvsmartmax64.dll nvsmartmaxapp.exe nvsmartmaxapp64.exe nvui.dll nvuir.dll nvvitvs.dll nvvitvsr.dll nvxdapix.dll nvxdbat.dll nvxdplcy.dll
    2 points
  10. Mine doesn't . That's why I included the manual patching process with WinHex in the tutorial. Which version do you run ? I guess I was wrong when I thought it would eliminate questions like from the above.
    2 points
  11. You defo need to read before you post, all of that was tested by me a long time ago (including the 391.35). The NVCPL in the 39x.xx does NOT work.
    2 points
  12. Keep it up brother! I want to see Windows 7 making a comeback.
    1 point
  13. Try sticking to the English version of 98SE and setting the locale to Czech because a lot of (un)official patches are only available for the English version. I no longer recommend big unofficial Service Packs for 98SE, install only whatever given program/game requires. (like IE6 SP1, DX9.0c, WMP9, VC++ 2005 redist, InstMsiA, etc...) Make sure you are using the SHELL32.DLL fix after IE6 SP1 is installed: https://msfn.org/board/topic/84451-98-fe-98-sp1-98-se-me-shell32dll-fix/ You can also use Windows Update Restored v4 to have as close as the original experience back in the day of updating 98SE: http://windowsupdaterestored.com/
    1 point
  14. ... I was mainly unavailable at the time that request was made; RL issues , plus I was researching/studying something else then, that couldn't be interrupted; hope you understand ... As a matter of fact, I didn't come up myself with anything else adding more "substance" to what you have already mentioned about the startupCache ; it would seem the relevant literature about it has been wiped out by now... Mozilla mention very little about it now, even below URI: https://firefox-source-docs.mozilla.org/contributing/directory_structure.html#startupcache has an empty description for it (which, personally, I find totally unacceptable ); mozillazine (not directly affiliated with Mozilla) do mention something (but very little, TBH) not in relation to Fx, but in relation to the e-mail client, Thunderbird: https://kb.mozillazine.org/Profile_folder_-_Thunderbird More info about the referenced startupCache.4.little file (inside the startupCache directory) was to be found in MSFN itself: https://msfn.org/board/topic/180462-my-browser-builds-part-2/?do=findComment&comment=1196115 The info there seems to be echoed by this dev's comment: https://groups.google.com/g/mozilla.dev.extensions/c/HM2GNAll_aU Unless instructed otherwise, for troubleshooting purposes (like in the recent case ), I tend to leave it alone in my UXP-based browsers; once a month I perform some profile "housekeeping" and IF the ".little" file has grown somewhat bigger , I may manually delete it - I've also confirmed it is, indeed, a compressed file format, because it can be easily extracted with 7-zip and its contents then probed ... That's all I found out, basically ... Regards.
    1 point
  15. I totally agree. And to tame and purify bloated websites, which are unbearable, for example, in New Moon 28, the extension uBlock Origin with good filter lists selected is the ultimate tool. Therefore, your recommendation here is not off-topic at all. A wonderful example is the website https://www.pcwelt.de/. If you surf this website with New Moon 28, you'll puke if you access it without the content blocker uBlock Origin. Especially on weaker hardware. However, with uBlock Origin enabled, it blocks nearly 1000 requests in my installation. Now, this site can be accessed easily again and seems to be suddenly a light one.
    1 point
  16. New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20240210-3219d2d-uxp-20d660f3c8-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20240210-3219d2d-uxp-20d660f3c8-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20240210-3219d2d-uxp-20d660f3c8-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20240210-d849524bd-uxp-20d660f3c8-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20240210-d849524bd-uxp-20d660f3c8-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20240210-d849524bd-uxp-20d660f3c8-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20240210-d849524bd-uxp-20d660f3c8-xpmod.7z Official UXP changes picked since my last build: - Issue #2465 - Do not use our in-tree metrics hints if using system-cairo (6d1bf36717) - Issue #2466 - Part 1: Reduce nsContentPolicy type usage. (4ea2206c15) - Issue #2466 - Part 2: Implement script-src-elem and script-src-attr (ff01a35bdb) - Issue #2466 - Part 3: Implement style-src-elem and style-src-attr (721ded9b48) No official Pale-Moon changes picked since my last build. No official Basilisk changes picked since my last build. My changes since my last build: - remove terse static assert added by upstream (20d660f3c8) Update Notice: - You may delete file named icudt*.dat inside program folder when updating from old releases. * Notice: From now on, UXP rev will point to `custom` branch of my UXP repo instead of MCP UXP repo, while "official UXP changes" shows only `tracking` branch changes.
    1 point
  17. Yes, thats wonderfull, was wondering whats the difference between your kernel and this one: https://github.com/vxiiduu/VxKex it seams this one does not require any core system files to be patched but is not developed anymore... I also found this: https://github.com/Blaukovitch/API-MS-WIN_XP which is a ported windows 11 apis back to windows 7 and XP which might be usefull to make programs that for some strange reason require (the strangest is when an updated does that) newer apis that windows 7 lacks
    1 point
  18. Today I released v3 of the Windows 7 Extended Kernel. Please give it a try! =)
    1 point
  19. PLEASE do not use Discord for software distribution and choose something that is likely to still be up in X years.
    1 point
  20. Although in Germany the Federal Office for Information Security (BSI) warned against the use of anti-virus software from the Russian manufacturer Kaspersky on 15 March 2022 https://www.bsi.bund.de/DE/Themen/Unternehmen-und-Organisationen/Cyber-Sicherheitslage/Technische-Sicherheitshinweise-und-Warnungen/Warnungen-nach-Par-7/Archiv/FAQ-Kaspersky/faq_node.html, I don't really share such concerns. The developers of Kaspersky software would ruin the entire company if they implemented malicious code in their software. For me, it's about a general statement, a sign of solidarity. And that may not always be fair, however Kaspersky has to thank for that a certain person.
    1 point
  21. For me, it is basically irrelevant in which country the software I use was developed. But every rule has its exceptions. What these look like in detail in my case cannot and won't be discussed here for well-known reasons. China exists to benefit Windows XP diehards? Nice try! As we all know, imagination knows no boundaries.
    1 point
  22. Yep, unfortunately! Unpredictable and unauthorised actions every now and then! Basically, avast! 2018 is a good protection program. I used avast! Premier in my system for years. But there were several reasons to switch to other programs. You can read more about that in this post: You should definitely reinstall avast! 2018 at regular intervals if you want to use this program in your system I personally no longer use avast! 2018. My protection program has been Malwarebytes Premium 3.5.1.2522 for some time, and I am satisfied with it. Cheers, AstroSkipper
    1 point
  23. If I had to choose between Windows XP x86 and x64, I would always go with x86. The driver support is much better in x86.
    1 point
  24. As I already mentioned, I chose Xubuntu LTS, too. It is leightweight, compatible with old hardware, and a lot of program packages are available. Managing, fixing, flashing Android devices and repairing devices is my main use of Linux. And, I was always successful, at least until now.
    1 point
×
×
  • Create New...