Jump to content

VistaLover

Member
 View Profile  See their activity

  • Posts

    2,307

  • Joined

  • Last visited

  • Days Won

    98

  • Donations

    0.00 USD 

  • Country

    Greece

 Content Type 

Everything posted by VistaLover

  1. VistaLover
    ... Many thanks for this find! However, the installer checks the OS version and blocks the installation on NT < 6.1 : One can extract the installer with 7-zip and run the browser.exe main executable directly on Vista SP2, however I still prefer myself "installing" and running the truly portable PAF package I linked to previously... Best regards
  2. VistaLover
    ... However, @GlowingLights is rather interested in x64 browsers for his XP Pro x64 machine ; most sadly, apparently SM 2.49.5 64-bit only supports Win7+ ...
  3. VistaLover
    Language packs are architecture independent, meaning the same one would apply to both x86 & x64 compiles of the same app version... Unfortunately, I quit using NM27/Tycho months ago, since it no longer supports GitHub ; so I'm not following closely that fork's development; you might try the official Tycho language pack at http://archive.palemoon.org/palemoon/langpacks/27.x/ru.xpi which should be the same as the RC2 linked to by @IntMD; however, I believe that relatively recent commits have added new strings that are missing in the old (and, of course, no longer maintained) official pack; so the official ru pack might well be a trial-and-error case; it may work partially, or prohibit the GUI from even launching at all... If that's the case, then obviously a Russian speaking member of this community could add and localise the new strings...
  4. VistaLover
    (OT, but relevant to MSFN ) ... attached image not showed To have an imgur photo upload display inline inside a forum post, please choose under the Get share links option the BBCode (Forums) entry, of the format: [img=https://i.imgur.com/[7-digit-code].jpg] ... and try to avoid their new beta photo uploader: https://imgur.com/upload?beta which is now being offered as the default ; the beta uploader uses much more resources here (CPU+RAM) compared to the old one: https://imgur.com/upload so the latter should be bookmarked and preferred in older hardware+browsers! Of course, the old one will cease to exist sometime in the near future, till then though, it's the obvious choice for me...
  5. VistaLover
    @Vistaboy : Please do what @looking4awayout did (and it's the thing I always recommend when troubleshooting): create a new pristine FxESR 45.x.x profile, devoid of any extensions; safe mode only disables extensions and some gfx related features (e.g. HW acceleration, if applicable), but doesn't negate the existing prefs.js file inside your dirty profile! You didn't tell us how your existing profile was initially created; often times, profile corruption due to mysterious extension interactions/conflicts, extension upgrades/downgrades and profile migration from different browser versions (from a higher Fx version to a lower one, not to mention between Firefox forks) may be the source of difficult to dissect issues... BTW, can you still bookmark a URL via other approaches, e.g. the "star" toolbar button? Best regards
  6. VistaLover
    Hi - I do hope you're fine ; however, what you report is nothing to be in awe of and/or exclusive to NM; "mixed content protection" has been implemented since Mozilla Firefox 23: https://blog.mozilla.org/tanvi/2013/04/10/mixed-content-blocking-enabled-in-firefox-23/ https://support.mozilla.org/en-US/kb/mixed-content-blocking-firefox In Italian: https://support.mozilla.org/it/kb/blocco-contenuti-non-sicuri Auguri
  7. VistaLover
    ... The culprit upstream change I linked to previously was first present inside the Aug 31st 2019 compiled builds (package bnavigator.win32-20190831-4c42623-uxp-11965adc1-xpmod.7z), as also indicated by its posted changelog:
  8. VistaLover
    This is why the extensions became incompatible; 0.9.0a1 < 1.0.0a1 Simply change to: <em:minVersion>0.9.0a1</em:minVersion> Responsible upstream commit: [Navigator] Version change https://github.com/binaryoutcast/binoc-central/commit/fdded3b Once again, the "Tobin" individual revolutionises app development by releasing updated code with a lowered app version number (for me at least, this is a first! ) .
  9. VistaLover
    OpenGL Extensions Viewer is a small utility that examines your system's GPU for OpenGL related features (or absence of... ) ; the latest release is v5.3.4 (2019-07-29). According to vendor's site : I did download the win32 setup (glview534.exe) and proceeded with the installation; it turns out the app has NO issues launching and successfully running here (Vista Home Premium SP2 32-bit, .NET FW 4.6.1): (Thanks to @jaclaz for mentioning this in a Win7 subforum thread... )
  10. VistaLover
    Wow ! Minutes instead of the hour(s) I had estimated... This is most excellent! But then again, as discussed, a small fortune was spent towards the purchase of this new hardware, so all's well that ends well.. Best greetings
  11. VistaLover
    ... And if I may ask, 1. Which ones of your 32-bit browsers take the least and most amount of time to compile? 2. How much is compilation time now, expressed in hours? Thanks in advance for satisfying my curiosity...
  12. VistaLover
    @Mathwiz : The @roytam1 UXP browsers are built from the https://github.com/roytam1/UXP/commits/custom branch, itself derived from the corresponding master branch: https://github.com/roytam1/UXP/commits/master itself forked from the upstream master branch: https://github.com/MoonchildProductions/UXP/commits/master The upstream master branch, in terms of code development, can be likened to the Mozilla trunk branch, https://hg.mozilla.org/mozilla-central/ on which the (twice-daily updated) Firefox Nightly builds are built (currently at version 71.0a1); so, that makes a staggering 730 Nightly builds released per year! The 52 (or less) UXP-based browser releases per year (from Roy) is really a small number compared to the above figure... With such short development cycles, there's really no room for proper testing and evaluation by beta/nightly testers - expect more bugs to be released in the wild on unsuspected Release Channel users, which would in turn require more frequent "point" and/or "chemspill" bugfix releases! But I think the driving force behind this inane change is to surpass Google Chrome in absolute version numbers; Mozilla is now targeting more and more younger users (who already stay clear of desktop browsers - the web to them means mostly mobile devices - or use the prevalent choice [Chrome] when they don't) who, in their naivete, may think a larger version number actually means a more recent/updated application (say, Firefox 110 vs Chrome 92). If I'm not mistaken, that was Mozilla's main argument when, back in the day, they switched to the 6 to 8-week release cycle... In all honesty, I'm not surprised by any of Mozilla's recent moves - their ship is sinking, they'll do any gimmick to keep it afloat for just a little longer...
  13. VistaLover
    ... And if anyone's in need of it, the Greek installer for WinRar 3.80 (x86): wrar380el.exe (originally saved in this old Vista laptop on June 3rd 2009 ; however, its modification timestamp dates to Oct 7th 2008! )
  14. VistaLover
    @sukistackhouse is right ; simply head to and read: https://www.atlantiswordprocessor.com/en/help/ebook.htm#kindle Best wishes
  15. VistaLover
    ... FTR, I did report the two contained in this thread (I suppose there exist site logs that can confirm my claim), sadly only after I had also posted about them (twice... ; but to my defence, the spammer did strike back, out of spite no doubt, after I had flagged his/her first attempt...); anyhow, thanks for the cleanup (and next time, I'll be wiser ) !
  16. VistaLover
    I just tested this on NM28/UXP and it still does! Test site to verify: http://browserspy.dk/browser.php (Please note this pref doesn't modify the reported Windows NT version contained in the User Agent String (navigator.userAgent), so a website checking both strings via JS may get conflicting results: )
  17. VistaLover
    ... Yet another spamming post (disguised as a help plea) right before this one, from - most probably - the same spammer, under a newly created account and associated user name... If you read this, move your spamming activities elsewhere ; most members here are smart enough not to click your spamming links ; I trust the site admins will soon take care of you...
  18. VistaLover
    MSFN rule 2.e might apply here: ... and possibly rule 4.a: @dencorso, what are your thoughts on this?
  19. VistaLover
    ... This isn't always a definitive test - many a times, lowering the subsystem string (to < 6.0) in the main executable will get it to launch, despite this initial warning; the only definitive test is to use dependency walker x64 on the 64-bit program executable (and, possibly, on the program DLLs it depends on) and look out for API calls to missing functions in the XP x64 kernel...
  20. VistaLover
    ... But I did say: ... and I did keep my promise more than 24h ago : You just hadn't revisited my edited post prior to posting... ... I opted for the original Adobe link: Hope everyone's content now...
  21. VistaLover
    The CSS fix posted by @mixit is indeed needed in FirefoxESR 52.9.1 and Serpent 55.0.0/Moebius, but not needed in the UXP browsers (NM28, Serpent 52.9.0, Bnavigator) and latest SeaMonkey 2.49.5, because this issue is fixed in the respective platforms - don't forget that in NM28 and St52 browsers (at least), SSUAOs are needed for instagram.com (with a Firefox version < 57.0).
  22. VistaLover
    Exactly! Just to confuse things further, Google have done some re-versioning to their WV CDM and what were to be versions "1.4.10.xxxx" are now versions "4.10.xxxx.xx", 10 being the interface currently supported. Interface 9 CDMs were revoked, as announced, on Aug 13th 2019 (14th, if - like me - you're in Europe) and thus official Basilisk/Serpent 52.9.0, with internal support for only WV CDM v1.4.9.1088, was broken by Google Widevine license servers (they won't serve decryption keys any longer to revoked versions of the CDM); unlike e.g. NPAPI Adobe Flash Player, you can't just upgrade the CDM and expect things to continue to work, especially when only newer "interfaces" of the CDM are current; the "guts" of the browser have also to be updated accordingly, to support the newer Widevine CDMs. EME and WidevineCDM support in UXP (in practice, in Basilisk only) is being tracked in https://github.com/MoonchildProductions/UXP/issues/962 Their "media" (and Linux) dev, @trav90, appears to be having some serious issues in real life, which keep him still away from contributing code in the project; despite Moonchild's plans, he had to release Basilisk 52.9.2019.09.03 without fixing its broken Widevine implementation; for Netflix and Adobe Prime, Basilisk/Serpent users will have to use SSUAOs to fake older Firefox versions and then install/use the Silverlight NPAPI plugin (more in the official forums); of course, other DRM services without a Silverlight fallback provision will be simply BROKEN! Before Aug 13th, @roytam1's Serpent 52.9.0 (with WV v1.4.9.1088) and 360 Extreme Explorer (with WV v4.10.1196.0 manually installed) were, AFAICT, the only two working implementations of Widevine under the Vista SP2 OS; both these two WV versions have been now deprecated/revoked/blacklisted, the one current and whitelisted by WV lic servers is v4.10.1440.19; most sadly, the corresponding widevinecdm.dll file has been compiled by Google with optimizations targeting the Win7+ kernel only, so it won't work under Vista (this is easily verifiable via dependency walker in Vista); since the WV source code is a tightly kept secret, no-one can recompile it and make it again Vista compatible; so, WidevineCDM is henceforth a DEAD technology under Vista
  23. VistaLover
    ... Please accept my most sincere apologies, both of you In my dirty SM profile, the AP CDM does indeed show up in both about:plugins and about:addons/Plugins; prompted by your reports, I then created a new, clean, SM profile and applied my instructions from here to install the CDM; lo and behold, I, too, couldn't see the CDM installed in either about:plugins nor about:addons/Plugins, though, as you both confirmed, the CDM does appear to be working as intended in "silent" mode! After comparisons between the prefs.js file on the dirty profile and the same file on the new profile, I did manage to find the culprit: My original instructions are missing one additional about:config pref: media.gmp-provider.enabled;true (boolean) I had added that pref in my dirty SM profile many months ago, in an attempt to install and use the WidevineCDM on SM under Vista SP2 (NPAPI Widevine on XP doesn't install/show up/work); SM, like the upstream Fx ESR 52.9.1, only supports version 1.4.8.903, which is now severely outdated and blacklisted by Google Widevine license servers ); this is the reason the mentioned pref was pre-existing (and overlooked ) when I started my Adobe Primetime CDM experiments in SM! The original instructions will be soon edited to remedy this omission... Sorry again!
  24. VistaLover
    Some points to be made: 1. If on Win7, you don't really need Adobe Primetime CDM as a HTML5 MP4 video decoder (on Serpent and/or SM); Win7 comes already equipped with WMF and M$ provided patented decoders for H264+AAC. 2. To test the successful functioning of Adobe Primetime CDM (as a decoder) on either Serpent (52+55) or SM under Win7 (actually Vista SP2 and higher), don't neglect to first turn off WMF in the browser's about:config ; in Serpent's case (as opposed to SM), don't also neglect to turn off the ffmpeg provided patented decoders, by setting media.ffvpx.enabled to false!
  25. VistaLover
    @TechnoRelic : I have the answer to your SM 2.49.5 issue of not being able to playback HTML5 instagram videos under WinXP: 1. Via the Adobe Primetime CDM a. [LATER EDIT: I was kindly asked to provide here a download link for the AP CDM files; links for those do exist in the "Enable MP4 (H.264 + AAC) HTML5 video in Firefox on Windows XP without Flash" pinned thread, so it isn't like it's hard to find them; however, I have opted to provide the original official link, straight from Adobe's servers: https://cdmdownload.adobe.com/firefox/win/x86/primetime_gmp_win_x86_gmc_40673.zip The link is still live and tested mere minutes ago - if you're wondering how I got there (because, tried as I might with web searches, I wasn't able to find it), it's by loading the following URI: https://aus5.mozilla.org/update/3/GMP/51.0.1/20170125094131/WINNT_x86-msvc-x86/en-US/release/Windows_NT%206.0.2.0%20(x86)/default/default/update.xml ... which is the URI queried by the internal gmp-manager of stable Firefox 51.0.1 32-bit under Vista SP2! ] Just make sure you do install the CDM properly inside your existing SM profile: ./<ProfileDir>\gmp-eme-adobe\17\[3 files, one of which is eme-adobe.dll] b. Create/modify accordingly the following prefs: media.gmp-provider.enabled;true (boolean) browser.eme.ui.enabled;true (boolean) browser.eme.ui.firstContentShown;true (boolean) media.eme.apiVisible;true (boolean) media.eme.enabled;true (boolean) media.gmp-eme-adobe.abi;x86-msvc-x86 (string) media.gmp-eme-adobe.enabled;true (boolean) media.gmp-eme-adobe.forceSupported;true (boolean) media.gmp-eme-adobe.lastUpdate;1500000000 (integer) media.gmp-eme-adobe.version;17 (string) media.gmp-eme-adobe.visible;true (boolean) media.gmp.decoder.enabled;true (boolean) media.gmp.decoder.h264;2 (integer) media.gmp.decoder.aac;2 (integer) c. Restart SM 2.49.5; head over to about:addons/Plugins and configure the CDM to Always Activate: If everything was done right, heading to https://www.instagram.com/p/B2Nb4FGFQZ8/ and pressing the white PLAY button, you should be able to view the video inline... (I tested this successfully under Vista SP2 by first toggling media.wmf.enabled to false, thus simulating XP) 2. Dirty hack, by using @roytam1's modified DLLs. All this was inspired from: http://forums.mozillazine.org/viewtopic.php?f=40&t=3040639 a. Download latest Serpent 52.9.0 package by Roy Tam b. Extract the .7z file to a folder, copy the following 3 files: mozavcodec.dll mozavutil.dll vcomp140.dll c. Locate your SM 2.49.5 installation folder - rename and back-up the original files mozavcodec.dll & mozavutil.dll (of version 52.9.1.7156) d. Place there the 3 aforementioned files, extracted from the Serpent package. e. Launch SM Now SM 2.49.5 should be able to use the patented decoders contained in the modded DLLs; so HTML5 MP4 should be playable! (not tested by me, though... EDIT: Just tested, and it works!) Best wishes
×
×
  • Create New...