Jump to content

Jody Thornton

Member
  • Posts

    1,593
  • Joined

  • Last visited

  • Days Won

    8
  • Donations

    0.00 USD 
  • Country

    Canada

Everything posted by Jody Thornton

  1. I don't suppose there's anyway you can build an x64 version of MailNews, is there? I'm waiting on an update for Interlink, and next month will mark a year since the last one. Even if a single updated build for x64 could be made, that would hold me for a bit. Just wanted to ask. Cheers Roytam!
  2. iOS 10 is unsigned for your device, so no - there's NO downgrade path. I actually prefer iOS 12, but still, I'm in a similar situation to you. I have an iPhone 6s that had iOS 12.4.1 still on it. Because I need to use a payroll time clock app, I HAD to upgrade iOS 15. Now that I'm leaving that positin, and no longer needing it, I still CANNOT downgrade to iOS 12.
  3. Not at all. We'll both have to see what happens this time around.
  4. But back then on XP/Vista, when you upgraded from Release 51.x, you were forced to upgrade to ESR 52.0. You could NOT install Release 52.0 (even though they were the same initial base release)
  5. And all in an answer to my question. So think about it, if I never pestered, we'd still be waiting for this news.
  6. Not so fast - ESR 52 ran on XP and Vista - but NOT the release version.
  7. But at least they made a decision. I had to ask to even get that. As for release versions though, who really knows. I suppose this is also good news for Vista Extended Kernel users.
  8. And now there's another, confirming that at least ESR 115 will run on Windows 7 and 8x https://bugzilla.mozilla.org/show_bug.cgi?id=1594270
  9. Well yoltboy01 gets the prize! After months of radio silence on the issue, Mozilla finally wrote back to my question on Bugzilla, that they WILL allow Windows 7 and Windows 8.1 to run Firefox ESR 115. This was up in the air as to when support was going to get yanked. For awhile, it seemed that maybe ESR 102 spelled the end of the line for these versions of Windows. I cannot speak for "release" versions of Firefox though. Anyway, here's our correspondence (at the bottom of the page) https://bugzilla.mozilla.org/show_bug.cgi?id=1594270
  10. I was reading througn (including the introductory post), and I wasn[t able to readily gather what the primary differences were between Builds 7 and 8. I understand that Build 7 is more efficient on RAM conscious systems (I have only 2 GB on this old Vista x86 notebook I keep at my girlfriend's, so that bode's well for Build 7). But am I missing anything with Build 8?
  11. Wow! I have to hand it to you for dealing with it. But this overall attitude and arrogance has been an ongoing issue with the Pale Moon forum from the top down. Sure, I spew A LOT of negative press about the Moon Team on here, Ghacks and Reddit (almost with career-like dedication I'll proudly admit), but THEY were the genesis of that toxic behaviour. I'm glad to see there are exceptional people there like you and Athenian (sp?) Now to answer your question over at the Apollo 13 site :p , at the time Basilisk 55 was deprecated, there were sites that rendered better than on Basilisk 52. That was the reason for porting it to a Serpent release, at least in part. Personally, I use Basilisk on Windows 8 for a very specialized work case, where I customize a work site into a web app basically using Classic Theme Restorer. I need WebRTC to record audio into it, and this way, the jobs run in a separate memory space COMPLETELY than my Firefox tabs. So I like the browser. I have my mom and dad on the newly-revived x86 version, so they can run some old Flash games, so if the improved WebComponents support hits Basilisk soon, that will benefit them certainly. Thanks for chiming in.
  12. I saw you there. I was surprised that you survived it ...lol
  13. Holy Crap! Look at this Basilisk thread, where I guess someone from here went to the Pale Moon Forum and dared to mistakenly ask about Serpent. It's not about the right or wrong I'm concerned with: it's the snotty nature that Moonbat conducts himself with. Just a p***-poor way to talk about people: https://forum.palemoon.org/viewtopic.php?f=61&t=28657&start=40#p237935
  14. Unless he has a good GPU. In such a case, the heavy lifting is shifted to the GPU, and not the CPU. I was using Vista x64 Ultimate on an HP xw8200 (a dual Xeon system, based on Netburst P4), I had 7 GB of DDR2 RAM in it, and my PCI-e slot was knackered, so I put in a nicely accelerated PCI dadapter. Aero sang sweetly on that, and I had no issues with Vista. This was especcailly the case with SP2 built in and the Platform update. On an XP-era computer? Sure disabe Aero.
  15. I'd say from a pure functionality and site compatibility standpoint, the 360Chrome Build 1300 is by far the best. MyPal comes a very close second. No disrespect to roytam1 and all of his efforts, but I think UXP inspired stuff has gone about as FAR as it can go. My thinking is, a modern, usuable browser in 2023 MUST render the modern web as it is. New Reddit, desktop Facebook, my Tangerine bank site, all need to render just as smooth and functionally as they would on the latest Chromium base. You might say, "but I never go to those sites and I only browse stuff that adheres to established web standards", however, WebComponents and all of the Google-fied stuff needs to work now. Otherwise it's niche at best.
  16. As time progresses, I find myself more in agreement with this. Up until recently, I was quite eager about the supposedly upcoming Unofficial SP3 for Vista, which will largely incorporate Server 2008 Updates and KernelEx for Vista. It's cool to think that current Chromium and Gecko browsers might just run on Vista. But as experience has shown me, installing Server 2008 updates on Vista (seemingly past March 2018), I found the stability of Vista somewhat degraded. Certain applications would hang, like uTorrent, and become unstable. Even with the extra year of updates from most 2017 to early to 2018, the fade in and out of the login screen to the desktop lacked smoothness. As to which update caused it, who knows? Even on Windows 8, where I've been installing Server 2012 updates since 2016, somewhere along the line, I found switching between visual styles ceased applying the background image properly. I can sill work around it, but the functionality was compromised by one of these updates somewhere along the line. Compound those issues with whatever issues an extended kernel might introduce, and things become worrisome. A user may not notice the impact of such issues until much later. I'd rather do without such instabilities. Once I can no longer freely install Server 2012 updates past this October, I will no longer seek methods to extend the longevity of Windows 8. By then, all current browsers will lack support for the OS. Besides, I have a machine all set to go with Windows 10 LTSC 2019 next January if need be.
  17. Hey Guys! (and perhaps @roytam1 in particular:) I run the x64 build of Interlink Mail and News on Windows 8. Binary Outcast hasn't updated it since last summer. So I have three questions. In each case, let's discount anything to do with Windows XP/Vista compatibility) (a) Other than the fact that you only provide an x86 build of MailNews, how are you updating Interlink, when Binary Outcast hasn't updated in seven months? In a synopsis, what is basically different from the official version? (b) Next thing, what are the key differences in the Windows version of IceDove that you create and MailNews? Are there UI and functional differences. (c) Last question (and least important of all) - Is IceApe a reworking of the Seamonkey Suite on UXP? Or is it MailNews and BNavigator combined? Thanks for your help
  18. Well, when it comes to security, you aren't accountable to me or anyone. I'm glad that you made your software available, and that's all I can ask However, I don't 100% agree with the security by obscurity stance that most MSFN board members side with here. Nor do I believe that AV or third party BS will save you either. But some of the holes that have been discovered on Chromium code has actually been exploited on users already. That's how they were discovered. That's also why up until recently I stuck more with Gecko based projects. Nonetheless, just because you think it's all BS, and you've never never been attacked on an old OS and browser, doesn't mean it's not a real thing. Anyway, 360Chrome is very promising. I'll keep using it conservatively on my Vista notebook (which is kept at my girlfriend's so it isn't a daily driver or anything like that), and I'll keep looking for newer backports and projects. Maybe it will be one of yours.
  19. That doesn't mean that I don't want my browser to be as secure as possible. Ideally, I'd like to bank on my notebook. That's not a stretch. If you look at ghacks, or anywhere Chrome releases are profiled, and you look at the number of security exploits and zero-day patches that are issued with each release, it's worse than Windows by a GREAT DEAL. That's not beating a dead horse at all. That's precisely why I was interested in that new v110 backport. However, I'll have to wait.
  20. Hey guys, what would be the major differences between builds 1350 and 2022 (besides the lower RAM requirements of the former)? I'm planning to use on an x86 notebook with Vista Home Basic (with 2 GB of RAM) Edit: I've been using Build 1350 with the above Notebook, so I didn't know if I was missing out with Build 2022)
  21. Without reading through the whole thread, has Thorium ever entered the conversation? It appears that security patches are just being applied to v109, but I could be wrong.
  22. Only x64 builds at the moment, I take it? Good to know this is out there Hopefully I can use it eventually on Vista Home Basic UPDATE: This requires Vista Extended Kernel, so it's of no use to and x86 Vista installation
×
×
  • Create New...