dencorso

You can try to do it right away... the way to do it already exists: WinXP x86 SP2 or SP3 also boot in EFI32 - tested only on VMware Workstation 8. EFI loader (files) are from Longhorn Vista x86 6.0.5219.0. Information on how to do this can be found from this post: https://www.betaarchive.com/forum/viewtopic.php?p=433345#p433345 Source: http://reboot.pro/topic/21851-boot-winxp-x64-in-efi-on-thinkpad-x220/

Wasn't there a way to cause IE8 to use Chromium rendering engine? If so, wouldn't it perhaps work with Eudora?

Tell him he should be able to login again, now. If not, then PM me and let me know.

That's what I meant: someone who gets pleasure from their own pointless unnecessary suffering.

1.) Huh? You've never said you'd decided to cancel it! Don't you think you owe your numerous potential user base some consideration, let alone, at least, a less meager modicum of information? 2.) It's not been that long ago we talked about you creating something to patch the relevant files in-memory, maybe even using the native API... if you were about to cancel your project, why have you had people lose their time considering your potencial problem?

No. Windows 10 is a mess. Version 1809 is just the tip of the crapberg.

Get the Extended Kernel32 to release quality 1st, before engaging in an even more difficult project. Your dispersiveness undermines your credibility. With all due respect.

+1

Can you elaborate? I don't seem to have SWMSM installed in the system. What filename does it hide under?

Both Primetime and Shockwave work perfectly with UXP 52. Adobe Primetime requires manual installation and media.ffvpx.enabled = false. I posted about that on the Adobe Primetime pinned thread, some time ago. As for Adobe Shockwave, it just works. Same applies to Silverlight.

Nagging won't make things any faster, but does annoy.

Sure. The ones I use are depicted below. I also have the Java Next Generation Plug-In but it's on "Ask to Activate" mode. The ones shown above are in "Always Activate" mode.

In your opinion. Maybe on your system, for some reason, involving other software. I do browse for many days without ever closing or minimizing UXP 52 and it has very little effect on my system's total memory usage. Now, if one keeps some pages that insist on updating continuously even when open in tabs on the background (typically newspapers in my case), then one may get in trouble... but that's bad page programming, not any browser's but IMO.

Why? As an exercise in masochism?

Obviously, it does equally work for ATI, too. Why is it nobody ever searches the forums?

I told you that once, way back when... the most perfect (and difficult) way to do it is to locate kernel32, ntdll, hal and if necessary ntkrnl in-memory and hook 'em there. It has the great advantage the simply by removing the module responsible for doing that restores the system to a plain-vanilla state. This should be done early during boot, preferably at the end of the 1st phase or (more difficult still) at the beginning of the 2nd phase. To do so requires much more savy programming than I ever attained, but I'm positive it's possible to be done. If you follow Alex Ionescu's twitter, you're sure to find some people able to do that. He himself obvously is one of those, but I doubt he'd be much interested in that, now that he became world-famous. But his twitter is a good place to meet others of like ability, and make some interesting friends. Sorry I cannot myself be of more help.

Ignorance is bliss...

In your opinion.

It'll be utterly irrelevant. It already is utterly irrelevant. It'll remain there, since it's unremovable, but will be used less and less.

@bigmuscle's simply applying the (Alice in Wonderland's) Code of the Queen of Hearts: whatever the misdeed...

In your opinion.

I understood @someguy25 wanted to update Office 2007 fully before moving on to IE8, of course. If so: Download manually and install manually the Office 2007 updates in reverse order (= from the one released more recently to the oldes released one). Since some supersede others, some of the older updates will refuse to install, because a later update is present, which is normal. Eventually, after all Office 2007 updates are installed, wu/mu won't take forever anymore. I know: it sucks... but life is like that. Else, do read this post.

That means your shortcut had not the "Start in:" directory pointed to the same directory inside which "Target:" is.