dencorso

I'm no gamer (using computers), so I really don't care for Direct3D and OpenGL. When I'm in the mood for playing (which is seldom, nowadays) I: * Either play cards (using real waxed linen-papar cards). * Or go to a pool hall to shoot some pool. I was thinking about using older software in Win 98 and, for that, VirtualBox is perfect, easy to set-up and free.

With all due respect, I disagree. Start with a sufficiently powerful machine, say, any Sandy Bridge or Ivy Bridge i7 with 8 GiB RAM. Add, as the host, the x64 version of either Slackware, Debbian, TrueOS or Win 7 SP1. Add VirtualBox 4.3.40. Then follow the well tested instructions of @Kurt_Aust, who's been doing it for a real long time already. Links (I) and (II). With 8 GiB RAM onboard, one can give a little more than 3GiB RAM to the VM, and max up the Win 98 experience (better with RLoew's RAM Limitation Patch, but that's optional, especially up to 2GiB RAM).

The best way of capturing an image nowadays is: give it a generous serving of pepper spray to the face bludgeon it to submission 'cuff it behind the head kick it forcibly into a .WIM It always works beautifuly, although some care is needed not to let it get speckled with purple...

The reason you had to do more than what is described in the 1st post is that you're running portable versions, which are a very different beast from the normal versions. So you adventured into uncharted waters, had a fair share of issues, but persistes and met with success! Great! Now, thanks to your hard work, others shall be able to do it much more painlessly, and we all know it does work, so it's not a longshot anymore. Hence, thanks are due to you! We sure appreciate your reporting the results of your hard work for the benefit of the whole community!

I don't see that on FF 52.2.1esr both on 7 SP1 and on XP SP3, both x86 (in case it may be relevant).

If they had a Retro Consumer Plan, say, US$25 for a lifetime license with driver pack for new hardware and no support but for a hobbyist forum, they might get a much wider market. As it is, I think only corporate users may have some interest in the so-called ArcaOS. ==========///==\\\========== OTOH, this may be really interesting: OpenVMS is back! And there's a x86 version in the works (although it's still just vaorware, at this point). Some more info about it in this report.

Well... it's known to work for FF 45 and higher, but AFAIK it wasn't even tested with any versions below that... BTW, why 42.0 in particular?

"ArcaOS (the new OS/2) Review" - Lunduke Hour - June 6, 2017

Not that I know of. But I'm pretty sure that an English-only (ENU, for instance) version of the exact same flavor than yours ought to accept your own valid license key all right, as a new install, regardless of language. So an original iso of the ENU version ought to be enough for you, no need to acquire another one, in case you decide to substitute German for English.

A DOS mode device? Crafted by yourself or 3rd party?

Adobe says: Source: Adobe's announcement. Which can be translated as: "Flash will remain available until way after POSReady 2009's eventual EoL"! As you all fully know, the relevant dates, according to MS are: Source: MSDN.

I have both activated, and hence YouTube defaults to Flash. Other sites not using Flash anymore also depict fine in my machines. I'm not on Instagram, Facebook or Twitter, however, so I cannot say anything about those...

It'd be more befittingly named Creator's Fall Update, however, when judging by the recent precedents...

Тільки англійською, будь ласка! [English only, please!]

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!

Well, in this case I'd say it's support, not advertising, because @ruthan's already bought that patch, way back when...

I think there's something about it in @Sfor's theread on the Eee PC...

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.

And I think many others rather prefer practicing omphaloskepsis than replying to people who act like you, too.

Then again, there's this adapter, too...

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.

@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! ============ Read also this article at ZDNet: http://www.zdnet.com/article/windows-xp-why-it-wont-die-for-years-to-come/

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"!

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").

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.