dencorso

You've just installed WUD, right? If so, the next best guess is something went wrong during installation. Try removing, rebooting, then reinstalling.

Yes. Read the post above yours.

See if you can get yourself an OCZ Vertex3... they're EoL now, so should cost little, but they do rock!

Sure. If you're using XP SP3 (hence x86 or 32-bit) you can install all the POSReady 2009 updates WU finds for you.

Well, just for the record: here's how to convert ESD to WIM. Scroll down, it's below about 1/3 of the page.

Which XP do you have? If XP SP3 (hence x86 or 32-bit) you should install the POSReady 2009 updates. Now, if it's XP SP2 x64 (64-bit), then you must use the 2003 SP2 x64 updates (and POSReady 2009 updates may hose your system).

Welcome to MSFN!

If I understand correctly, NGEN 4 set to Auto and NGEN 2 set to Manual causes all .NET versions to be optimized, because NGEN 4 will start NGEN 2 (if set to Manual, not Disabled), only when it's really necessary. But that may be just an urban legend, since I've never found official documentation that confirms it.

7.1 is 7.10 as much as 7.0 is 7.00, both do not "exist" the 7.00 (or 7.0 is the same) is the DOS underlying the first release of Windows 95 or Windows 95 A, the 7.1 (or 7.10 is the same) is the DOS underlying the later windows 95 and 98 releases. Wiindows ME has underlying a DOS 8.0 (or 8.00 is the same). However, the MS-DOS 7.10 from Win 95B/C is slightly different from that in Win 98 FE/SE, so that the latter is sometimes referred to as "7.11", although, in fact, from Win 95B to Win 98SE, MS-DOS will always return "7.10" as major.minor version. One wishing to create a standalone install od MS-DOS for general use should use 7.10 from Win 98SE, since 8.00 is difficult to isolate from Win ME.

Is it a NEC-V20 (or V30) machine?

What I meant is: the list has 21 machines without RLoew's patches and 23 using them, having 2 GiB or more of RAM installed. Of course, RLoew contributed with 9 machines, but the point I'm trying to make is RLoew's patches are more necessary for 2 GiB and above. Below that, with no SATA drives, Usher's method and LLXX patch should be enough in most cases (but Xeno86's Vcache also helps). The list, as it is, supports these conclusions, IMO. And, BTW, statistics don't lie and neither drink coffee: people, OTOH, do both, and may use both statistics and coffee as props for lying, but coffee is of little help for that end.

Statistics don't lie. Most multibooting power users here at MSFN use the RAM Limitation Patch and some use also other RLoew programs besides that one. Some don't. Everybody should know the options, of course. With LLXX's patch and Usher's method, it's relatively easy to set an up to 1.5 GiB system on a non-SATA only motherboard. Going further up gets tough. Then again, why would anyone want to go beyond 1.5 GiB? Easy: multibooting. That's how it is.

KB195446 refers to SysPrep for Win NT 4.0. What you want is this, which link I got from the selfsame thread you quoted, but failed to read as fully as you should...

My reasoning for waiting stems from the following: Fact 1 - Win 7 SP1 EoS Jan 14, 2020; Fact 2 - POSReady 2009 EoS Apr 09, 2019; Fact 3 - There're no counterparts to those two updates (viz.: KB2990214/KB3050265) for POSReady 2009. Hence MU (or, at the very least WU) ought to keep working as it does today, at least until Apr 09, 2019.

So you'd allow the updates below to install, if I get you right, is that so? KB2990214 for Windows 7 SPx and KB3044374 for Windows 8.1 (for WU) KB3050265 for Windows 7 SP1 and KB3050267 for Windows 8.1 (for WU) Since they can be saved for later, I, for one, shall keep them out of my 7 SP1 x64 installations, up to the day they become inevitable. Of course, that's just my choice, and I'm not saying anybody should follow this path on my say-so. Everyone should decide on his/her own, of course. And I do agree it's no easy decision.

Well, with all due respect, what do you think a XP and 9x diehard is, if not out on one's own, for a long time, already?

If you have both the ".NET Runtime Optimization Service v. 2.0.50727" and the "Microsoft .NET Framework NGEN v4.0.30319", set the former to Manual and the latter to Automatic. It makes no difference whether the v4 NGEN is 4.0 or 4.x, that's the one that should be set to Automatic. Let's see whether this removes the Event ID: 1111 or not.

Well, I've got good news for you: you actually do know two of them, you just didn't know you do! They're MagicAndre1981 and cluberti. I hope you never need their help, but if you ever do, now you know whom to ask.

You've got duplicate entries... here's the full list: KB2952664 KB2976978 KB2990214 KB3021917 KB3022345 KB3035583 KB3044374 KB3046480 KB3050265 KB3050267 KB3068708

Welcome to MSFN! Long live XP!

You bet! jaclaz posted elsewhere on MSFN about running Win 3.1 on DOSBox... while I'm not quite keen on using VMs, it sure seems a good option for games requiring very slow hardware (read 4.77MHz 8088 like). It's also the best option for running DOS executables and Win 16 protected mode executables on x64 NT OSes... So maybe we should open a thread dedicated to it, shouldn't we?

True. But since one can turn off the machine by using the ACPI or the APM interface (when using an ATX motherboard), many see it as part of the power management functionality.

Just to keep this up to date (not that it has changed that much since then), the Sao Paulo State Minimum Wage (the highest in Brazil) is, since 01/01/2015, US$ 2.05 per hour (using 2.82, the jan 2015 the Big Mac index as the exchange rate). It also means US$ 4275.48 per year, so there has been a loss of real purchasing power to it of about 11%, as compared to 2012...

There's really nothing to be unsure about: it's a very well known fact that ACPI support on 9x/ME is problematic, to say the least. The fact that you have a specific setup (or even more than one) in which ACPI works fine should be included among those rare exceptions that confirm the rule. I'm really glad it never was a problem for you, believe me. But do not generalize, based solely on your experience, because there are really many cases known of serious problemas with ACPI (and, sometimes, even with APM).

Yeah. Take the battery out, let it alone overnight, then put in a brand new battery, and let's see what happens.