looking4awayout
Content Type
Profiles
Forums
Events
Everything posted by looking4awayout
-
Yeah, I just tried by myself, and that sucks especially for people who tweak the UOC Patch to suit their taste. I think the least worst idea when it comes to those "stubborn" prefs is to just make a user.js file with only those ones, so they won't interfere with the rest of the patch. This "mini patch" can be optional and anyone is free to download it to complement it. Do you think it would be a good idea? -
Interesting. I have to try to make the patch as a user.js file and see if the values I want to be applied, get applied automatically. If they do, I'll have to make the UOC Patch into a user.js file. Any drawback about that?
-
I'm not a programmer, unfortunately, so I have no clue about how to write an extension... In that case I'd have to hand the development of the extension to someone who's capable of doing that. Due to the lack of skills and time, that isn't a viable option for me, I'm afraid. :(
-
I have found two other keys that Firefox "hardcodes" forcing the user to set them manually. Here they are. Set them the way listed below: dom.ipc.plugins.asyncdrawing.enabled - True plugin.allow.asyncdrawing - True And an experimental key, that is normally set to True in the 45 ESR version of the patch (it's disabled in the 38 ESR version as it causes a 100% CPU usage all the time), but I'm testing the browsers with the value disabled. layers.async-pan-zoom.enabled - False Please set these other three values the same way and tell me if you notice any improvement in performance. Don't forget to set the other values I listed in the main post, because if you do notice improvements, I will implement them in the first page as well. For Mozilla experts, is there a way to circumvent the "hardcoded" keys in the about:config? The UOC Patch sets most of the keys the way I want, but the ones I listed above, even if I put them in the patch, won't be applied, forcing me to set them manually. I've tried the AutoConfig way mentioned in the Mozilla wiki, but the only thing that does is crashing the browser. There must be a way to fully implement the patch without tampering with the about:config... Do you have any suggestion @roytam1? Your opinion would be very helpful to me.
-
Don't forget to apply the UOC Patch to your browser, which I made to optimize Mozilla based browsers for old computers.
-
No new version of the UOC Patch for the moment, but I want to give you a little heads up that I found out while messing with the about:config. If you set the settings below this way: webgl.force-layers-readback - False webgl.enable-privileged-extensions - True webgl.enable-draft-extensions - True dom.enable_performance_observer - True dom.performance.enable_notify_performance_timing - True dom.performance.enable_user_timing_logging - True The performance of Mozilla based browsers will significantly improve. Unfortunately they don't work if I implement them in the Patch, so you will have to set these parameters manually through about:config. But give them a try, on my machine they work and sped up the browser further. Tested on Firefox 45 ESR SSE, New Moon 27 SSE and Seamonkey.
-
My Browser Builds (Part 1)
looking4awayout replied to roytam1's topic in Browsers working on Older NT-Family OSes
Just tested both New Moon 27 and Firefox 45 ESR SSE with the UOC Patch. They run twice as fast than the previous versions of the browsers. I also noticed that sites load faster and there's a lower CPU usage during that process. Great work, @roytam1! -
UPDATE! I have disabled two options regarding non essential tasks about SVG elements in a webpage, mostly used for testing purposes. On my machine, the browser increased its responsiveness with these two options disabled. I've also noticed that NoScript 2.6.9.32 and 2.6.9.27 tend to cause issues with Mediafire, if used on Firefox 45 ESR SSE, but on New Moon 27, there are no issues with the site. So, I recommend you to use NoScript 2.9.0.9 upwards if you are using it on Firefox 45 ESR SSE, and leave 2.6.9.32 or 2.6.9.27 to New Moon only. You can find those versions on the Legacy Collector website. Please update and remember that the UOC Patch is offered AS IS!
-
@Mathwiz has been faster than me at providing you the link. I got it from that site. It's super useful! Pardon for the slow reply, we had a theft at work and so I had no time at all to check the RDD out.
-
If you can wait a couple of hours, I will provide you the link for the best version.
-
That's nice to see the patch improved the speed of your browser. And yeah, if you want some extra speed, you absolutely need a DirectX 9 compliant graphics card, the S3 Virge and the Radeon 7200 are not D3D9 compliant. Make sure you apply the two settings in the about:config I've mentioned in the main thread, to save some more resources. Besides NoScript, don't forget to use uBlock Origin 1.10.0 as well as Bluhell Firewall and Decentraleyes. Those extensions, alongside NoScript, help a lot in terms of saving resources.
-
My Browser Builds (Part 1)
looking4awayout replied to roytam1's topic in Browsers working on Older NT-Family OSes
The patch will work nonetheless. -
My Browser Builds (Part 1)
looking4awayout replied to roytam1's topic in Browsers working on Older NT-Family OSes
Did you try New Moon SSE with the UOC Patch? Your computer would be an interesting test bed for my patch, as I don't have a Celeron Coppermine system. -
I'm very honoured that you have replied in my thread! :) I hope the patch really does bring benefits to old computers. Maybe in future, if you wish, you can even embed it in your browsers. That would be a honour for me.
-
It's strange that on your computer you need to put the patch in your profile folder too, in other computers, the patch just works by putting it in the \Defaults\Pref\ folder, of course, being a defaults replacement, you won't see any custom entry in your about:config, because the entries that are modified by the patch are now considered as default ones, and so they won't appear highlighted, nor they will appear in the prefs.js, that contains only the parameters edited by the user*. That's how me and the others install it. But hey, I'm glad you got that site working now, even though you had to install the patch twice. *: However, I discovered that there are two parameters that for some reasons, the patch ignores, but they can be edited manually in the about:config. Here they are: image.mem.max_decoded_image_kb 512000 browser.urlbar.maxRichResults 1 While it's not strictly compulsory to reduce the "awesome bar" to just one entry, I do it to save RAM. It's important to set the max decoded image memory to 512000 though, as that further speeds up images rendering. For some reasons, the browser ignores just these two parameters. But it's just a quick fix, just open about:config and edit the two parameters above. Remember, the UOC Patch is not set in stone, you can edit it to suit your needs and add or remove some features you like/dislike. But I'm glad you sorted your issue out. I've updated the main post with the two settings for the awesome bar and the maximum decoded memory for images.
-
You're basically running the browser unpatched now. You must install the UOC Patch in the "C:\Program Files\Mozilla Firefox\Defauls\Pref\" folder. It is independent from the prefs.js in your Firefox profile folder. Do not put the patch in your profile folder, or else it won't work! You must redownload the patch (since the one you have renamed and put in your profile folder has essentially become empty, all the custom entries have been removed...) put it in the "C:\Program Files\Mozilla Firefox\Defauls\Pref\" folder. The old prefs.js file you see in your profile folder must be deleted in order to let Firefox create a new one. Often, the prefs.js file becomes clogged with old entries from older versions of Firefox and that can cause conflicts with the UOC Patch, as it replaces the default values (since the UOC Patch gets installed as a defaults value replacement file) with custom ones. So it's always recommended to backup and delete the old prefs.js after installing the UOC Patch, for better compatibility.
-
Oh no no! You can find your Prefs.js file in your profile folder. If you have XP go to "C:\Documents and Settings\(Your Username)\Application Data\Mozilla\Firefox\Profiles\(Your Profile folder)" In case of Vista, go to "%Appdata%\Roaming\Mozilla\Firefox\Profiles\(Your Profile folder)" EDIT: Just tried the page you linked. No issue by my side, except I had to whitelist the site in Noscript. No lockup. To put additional strain on the A64, I'm also making a Windows 10 USB drive through the Media Creation tool.
-
I'm not sure about the plugin container issue, as I haven't had any stability issue on my machine (and I usually keep 10+ open tabs on my Tualatin). You should not have the plugin container. The UOC Patch disables it. That's strange. Do you have a custom Prefs.js? Try to delete it and let Firefox recreate a new one, and see if it makes any difference. On the machines I tested the patch, the plugin container gets disabled as soon as I run the patch, reducing the memory footprint. No stability issues encountered by my side. Do you have any kind of add-on installed? If you haven't done it already, I recommend you to use Noscript, uBlock Origin 1.10.0 and Bluhell Firewall for a better experience alongside the patch. For YouTube I use the vastly superior YT2Player plugin, that sends YouTube videos to VLC, preventing the CPU to get clogged. In-browser YouTube videos play fine on my machine but stutter a bit due to lack of CPU power, hence why I use that add-on. I wholeheartedly welcome someone who can help me ironing the patch out, as I'm clueless about what else I could do to improve it due to lack of coding skills and such. EDIT: I'm testing the patch on a single core S754 AMD Athlon 64 3000+, 3GB of RAM, a Geforce GT240 and Windows 7 x86, using Firefox 45 ESR SSE and a fresh prefs.js. No issues encountered with more than 5 tabs opened. I have stumbled upon the Youtube issue though, and I fixed it by just disabling uBlock Origin on Youtube. In case you get the "endless spinning circle" issue, just pause the video and resume it again. That did the trick for me. All the other videos worked fine for me afterwards. Don't use the "No Google Analytics" add-on! It's a CPU hog and slows the browser down!
-
Sorry for the double post, on what computer did you install it? Did you also test it on non SSE CPUs such as the Pentium II or the original Athlon? I'm curious about it. :)
-
Awesome! Thank you for your feedback. I'm glad the patch is breathing new life on your old computer, making it still "web worthy" despite the age. I don't use any language pack on FF45, just the standard English one.
-
UPDATED! I have reworked the way layers work and set them to -1. I've also enabled the use of deprecated textures. Apparently, in this way, the browser seems to run faster. Please update and test the new versions! Archive build is n2c. Please update, let me know how it runs and remember that the UOC Patch is provided AS IS. Thanks!
-
After releasing the updated version of the UOC Patch for Firefox 45 ESR based browsers (build N2b), I have ported the updates to the 38 ESR version. If you haven't done it already, please update! Thank you for your support, and don't forget to test the UOC Patch on as many machines as you can! I also encourage the more expert users to tweak the UOC Patch, I think that together we can make something even better. I'm not a programmer and I have zero experience at tweaking Firefox, all I'm doing is just a series of trials and errors and see what setting does what, and if it can bring benefits. So far, I've been lucky. But if there's someone who knows his way around this browser (and I'm pretty sure there is!), maybe the patch can speed it up even further... And maybe someday, with @roytam1's permission, it could be even incorporated into his browsers, making New Moon and Firefox 45 ESR SSE "old computers friendly" right from the start.
-
I would like to find a way to disable service workers while "filtering" the sites that need them... I will investigate it once I have enough time to delve deep in the patch. Meanwhile, I have released a new version, to fix some bugs. The archive name is the same, "2a", but there are some minor improvements under the hood. As always, please update and let me know if things run better.
-
Please re-download it! I have re-released the patch with the Service Workers enabled. You can find it in the main page. Yesterday I tried to upload a test file of 1KB, and after enabling service workers, Mediafire started working again. It might be a problem with the site. EDIT: Mediafire uploads successfully on my computer with the post-fix UOC Patch. EDIT 2: I have tested the 45 ESR version of the UOC Patch on Seamonkey, and I can confirm it works very well. So now, the UOC Patch for 45ESR based browsers, is Seamonkey friendly!
-
UPDATED! I have done some reworks and bugfixes on both versions. I've increased the initial paint delay for webpages, in order to make them more responsive while they load. I had to re-enable service workers because they break Mediafire. Please test the patch, and as always, it is provided AS IS. Thanks!