Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 07/10/2019 in all areas

  1. You can download a new (FF53+) theme that you like, extract the xpi with 7 zip or maybe winrar, it's just a fancy zip. Inside you'll see the actual banner image, which is the theme. You can get the "Personas Plus" add-on for the Classic Addons Archive, which you can use the image you extracted to remake the theme using this add-on. More information on using Personas Plus: https://www.howtogeek.com/203803/HOW-TO-CREATE-YOUR-OWN-FIREFOX-BROWSER-THEME/ This isnt a beautiful process, but it works fine. :)
    1 point
  2. I'm going to look into trying this, but one quick note: your links are reversed! the link for 45 ESR leads to the 38 ESR UOC patch and vice versa. c
    1 point
  3. UPDATE! After some weeks of intense development, I have finally released the new version of the UOC Patch, build number is N2F. Compared to the previous version, this new one has been reworked almost entirely: many entries that point to my FF45 ESR SSE installation have been removed, shaving the size down to around 25KBs, making it even easier to fit in a floppy disk (3.5" or 5.25", your choice, for easier portability), but I've also reworked the loading routine of webpages, disabling the asynchronous panning and zoom feature, which instead of offloading the CPU, it is somehow bugged even on 45 ESR based browsers, causing an excessive spike in the CPU usage. Also, scrolling webpages while they are loading images should be smoother now, at least it is on my Tualatin RDD. I've also increased the memory cap of Javascript processes to 96MB, which seems the sweet spot between usability and performance, at least on my machine. But the biggest news is the introduction of the UOC Enforcer. The UOC Enforcer is a custom "user.js" file that must be placed into the browser's profile folder and that tells the browser to change the "stubborn" entries in the about:config that are hardcoded by the developer, making the UOC Patch work even better. You must remember though that the UOC Enforcer doesn't let you change the edits from the about:config, so if you want to change a "stubborn" entry, you must edit the user.js file directly (you can do it with Notepad). Therefore, I strongly suggest you to open the UOC Enforcer file and check out what are the stubborn settings, in case you want to change them in future. Most likely, you won't need to do that. While the Enforcer is optional, I strongly recommend it in order to get a better experience with the UOC Patch, as it tweaks the browser further. You can download the updated version of the UOC Patch and the UOC Enforcer in the main post. Please test the patch on as many machines as possible, and remember that it's offered AS IS, since I develop it in my free time, in order to squeeze some more power out of old computers and making them still useful online just like when they were new. Thanks!
    1 point
  4. The Autoconfig method seems to work for me. However it's a bit of a PITA; if you get anything wrong the browser refuses to start and tells you to contact your IT administrator (or words to that effect). Here's how it works (if everything's set up right): You need to set two prefs in your "main" pref file to invoke Autoconfig: pref("general.config.obscure_value", 0); pref("general.config.filename", "myuseragents.js"); (As you can tell, I'm using this trick for my SSUAO list, since it lets me override SSUAOs built into the browser, whereas the built-in SSUAOs take precedence if doing this the "normal" way, much like the problem you're having with the prefs you listed.) Then you put the file named above (myuseragents.js) in the same directory as the browser (firefox.exe, palemoon.exe, or whatever.exe), and it has to look like this: // Needs to start with a comment line defaultPref("webgl.enable-draft-extensions", true); defaultPref("webgl.enable-privileged-extensions", true); defaultPref("dom.ipc.plugins.asyncdrawing.enabled", true); Notice the mandatory comment line at the top, as well as the use of defaultPref() vs. pref(). In an Autoconfig file, pref() works like user_pref(), while defaultPref() works like pref(). If you get everything right, the browser will start, and if you check about:config, you'll see the prefs above all default to true now (which you can still override back to false if desired). But since it's so easy to break this with a typo, and since the browser is completely unhelpful in troubleshooting problems, it's still not an ideal solution.
    1 point
  5. Hearts from 3x/9x do not use a central server like Internet Games do, should be fine forever, I think it's like a LAN thingy...
    1 point
  6. Good. Only for the record the idea is "generic", a USB bridge uses (obviously) the USB protocol to communicate, and a number of factors (including the actual protocol, the drivers used, the actual OS features, the specific USB bridge chipset AND firmware and also *whatnot* ) may make a particular command either to NOT "pass through" or to "pass through" but in a slighly modified way (which may lead - you can never know - to either "nothing" or to a "destructive" result). As an example, a number of "mass production tools" for USB sticks require the use of a specific, dedicated driver (which doesn't work as a "normal" USB mass storage driver) to access some settings in the controller of the stick. As well some of the USB "direct" hard disks (i.e. with the USB bridge/interface directly on the hard disk PCB) cannot be in some cases analyzed/fully accessed/reset via that and you need to "pin out" the SATA connection (when possible): https://blog.acelaboratory.com/if-you-are-planning-to-work-usb-external-hard-drives.html https://blog.acelaboratory.com/pc-3000-hdd-how-to-solder-a-sata-adapter-to-the-usb-western-digital-drive.html https://blog.acelaboratory.com/soldering-of-sata-connector-to-samsung-spinpoint-usb-pcb.html So, again generally speaking, don't, just don't fiddle with this kind of stuff via USB if you have a more direct SATA access. jaclaz
    1 point
×
×
  • Create New...