Leaderboard

Well I am not gonna lie to you.. It helps to not p*** me off. I am well aware of my flaws. I am also aware that the bulk of what you have experienced from me here has been negative. But as I alluded to that isn't the totality of reality. Posts like the last one I have been making for years and years on the Pale Moon forums. But like here, people do have a tendency to p*** me off when they don't listen or try to understand basic concepts. However, I am also still against there still not being branding and specifically still not happy that trunk and/or unreleased code that happens to exist is being distributed. Branding would be an instafix. I might even help you on occasion. I have been exploring this stuff for over 10 years and have been actively involved in stuff for over five years. I know a lot. AND I know something else.. As far as the applications in binoc-central are concerned... I can help you a lot more than what will ever be be permitted in the UXP repo. Here is what I am going to offer to you roytam1 et all: Formulate branding for Navigator and Mail (a large size png logo and a name) and start building following defacto release code and I will do the work upstream to implement the branding it plus his patches under the ifdef XP_WHISTLER. That way there is less of a burden downstream and maybe roytam1 can establish a more legit (in my eyes) thing. You will still have to use your modified UXP but you could start to use binoc-central as-is. BONUS: Do it for Pale Moon and Basilisk too and I will actually support your efforts to any XP Users and add you as non-aligned on thereisonlyxul.org. I will also teach and help you setup facilities like aus, the blocklist, etc. Allow me to reiterate: Branding and using release code rather than trunk code and you guys can rise and serve the Windows XP (and Vista I guess) Community in a way that has yet to be seen. You have this chance once again. I'd suggest you not squander the opportunity.

I hope whoever has them will see that ALL of his programs and patches are uploaded and archived at the archive.org link posted above, both the free and pay ones. They should all be stored together for easy access. That the family has graciously encouraged that rlowe's work be preserved and distributed is a truly kind and wonderful thing. Their wish, and his memory, should be respected. Cheers and Regards

I didn't realize that people would find out so soon about my father's passing. I wanted to express my appreciation of the impact he has had for many of you with all his work on Windows. I got to hear about it for years over meals and I never realized how many people found value in his patches. It is a busy time right now but I did want to clear the air regarding the patches. I would like them to continue to be distributed, for his work to be remembered and to be beneficial to others. So, please, freely distribute what you may have in terms of the work my dad did. When things are more settled, I will see what I can do regarding anything missing he might have had available and whatever relevant material there might be that someone could use to further pursue his work.

since there is no significant commit from upstream, there will be no new UXP based builds today.

This iBook G4 features the Radeon Mobility 9550 32MB. I have used the enforcer yet, but it is on my docket of things to do today. I can confirm what you've stated about Intel GMA performing well in webgl. In my experience, it performs EXTREMELY well, and considering the low power consumption, I actually prefer Intel GMA in older laptops, as opposed to dedicated GPU's due to excellent webgl performance, low power consumption, and excellent reliability (old laptops were plagued by GPU BGA issues).

Awesome! What is the graphics card of your Power Macintosh? Did you use the Enforcer too? Today I've applied the Patch for the first time on a Vista-era laptop: an Acer Extensa 5230 with a Celeron 560 CPU, 1.5GB of RAM and the infamous Intel Graphics Media Accelerator (or Decelerator, as often nickname it) X3100, born with Windows Vista Basic but came with Windows 7 installed. The Patch made Firefox much more usable and scrolling was actually smooth, which is quite impressive considered the ultra low end architecture of the machine itself. Unfortunately the HDD was not in the best shape (the SMART reported several failures), so if it worked properly, it could've ran even better. I also got a slight improvement in hardware acceleration after enabling tiles. So apparently the trick reserved for ATI cards might also work with Intel IGPs, or at least it does on the GMA X3100.

I haven't seen any feedback regarding testing on OSX PPC, so I figured I'd chime in here. Prior to applying the UOC patch, TenFourFox was borderline unusable, even on the fastest Powerbook / iBook laptops. After doing so, I've noticed quite a big uptick in performance, especially while scrolling! So, with that being said, double thanks, @looking4awayout!

With that insight, along with the fact that the number of reserved sectors in a FAT32 volume defaults to 32, it occurred to me that if I could just "round up" the number of FAT sectors to the nearest multiple of 32, then both FATs and the data clusters area would all be 16KiB-aligned! So with that in mind, I downloaded the source code to mkdosfs, made that change (turned out to be a one-line fix), and recompiled it with VS2010. And it works: The key is that the FATs are 27344 sectors long vs. the 27333 sectors calculated by the original version. (BTW, the Linux code in mkdosfs will auto-select FAT32 - you don't have to specify "-F 32" if the volume is 512MiB or larger - but that change was never ported to the Win32 code, so I did that too "while I was at it.") CrystalDiskMark indicates that aligning the FATs in this manner doesn't make a noticeable difference, but it may not tell the full story. It creates test files, then measures sequential and random read/write speeds to them, so the FAT doesn't get updated while the benchmark tests run. I looked online for a program to benchmark file system operations, as opposed to raw read/write speeds, but didn't find much. There is a program called Iozone, but it's a very complex command-line program with very little help or documentation, so I couldn't figure out how to use it.

I think that's exactly right. FUEL isn't something new or updated add-ons should ever use, but it's good to leave it in PM (and hence NM) so that extensions that did use it (but that are no longer being maintained) can still run. Speaking of which.... Mozilla announced the details of its plan for the deprecation of TLS 1.0 and 1.1. This will happen in March 2020. Others may disagree, but I don't have a problem with this. TLS 1.2 has been recommended since 2008; by now, every Web server should support it. The concern I have, though, is that this industry-wide move will encourage even more Web sites to disable TLS 1.0 and 1.1. That's not a problem with desktop browsers (even XP supports TLS 1.2 with the appropriate patches), but it's a big problem for users of older mobile devices, since mobile apps rely on the OS to provide TLS support, the OS on these devices cannot always be updated (particularly with Android), and many mobile devices were shipped without TLS 1.2 support through at least 2012. I know that the Powers That Be have decreed that everyone shall throw their old mobile devices in the trash and buy brand-new ones every year or two, but that's always rubbed me the wrong way. Online banking is one thing, but if I'm just downloading a podcast that's available to the public anyhow, I don't mind not using "current and recommended cipher suites."

> Oh crap, Tobin's here.. what insanity does he have this time? WELL non-existant but likely quote, I am gonna clarify both the Navigator version reduction and the deal with FUEL. The reason the version was changed to a lower version is because I intend to start making releases of what is essentially an unfinished product and thus isn't 1.0 quality. I announced this would be happening eventually some months ago but other priorities have delayed it. When it does happen, consider it a public beta and technology preview with a goal of reaching a true 1.0 status. As for fuel.. As Australis Technology progressed, FUEL was an ancient developmental burden in the eyes of Firefox developers. It was eventually depercated and removed from Firefox. Proper Basilisk comes from a time where FUEL was long gone and the Australis Technology progressed (or is that regressed) the specific capabilities of the browser application code. It doesn't make much sense with the custom Australis Based UI of the main window. As for its deprecation in Pale Moon.. As you may know, the specific Application code for Pale Moon 28 is actually an uplifted and evolved form of code that started life in 2013 as Firefox 24 modified for Pale Moon 24 though 26, ported to Tycho for Pale Moon 27, and ported again to UXP for Pale Moon 28. There is absolute continuity for the application specific code from 2013 to today regardless of the platform codebase. This has been my design and the bulk of my research and contribution over the past five years. Pale Moon has stayed Pale Moon as I have promised so shall it is. I considered removing FUEL but decided against it for extension compatibility reasons and instead added a deprecation warning so that forks and new extensions do not use the component. It is not outside the realm of possibility it could be removed at a future date but it is exceedingly improbable. Think what you will about me and how I conduct my self but truth be told I have been the driving force for years in ensuring as much compatibility with extensions as reasonably can be achieved and the general continuity of Pale Moon AS what everyone expects Pale Moon to be. Without that influence over the years, I shudder to think what might have happened. Likely potential eventualities may have followed a path similar to the likes of Cyberfox and Waterfox. We shall never know because not only will my influence never be wiped out and I shall never be stopped from continuing forward on the path I helped to lay out. Sometimes you have to accept the good with the bad and perhaps I am neither.. Or perhaps I am all those things and more.

Some leads on drivers... Software: ftp://ftp.hp.com/pub/tape/ Possible softpaq ID: ftp://ftp.hp.com/pub/softpaq/sp23501-24000/sp23518.txt move up on dir on that to get the exe.

This is sad. If I've offended anyone in the past I'm truly sorry and please forgive me. Life is too short to be fighting and bickering. Again, sorry for any troubles I've caused. God rest his soul...