Leaderboard

Okay, this works to block all of the search engines that you cited.

I'm not finding anything that will block Infinity Search, Okeano, and Swisscows. I'm sticking with this for now -- https://greasyfork.org/en/scripts/375216-block-opensearch-descriptions/code

It's really bad, makes Windows 10 actually look decent in comparison.

I had the same crash as andreymd87, and this latest build seems to have fixed it.

What I am seeing, based solely on your information, is that Humming Owl's releases broke some javascript and then displayed it as text instead of performing the "function" that the javascript was intended to perform. But that mine did not break the javascript so the broken code was not displayed as text. Or, the broken javascript code is simply "dropped" / "ignored" by my builds but Humming Owl's doesn't know what to do with it so it displays it as text. Not sure what you think needs "fixed" here. If it sets your mind at ease, I opened that link and clicked the gigantic YOU in Dixel's v13 360Chrome, Humming Owl's v13 360Chrome, and my v12 360Chrome both in XP x64 SP2 and in Win7 x86 and all three gave me the EXACT results, letter for letter. So then I installed Chrome v94.0.4606.71 in Win7 and it too gave me the same EXACT results. Mozilla-based browser will give an entirely different view. Maybe that "test page" is intentionally 'coded' to only work on Firefox and not on Chrome - who knows.

I did not do any of the themes, they were already among the original browser files (just for the record ). The "Preferences" file changes overtime, in my case the ""theme":" entry is located at the middle of the document. The dark theme starts affecting pages (the ones compatible with a dark theme) from v12. v11 starts using the dark theme but only for the interface of the browser. Cheers.

Does it have to do with the "Browser time discrepancies" section of the first post? Nice to hear that. If you find any problems feel free to report. Cheers.

If you are looking for WildBill's post-EOL patches for Windows 2000 go to Post #3 Now, for the PE Tool for creating patches, here's the Download link: PE Tool 0.0.5 Version 0.0.1 ------------------ INITIAL RELEASE Version 0.0.2 ------------------ Improved the disassembly view: if an address evaluates to a known name, the name will be shown instead and color-coded. Version 0.0.3 ------------------ - Fixed some bugs in the assemble instruction dialog where certain edit fields weren't being enabled. - Fixed some bugs where the clicked-on address didn't match the assembly text. - Improved detection of .map entries so that they show up in the disassembly. - Added a menu entry for changing the code entry point. - Improved the feedback in confirmation dialogs when working with relocs. - Updated the .map files with my newest versions. Version 0.0.4 ------------------ - Fixed some disassembly bugs. - Fixed some bugs when assembling instructions. - Added a menu entry under Directories... that lets you change the address of an exported function. Version 0.0.5 ------------------- - ***LOTS*** of fixes - Adds control over the listing font to the preferences window. - Automatically updates build timestamps. - Tries to detect the need for relocs and will list them as warnings at the bottom in a new message window. - Highlights instructions where it thinks a reloc is needed in red. - Added buttons to the hex bytes dialog to make it easy to insert ANSI or Unicode strings. - Added the ability to split sections. - Added the ability to chop off the beginning of sections. - Added the ability to move the entire export table. - Added support for adding forwarded exports. - Added the ability to grow the file header if space is available. - Added an "Update exports" menu entry that will force rebuilding the export table. I've been trying to build a simple tool that will hopefully make creating security patches easier. It's still pretty rough around the edges, but here is a screenshot of what I've got so far: I've been using it to make a Win2k patch for KB982214, the SMB vulnerability. I'll probably be able to test the patch tomorrow in a VM. The tool lets you do a few simple things so far: - Add relocation chunks and chunk entries - Move certain sections (this is somewhat dangerous for most sections, but moving resources and relocations should be safe) - View some directory information, like imports and relocations - Automatically fixes up certain directory information if the section that contains them moves (relocations, imports, debug info, etc.) - Grow sections to fill any available slack between them and the next section - Change bytes - Assemble instructions - Fix a file checksum If you have a .MAP file the disassembler can resolve symbols and color-code them, as the pic shows. It's also showing relocations in red. I didn't write the disassembler portion and it's not perfect, but I've managed to fix some of the worst issues.