Jump to content

dencorso

Patron
  • Posts

    9,129
  • Joined

  • Days Won

    63
  • Donations

    25.00 USD 
  • Country

    Brazil

Everything posted by dencorso

  1. It's just the current buggy IP.B! There's nothing in particular causing it, it seems to be fully random, in fact.
  2. On your daily usage. Yes. One's MMV, of course...
  3. Try just this from a dos box before anything. I've used it many times in the past. It just works. %systemroot%\Microsoft.NET\Framework\v4.0.30319\ngen.exe executequeueditems
  4. Well, what I do criticize in your posts is the way you usually avoid saying anything. You instead direct the reader to a link or image and let the reader deduce or conclude what you're posting about by her(him)self. I'm not trying to bully you. When, sometimes, I've criticized the content of some of your posts, it was in the sense that you adopt a paranoid attitude. I do criticize @glnz about that, too, and he's never offended by it, even because there's really no offense meant. Not to him and not to you. There was no need to delete the contents of that post. My replies were intended to be constructive, not offensive. I apologize if you felt offended.
  5. You sure ought to try to be somewhat terser... with all due respect, your prolixity is really unbelievable!
  6. Well, the published way to disable the Spectre and Meltdown mitigations is in the attached .reg file below. No need to actually avoid any update because of them. But I'd sure skip the telemetry-related updates (especially KB2976978) and the Universal CRT (KB2999226). There are other updates to avoid (the ones related to update to 10) but I'm not sure they even remain being offered. Effectively, by updating from the latest to the oldest updates, you ought not to be offered any superseded updates without Incurring in any known issue, AFAIK. But I'd do that only if installing 8 from scratch, as I'm no fan of reinstalling an otherwise working OS. Bit rot is nothing more than a PEBCAK, IMO. My oldest still active XP machine was originally installed in Sep 09, 2007 and runs at present no worse than it did at first... actually it does it better because I used to have AVG 9 on it and now it runs just MSE 4.4.304.0, which does tax much less the machine. It was an Athlon XP 3000+ machine originally, but now it runs on a Phenom II X4 940 Black Edition (even so, either one of my two i7 3770Ks run circles around it,,.). KB4078130_Off.REG
  7. So, isn't it best to actually disable both? With just a properly patched browser one should be safe from all attacks coming from outside the console. And, in case the attacker has actual access to the console, Spectre and Meltdown aren't the only ways to pwn it, anyway.
  8. For users of LvLLord's patcher to avoid EventID 4226 only (if you don't know what I'm talking about, you probably don't need it): MS has released yet a newer TCPIP.SYS v. 5.1.2600.7510 in KB4291391. The current LvLLord's Patcher 2.23d remains capable of changing the half-open tcp limit, a testimony of how a well written patcher resists passing time.
  9. I'm getting that, from time to time, too! It's this "wonderful" forum software, as always! Hope xper fixes it soon!
  10. You actually don't need to remember even you own name, provided you install Nirsoft's fantabulous WinUpdatesList aka wul. Do give it a try! It's a pity it's not as useful for Windows 7 (not worth installing, in fact), but for XP it's a real must!
  11. Most people are not even aware that each of the three types of flash player installers come in two different flavors: (i) one signed with sha256 (which XP considers invalid because it does not know how to authenticate, despite their being OK), which can be downloaded from the links you posted; (ii) another signed with sha1 (which XP does authenticate as OK), from the links @Bersaglio used to post and which I have posted this time, since he didn't. Those links change with every new version, but are easy to create by hand once the version number of the latest release is known. However both flavors of installers have the same payload, for each one of the three existing types of flash player. Now, those who find what I just said confusing or do not know what I'm actually talking about may as well ignore it totally, since it's just a daetail of little importance for most of us, except for those affected by supermegaueberparanoid (me included, in this case) tendencies, and want to validate the installers before use, without having to make use of a Vista+ machine just for that. That's all there is to it,
  12. You can write a .cmd using the start command to accomplish that.
  13. I assume you are using @heinoganda's modded KB4134651. If not, remove the original and install the modded one. In case that is taken care of and the problem persists, I doubt it may be the any of the updates, but we'll know for sure only if you investigate further... Try removing just KB4339291, then reboot and see whether the problem persists. If so, reinstall it, reboot, remove one of the other KBs, reboot, test, and repeat until you test all combinations of just one missing update. Then report and we'll go from there. Obviously that's easier to do on the VM, so that's the way to go. Good luck!
  14. However, for those wanting old-fashioned sha1 Digital Signatures that can be validated by Windows XP, the direct download links are those below: Internet Explorer ActiveX: http://fpdownload.adobe.com/get/flashplayer/pdc/30.0.0.134/install_flash_player_ax.exe Mozilla Firefox NPAPI (also for Opera Presto/Google Chrome 44 and earlier): http://fpdownload.adobe.com/get/flashplayer/pdc/30.0.0.134/install_flash_player.exe Google Chrome 45 through 49 PPAPI: http://fpdownload.adobe.com/get/flashplayer/pdc/30.0.0.134/install_flash_player_ppapi.exe ... as usual.
  15. Let's say you've got jre1.8.0_152 already installed. It'll be at C:\Program Files\Java\jre1.8.0_152 Rename that to C:\Program Files\Java\Old_java Create a new folder and rename it to C:\Program Files\Java\jre1.8.0_152 (it'll be empty, of course). Extract all the contents (subfolder included) from jre-8u172-windows-i586.tar.gz into that empty folder just created. Merge the attached .reg to the registry (it must be modified for each new version, of course). Replace the old javacpl.cpl at C:\WINDOWS\system32 by the new version from now on C:\Program Files\Java\jre1.8.0_152\bin Reboot and enjoy your updated java! Note: updated .REG file is in the post below.
  16. Well, if your problem is just to install one or more program, @blackwingcat's version spoofer might be the best option, and it should be worth a try, in any case. Here's it: fcwin2k
  17. At the App Store, by forking up $$$, of course!
  18. Well, our continued critical attitude regarding Windows 10 and our unrelenting defense of the right people has of continuing to use older OSes, including giving actual support for such users (us included, of course), is bound to annoy seriously most MS fanbois... but I doubt it might reach the point of their deflagrating an actual DDoS on MSFN. In case it may be so, well, it an honor to be so distinguished, IMO.
  19. SP4 was created by @harkaz, who's a member both here and at RyanVM's, which forum actually is a sister org to MSFN, and also it's the place where we regroup when MSFN is down for some reason... The last SP version ever released by MS for XP is, in fact SP3.
  20. You can always convert such a link (when you know the topic ID) to this format, and it'll work: http://www.msfn.org/board/index.php?showtopic=177570
×
×
  • Create New...