dencorso

Methinks most of the rest of the world didn't actually partake of your opinion, however...

No wonder. HD 5500 is Broadwell-U. This tread title says Ivy Bridge (so, 3rd gen). Broadwell-U is 5th gen. What did you expect?

Does Rule #1 ring any bells, perhaps?

I didn't. @WildBill is/was a very careful and thorough reverser, who took for himself the mission of porting to 2k all the patches MS was (and remains) denying it. He studied carefully each pach until he fully understood it, then made the port. His ports are safer even than MS's originals. He went even further and reversed kernell32.dll to the point he had a working compilable source he then made public, thus providing a precious source of information regarding what he found out about kernell32.dll to anyone carefull enough to read and meditate about his soure code. And also gave people his free PE tool. But you're wrong about one detail: @blackwingcat had been extending the 2k kernel some time before @WildBill began to release his own work, and IIRR, the 1st ever to extend the 2k kernel was @OldCigarette (whom, I'm sad to say, I'm even surer isn't among us anymore).

Some of our members (with all due respect) indulge in the latest version fetish (LVF), which can be mostly harmless when not taken to extremes. I, myself, do indulge in it sometimes, I reckon, but the farthest I usually go is to change the minimum "Subsystem Version" to allow executables to run, nowadays. If I really have something that only runs on Win 7+, I either do it on 7SP1 or eschew it, usually the latter. As of today, all that I need to do in my day-to-day can be done in XP SP3. I consider the Extended Kernel approach mostly useless, although I dedicate lots of respect to @Xeno86, @jumper, and @blackwingcat. I consider the WDMSYS/WDMEX (Extended Driver Interface) very useful, but nobody has been ever able to port to the NT-family OSes what Walter Oney and @rloew ( ) did for 9x/ME... and that's why we still haven't working Intel USB 3.0 drivers at this point in time. Of course, these are just my 2¢ and everybody may disagree. Moreover, YMMV, obviously. But, considering @Thomas S. did ask the queestion above, I felt it shouldn't remain unanswered. That's all. Sage words and attitude, IMO. +1 It depends, IMO: people I know (even if just through the internet) and trust I don't consider foreign sources. Otherwise I do agree to that, too.

https://www.wimp.com/possibly-the-best-skyfall-cover-yet-by-our-last-night/

Welcome to MSFN! If any forum can make one discover something new in this world, you can bet it's MSFN, IMO. I sure hope you like your stay!

Very good.

And highlighting it can only make it even worse, ain't it?

Quod abundat non nocet!

But Windows Embedded POSReady 7 has both x86 and x64 versions and has the same EoS as Windows Thin PC, and its unmodified updates just work, so ...

While I'm already also a Win 7 SP1 user, and sometimes even provide it support, my main, day-to-day OS is XP SP3, and I'll cling to it until it becomes nearly impossible to use (I've used 98SE from late 1999 to about 2014, so ca. 14 years as main day-to-day OS, and I hope to use XP SP3 like that for even longer, but my 1st XP install was from late 2007, so I'm not even 12 years on it, yet). I doubt I'll transition fully to 7 SP1 much before 2021 !!!

No, not legally, at the very least. Then again, they may surface somewhere (as it did happen with jre6 restricted updates for some time). In any case, however, no support for that may be provided here, on the open forums, as you know. +1 Yes. And... starting on May the 14th: Ragnarök!!! Get ready your Velostat caps, already!

Great! And, BTW, welcome to MSFN, Matt! Constructive attitudes lead to awesome results. Amen to that! ===== Now, for the Pale Moon fork, I wish to renew my initial proposal of the "Bright Night" name, whereas, for the Basilisk/Serpent fork (my favorite and the one I use every day), let me suggest: Jörmungandr!

True enough. Moreover, you're right in that, at least in Serpent, there's plenty of references to Pale Moon / Basilisk / Moonchild Productions / Binary Outcast / Matt A. Tobin / etc. in the "About Serpent" window and links therein, which must be rectified as requested. I don't use the other browsers, so I cannot be sure, but I presume the same applies to them, too. I'm sure @roytam1'll fix this to everybody's satisfaction, since there's no reason not to. My 2¢ only, of course.

Try this. Don't delay.

+1

The java directory structure must be in C:\Program Files\Java\jre1.8.0_152 (so there'll be the bin and lib subdirectories inside this one) and the executables must be located in C:\Program Files\Java\jre1.8.0_152\bin *and* a copy of the 202 cpl in system32. If so the reg attached below should work (but do read, it just in case, before merging it): Jre_8u202_Mod152.zip

Windows NT 3.1 was released on July 27, 1993... almost 26 years ago. NetBSD and FreeBSD are from the same year, while Linux is from 1991, mind you.

Don't hold your breath, though.

The default in XP mode is to have just one core in the virtual CPU. As such it behaves as a sigle core CPU and KB4486463 installs but does not substitute %windir%\system32\ntoskrnl.exe. It's OK! Hide it, and forget about it.

Yes. Substitute Windows 10 by TrueOS x64.

They are correct for single-core. You should hide the update if offered again.

Yes. I'd expect that. @mixit is right: delay-load linkages may not be a problem even when unsatisfied, because the software may have been written to test for presence before actually calling them. Dependency Walker cannot decide whether this is the case or not, but when the same unsatisfied delay-load linkage exsts in a previous version, known to cause no problems, then it's a safe bet it's no problem in a later version. So, checking a previous version fot it, when a suspect unsatisfied delay-load linkage exsts in a new update is the way to go, as he just demonstrated. all right you're right, it still works after updating here.