Jump to content

Mathwiz

Member
 View Profile  See their activity

  • Posts

    1,830

  • Joined

  • Last visited

  • Days Won

    50

  • Donations

    0.00 USD 

  • Country

    United States

 Content Type 

Everything posted by Mathwiz

  1. Mathwiz
    Actually I did read that; I merely chose to ignore it!
  2. Mathwiz
    Mozilla's decision to remove support for all pre-WE APIs, of course, broke CTR for FF 57+. Then their decision to remove all pre-WE add-ons from AMO meant that only "legacy" / classic add-on repositories would have a link to CTR. I checked legacycollector and addons.basilisk-browser.org first with no luck, then found it in the CAA database and thought my search was done, unaware that development is continuing for Basilisk / Waterfox at GitHub. So now, I've updated Serpent 55 to v1.7.8, and Serpent 52 (which should be on par with "official" Basilisk) to v1.7.8.2019.10.7! I'll update my old FF 52.9 (and XomPie-patched FF 53) next. CTR has so many options, though, I can't readily tell what was added between 1.7.7.2 and 1.7.8 et seq. One weird thing I did discover, though was that v1.7.8.2019.01.21 removed the option to display the version number in the Add-On Manager screen so by updating Serpent 52 to the "latest" version, I lost that bit of info. The author explained, "Basilisk 2019 and Waterfox don't need this option, because version number is active by default." If so, that would be a question for @roytam1: What is the difference between Serpent 52 and "official" Basilisk that accounts for this slight UI change? Inquiring minds want to know.... Maybe I'll roll it back to 1.7.8 so I can tick that option back on; I like having my add-on version numbers visible at a glance. Serpent 55 still searches AMO for updates. Serpent 52 searches, um - what should we call it? ABBO, I guess. But I haven't found ABBO particularly useful (as mentioned it doesn't even include CTR), so I switched the prefs in about:config back to AMO (you have to change %APP% to firefox). That way, at least my WE add-ons stay updated. Surprisingly, quite a few are still compatible with FF 52/53 and Serpent 52/55.
  3. Mathwiz
    That's good; your last post had me worried! My yellow shield was there this AM with the three Office 2010 updates. Since manual installation still works, here are links to their support pages: https://support.microsoft.com/kb/4484164 https://support.microsoft.com/kb/4484127 https://support.microsoft.com/kb/4484160 You can go to each support page, scroll down to "Option 3: Microsoft Download Center," and find links to the standalone installers for both 32- and 64-bit versions of Office 2010. (I would assume the vast majority of folks have 32-bit systems, but just in case....)
  4. Mathwiz
    That isn't a problem only for users of older OSes; it's a problem for anyone who prefers a platform other than Google's Chromium! Opera switched to Chromium long ago. Micro$oft switched from IE to Edge a little less long ago, but the "new" M$ Edge for Win 7/8.1? It's Chromium-based. It's gotten to where Chromium is the new IE monopoly! (But at least M$ wasn't using IE to spy on me or to dragoon me into helping train their AI.) I sometimes wonder if I should have a SSUAO for Google sites, claiming to be Chrome, just so Google's reCaptchas don't bug me quite so much, but then I remember I'd have to update the SSUAO almost as often as @looking4awayout updates the UOC Patch! No, he means New Moon, as the Pale Moon folks will angrily tell you if you ever make that innocent mistake on one of their forums. "Pale Moon" is only one of the browsers officially released by Moonchild Productions. Pale Moon does not run on OSes considered "obsolete," like XP or Vista, and woe to the poor soul that mentions XP or Vista on a Pale Moon forum. Anyone else's build is "New Moon" unless they develop their own branding (e.g., MyPal, Arctic Fox) for their own fork of Pale Moon. Edit: Doggone it, @VistaLover beat me to it again! Foiled by a page break....
  5. Mathwiz
    That actually sounds like an old problem that's come back! We used to complain about this all the time on the POSReady '09 thread. Then M$ did something and the problem went away - until now. Uh-oh; that sounds more serious. It sounds like M$ is now signing Office updates with SHA2 signatures. XP was never updated to validate that type of code-signing signature. Your only hope is to extract the updated files with something like 7-Zip and replace the original files manually.
  6. Mathwiz
    If I could figure out how to automate downloads from Mediafire I'd just put the code to do it in my batch file. Then every time I installed a new version it'd get the new UOC Patch!
  7. Mathwiz
    Yes, I tested it with the latest PM 28, and it works! E10s remains disabled even with the "standard" FF 52 version of the patch. Thanks! So, the separate NM28 version of the patch is no longer needed.
  8. Mathwiz
    Try the "Classic Theme Restorer" add-on: https://ca-archive.biz.tm/storage/472/472577/classic_theme_restorer_fx29_56-1.7.7.2-fx.xpi?origin=caa&action=install
  9. Mathwiz
    To be specific, I was trying to install the Chromium-based version linked to in @jumper's post directly above mine. (The FF 52-based version is old news.) The Web site claimed XP compatibility, but I was skeptical, and sure enough, it doesn't install.
  10. Mathwiz
    I think there's an about:config preference you can set to false: plugin.load_flash_only Try it and see. Edit: Yep, it works! You have to create the Boolean pref above and set it to false, but it works. BTW, Serpent 55 is essentially an updated version of FF 53, and it does support NPAPI plugins. Also, it's probably worth pointing out that you will lose some security fixes in moving from FF 52.9 ESR to FF 53.
  11. Mathwiz
    The "best" browser for XP depends on your hardware. For pre-SSE2 processors, I agree with @looking4awayout: If your system is even older (pre-SSE) your best bet is probably @roytam1's no-SSE build of New Moon 27. For newer systems you have more options. The Chinese Chromium backports are OK if you like Chromium and can deal with the Chinese language. If you prefer a Firefox-based browser, I've had pretty good luck with @roytam1's Serpent 55. It supports more add-ons than his Serpent 52 and I almost never have problems with Web sites not displaying correctly.
  12. Mathwiz
    Despite claims at the Web site, it doesn't seem to install in Win XP:
  13. Mathwiz
    Images often downloaded separately from the email that contains them because they're so large. Outlook uses IE to download these images. If IE can't download an image you'll get the red X, but there are lots of reasons IE might not be able to download from a particular server besides a certificate problem. For example, there may not be a TLS cipher that both the server and IE support. You may find that installing @heinoganda's version of ProxHTTPSProxyMII will resolve many of those download failures.
  14. Mathwiz
    One thing to watch out for: the file names are different (e.g., UOC_Patch_38.js vs. UOC_Patch_45.js). So besides copying the _38.js files, you also need to delete the *_45.js files you copied earlier; otherwise NM 27 will load both and the result will probably not be what you want!
  15. Mathwiz
    Nothing new in this post; it's just a summary of what's been discovered so far about this issue. To play Instagram videos in your FF (or FF-derived) browser, you need three things: Most obviously, you need to be able to play MP4 videos. This won't be a problem with @roytam1's UXP forks (NM and Serpent) since he includes his MP4 video DLLs in the build. For FF 45 though 52 or SeaMonkey 2.49.5, you can install the Adobe Primetime CDM according to the instructions pinned atop this forum; either method works. (Those instructions were recently modified slightly to work with SeaMonkey.) You need to set your user agent to spoof FF 56 to instagram.com. You can either set the general.useragent.override preference in about:config to Mozilla/5.0 (Windows NT 6.1; WOW64; rv:56.0) Gecko/20100101 Firefox/56.0 or use an Instagram-specific user agent. FF versions before 56 work too, down to a point, but basically nothing on Instagram works at all if you spoof any version newer than 56. If you're not using NM, Serpent 52, or SeaMonkey, you need the following code in file userContent.css in the "chrome" subfolder of your profile: Note that this code is changed somewhat from @mixit's original fix; Instagram changed some of their random class names, requiring an update. Instagram will probably change them again someday, and we'll have to get @mixit to update his fix yet again.
  16. Mathwiz
    Not sure if KM 74 has the pref security.ssl3.ecdhe_rsa_aes_256_sha, but setting that pref true is probably your best bet for Startpage.com. (I have it set false on mine because SHA1 suites are considered weak, but I've enabled other cipher suites that Startpage.com can use.)
  17. Mathwiz
    Thanks for trying a new profile and confirming that it doesn't help. I don't think it's a matter of you and @kitaro1 being ignored, so much as the fact that no one here has a solution to the problem. I haven't tested it, but I strongly suspect "official" Pale Moon and Basilisk (on Win 7+) will have the same issue. I seriously doubt this is a bug that both @roytam1 and @feodor2 have both independently managed to introduce into their respective PM forks. So unless @looking4awayout's UOC patch helps, we're at the mercy of MCP to come up with a fix. Unfortunately the browsers (that @kitaro1 mentioned) that don't have this issue with GMail simply don't run on XP (or Vista), and can't be made XP-compatible. If that's the case, you know the drill: confirm the issue with official PM on a supported OS (Win 7 or later) and report it to MCP directly via PM's Help / Submit Feedback link. I agree; this has bitten me too when trying multiple versions of, say, Firefox, on the same PC. @VistaLover has the right answer - install at most one non-portable version of each browser - but it's easy to forget and not always practical. Luckily some combinations do work: Basilisk/Serpent 52, Serpent 55, PM/NM, BNavigator, Seamonkey, and FF all use different profile folders, so one of each of those can coexist peacefully without using "portable" versions. That's a bit much to ask of, say, 7-Zip; how's it supposed to know that what you're unzipping is a browser with this particular potential issue? But I'll look at adding a message of that sort to my "Download Latest Browser" batch file. AFAIK e10s/multiprocess only works on FF and Serpent, not NM; trying to enable it on NM just crashes it. But @roytam1 is customizing NM by locking some e10s-related preferences, so inadvertently installing the "wrong" UOC patch from @looking4awayout won't crash the browser.
  18. Mathwiz
    Due to concerns about potential copyright infringement issues, ReactOS is quite explicitly not based on One-Core API.
  19. Mathwiz
    Thanks. When I get a chance, I'll test it. If it works, @looking4awayout won't need to maintain a separate NM28 version of his patch (NM28 will simply ignore the preferences that enable e10s).
  20. Mathwiz
    I think we all hate captchas. I especially hate Google's reCaptcha for the reason I gave above. Google's reCaptcha is used by many Web sites, but the data is hosted by Google, and your responses are validated by Google. They sneak a few images into their reCaptchas where the "correct" answer is unknown, so they can use the user's responses to train their self-driving car software. I don't even mind Google developing self-driving car software; I wish them the best of luck in that. I just resent being dragooned into helping them develop it, just to use a Web page. I don't hate everything about Google; I still use their search engine (albeit via Startpage.com).
  21. Mathwiz
    I think we all hate them. I especially hate Google's since I learned that Google is using reCaptcha challenges to train its AI. If they want me to work for them, I think they should pay me.... Which site / captcha is giving you trouble? JFYI, Serpent 55 has no problem with Google's reCaptcha demo page at https://www.google.com/recaptcha/api2/demo with the user agent overridden to Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.9) Gecko/20100101 Firefox/60.9.
  22. Mathwiz
    You're right; it is. I guess the list isn't in exact alphabetical order I wonder why archive.org's Web crawler didn't pick it up then? There's no robots.txt there AFAICS Oh, well; in any case it's archived for posterity now.
  23. Mathwiz
    Re: Keep in mind that this will crash NM 28, even though it works fine in FF 52, Serpent 52, and Serpent 55 (and probably BNavigator, although I haven't tried e10s on that browser). You may want to create a separate version of the 52 ESR Patch for PM/NM/MyPal that doesn't turn e10s on.
  24. Mathwiz
    Are you using NM 27 or NM 28? The hack above will only work on NM 28. fp.isGecko45 won't be true for NM 27 or for Arctic Fox, which is based on NM 27.
  25. Mathwiz
    The good news is that Classic Theme Restorer runs just fine on my systems with e10s enabled, even though it claims to be incompatible. So there's a good chance it'll run OK on your system too. Of course, the only way to know for sure is to try enabling e10s and see what happens.
×
×
  • Create New...