Jump to content

NotHereToPlayGames

Member
  • Posts

    6,759
  • Joined

  • Last visited

  • Days Won

    84
  • Donations

    0.00 USD 
  • Country

    United States

NotHereToPlayGames last won the day on September 14

NotHereToPlayGames had the most liked content!

8 Followers

About NotHereToPlayGames

Profile Information

  • OS
    Windows 10 x64

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

NotHereToPlayGames's Achievements

3.4k

Reputation

  1. And for what it is worth, my older Serpent can only get to the green box that indicates that the slide "passed" but it does not advance to the next page. It eventually times out and requests the slide mouse again. Both results are TECHNICALLY THE SAME! ie, the SECURITY CHALLENGE CANNOT BE LOADED.
  2. I now get this with both of my ISP's. ie, both land on the slide mouse page, both get the green box that the slide mouse page PASSED, but then both end up being blocked with "We couldn't load the security challenge."
  3. Okay, well, I can report that the Restore Session page **IS** working in the most-recent version of Serpent v52. I terminated via Task Manager ten consecutive times and ALL TEN presented a populated windows/tabs table. In the past, two or three of those ten would *NOT* present the table, it would just open/restore my last session **WITHOUT** presenting the table - this is not a "functioning" feature. But I can not replicate this behavior with most-recent version, ALL TEN terminations function properly.
  4. That may be promising! MAYBE it's fixed. Just how did you get to the Restore Session page? What really has *never* worked for me in "newer" versions is for me to have only two windows open, each with only one tab, and Serpent.exe is TERMINATED via Windows Task Manager / System Informer / et alia.
  5. I'm afraid that I will have to decline from that experiment. My apologies. Newer versions of Serpent *do not work* on my end because Session Restore is a **MUST**. I have noted these Session Restore issues in the past and intermittent as they are in newer, I have *ZERO* problems with Session Restore in my older version. I have had way WAY too many updates over the years only to REVERT to the version that WORKS for me. Sorry, my version has to remain where it is. When I can no longer text and email from it, then I'll have to cross that bridge when I come to it. Until then, "long live my OLD Serpent". This version WORKS for me and NEWER versions do NOT. Not to sound too blunt, but I have lost interest in newer versions of Serpent all on account of SESSION RESTORE table of tabs/windows NOT POPULATING in newer versions. Again, intermittent as it is, the version that I use always ALWAYS **ALWAYS** populates the Session Restore table, so this is going to be my last version of Serpent until I see changelogs reflect Session Restore fixes.
  6. If you're open for alternatives, I used doPDF on XP. Most likely *not* the 'newest' version, I'd have to pull up my XP archives to track down version. I would still have the installer if it's not available online anymore.
  7. You do not fully understand the intent behind such things as ESR (and LTSB/LTSC). That said, many home-based consumers that use corporate-based products for non-corporate use may very likely also not fully understand the underlying intent. Personally, to me, in my opinion, yadda yadda yadda, ANY product that is EXTENDED is GREAT NEWS for the CONSUMER.
  8. I did just discover that the paypal slide mouse screen in my older version of Serpent is DEPENDENT UPON the ISP that I use. I canceled my previous ISP but it remains active until the end of my billing cycle (I only have two more days) - I get no slide mouse screen in Serpent when connected via my previous ISP (cable). I *DO* get the slide mouse in Serpent (unsolvable - checkbox turns green but page does NOT advance) in Serpent when connected via my new ISP (fiber optic).
  9. Okay, then "might" not be a cert issue. Move on to the next domino - what css/js is your Supermium capable of that your Serpent is not capable of. Good Luck! Me Thinks that you're just going to turn yourself into a dog with a flea on the tip of its tail, running in a circle trying to bite at that flea. All I can really tell you on this end is that I do *not* get the slide mouse screen in my OLDER version of Serpent. But I also run that OLDER version of Serpent (daily! 24/7!) from within Win10 and not XP.
  10. His report is that he needs to go the other way. That he can NOT paypal in your browsers but CAN in Supermium.
  11. You should only need to SORT them by EXPIRATION DATE and isolate which have been updated most recently. HOWEVER, this is NOT a guarantee that you will end up getting paypal to work in non-chrome. IT IS ONLY THE *FIRST* HURDLE and there could be a DOZEN hurdles in front of you. It doesn't even mean that you will find a cert! Again, there are going to be a DOZEN hurdles, certficates should always be the FIRST (in my opinion) to clear. Nowadays, CSS is next. Then JS. And DON'T EVEN BOTHER changing your user agent! The sooner you break that "old school" thinking, the better. (again, just my opinion)
  12. Well... Um... When I was a know-it-all college kid, I was a "death to IE, Firefox ONLY" punk! My bias to use Firefox and NOTHING ELSE ended up nearly getting my fired! FIREFOX let a virus in and three production facilities were shut down completely for several hours. All because I would never touch anything but Firefox. My answer to you, and you're not going to like it, is that you just may have to learn to know when to use CHROME and when you can stick with your already-stated bias against anything Chrome.
  13. Yes! Because Supermium uses the OPERATING SYSTEM'S "certificate store" and the firewall flagged that the "cert store" was being updated. Now that the OS's cert store is getting your paypal working, you could try importing the OS certs into the non-chrome browsers.
  14. My guess is that Google is "experimenting" and it hasn't actually "landed" yet. I don't think that they are even aware (yet) that their "experiment" is even making H#LL out of using Google on even something as modern as Chrome v136. Did not go beyond that, I only know that my v136 is hit with a CAPTCHA each and every d#mn browsing session !!! I can't believe that this is what they "intended" to do to those of us that run "ungoogled" or session-only or cacheless browsers even on something as 'new' as v136. I have witnessed these every-d#mn-session CAPTCHAs in the past on Google and it takes them a WEEK or so to realize it and reverse the experiment, "oops, that wasn't what I was expecting".
  15. In Task Manager, are there any processes running over 80% or so during your slow connectivity?
×
×
  • Create New...