Jump to content

VistaLover

Member
  • Posts

    2,279
  • Joined

  • Last visited

  • Days Won

    97
  • Donations

    0.00 USD 
  • Country

    Greece

Everything posted by VistaLover

  1. OT: Today, it has come to my attention (quite by accident, TBH ) that an Eclipse forums member has appropriated my MSFN forums "username" (VistaLover): https://board.eclipse.cx/memberlist.php?mode=viewprofile&u=239 Until one specifically visits that member's profile page, it isn't clear/evident (by simply reading posts of him[?]) that "I" have no affiliation whatsoever with that member there; of course, I don't claim any copyright over my MSFN username , just thought I'd make it crystal clear to those MSFN members happening to have an account at Eclipse (some sharing the exact screen name between the two) that I am not that member ... Apologies for the OT, hope you all have a great New Year...
  2. Agreed! ... Right ... But "10 years ago or more", besides me having a lot more hair on my head and less fat in my body , I was a lot less tech savvy than now; "touching" the registry, for whatever reason, was considered by me (after the advice given by many IT-literate people at the time) as a serious "faux pas"...
  3. It probably tries to connect to OE Classic' s Activation Server, a now popular method for activating payware; the AS checks the validity of used license code (being legitimately acquired/"whitelisted" and not being shared beyond the sanctioned number of different devices/installations); should be easy to discover the hostname/IP of the Activation Server it tries to connect to via a MITM proxy; I suppose software like ProxHTTPsProxy could be used for that task... You probably want an "off-line" activation method for your work copy, but the author may respond, and rightly so, that such a method hasn't been provisioned for an app (e-mail client) that has to connect to the web for its intended (premium) functions... FWIW, their order page promises "instant" access (in bold) to the premium features ... https://www.oeclassic.com/order
  4. It occurs to me that WETV would be a great set of call letters for a US TV station, but a quick search shows there are none with those call letters. ... Presumably refers to https://www.wetv.com/ a US-exclusive streaming service I can't test from my location ... If it's anything to go by, the homepage renders "problematically" in St52/UXP, with humongous "social media" icons taking up most of screen room...
  5. Yep, forum software still thinks you're a mod :
  6. Greetings jaclaz : You should've then arrived at: https://msfn.org/board/ignore/ "ignore options" include: FTR, you being a mod means you just can't be "ignored/blocked" by other "plain" members... Buon Anno !
  7. No worries ; and now that you elaborated a bit , I sort of understand your train of thought... I've been using myself, for quite a long time, the BBCode "sharecode" and it "appears" to function as intended (but, of course, I'm oblivious to the inner workings of the forum software ); if by "Direct Link" you mean what imgur calls "Share Link", then obviously that one doesn't behave in a fashion similar to BBcode (i.e. doesn't embed inside a MSFN forum post), plus imgur might serve ads on the arriving picture page... But your advice is noted for when/if things break "on the forum side"... Warmest festive greetings !
  8. 10 years ago or more, I used to have both Firefox 3.5.x and 4 installed, in their own "Program Files" directories of course , each assigned its own separate profile via the method you detailed above ... The move by Mozilla from Fx-3.5.x/3.6.x to Fx-4.0 (and higher) introduced major profile incompatibilities in a way that whenever a Fx-3.x.x profile was (even once) touched by Fx-4.0+, it became corrupted beyond repair and could no more be used by Fx-3.x.x ... Launching the browser(s) via the dedicated shortcut(s) (pointing to the right profile) worked as expected, but... when I clicked a link inside a document (Word, PDF, etc.) or e-mail, often times catastrophe would strike ... Depending on which Fx version was configured as the system default browser (associated with these links), Fx-4.0 would open the link in the Fx-3.x.x profile (thus corrupting it), because the plain document/e-mail links don't contain the "-no-remote -p" options... So, I had to always keep a back-up of the Fx-3.x.x profile in case s**t happened (pardon the language ) ... Fortunately, in a later stage, I migrated to using the two different Firefox versions inside their dedicated "PortableApps.com" format (PAF) installations and had made IE9 the system browser - no "accidents" happened since, that is until Fx-3.x.x was ditched altogether and the "newer" Firefox was adopted permanently ... (Happy New Year to the frequenters of these threads )
  9. @Sergiaws : Besides being OT for this thread , you chose the wrong "share" code from imgur; should've been "BBCode (Forums)", not "Embed in HTML" ...
  10. ... As I added later, it's because of: with Goanna versions being different between Pale Moon (5.2.1, but recently changed to 6.0.0 in official UXP master) and the UXP forks (4.8.6) discussed in this thread...
  11. Damned they be! They plainly reject the UA sent by Serpent 52/55 (the Goanna and/or Basilisk slices) ... Edit: It's the "Goanna/*" UA slice they really object to ... The site loads fine via spoofing a "pure" Firefox UA, e.g. : "Mozilla/5.0 (Windows NT 6.3; rv:52.0) Gecko/20100101 Firefox/52.0"
  12. @roytam1 (hoping your fracture is healing nicely ): I can't seem to be able to open https://www.ldoceonline.com/dictionary/ in latest Serpent 52.9.0: This is a fresh testing profile, at default settings... OTOH, 360EE, IE9 (!) and 2018-era FxESR 52.9.1 have no issues with it ... FWIW, none of the 3 certificates in the chain have expired : and SSL Labs give the "www.ldoceonline.com" hostname a superb A+ overall rating (only TLSv1.2 supported by that server) ... Edit: Latest Serpent 55.0.0 exhibits the exact same issue ...
  13. ... Of course, that was probably a phony username, but Carlotta (I think) is a female's Christian name ... Later addition: @NotHereToPlayGames : I'm not going to argue on this, you being a native speaker, but... 1. I was taught English in my teen years by a posh Londoner (Mr Andrew Salters, where are you? ) ... 2. If "wordreference" is to be trusted, the singular number refers to a male:
  14. According to its Release Notes, the well-known H/W-monitoring tool Core Temp has dropped Vista SP2 support in its 64-bit edition: Thus, CoreTemp-1.17.1-x64 would be the last that natively supports VistaSP2_x64... The InnoSetup installer (the same for both Vista x86 and x64) is no longer offered from the author's site (only the ZIPPED "portable" version is), but it has been archived below: https://archive.org/details/core-temp-setup_20220226 Current version 1.18 will successfully install and run under Vista SP2 x86, but it's plagued by this bug, so I had to revert to previous v1.17.1 (on my Vista SP2 32-bit laptop) ...
  15. The usual reasons : 1. Increase the amount of user-info (telemetry) they're harvesting via their "spyware" browser application, 2. undermine the competition and break older (aka "legacy") browser platforms at the same time... See upstream #2053 Google's implementation of the measure() function (measureOptions parameter) requires at minimum Fx103; with 102 being the current FxESR (and the one Win7/8.1 uses will, purportedly, be downshifted to once Mozilla drop support for these OSes), GT should be, as of Dec 6th, also broken in latest FxESR (but can't test this myself now ); hopefully, Mozilla will backport the necessary changes to the Fx102 codebase, too ...
  16. Thanks for the clarification ; because the quote by @Humming Owl in your previous post was specifically referring to the WidevineCDM, not the underlying browser engine of DCB_v4.0.7.22 ... Χρόνια Πολλά και Καλή Χρονιά!
  17. I don't know about "such", but last thing I read was that Netflix specifically had a fallback DRM mechanism based on the (deprecated) NPAPI Silverlight plugin, on "legacy" browsers that still support that plugin... I can't test the current validity of that, as I don't have a Netflix subscription myself... PlayReady (aka MSPR) is a Microsoft-owned DRM technology, as such is supported in IE11 and Edge MS browsers; MSPR must also be "defined" inside the CENC manifests (MPD, ISM) the media servers (CDNs) are delivering to the browser... As per my comment above, the site does support MSPR (in addition to WV): drm: { widevine: { LA_URL: 'https://cwip-shaka-proxy.appspot.com/no_auth' }, playready: { LA_URL: 'https://playready.directtaps.net/pr/svc/rightsmanager.asmx?PlayRight=1&ContentKey=EAtsIJQPd5pFiRUrV9Layw==' } }
  18. Are you talking about the browsers themselves? If so, yes, I know they're both Vista SP2 compatible... And I believe both are supplied in 32-bit flavours ; my original query was for the latest WidevineCDM v4.10.4557.0 (32-bit) transplanted into either one; does it then work in the linked test page under a fresh browser profile? Extrapolating from my findings in Vista SP2 32-bit tells me it should not work in Vista SP2 64-bit without the Extended Kernel (aka "vanilla x64") ... @UCyborg, time permitting, could you be able to shed more light on this? Thanks ...
  19. Oops, mea culpa , you're correct ; DCBrowser v4.0.1.4 was the first based on Ch75, and next v4.0.2.4 was the first based on Ch75 to run under XP SP3; DCBrowser did not change its Chrome Core to v86 until v5.0.1.48, but that one required Win7SP1+ to launch ... I must've confused DCBrowser with another Chinese browser based on Ch55 and popular with the XP community ... My deepest apologies (previous post of mine shall be edited ) ...
  20. Relevant upstream support forum thread: https://forum.palemoon.org/viewtopic.php?f=70&t=29165 @Mathwiz ...
  21. The last version of the Google WidevineCDM that was compatible with Vista SP2 (32-bit/64-bit) was v4.10.1196.0 (digitally signed on 20181009); all later versions contained one (or more) call(s) to APIs that are only found on Win7 SP1 and up... v4.10.1196.0 originally shipped with Chrome 70; that version, of course, wouldn't launch under Vista SP2, but the CDM could be transplanted into 360EEv11/v12/v13 and there it worked until it got deprecated/revoked by Widevine Licence Servers on 20190814 (FWIW, that was the same date on which WVCDM v1.4.9.1088 - that ships with Serpent 52.9.0 - was also revoked ) ... Currently, the only supported version of the CDM that is "whitelisted" by the Lic Servers is v4.10.2557.0 (digitally signed on 20220923); the immediately previous one, v4.10.2449.0, has been recently revoked ... Probing the 32-bit widevinecdm.dll v4.10.2557.0 with DW reveals two calls to GetThreadGroupAffinity TryAcquireSRWLockExclusive which are not available inside Vista SP2's kernel32.dll system file... @shelby : If you're using Vista's Extended Kernel (by win32) on Vista SP2 64-bit, you should clarify that, because a "generic" claim like the one I quoted may lead to misunderstandings... DCBrowser 4.0.7.22 (discussed in the posts above yours) is based on Chromium 75; WVCDM v4.10.2557.0 demands at least Chromium 68: { "manifest_version": 2, "update_url": "https://clients2.google.com/service/update2/crx", "name": "WidevineCdm", "description": "Widevine Content Decryption Module", "version": "4.10.2557.0", "minimum_chrome_version": "68.0.3430.0", "x-cdm-module-versions": "4", "x-cdm-interface-versions": "10", "x-cdm-host-versions": "10", "x-cdm-codecs": "vp8,vp09,avc1,av01", "x-cdm-persistent-license-support": true, "x-cdm-supported-encryption-schemes": [ "cenc", "cbcs" ], "icons": { "16": "imgs/icon-128x128.png", "128": "imgs/icon-128x128.png" }, "platforms": [ { "os": "win", "arch": "x64", "sub_package_path": "_platform_specific/win_x64/" }, { "os": "win", "arch": "x86", "sub_package_path": "_platform_specific/win_x86/" }, { "os": "win", "arch": "arm64", "sub_package_path": "_platform_specific/win_arm64/" } ] } (you can grab WVCDM v4.10.2557.0 from within a Google Chrome 107+ installation) Testing site: https://bitmovin.com/demos/drm ... Sadly, the DARK side is that Google's DRM is spreading like metastatic aggressive cancer cells, it's EVERYWHERE now (when before it used to be only in paid-for media services); have a look inside youtube-dl/yt-dlp issue trackers and you'll see what I mean ... DRM is really EVIL (more so for users of "legacy" browsers on "legacy" systems); Google have recently abandoned Win7/8/8.1 in their browser, a not-so-distant WidevineCDM updated release will only run under Win10+ ...
  22. Most sadly, that test can't be run under a UXP-based browser , because the website requires Javascript features not supported in UXP: This is a well known villain when it comes to UXP (i.e. dynamic module import): https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/import First implemented in Firefox Quantum 67, UXP has a longstanding "open" issue about it: https://repo.palemoon.org/MoonchildProductions/UXP/issues/1691 TL;DR: No light at the end of the tunnel any time soon, if ever... People, "we" should accept UXP is on its deathbed, under life support ...
  23. Thanks for your kind reply ; obviously, I wasn't aware ... Today, with more free time on my hands, I searched this further and it seems it was first removed in Chrome 65, then reinstated in Chrome 66, to be permanently removed, as you wrote, in Chrome 76 ; what a mess ; of course, all was done to cater to "user security", the usual "excuse" when useful features are being removed:
  24. ... Have any of you tried the " --disable-infobars" cmdline switch to hide the "unsupported OS" header/banner? It shouldn't require a PC restart, just a browser restart...
  25. ... Turns out that UXP-incompatible script (requiring customElements) is being served from this company: https://www.reevoo.com/ i.e. when invoked, the script displays (in a popup) "after-sale" opinions/evaluations/comments (by "verified" customers) about an item bought from MM ; I had to open 360EEv13 to actually discover the function of that script ...
×
×
  • Create New...