Jump to content

VistaLover

Member
 View Profile  See their activity

  • Posts

    2,109

  • Joined

  • Last visited

  • Days Won

    93

  • Donations

    0.00 USD 

  • Country

    Greece

 Content Type 

Everything posted by VistaLover

  1. VistaLover
    Happy New Year @Jody Thornton This has come up before, not sure if it was just you, but: Latest Serpent 52.9.0 build is more up-to-date compared to the official Basilisk build (under a new maintainer now, Basilisk-Dev); last release of Basilisk was on Nov 4th 2022, I sense a new release is imminent... Latest New Moon 28 build is more-up-to-date compared to the last official Pale Moon release (v31.4.2), though a new PM release should be imminent (v32.0.0?) ... appVersion has nothing to do in these cases (and I've explained that in the past, too), it's the actual source code used to build the releases that matters... Roytam1 cherry-picks all feature enhancements from the upstream platform (UXP by MCP) and upstream applications (PM by MCP and Basilisk by Basilisk-Dev) and merges them into his UXP fork - security patches come via the MCP and/or Mozilla repos... A few upstream features/commits are not being adopted, because they are incompatible with the OSes roytam1 targets; others (like the JPEG-X decoder) are not compatible with the compiler (MS VS2015) currently employed to build his releases... As for Serpent 55.0.0(/moebius), there's nothing "upstream" now to compare it to, is there? Roytam1 just tries to keep that "close" to his UXP offerings... @XPerceniol : Please, just stop examining "file versions"; these mean nothing... A certain exe's/dll's "file version" only changes when a full re-compilation takes place from scratch (what's called "clobber"); this is time and energy consuming and it's to be avoided in weekly releases... Only those few files that get changed and rebuilt come with "newer" file versions... The latest St55 (32-bit) build is "basilisk55-win32-git-20221231-7637d8917-xpmod.7z"; update to it, if you haven't already; its buildID should be 20221230020814 (Help -> Troubleshooting Information -> Build ID) ... To ALL: Source code repos for Roytam1's browsers are public and accessible on GitHub (links in the "weekly releases" posts); it's all "transparent" there, if you take a minute or two to read committed code and compare it to the upstream repos... That's what I do... Disclaimer: I'm not a coder myself...
  2. VistaLover
    ... Thanks ; at least a certain MSFN member doesn't frequent this thread, because it appears "socksifying" apps have been developed mostly by the Russians and Chinese (probably to circumvent state-implemented web censorship ) ; but that is not the gist of my post... One of the hosters SocksCap64 is distributed through is MEGA: https://mega.nz/folder/qBoD2BiB#BZbHB1tetB79SAvJEoVlLw Since my daily driver is Serpent 52, I loaded that link there and all 3 initial stages (Requesting folder data, Receiving folder data, Decrypting folder data) completed fine, with the page loading as expected; however, when clicking the green "Download all as ZIP" button, the download attempt invariably fails , claiming a "Temporary error, retrying": (you've guessed it, "retrying" doesn't succeed ) The same thing happens when using latest Serpent 55.0.0 (doesn't come as a surprise to me) ... To exclude any interference caused by my "dirty" profile, I tested this in a new St52 profile, too: It appears "upstream" have been made aware 5 days ago, but nothing of practical value posted there, yet... AIUI, MEGA first downloads data as a blob stored in RAM, and it then offers to save the full download to disk... It worked in St52 the last time I used it, ca. a month ago... Having MEGA currently broken in UXP is a "bummer", because I do use the service often... @roytam1, could you please investigate/offer some insight/workaround? FWIW, I had to use 360EEv12 (Ch78-based) to fetch from MEGA and it worked OK the first time (Ch78 being quite "old" by now, hopefully the UXP-breakage isn't related to some "exotic" Javascript being recently implemented by MEGA...).
  3. VistaLover
    Happy for you and glad my mention proved helpful ...
  4. VistaLover
    Thanks ; had forgotten ; while "netsh" itself is available under XP, it appears "netsh winhttp" syntax is NOT: https://www.computerhope.com/netsh.htm#xp It's by the same author; I unearthed a more recent version (1.5 compared to 1.4 you linked) in https://widecap.software.informer.com/
  5. VistaLover
    ... Well, OE Classic has to access the web to connect to its Activation Server ; not respecting system proxy settings aside, the only way it can reach the internet is via your Network Adapter (Ethernet/Wireless/TAP (aka OpenVPN); I believe packet inspectors/sniffers that bind directly to the Network Adapter are available ... So, by inspecting web requests made by OE Classic, it is possible, at least in theory, to identify the Activation Server's "details"; however, even when you get such "details", you still have to devise a way for the app to connect to it... Have you also tried the cmdline way (needs Administrator privileges) ? netsh winhttp import proxy source=ie netsh winhttp show proxy (to revert: netsh winhttp reset proxy ) Edit: Sadly, above syntax needs Vista+ (thanks @AstroSkipper ) FreeCap is a similar, FREE, software... Sadly, development has been discontinued at version 3.18 (original author's site has been taken down since) ; review below: https://www.raymond.cc/blog/route-all-internet-software-and-game-connection-through-open-proxy-servers/
  6. VistaLover
    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...
  7. VistaLover
    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"...
  8. VistaLover
    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
  9. VistaLover
    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...
  10. VistaLover
    Yep, forum software still thinks you're a mod :
  11. VistaLover
    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 !
  12. VistaLover
    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 !
  13. VistaLover
    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 )
  14. VistaLover
    @Sergiaws : Besides being OT for this thread , you chose the wrong "share" code from imgur; should've been "BBCode (Forums)", not "Embed in HTML" ...
  15. VistaLover
    ... 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...
  16. VistaLover
    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"
  17. VistaLover
    @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 ...
  18. VistaLover
    ... 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:
  19. VistaLover
    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) ...
  20. VistaLover
    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 ...
  21. VistaLover
    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 ... Χρόνια Πολλά και Καλή Χρονιά!
  22. VistaLover
    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==' } }
  23. VistaLover
    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 ...
  24. VistaLover
    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 ) ...
  25. VistaLover
    Relevant upstream support forum thread: https://forum.palemoon.org/viewtopic.php?f=70&t=29165 @Mathwiz ...
×
×
  • Create New...