Leaderboard

I read the thread (Beware of Office 2010 Updates!) And understood that you are trying to decrypt or encrypt Word files in XP. And that's broken with the two TLS updates for POS. If that is the correct short summary (otherwise please correct) then I think your conclusion is wrong. From my point of view, current TLS support is more important than working with Word encryption under XP POS. Or why do you have to rely on XP + Word? The subject of "encryption" and "data security" using XP seems a bit strange anyway - XP is becoming more and more insecure. And then to leave out the few updates with new and improved encryptions just because Word has a problem with them ... Hmmmm ... Then it's better to use a current OS + Word.

It seems like this could help achieve my newest goal: https://github.com/Mattiwatti/EfiGuard This disables PatchGuard and Driver Signing Enforcement, but only with UEFI. And apparently W7 can run with Secure Boot on with this applied (possibly Vista as well?). But, what about us Tandy 1000 users with our obsolete BIOS and MBR (oh, and don't forget Tandy graphics. Aero looks exceptionally awesome with those)? This guide to patching should suffice: http://web.archive.org/web/20170812173323/fyyre.ru/vault/bootloader.txt Well, I think I saved myself a lot of time searching through ntoskrnl in IDA and seriously advanced the cause of Windows Vista. Great thanks to those who also want to control the OS, as opposed to having the OS control you.

@Sonic There is no such feature, virtual disk expect mounted iso will still be available after winntsetup closed. @wimb Thanks for the report, seems MS has changed that in wimgapi.dll. Will be fixed in next version.

oh, I haven't finished it yet (about ~95% done - and when I had access to the test machine I had many other things to deal with, which is why progress has been slow lately). And I'm first doing it with a base SP2 file because my test machine has serious problems with Windows Update that cause updates to fail most of the time. If it works there, then I'll adapt it to the extended kernel's kernel32. I only have a few select files. @burd has the entire patch though.

Many things were tried today. Attempts to expand the import table to accommodate ntext.dll would require all import calls to be refactored. In almost all 1250 functions. Tried implementing BWC's version of one K32* function (which doesn't directly refer to any import calls). That tripped ntdll in part of a function (LdrLoadAlternateResourceModule) responsible for MUI support. I even tried forwarding some K32* functions to their predecessors in psapi.dll, which is what ExtendedXP/One-Core-API do. Result: same as above. The overly simplified Windows 8.1 version of the function? BEX. There is one thing left, which is to call ntext and its functions as offsets with the W7 versions of the functions. If it doesn't work, then this part of the project is on hold until I can think of another way to workaround these difficult limitations. Or I'll just hang around other OSes that aren't crippled to the casual modder like Windows 2000 or XP x64.

Lavfilters for XP 0.74.1 (Fork of the latest stable release): https://github.com/3dyd/LAVFiltersXP/releases Haven't tested it on XP but it seems to run fine on ME + KernelEx with Zoom Player so should be OK on its intended target system too I guess.

A workaround was deployed by hcaptcha.com shortly after I brought it up on Pale Moon forum. Since then, baseline JIT compiler, which is related to the problem, is disabled by default on 32-bit builds.

I sure do miss my window borders. Don't get me wrong, I love translucency, but to me the biggest improvement I've felt from Big Muscle's software is to be able to create compositing resources that include a visible border. There is no substitute for visually finding the window border for resizing, etc. I can't tell you how many times I've been frustrated by trying to grab the corner, no, inside the corner, no just outside the corner, only to have a window underneath jump up unexpectedly or something. -Noel

Big thanks to @daniel_k for discovering this method. Tools you'll need: A copy of Windows 8 Embedded Standard (MS is gracious enough to provide us with a download link: https://www.microsoft.com/en-us/download/details.aspx?id=37019) 7-Zip to make it easier to copy files from inside the install.wim This tutorial applies to both AMD64 and X86. Download all 3 parts of Standard_8_64Bit_Bootable_IBW if using 64 bit, or all 2 parts if using 32 bits, and open part 1 to extract the ISO. After this you should have Standard_8_64Bit_Bootable_IBW.iso or Standard_8_32Bit_Bootable_IBW.iso Open the ISO with 7-Zip and navigate to "sources/install.wim". Right click on the install.wim and select "Open inside". Inside the install.wim, go to "Windows/servicing/Packages" Here's where it differs for both architectures. For 64 bit copy the following files into a folder in your computer: For 32 bit copy the following files: Next go to "Windows/winsxs/Manifests" and... For 64 bit copy these files into the same folder you extracted the previous ones: For 32 bit copy these files: Now here's the interesting part. Open command prompt with Admin privileges and run: If using 64 bit: dism /online /add-package /packagepath:<path to folder>\Microsoft-Windows-Embedded-SKU-Foundation-Package~31bf3856ad364e35~amd64~~6.2.9200.16384.mum If using 32 bit: dism /online /add-package /packagepath:<path to folder>\Microsoft-Windows-Embedded-SKU-Foundation-Package~31bf3856ad364e35~x86~~6.2.9200.16384.mum Reboot and install IE11 like you normally would. This time it will finish the installation and prompt you to reboot. After that, IE11 will be fully operational on your machine! Here's some pics of the results: