Leaderboard

Works OK here in NM28 32-bit (Vista SP2 x86); direct link for KB4092483 32-bit: http://download.windowsupdate.com/d/msdownload/update/software/secu/2018/09/mso-x-none_852c8f4c16a121d662c070374553e1ffe159779a.cab

works for the Internet Explorer-specific version of Update Catalog. So they've managed not only to screw up searching by hardware identificators (which is far useful for locating newest WHQL'd drivers) and how the results in general were less accurate, but also they screwed up searching at all for the non-IE version. nice, EDIT: seems to be back now, for non-IE browsers, and they have finally unf***ed searching by HWIDs.

All updates are OK, except the ones that replace MSO.DLL with an incompatible version. IMO the easiest way to make sure you get the latest (and now last) usable versions of all the Office 2010 files is to install all the most recent updates and then simply replace the MSO.DLL file with the one from KB4092483, which contains the last version which works on XP systems. Remember that updates which replace MSO.DLL can replace other files as well, but you only need to replace that one file to get the system working again.

There's little more behind dependentlibs.list than the mere check for listed DLLs. Arbitrary DLL may be dropped in the application directory and have its name added to dependentlibs.list before xul.dll and the listed DLL will be loaded at application startup. The reoccurring pattern is that said .list file lists non-system DLLs that xul.dll depends on, with xul.dll being the last on the list. I don't see a good reason for existence of dependentlibs.list and the logic behind it. When it comes to actual dependencies of xul.dll, they are resolved by the operating system when the library is loaded. Why the extra code to load them explicitly?

I am going to come out and show what I referred to as project SUBJECT CLASSIFIED in the past to some people: People are starting to ask for newer programs to run on 7 and application compatibility is starting to collapse for the OS as well (though many of those incompatibilities remain truly forced for now). So a week ago I decided that it was about time to start a proactive response to the impeding avalanche (July 2021 or whenever Chromium is supposed to kill 7 support, and possibly .NET 5.0). In the four months working on Vista I learned many things which I will apply to this project. I had no idea what I was doing when I started this in mid-June, though after five days I realized what was necessary to get new applications running! Will it be difficult for me to manage the extension of four separate operating systems? Well, I think we will be back down to two in a few years as x86 slowly dies and the sources of our collective grief go x64 which is a considerably easier platform to expand on. Qihoo 360 is definitely ready...

WinNTSetup 4.2.5 - added ini option NoHiberBoot - added ini option KeepISOAlive ! Microsoft removed Assessment and Deployment Kit 8.0 from their servers If you still have these files and want to run WinNTSetup on XP/Vista overwrite the following: Tools\x??\bcdboot.exe Tools\x??\bcdedit.exe Tools\x??\bootsect.exe Tools\x??\wimgapi.old

Windows 10 is the worst thing that Microsoft has ever done