Leaderboard

So just replacing bitmap while keeping same layout is just boring. What about putting Beta boot screen into retail? cross post from betaarchive: I think I found the position that sets progress bar and scrolling bar: NTOSKRNL.EXE 5.0.2195.7376, CHT, 1,691,648 bytes File Date: Thursday, 18 February, 2010, 20:17:26 SHA256: 86356E3BB6DB3E873AE8C881358233F5CD142EC2CEDF34D7B007B427CE085394 .text:0041D14A loc_41D14A: ; CODE XREF: sub_41CFF6+14Aj .text:0041D14A push 1B5h .text:0041D14F push 112h .text:0041D154 call sub_41CDAC .text:0041D159 push offset loc_41D1F4 .text:0041D15E mov dword_476070, 1A0h .text:0041D168 mov dword_47606C, esi .text:0041D16E mov dword_476000, 280h .text:0041D178 mov dword_475F40, 0Ah .text:0041D182 call InbvInstallDisplayStringFilter Y = 0x1B5=437, X = 0x112=274 is progress bar starting location Y= dword_476070 = 0x1A0 = 416 X = dword_47606C = esi = 0 W = dword_476000 = 0x280 = 640 H = dword_475F40 = 0x0A = 10 is scrolling bar location. but there is difficulty on setting dword_47606C, since "mov dword_47606C, esi" is 4-bytes shorter than others. -- so hacking around it is working! (VA)0x41d14a: 68 b5 01 00 00 push 0x1b5 e9 6d 29 04 00 jmp 0x45fac1 be a0 00 00 00 mov esi, 0xa0 /* it is 0x41D154 here */ (VA)0x45fac1: 68 21 01 00 00 push 0x121 e8 e1 d2 fb ff call 0x41CDAC e9 84 d6 fb ff jmp 0x41D154 that splits call to sub_41CDAC into half, pushing X value goes to 15-bytes spaces at 0x45FAC1, call 0x41CDAC can jumps back to 0x41D154 for making a space to set ESI. Thanks http://shell-storm.org/online/Online-Assembler-and-Disassembler/ for a flexible-enough online assembler.

Come on man no need to take any chance. Last two years I have not got any virus that infected my computer. Most showed not a valid win32k application and some other shown missing API . Now minimum requirements to run virus is 7 and above . Do you want to upgrade to run viruses?

yeah, I'm preparing a Tycho-history repo for a clean history (like my palemoon*-history repos) will have a look after history repo is ready. yes, they ported upstream(mozilla-esr) changes into their repo, and I cherry-picked non-PowerPC exclusive patches into my repo, and M*** are actually bugzilla.mozilla.org bug numbers.

@glnz - Yes, try what Dencorso suggests to scrub any traces of the new version. It sounds to me like when you reinstalled it got the new version again. Like so many other security apps these days it may immediately "phone home" to check for newer versions and "help" you by fetching the newer version to replace the "old" one. If there are no install options to avoid this you may need to use the trick I use to keep old versions of Avast running. (And yes I do still put Avast *6* on my new builds of XP, and it does not refuse to install the old version for me.) Are you using the same old installer from before? If you can't find it, visit https://filehippo.com/download_malwarebytes_anti_exploit/ and try looking at the list of versions on the right side of the page for the one you want to use. When you are ready to install, first disconnect your ethernet cable or other internet access. Second, look at the signature date on the installer file. (Right click, Properties, select tab Digital Signatures, move the scroll bar to see the timestamp.) Adjust your system date/time to when that version was freshly released, then install. Go through the settings to disable auto update features, at least for program version updates. For Avast I would now manually insert a previously obtained license key, I don't know if MBAE uses one or not. Reboot if needed. Once all settings are okay, adjust system date/time back to the present, optionally reboot once more, and re-establish your internet connection.

I'm also someone who likes to keep settings as strict as possible, but Mozilla's pref jungle keeps growing wildly. Must be about 2000 prefs now, no chance anymore really :-( Here's another video pref you might test, affecting html5-videos: permissions.default.media=1/2/3 where: 1= allow all 2= block all 3= allow same domain Just a general tip in case you're not aware yet (or other readers), the easiest way to test single settings is on the about:config page. Because most changes there work immediately, without a browser restart. And you'll still discover your prefs.js was changed accordingly after next exit, because this is where about:config stores your changes. If a line then has vanished inside prefs.js, that's just because you chose the browser's default setting, since only different settings are stored in the user profile prefs.js, not all thousands of default prefs. To make sure a personal prefs list keeps those lines too, and also keeps user comment lines, and also keeps your own sorting order, and that it can only be edited by yourself, and that those prefs will be enforced again at next browser start, write them into "user.js". At every browser start the prefs in this file will function as startup prefs, overruling any different ones in prefs.js (Just writing this because I wish anyone had explained it to me YEARS earlier)

Yes, the Flash Player 29 still works but there will be no more updates (29.0.0.171 is the final version).