dencorso

Supervisor
  • Content count

    7,566
  • Joined

  • Last visited

  • Days Won

    52

dencorso last won the day on June 11

dencorso had the most liked content!

Community Reputation

501 Excellent

1 Follower

About dencorso

  • Rank
    Iuvat plus qui nihil obstat
  • Birthday

Contact Methods

  • Website URL
    http://

Profile Information

  • OS
    XP Pro x86
  • Country

Recent Profile Visitors

7,483 profile views
  1. It'd be more befittingly named Creator's Fall Update, however, when judging by the recent precedents...
  2. Тільки англійською, будь ласка! [English only, please!]
  3. And no Gauloises? In a deep dungeon, they may bring some comfort, you know... ===== Anyway, it's too late, @glnz, you're omnium consensu capax praeceptionis, there's no going back now!
  4. Well, in this case I'd say it's support, not advertising, because @ruthan's already bought that patch, way back when...
  5. I think there's something about it in @Sfor's theread on the Eee PC...
  6. I confirm your findings. My now decommissioned A7V600-X with an Athlon XP 3000+ run XP SP3 great... but the lack of SSE2 annoyed me to the point of eventually decommissioning it. The worse part of it is that planned obsolescence, enforced by MS, not actual need, is actually the main problem, for most cases: MS VC++ 2012 (released 10/31/2012), was the 1st MS VS that enabled SSE2 by default (and all its successors do so, too). For MS VC++ 2012, it was possible to compile for non-SSE, by using the /arch:SSE and /Oi- compiler directives, but I don't know whether later MS VS versions still offer such compiler directives or not. In any case, since the default became to compile for SSE2 from MS VC++ 2012 on, almost no author ever bothered to disable that, even if SSE2 instructions weren't actually needed or helpful for the software being compiled. That's why I reckon that, nowadays, non-SSE2 machines are already a lost game.
  7. And I think many others rather prefer practicing omphaloskepsis than replying to people who act like you, too.
  8. Then again, there's this adapter, too...
  9. Go to C:\WINDOWS\system32 and find kernel32.dll. Highlight it, right click for the menu, select properties, then version. It should be v. 5.1.2600.7248. If the number is less than that, then you've got v1.
  10. You want to be OP, your wish is my coomand! So, now you're OP again and I've copied the original content to it. Your original initial post remains at the place @jumper pointed you to. Please do transfer the links and other details I missed to the new initial post. I would never have deleted a whole thread for no reason: my task is to supervise, not troll, you know...
  11. Done. Enjoy!
  12. @glnz: Thank you very much for kindly volunteering to create and mantain at the 1st post of this thread "a compressed guide to what we're doing now"! I have accordingly transformed you into the OP of the thread, so as to allow you to do it easily, and to modify it as many times as you feel it's warranted. Don't worry, we sure will have lots of suggestions to improve it, once you create it! Enjoy!
  13. I think maybe @niko32: has just hit jackpot. But, in any case, besides serving as a Guinea pig for updates every month, your fellow user here (aka me) would appreciate very much some feedback about that issue, because, as you fully know, "Knowlwdge is Power"!
  14. How do you intend to invoke it? By typing just "MSInfo32" on the "Run" box it should work, but it shouldn't actually work from a "DOS Box" (aka "CMD Window"), because that folder isn't in the path. So that's a feature, not a bug (= "it's by design").
  15. KB4025398 is MSInfo.EXE v. 5.1.2600.7292... adding it, even if your machine doesn't have it, should cause no harm, much less updating it. It's default location is C:\Program Files\Common Files\Microsoft Shared\MSInfo and the reason for issuing the update is CVE-2017-8557.