Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 12/02/2018 in all areas

  1. I didn't realize that people would find out so soon about my father's passing. I wanted to express my appreciation of the impact he has had for many of you with all his work on Windows. I got to hear about it for years over meals and I never realized how many people found value in his patches. It is a busy time right now but I did want to clear the air regarding the patches. I would like them to continue to be distributed, for his work to be remembered and to be beneficial to others. So, please, freely distribute what you may have in terms of the work my dad did. When things are more settled, I will see what I can do regarding anything missing he might have had available and whatever relevant material there might be that someone could use to further pursue his work.
    32 points
  2. To prevent user confusion, I strongly recommend disregarding the tutorials and contacting me directly instead about the extended kernel. The original post was removed as it was continuing to confuse users. There will be further discussion about the evolution of the extended kernel in the coming pages.
    27 points
  3. NTOSKRNL Emu_Extender Library of missing functions for Windows XP/2003/Vista/7 NTOSKRNL.EXE Project is intended to help in porting drivers from Windows 7/8/8.1/10 for work with Windows XP/2003/Vista/7 How-To: Compile sources to make ntoskrn8.sys Make corrections to target driver XXX.sys so that it loads ntoskrn8.sys instead of the original ntoskrnl.exe If XXX.sys is driver made for Windows 8, change security_cookie to random value, security_cookie is constant 0x4EE640BB(x32) / 0x32A2DF2D992B(x64) inside file, change only first match ! Place ntoskrn8.sys to X:/Windows/system32/drivers/ folder Compiling: 1) Install Windows 7 DDK v7.1.0 (download from Microsoft site) 1a) Original DDK header files has mistake with definintion of MmAllocateContiguousMemorySpecifyCacheNode, apply fix to two files \WinDDK\Win7\inc\ddk\ntddk.h and \WinDDK\Win7\inc\ddk\wdm.h: replace: #if (NTDDI_VERSION >= NTDDI_WIN2K) typedef ULONG NODE_REQUIREMENT; to: #if (NTDDI_VERSION >= NTDDI_VISTA) typedef ULONG NODE_REQUIREMENT; 2) Download project files to any local folder git clone https://github.com/MovAX0xDEAD/NTOSKRNL_Emu 3) Choose Target OS (XP, 2003, Vista or WIndows 7) for which OS Emu_Extender will be compiled. Keep in mind that depending on the target operating system the way of exporting the functions changes, if a function already exists in the kernel it will be simply redirected without injecting emulation code 4) Run shell: "Start Menu\Programs\Windows Driver Kits\Win7 7600.16385.1\Build Environments\Windows XXX\YYY Free Build Environment" (XXX - target OS, YYY - target CPU) 5) In shell change current directory to local project folder 6) Use shell command BLD to compile project 7) Compiled ntoskrn8.sys will be in ntoskrn8/objfre_XXX_x86/YYY folder STORPORT Windows 7 Emu_Extender This is Library of missing functions for Windows 7' STORPORT.SYS v6.1.7601.23403 to emulate Windows 8' STORPORT.SYS How-To: Compile ntoskrnl Emu_Extender Place storpor8.sys to X:/Windows/system32/drivers/ folder Make corrections to target xxx.sys so that it loads storpor8.sys instead of the original storport.sys Place backported storport.sys from Windows 7 to X:/Windows/system32/drivers/ folder Ported drivers: Windows 7's WDF 1.11 for Windows XP/2003 x32 Last version for Windows XP/2003 is 1.9, but possible to backport 1.11 version: 1) Get files from Windows 7 Updates (KB3125574): WDF01000.SYS v 1.11.9200.20755 WdfLdr.sys v 1.11.9200.16384 2) In WDF01000.SYS replace string ntoskrnl.exe to ntoskrn8.sys in import section 3) Recalc checksum If need coexist with original WDF1.9 drivers: 4) Rename WDF01000.SYS->WDF01_W8.SYS, WdfLdr.sys->WdfLdr8.sys 5) In WDF01_W8.SYS replace string WdfLdr.sys to WdfLdr8.sys in import section 6) In WdfLdr8.sys replace unicode string \Registry\Machine\System\CurrentControlSet\Services\Wdf%02d000 to \Registry\Machine\System\CurrentControlSet\Services\Wdf%02d_w8 7) In WdfLdr8.sys replace hex pattern F6 78 1B F6 to F6 EB 1B F6 (x32), ** ** to ** ** (x64) 8) In target driver XXX.sys replace string "WdfLdr.sys" to "WdfLdr8.sys" in import section 9) In .INF of ported driver add creating new service: AddService=WDF01_W8,, WDF.AddService .... [WDF.AddService] DisplayName = "Windows Driver Framework v1.11 for XP/2003" ServiceType = 1 ; SERVICE_KERNEL_DRIVER StartType = 3 ; SERVICE_DEMAND_START ErrorControl = 1 ; SERVICE_ERROR_NORMAL ServiceBinary = %12%\WDF01_W8.SYS LoadOrderGroup = Base Recalc checksum of all edited *.sys Windows 7's Storport.sys for Windows XP x32 Storport was released since Windows 2003, but possible to backport Windows 7 version: 1) Get files from Windows 7 Updates (KB3125574): storport.sys v 6.1.7600.23403 2) In storport.sys replace string ntoskrnl.exe to ntoskrn8.sys in import section, now storport.sys will import all kernel functions only from Emu_Extender 3) Storport uses MSI interrupts, need to force use only legacy/compatible interrupts x32 - replace hex pattern 8B 8E 3C 01 00 00 to B9 00 00 00 00 90 (mov ecx, [esi+13Ch] -> mov ecx, 0) x64 - replace hex pattern 8B 83 C0 01 00 00 to B8 00 00 00 00 90 (mov eax, [rbx+1C0h] -> mov eax, 0) 4) Recalc checksum Windows 7's NVMe driver for Windows XP x32 1) Get files from Windows 7 Updates (KB3125574): stornvme.sys v 6.1.7600.23403 2) MS Win7 NVMe driver require Win7 Storport.sys, use backported one Windows 8's USB3 driver for Windows XP x32 1) Get required files from Windows 8 (KB4534283/4556840, KB2984005, RTM ISO): ucx01000.sys v6.2.9200.22453 usbhub3.sys v6.2.9200.21180 usbxhci.sys v6.2.9200.22099 wpprecorder.sys v6.2.9200.16384 usbd.sys v6.2.9200.20761 from Vista Beta/Longhorn 5456.5: ksecdd.sys v6.0.5456.5 2) In files ucx01000.sys, usbhub3.sys, usbxhci.sys, wpprecorder.sys, usbd.sys change security_cookie to random value 3) In files ucx01000.sys, usbhub3.sys, usbxhci.sys, ksecdd.sys replace string name "ntoskrnl.exe" to "ntoskrn8.sys' in import section 4) Rename ksecdd.sys->ksecd8.sys, usbd.sys->usbd_w8.sys 5) In usbhub3.sys replace string name "ksecdd.sys" to "ksecd8.sys' in import section 6) In usbhub3.sys replace string name "usbd.sys" to "usbd_w8.sys' in import section, 7) recalc checksum Windows 8’s STORAHCI driver for Windows XP x32 STORAHCI driver requires storport.sys from Windows 8, but possible to use storport.sys v6.1.7601.23403 from Windows 7 Storport.sys from Windows 7 more compatible with Windows XP/2003 because it still call required PoStartNextPowerIrp when processing power IRPs. Microsoft removed calls to PoStartNextPowerIrp in Windows 8's storport.sys, without this call Windows XP/2003 kernel cannot finish current power IRP and start next IRP => it generate BSOD (0x0000009F). Also storport.sys from Windows 7 has compatibility mode to allow old XP/2003 kernels write crashdumps through storport based disk drivers. In storport.sys from Windows 8 compatibility mode was removed, writing crashdumps possible only with new kernels. Take attention: Windows 8's STORAHCI + Windows 7's STORPORT may have significal performance drop and high CPU usage, there is no fix yet 1) Get files from Windows 8 (RTM ISO): storahci.sys v 6.2.9200.16384 2) In storahci.sys replace string storport.sys to ntoskrn8.sys in import section 3) Storahci.sys was compiled with Windows 8 DDK's storport.h and writes values to new fields of _PORT_CONFIGURATION_INFORMATION struct, these fields not exist in Windows 7's storport.sys. Need to skip these writes to avoid damaging other structures in memory x32: Replace hex pattern 83 A6 C8 00 00 00 00 to 90 90 90 90 90 90 90 (and dword ptr [esi+0C8h], 0 -> nop) Replace hex pattern 83 8E CC 00 00 00 03 to 90 90 90 90 90 90 90 (or dword ptr [esi+0CCh], 3 -> nop) x64:Replace hex pattern 44 89 B7 D8 00 00 00 to 90 90 90 90 90 90 90 (mov [rdi+0D8h], r14d -> nop) Replace hex pattern 83 8F DC 00 00 00 03 to 90 90 90 90 90 90 90 (or dword ptr [rdi+0DCh], 3 -> nop) If you want compile storahci from sources (from Windows 8 DDK Samples), comment two lines ConfigInfo->BusResetHoldTime = 0; ConfigInfo->FeatureSupport |= STOR_ADAPTER_FEATURE_STOP_UNIT_DURING_POWER_DOWN; 4) In storahci.sys change security_cookie to random value 5) Recalc checksum Windows 7’s MSAHCI driver for Windows XP x32 1) Get files from Windows 7 Updates(KB3125574): atapi.sys v 6.1.7600.23403 ataport.sys v 6.1.7600.23403 msahci.sys v 6.1.7600.23403 pciidex.sys v 6.1.7600.23403 2) In ataport.sys, pciidex.sys replace string ntoskrnl.exe to ntoskrn8.sys in import section 3) Pciidex.sys uses MS Internal/Undocumented HalDispatchTable way to call functions from Kernel/HAL, for Windows XP/2003 need to use compatible variant: x32: Replace hex pattern FF 50 3C to FF 50 40 same in asm code: mov eax, ds:HalDispatchTable ... call dword ptr [eax+3Ch] => call dword ptr [eax+40h] x64: Replace hex pattern FF 50 78 to EB 2A 90 Replace hex pattern at offset +2Ch: CC CC CC CC CC CC CC CC to FF 90 80 00 00 00 EB CF, same in asm code: mov rax, cs:HalDispatchTable ... call qword ptr [rax+78h] => jmp patch orig: mov r10d, eax patch: call qword ptr [eax+80h] jmp orig 4) Recalc checksum 5) MSHDC.INF from Windows 7 conflict with original mshdc.inf from Windows XP/2003. msahci.sys enumerates IDE/SATA channels as "Internal_IDE_Channel" and compatible ID is "*PNP0600". Original mshdc.inf from Windows XP/2003 for compatible Device ID "*PNP0600" will install wrong "Standard IDE/ESDI Hard Disk Controller" driver Intel RSTe (Enterprise/Premium) AHCI/RAID driver 4.7.0.1098 for Windows XP/2003 Intel RST AHCI/RAID drivers (any version, last compatible is 16.8.3) for Windows XP/2003 These drivers require storport.sys from Windows 7, use backported version. 1) In file iaStorA.sys/iaStorAC.sys/iaStorAVC.sys replace string “ntoskrnl.exe” to “ntoskrn8.sys” in import section (do not change second string “NTOSKRNL.exe”) now these *.sys will import kernel functions only from Emu_Extender 3) Recalc checksum Implemented Func List v60: _chkstk _i64toa_s _i64tow_s _itoa_s _itow_s _ltoa_s _ltow_s _makepath_s _snprintf_s _snscanf_s _snwprintf_s _snwscanf_s _splitpath_s _strnset_s _strset_s _strtoui64 _swprintf _ui64toa_s _ui64tow_s _ultoa_s _ultow_s _vsnprintf_s _vsnwprintf_s _vswprintf _wcsnset_s _wcsset_s _wmakepath_s _wsplitpath_s _wtoi _wtol DbgkLkmdRegisterCallback EmClientQueryRuleState EtwActivityIdControl EtwEventEnabled EtwProviderEnabled EtwRegister EtwRegisterClassicProvider EtwUnregister EtwWrite EtwWriteString EtwWriteTransfer ExAcquireRundownProtectionCacheAware ExAcquireRundownProtectionCacheAwareEx ExAllocateCacheAwareRundownProtection ExDeleteLookasideListEx ExEnterCriticalRegionAndAcquireFastMutexUnsafe ExEnterCriticalRegionAndAcquireResourceExclusive ExEnterCriticalRegionAndAcquireResourceShared ExEnterPriorityRegionAndAcquireResourceExclusive ExEnterPriorityRegionAndAcquireResourceShared ExFreeCacheAwareRundownProtection ExfReleasePushLockShared ExfTryToWakePushLock ExGetFirmwareEnvironmentVariable ExInitializeLookasideListEx ExInitializeRundownProtectionCacheAware ExReInitializeRundownProtectionCacheAware ExReleaseFastMutexUnsafeAndLeaveCriticalRegion ExReleaseResourceAndLeaveCriticalRegion ExReleaseResourceAndLeavePriorityRegion ExReleaseRundownProtectionCacheAware ExReleaseRundownProtectionCacheAwareEx ExRundownCompletedCacheAware ExSetFirmwareEnvironmentVariable ExSizeOfRundownProtectionCacheAware ExWaitForRundownProtectionReleaseCacheAware IoAllocateSfioStreamIdentifier IoConnectInterruptEx IoDisconnectInterruptEx IoFreeSfioStreamIdentifier IoGetActivityIdIrp IoGetAffinityInterrupt IoGetDevicePropertyData IoGetIoPriorityHint IoGetSfioStreamIdentifier IoInitializeWorkItem IoQueueWorkItemEx IoSetActivityIdIrp IoSetDevicePropertyData IoSizeofWorkItem IoUninitializeWorkItem IoUnregisterPlugPlayNotificationEx KdRefreshDebuggerNotPresent KeAcquireGuardedMutex KeAcquireGuardedMutexUnsafe KeAlertThread KeAreAllApcsDisabled KeEnterGuardedRegion KeExpandKernelStackAndCallout KeGetCurrentNodeNumber KeGetCurrentProcessorNumberEx KeGetProcessorIndexFromNumber KeGetProcessorNumberFromIndex KeInitializeGuardedMutex KeInvalidateAllCaches KeInvalidateRangeAllCaches KeLeaveGuardedRegion KeQueryActiveGroupCount KeQueryActiveProcessorCount KeQueryActiveProcessorCountEx KeQueryDpcWatchdogInformation KeQueryGroupAffinity KeQueryHighestNodeNumber KeQueryLogicalProcessorRelationship KeQueryMaximumGroupCount KeQueryMaximumProcessorCount KeQueryMaximumProcessorCountEx KeQueryNodeActiveAffinity KeReleaseGuardedMutex KeReleaseGuardedMutexUnsafe KeRevertToUserAffinityThreadEx KeRevertToUserGroupAffinityThread KeSetActualBasePriorityThread KeSetCoalescableTimer KeSetSystemAffinityThreadEx KeSetSystemGroupAffinityThread KeSetTargetProcessorDpcEx KeTestAlertThread KeTryToAcquireGuardedMutex LdrResFindResource LdrResFindResourceDirectory LpcReplyWaitReplyPort LpcRequestWaitReplyPortEx LpcSendWaitReceivePort memcpy_s memmove_s MmAllocateContiguousMemorySpecifyCacheNode MmAllocateContiguousNodeMemory ObDeleteCapturedInsertInfo ObfDereferenceObjectWithTag ObfReferenceObjectWithTag ObGetObjectType ObQueryNameInfo PcwAddInstance PcwCloseInstance PcwCreateInstance PcwRegister PcwUnregister PoDisableSleepStates PoEndDeviceBusy PoGetSystemWake PoReenableSleepStates PoRegisterPowerSettingCallback PoSetDeviceBusyEx PoSetSystemWake PoStartDeviceBusy PoUnregisterPowerSettingCallback PoUserShutdownInitiated PsAcquireProcessExitSynchronization PsEnterPriorityRegion PsGetCurrentProcessWin32Process PsGetCurrentThreadProcess PsGetCurrentThreadProcessId PsGetCurrentThreadTeb PsGetCurrentThreadWin32Thread PsGetCurrentThreadWin32ThreadAndEnterCriticalRegion PsGetProcessSessionIdEx PsIsProtectedProcess PsIsSystemProcess PsLeavePriorityRegion PsReleaseProcessExitSynchronization PsSetCreateProcessNotifyRoutineEx RtlCheckPortableOperatingSystem RtlGetIntegerAtom RtlGetThreadLangIdByIndex RtlIsNtDdiVersionAvailable RtlQueryElevationFlags RtlQueryRegistryValuesEx RtlSetPortableOperatingSystem SeReportSecurityEventWithSubCategory SeSetAuditParameter SeSetAuthorizationCallbacks sprintf_s sscanf_s strcat_s strcpy_s strncat_s strncpy_s strnlen strtok_s swprintf_s swscanf_s vsprintf_s vswprintf_s wcscat_s wcscpy_s wcsncat_s wcsncpy_s wcsnlen wcstoul ZwAllocateLocallyUniqueId ZwAlpcConnectPort ZwAlpcSendWaitReceivePort ZwQueryLicenseValue ZwQueryVirtualMemory Download Sources https://github.com/MovAX0xDEAD/NTOSKRNL_Emu
    22 points
  4. Here is the future of Chromium on Windows 7: https://github.com/win32ss/supermium I have been closely tracking the many changes made to Chromium since November 2022, made with the intent of dropping support for Windows 7 and 8.x. As of version 111, it became very difficult to keep the newest versions running on Vista with the extended kernel; shared memory allocation changes made it impossible to do so as subtle changes to the API (which were done in kernel mode) prevented stable operation of the browsers. So I decided to build my own Chromium. I discovered that a further change was made to the shared memory allocation which broke it even further; the successor to mojo, IPCZ, was forced on by default. It only works properly with Windows 8.1+'s shared memory API. I disabled IPCZ for pre-8.1 and this made the sandbox work again on Vista and 7. Perhaps I will see exactly why IPCZ is broken (from the Windows API level) and try to fix it for the next release. The only win32 API link I can find is CreateFileMappingW, which I need to test with an IPCZ-enabled build on both 8 and 8.1 to see what makes it fail.
    21 points
  5. ProxHTTPSProxy and HTTPSProxy in Windows XP for future use 0. Table of Contents 0. Table of Contents 1. Introduction 2. Purpose of ProxHTTPSProxy and HTTPSProxy 3. Area of application 4. The TLS protocols and their cipher suites 5. Certificates - CA and Root Certificates 5.1. The CA certficate of ProxHTTPSProxy 5.2. The Root Certificates of Windows XP 6. The TLS 1.2 proxies ProxHTTPSProxy and HTTPSProxy 6.1. Prerequisites 6.1.1. Detailed information 6.2. Installation 6.3. Configuration 6.3.1. Configuration of ProxHTTPSProxy 6.3.2. Configuration of HTTPSProxy 6.3.3. Configuration of these proxies to access the MU website successfully nowadays 6.4. Usage 6.4.1. Usage of ProxHTTPSProxy 6.4.2. Usage of HTTPSProxy 6.5. Maintenance of ProxHTTPSProxy and HTTPSProxy for future use 7. The TLS 1.2 proxy ProxHTTPSProxy's PopMenu 3V1 7.1. Prerequisites 7.2. Purpose and components of ProxHTTPSProxy's PopMenu 3V1 7.3. Features of ProxHTTPSProxy's PopMenu 3V1 7.4. Changelog of ProxHTTPSProxy's PopMenu 3V1: 7.5. Installation and configuration of ProxHTTPSProxy's PopMenu 3V1 7.6. Tranferring all settings of an existing ProxHTTPSProxy's installation 7.7. Usage of ProxHTTPSProxy's PopMenu 3V1 8. The TLS 1.3 proxy ProxyMII 8.1. Prerequisites 8.2. General information about ProxyMII 8.3. Specific information about the different ProxyMII releases 8.3.1 ProxyMII (20220717) 8.3.2 ProxyMII (20230813) 8.4. How to set up and use the TLS 1.3 proxy ProxyMII 9. The TLS 1.3 proxy ProxHTTPSProxy's PopMenu TLS 1.3 9.1. Prerequisites 9.2. General information about ProxHTTPSProxy's PopMenu TLS 1.3 9.3. ProxHTTPSProxy's PopMenu TLS 1.3 3V3 9.3.1. Features of ProxHTTPSProxy's PopMenu TLS 1.3 3V3 9.3.2. Changelog of ProxHTTPSProxy's PopMenu TLS 1.3 3V3 9.3.3. Installation and start of ProxHTTPSProxy's PopMenu TLS 1.3 3V3 10. Versions 10.1. Versions of the TLS 1.2 proxies ProxHTTPSProxy, HTTPSProxy, and ProxHTTPSProxy's PopMenu 10.2. Versions of the TLS 1.3 proxies ProxyMII and ProxHTTPSProxy's PopMenu TLS 1.3 11. Downloads 11.1. Archived Downloads {obsolete}: 11.2. Latest Downloads 11.2.1. Downloads related to the TLS 1.2 proxies 11.2.1.1. Downloads related to ProxHTTPSProxy 11.2.1.2. Downloads related to HTTPSProxy 11.2.2. Downloads related to the TLS 1.3 proxies 11.2.3. Downloads related to cacert.pem Certificate Update 11.2.4. Downloads related to Root Certificate Updates 12. Update notifications 13. Conclusion 14. Disclaimer 1. Introduction: The idea of this thread is to provide information and recent findings I've made relating to the TSL proxies ProxHTTPSProxy and HTTPSProxy. Due to the fact that I don't use other older NT based Operation Systems (OSs) except Windows XP Professional all my observations and explanations are referring to both proxies in Windows XP only. So, please do not comment off-topic in this thread! I am AstroSkipper, a member of MSFN since 2010, and was involved in restoring of access to the Microsoft Update (MU) website in Windows XP (and some other OSs). This is the thread: While restoring MU in my own Windows XP Professional system, I had to solve a lot of problems and had among other things some significant findings relating to ProxHTTPSProxy and HTTPSProxy, too. The above mentioned thread is now over 140 pages long and unfortunately very bloated. In most cases visitors or members of MSFN don't want to read that much of pages for getting information they have looked for. A lot of comments are part of conversations which no longer can be retraced or understood easily by people who weren't participated. Therefore, I wanted to make my own findings accessible to all interested people in a clear, short way. That's why I decided to make my own thread to provide some facts, tips and especially news referring to these proxies. It is an unfortunate circumstance that the creators of ProxHTTPSProxy and HTTPSProxy, @heinoganda and @Thomas S., haven't been here for a long time and no further development of these proxies has been made the last years. Of course, we thank both creators explicitly for these outstanding proxies, we are very glad to have them, but they have to be used as they are. For this reason, we have to ask ourselves whether they'll continue doing their job in the future or not. But maybe some of you don't really know what actually their job is. 2. Purpose of ProxHTTPSProxy and HTTPSProxy: Originally, ProxHTTPSProxy was created for Proxomitron as an SSL Helper Program. Proximotron is a local HTTP web-filtering proxy. Here are two links about Proxomitron: http://www.buerschgens.de/Prox/index.html (German website, use Google Translator if necessary) and https://msfn.org/board/topic/183295-web-browser-proxomitron-reborn-ptrongui-a-how-to-guide/. This is a quotation from a post of the developer called "whenever" who had made ProxHTTPSProxy originally: Source link: https://prxbx.com/forums/showthread.php?tid=1618. Here is an image to show how ProxHTTPSProxy works: ProxHTTPSProxy and HTTPSProxy were created by our members mentioned above to provide modern nag-free HTTPS connections for an HTTP proxy. The main purpose in Windows XP is in adding modern ciphers to HTTPS connections of the Internet Explorer (IE) to improve either its missing TLS 1.2 functionality or its rudimentary TLS 1.2 functionality last added by Microsoft after installing some relevant POSReady updates (KB4230450, KB4316682 and KB4019276). Here is a link with further information how TLS 1.1 and TLS 1.2 can be enabled in Windows XP: https://msfn.org/board/topic/178092-enable-tls-11-and-12-in-windows-xp-correctly/?do=findComment&comment=1158544. The original ciphers of IE are outdated and therefore a lot of websites can't be accessed or they don't work properly due to SSL issues. More information about these proxies you can find in the original thread: https://msfn.org/board/topic/176344-problems-accessing-certain-sites-https-aka-tls/. 3. Area of application: As already said, the main purpose of these proxies is in adding modern ciphers to HTTPS connections of IE to improve either its missing TLS 1.2 functionality or its rudimentary TLS 1.2 functionality last added by Microsoft after installing some relevant POSReady updates. Therefore, ProxHTTPSProxy or HTTPSProxy is often used in combination with IE to access websites which couldn't be called up by IE without it. Some programs use Internet Explorer's browser engine called Trident to get data from Internet, to search something or to check for updates. For example my favourite movie database program All My Movies™ checks for updates using IE engine. Without one of these proxies it will fail. Some e-mail clients like eM Client or Eudora are using IE engine too. Some browsers like 360 Extreme Explorer are able to use IE engine for surfing. Another new purpose is to access Microsoft Update to look for updates. As I mentioned above I was involved in restoring of access to the Microsoft Update (MU) website in Windows XP (and some other OSs), and we were successful by now. If you're interested in restoring MU functionality, I've written a little guide with the title "Complete guide for restoring IE's access to WU/MU website using ProxHTTPSProxy or HTTPSProxy in Windows XP" which can be found here: This thread is about different proxies to establish secure connections to servers or, more generally, to the internet. You often read about TLS, cipher suites, and certificates here. Therefore, I disseminate here some information about these "termini technici" for those who do not know exactly what is meant by them. 4. The TLS protocols and their cipher suites If you research the term TLS on the internet, you will get a lot of information, sometimes very simply presented, sometimes very technical, more for IT experts. With this small article, which can be seen more as a summary, I try to provide a little more transparency in this stuff. Transport Layer Security, abbreviated TLS, is a protocol for the authentication and encryption of Internet connections. For this purpose, TLS is inserted as its own layer between TCP and the protocols of the application layer. Here is a linked graphic to make it more clear: The individual tasks include authentication, certification, key exchange, integrity assurance and encryption. The main tasks are to guarantee the authenticity of the contacted remote stations, in most cases a server, by means of a certificate and to encrypt the connection between the remote stations. Here is a second linked graphic to demonstrate the actions and reactions in the communication between a client and a server: The used protocol defines the basic communication for the connection and is as crucial for a secure connection as the encryption protocol itself. Due to a series of vulnerabilities, the SSL2 and SSL3 protocols must be considered a security vulnerability and should be avoided at all costs. The successor to SSL3, TLS 1.0 should also be avoided, as the protocol offers a method to downgrade an established TLS 1.0 connection to SSL3. Thus, the connection is again vulnerable to the vulnerabilities that affect SSL3. Unfortunately, its successor TLS 1.1 is also no longer up to date and should be rather avoided nowadays. For a long time, the TLS 1.2 protocol was considered secure and therefore recommended. It offers a number of improvements that should ensure the security of connections again. In general, each new SSL or TLS version has brought additional features and options, making configuration a little more confusing, implementation more error-prone and handling more tedious. Overall, the use of TLS has become more insecure. With TLS 1.3, this should change, at best. Or, this was and is the actual goal, at least. For this reason, every single function of TLS has been tested for its security benefits and risks. In the process of development and in regard to the present knowledge, some parts were removed that no longer offer security and some of which are now also considered insecure. At the same time, security was improved with new procedures. Furthermore, measures for performance optimisation and preventive hardening measures for future attacks were taken into account. TLS 1.3 breaks backwards compatibility for the first time, which unfortunately causes some problems in practice. Connections with TLS 1.3 can be interrupted either because the connection is not accepted en route or due to a defective web server. Anyway, the protocols TLS 1.2 and, above all, TLS 1.3 are recommended as secure protocols nowadays. Here is a list of typical protocols and their cipher suites used by the TLS 1.3 proxy of my current program package ProxHTTPSProxy's PopMenu TLS 1.3 3V3 as an example. It's a screenshot taken from the website https://browserleaks.com/ssl: In the screenshot above, you can see many so called cipher suites belonging to specific TLS protocols. A cipher suite is a standardised collection of cryptographic procedures (algorithms) for encryption. In the Transport Layer Security (TLS) protocol, the cipher suite specifies which algorithms are to be used to establish a secure data connection. A cipher suite is generally displayed as a long string of seemingly random information but each segment of that string contains essential information. Generally, this data string is made up of several key components: The used protocol, in most cases TLS. The key exchange algorithm dictates the manner by which symmetric keys will be exchanged such as RSA, DH, DHE, ECDH, ECDHE. The authentication algorithm dictates how server authentication and (if needed) client authentication will be carried out such as RSA, DSA, ECDSA. The bulk encryption algorithm dictates which symmetric key algorithm will be used to encrypt the actual data such as AES, 3DES, CAMELLIA. The Message Authentication Code (MAC) algorithm dictates the method the connection will use to carry out data integrity checks such as SHA, SHA256, MD5. In some cases, there is an Elliptic Curve Cryptography (ECC) which is an encryption technique that provides public-key encryption similar to RSA. While the security strength of RSA is based on very large prime numbers, ECC uses the mathematical theory of elliptic curves and achieves the same security level with much smaller keys. Here are three linked graphics to illustrate these strings with examples: 5. Certificates - CA and Root Certificates Although Windows XP was abandoned and updates of root certificates were not provided anymore by Microsoft for this OS, we still found ways to update them. And, if we want to install one of our TLS proxies, we have to install a CA certificate to get them working. In both cases, certificates are needed, and this short article is intended to shed some light on this certificate jungle with regards to our TLS proxies. 5.1. The CA certficate of ProxHTTPSProxy A certificate authority (CA) is a trusted entity that issues digital certificates. These are files that cryptographically link an entity to a public key. Certificate authorities are an important part of the Internet's Public Key Infrastructure (PKI) because they issue the Secure Sockets Layer (SSL) certificates that browsers use to authenticate content sent from web servers. All popular web browsers use web servers' SSL certificates to keep content delivered online secure. They all need to trust certificate authorities to issue certificates reliably. SSL certificates are used in conjunction with the Transport Layer Security (TLS) protocol to encrypt and authenticate data streams for the HTTPS protocol, and are therefore sometimes referred to as SSL/TLS certificates or simply TLS certificates. The first time ProxHTTPSProxy is started, it creates the keys for a certificate authority in its program directory if there is none. This file CA.crt is used for on-the-fly generation of dummy certificates for each visited website which are stored in the subfolder Certs. And, there is a second file called cacert.pem located in ProxHTTPSProxy's program directory. This file cacert.pem contains the currently valid root certificates (will be considered in more detail below) used by the proxy to verify the server connections. Since your browser won’t trust the ProxHTTPSProxy's CA certificate out of the box, you will either need to click through a TLS certificate warning on every domain, or install the CA certificate once so that it is trusted. It has to be installed in the Trusted Root Certification Authority of Windows XP and in some cases additionally in the Certificate Manager of a browser as in the cases of New Moon, Pale Moon, Firefox, and others. The Internet Explorer doesn't possess an own certificates store and uses the Trusted Root Certification Authority of Windows XP. Typically, digital certificates contain data about the entity that issued the certificate and cryptographic data to verify the identity of the entity, including the entity's public key and expiration date for the certificate, as well as the entity's name, contact information, and other information associated with the certified entity. Web servers transmit this information when a browser establishes a secure connection over HTTPS. In doing so, they send to it the certificate and the browser authenticates it using its own root certificate store. The following graphic illustrates the structure of a Certificate Authority as for example GlobalSign: SSL/TLS certificates are based on PKI as mentioned above, and there are a few key parts that need to be in place for the SSL certificate to work: A digital certificate (for example, an SSL/TLS certificate) that proves the website’s identity. A certificate authority that verifies the website and issues the digital certificate. A digital signature that proves the SSL certificate was issued by the trusted certificate authority. A public key that your browser uses to encrypt the data sent to the website. A private key that the website uses to decrypt the data sent to it. Here is another graphic to illustrate the role that a certificate authority (CA) plays in the Public Key Infrastructure (PKI): When installing such CA certificates in Windows XP manually, then there is something else to note. It can be of crucial importance whether one installs a root certificate under the account of the Current User or Local Computer. In this article a little further down, you can find more information on that. Furthermore, exiting ProxHTTPSProxy completely, deleting the old CA.cert file in ProxHTTPSProxy's program directory, and restarting ProxHTTPSProxy will result in the generation of a new CA.crt that will be valid for another ten years. In addition, the certificate bundle cacert.pem should be updated, at best regularly. You can do that with the tool cacert Updater Fixed which can be found in the download section 11.2.3. Downloads related to cacert.pem Certificate Update. This tool is also included in my program package ProxHTTPSProxy's PopMenu. And, that is the moment to note something very important. Any change to a ProxHTTPSProxy installation regarding the CA certificate or a severe system crash while one of the proxies is running in the background always requires a reset of all dummy certificates in the Certs subfolder. The word "reset" at this point means deleting all certificates that have been created in the Certs folder, manually by the user. The next time the proxy is started correctly, all necessary certificates will be created again when the corresponding websites are accessed. Here are a few screenshots of ProxHTTPSProxy's CA certificate (German edition of Windows XP, sorry!): 5.2. The Root Certificates of Windows XP In cryptography and computer security, a root certificate is a public key certificate that identifies a root certificate authority (CA). Root certificates are self-signed and form the basis of an X.509-based PKI. Either it has matched Authority Key Identifier with Subject Key Identifier, in some cases there is no Authority Key identifier, then Issuer string should match with Subject string (RFC 5280). For instance, the PKIs supporting HTTPS for secure web browsing and electronic signature schemes depend on a set of root certificates. A certificate authority can issue multiple certificates in the form of a tree structure. A root certificate is the top-most certificate of the tree, the private key which is used to "sign" other certificates. All certificates signed by the root certificate, with the "CA" field set to true, inherit the trustworthiness of the root certificate. A signature by a root certificate is somewhat analogous to "notarizing" identity in the physical world. Such a certificate is called an intermediate certificate or subordinate CA certificate. Certificates further down the tree also depend on the trustworthiness of the intermediates. The following graphic illustrates the role of a root certificate in the chain of trust: The root certificate is usually made trustworthy by some mechanism other than a certificate, such as by secure physical distribution. Root certificates are distributed in Windows XP by Microsoft and located in special certificate stores. These certificate stores may be viewed through the Certificates snap-in Certmgr.msc in the Microsoft Management Console (MMC). You can open the Certificates console focused on the Current User on a Windows XP computer by executing Certmgr.msc in the Run dialog box. Here is a screenshot of what you see running this command (German edition of Windows XP, sorry!): The root certificates of Windows XP can be updated by @heinoganda's Certificate Updater, @Thomas S.'s CAupdater, or by my self-created Root Certificate and Revoked Certificate Updaters, in all cases to the most recent ones provided by Microsoft. These updaters can be found in the download section under 11.2.4. Downloads related to Root Certificate Updates. There is no automatism for this updating. It must be done manually by the user and, if possible, regularly. @heinoganda's Certificate Updater is also included in my program package ProxHTTPSProxy's PopMenu. And now, back to our proxies. 6. The TLS 1.2 proxies ProxHTTPSProxy and HTTPSProxy 6.1. Prerequisites: A CPU with SSE2 instruction set is required to run the more recent versions of these TLS 1.2 proxies under Windows XP. 6.1.1. Detailed information: Testing system: Windows XP Professional SP3 POSReady with an AMD Athlon XP 3200+ (Thoroughbred), an old CPU providing SSE, but lacking of SSE2 instruction set. After testing of all proxies mentioned in this article, I can confirm that all @heinoganda's releases ProxHTTPSProxy REV3b, ProxHTTPSProxy REV3d, ProxHTTPSProxy REV3e and @Thomas S.'s release HTTPSPoxy in version HTTPSProxy_Launcher_v2_2018-11-06 require a CPU with SSE2 instruction set. All these proxies crashed when starting 'ProxHTTPSProxy.exe' or 'HTTPSProxy.exe'. But @whenever's release ProxHTTPSProxyMII 1.3a could be started without crashing, and after testing I can confirm this proxy is fully compatible with a CPU possessing SSE instruction set only. Therefore, this proxy can be used in such old systems, but only if absolutely necessary. For safety reasons. More detailed information below in the section 10.1. Versions of the TLS 1.2 proxies ProxHTTPSProxy, HTTPSProxy, and ProxHTTPSProxy's PopMenu. 6.2. Installation: The program packages provide documents and instructions, actually sufficient. Both proxies do not need any installation. There is no setup installer. They are fully portable with a few exceptions. The user has to edit the config file according to his needs, he should update a special certificate called 'cacert.pem' and he has to install the proxy's root certificate properly in any case. But to avoid unnecessary repetitions, I'll come back to that later in the section 6.3. Configuration. The location of their program folder can be chosen freely. For this purpose, I've created a folder "Portable" in my system partition. I have created this folder to remind me that programs inside folder Portable do not have to be uninstalled. 6.3. Configuration: The configurations of these proxies are a bit different. 6.3.1. Configuration of ProxHTTPSProxy: - Install ProxHTTPSProxy's root certificate 'CA.crt' under the Trusted Root Certification Authority manually or apply 'ProxHTTPS Cert Install.exe'. Alternatively you can use the more recent ProxHTTPSProxy Cert Installer which has been modified and updated by me. You can find it in the section 11.2.1.1. Downloads related to ProxHTTPSProxy. - Edit the config file 'config.ini' according to your needs. More detailed explanations at the end of this section. - Update the certificate 'cacert.pem' by downloading and inserting it manually (see cacert Update.txt) or automatically by applying 'cacert_Updater.exe'. Due to the circumstance that @heinoganda's original cacert Updater doesn't work anymore, I have fixed it. This "cacert Updater Fixed" can be downloaded in the section 11.2.3. Downloads related to cacert.pem Certificate Update. 6.3.2. Configuration of HTTPSProxy: - Generate a new HTTPSProxy's root certificate 'HTTPSProxyCA.crt' by opening 'HTTPSProxy.exe' and closing its window when the process is over. - Install HTTPSProxy's root certificate 'HTTPSProxyCA.crt' under the Trusted Root Certification Authority manually. Alternatively you can use the brand new HTTPSProxy Cert Installer which has been created by me. You can find it in the section 11.2.1.2. Downloads related to HTTPSProxy. - Edit the config files 'config.ini' and 'Launcher.ini' according to your needs. More detailed explanations at the end of this section. - Update the certificate 'cacert.pem' by downloading from url https://curl.se/ca/cacert.pem and inserting it manually (see Installation-Update_EN.txt) or automatically by clicking cacert.pem update in Launcher's menu. - Execute the reg file 'Inet_CurUser_ProxySettings.reg'. Both proxies have got a config file called 'config.ini'. The following parameters of the proxy can be specified there:: ProxAddr, FrontPort, BackPort, LogPort and LogLevel. Look into this file and you'll get short descriptions of these parameters. Furthermore there are special sections titled [SSL No-Verify], [BLACKLIST], [SSL Pass-Thru] and [BYPASS URL]. In these sections url addresses can be inserted letting the proxy know how to perform them. HTTPSProxy has a second config file called 'Launcher.ini'. Here you can set up the Launcher of HTTPSProxy. A short description can be read at the beginning of each file section. Here you can see HTTPSProxy's config file similar to the one of ProxHTTPSProxy: More detailed information about the parameters and sections can be found in their doc files. Both proxies can be set as system-wide proxies using the executable proxycfg.exe. Here are proxycfg's command line parameters: The command proxycfg displays the current WinHTTP proxy settings. The command proxycfg -d specifies that all HTTP and HTTPS servers should be accessed directly. Use this command if there is no proxy server. The command proxycfg -p proxy-server-list optional-bypass-list specifies one or more proxy servers, and an optional list of hosts that should be accessed directly. If a proxy server is not specified for a given protocol and that server is not in the bypass list, the -p option specifies that the server cannot be accessed at all. The command proxycfg -d -p proxy-server-list optional-bypass-list specifies one or more proxy servers, and an optional list of hosts that should be accessed directly. If a proxy server is not specified for the given protocol, the -d option specifies that the server should be accessed directly instead. The command proxycfg -u imports the Internet Explorer proxy settings of the current user. WinHTTP does not support auto-discovery and configuration script-based proxy settings. So far so good, but unfortunately that's not the whole truth. 6.3.3. Configuration of these proxies to access the MU website successfully nowadays: The MU website can be accessed only by IE, but nowadays it needs the more recent cryptographic protocol TLS 1.2. That's the reason why MU wasn't available in the past. Therefore we have to use one of these proxies to gain access. If all steps of my Complete guide for restoring IE's access to WU/MU website using ProxHTTPSProxy or HTTPSProxy in Windows XP have been performed properly, you would like to call up MU website. But in some cases problems could occur. One of them is to get a MU website with output of error code 0x80072f8f (hexadecimal notation). I had examined this error deeply and could solve it. But what does that have to do with our proxies? Of course a lot, otherwise I wouldn't have mentioned it. Here you can read my short post "Final fix of error code 0x80072f8f while accessing WU or MU website": The steps in order: Delete the old CA.cert file in ProxHTTPSProxy's program folder. Delete all certificates in ProxHTTPSProxy's certs subfolder. Update the certificate cacert.pem. Run the executable ProxHTTPSProxy.exe. A new ProxHTTPSProxy CA certificate CA.crt valid for another ten years has been generated. Import this new ProxHTTPSProxy CA certificate to Trusted Root Certification Authority but under the account local computer. And exactly here lies the problem. You have to import this certificate in a special way to ensure it is really installed in Trusted Root Certification Authority under the account local computer. Otherwise, it can happen that this certificate is installed in Trusted Root Certification Authority under the account current user. And that is definitely the cause of error code 0x80072f8f. No one had told us where this certificate has to be installed to. No hints in the doc files of both proxies. And, how can we do that? Here are the detailed steps using the Microsoft Management Console: Open console by typing mmc. Add a snap-in for certificates. Choose for local computer. Import your recently generated ProxHTTPSProxy CA certificate to Trusted Root Certification Authority. Finished. Now, we have to modify the config file. Alternatively you can use my pre-configured config files in the section 11.2.1. Downloads related to the TLS 1.2 proxies. Open the file config.ini in an editor of your choice. Add these urls under the section [SSL No-Verify]: urs.microsoft.com c.microsoft.com* *one.microsoft.com* download.windowsupdate.com cc.dcsec.uni-hannover.de fe2.ws.microsoft.com *update.microsoft.com ds.download.windowsupdate.com - Save your changes. - Finished. Of course, same procedure for HTTPSProxy with one exception: HTTPSProxy's root certificate is named HTTPSProxyCA.crt. Fixing error code 0x80072f8f leads to fixing another problem and that is the validity of Proxy's root certificate. From now on a freshly generated root certificate of ProxHTTPSProxy or HTTPSProxy valid for another ten years will be fully functional because we finally know where it exactly has to be imported to. Maybe, you understand now how important it is to configure these proxies properly. Otherwise, they wouldn't work flawlessly. In the section 11.2.1. Downloads related to the TLS 1.2 proxies, I provide separate CA Certificate Installer and Uninstaller for both proxies. They have been created by me for the people who do not dare to generate and install certificates themselves. Due to a modification made by me, these installers and uninstallers do now their job properly, i.e. the certificate installation will be definitely performed in the Trusted Root Certification Authority under the account local computer. If you asked me which kind of certificate installation you should choose, I would recommend the manual method. For security reasons only. The installers contain a pre-generated root certificate of its proxy which will be installed properly. But as a result all users of these installers will have got the same certificate unfortunately. Normally, no good. But, do we really want to spy each other? I don't think so. On the other hand, using the manual method we all will have an unique certificate without any risks. So it's up to you! 6.4. Usage: The usage of these proxies is very simple but a bit different. 6.4.1. Usage of ProxHTTPSProxy: The best way to start ProxHTTPSProxy is to execute the file ProxHTTPSProxy_PSwitch.exe. In this case, ProxHTTPSProxy will set up itself automatically and delete its settings when closing. You can check the settings of ProxHTTPSProxy in Internet Options of IE. Here is a screeshot of ProxHTTPSProxy's program window: 6.4.2. Usage of HTTPSProxy: The way to start HTTPSProxy is a bit different. For starting it, you have to simply drag the executable HTTPSProxy.exe onto a second executable Launcher.exe by drag & drop and a new system tray icon appears. Via this icon, all available options of HTTPSProxy's Launcher are accessible. There are a lot of options: HTTPSProxy exit, HTTPSProxy restart, HTTPSProxy show, HTTPSProxy hide, HTTPSProxy launch with Windows, config.ini edit, cacert.pem update, HTTPSProxy enabled - settings - log, Update Windows root CAs, Launcher.ini edit and so on. Here are some screenshots of HTTPSProxy: Launcher's menu: HTTPSProxy - switched on and switched off: HTTPSProxy's program window: HTTPSProxy while accessing MU: If connection errors occur, you can check the settings of HTTPSProxy in Internet Options of IE and set them manually or automatically by applying reg file 'Inet_CurUser_ProxySettings.reg'. And now one important hint. If you want to use both proxies in your system, you mustn't run them in RAM at same time! Otherwise the selected proxy won't work at all. You have to close the unused proxy to use the other. Keep that in mind! 6.5. Maintenance of ProxHTTPSProxy and HTTPSProxy for future use: We have to carry out a bit of maintenance to ensure that these proxies are working properly. First of all, the system's root certificates should be updated every three months. If you have not done that yet, you can use one of the root certificate updater in the section 11.2.4. Downloads related to Root Certificate Updates where different online and offline versions can be downloaded from. Then you should check following list: Regular update of the file 'cacert.pem'. Maintenance and check of the file config.ini according to your needs. Checking the validity of the proxy's root certificate. Deleting of all certificates in the folder 'Certs' if the proxy isn't working properly. Checking the state of the Proxy in IE or in your system. 7. The TLS 1.2 proxy ProxHTTPSProxy's PopMenu 3V1 7.1 Prerequisites: A CPU with SSE2 instruction set is required to run this TLS 1.2 proxies under Windows XP. 7.2. Purpose and components of ProxHTTPSProxy's PopMenu 3V1: This is the first release of ProxHTTPSProxy's PopMenu 3.0 in version 1.0.0.0 shortened 3V1. ProxHTTPSProxy's PopMenu 3V1 is a one-click menu in systray to access and control @heinoganda's ProxHTTPSProxy REV3e. ProxHTTPSProxy's PopMenu 3V1 is a synthesis of self-programmed executables, a very few commands, credits to @AstroSkipper at MSFN, and the freeware PopMenu 3.0, credits to Jochanan Agam at freeware.persoft.ch. All the information I spread about ProxHTTPSProxy in the sections above is of course also valid for ProxHTTPSProxy's PopMenu. 7.3. Features of ProxHTTPSProxy's PopMenu 3V1: ProxHTTPSProxy's PopMenu is not a classical launcher, it is rather a systray popup menu. It can be totally customized and continuously extended according to user's needs due to its modular structure, therefore much more flexible than a classical, compiled launcher. More features can be added easily without touching existent code. Due to ProxHTTPSProxy's PopMenu's modular structure the user can change, add, delete and reorder features. Even the icons in menu can be changed easily by the user. Here is the complete list of features implemented in ProxHTTPSPoxy's PopMenu 3v1: Start ProxHTTPSPoxy Stop ProxHTTPSPoxy Hide ProxHTTPSPoxy Show ProxHTTPSPoxy Check if ProxHTTPSPoxy is running (in RAM) cacert.pem Update Root Certificates Update Open IE Proxy settings Close IE Proxy settings Check system proxy status Enable ProxHTTPSProxy system-wide Disable ProxHTTPSProxy system-wide Edit config.ini Read documentation And here is a screenshot of ProxHTTPSProxy's PopMenu 3V1: ProxHTTPSPoxy's PopMenu is provided together with ProxHTTPSProxy REV3e. This new archive called "ProxHTTPSProxy_REV3e_PopMenu_3V1" has been additionally updated by me. These are the changes to original package of @heinoganda: 7.4. Changelog of ProxHTTPSProxy's PopMenu 3V1: @heinoganda's Certificate Updater 1.6 added. Old CA Root Certificate CA.crt replaced by new one valid until 02/19/2032. ProxHTTPSProxy CA Certificate Installer and Uninstaller replaced by more recent ones corresponding to pre-generated CA Root Certificate valid until 02/19/2032. Old cacert Updater removed, recreated cacert Updater Fixed added. cacert.pem updated to most recent one. Alternative latest cacert.pem dated of 2022-04-26 from Mozilla added with download url. All self-programmed executables of ProxHTTPSPoxy's PopMenu 3v1 created in two different versions, UPX and noUPX, following the spirit of ProxHTTPSPoxy's creator. 7.5. Installation and configuration of ProxHTTPSProxy's PopMenu 3V1: 1. Unpack archive and copy the complete folder ProxHTTPSProxy_REV3e_PopMenu_3V1_noUPX or ProxHTTPSProxy_REV3e_PopMenu_3V1_UPX (or its complete content) to desired location. 2. Although both, ProxHTTPSProxy REV3e and ProxHTTPSPoxy's PopMenu 3V1, are fully portable, the config file of program PopMenu has to be adjusted to new location. This can be done manually or much more comfortable automatically by a tool I created for this purpose only. Go to subfolder PopMenu and execute "Configure PopMenu.exe". This procedure will always set the menu back to default settings. If you modified the menu in the past to your needs, you have to adjust the config file "PopMenu.ini" manually, otherwise you'll lose your modifications. In any case the paths in config file "PopMenu.ini" have to be adjusted when the complete program folder (or its complete content) was copied to a new location. 7.6. Tranferring all settings of an existing ProxHTTPSProxy's installation: Copy the files "CA.crt" and "config.ini" from old installation folder to new one. Same with complete subfolder "Certs". Doing it in that way you won't lose any old settings. 7.7. Usage of ProxHTTPSProxy's PopMenu 3V1: To start ProxHTTPSPoxy's PopMenu, just apply "ProxyPopMenu.exe" in main program folder ProxHTTPSProxy_REV3e_PopMenu_3V1_noUPX or ProxHTTPSProxy_REV3e_PopMenu_3V1_UPX. ProxHTTPSPoxy's PopMenu can be set to "Start automatically at Windows startup" in context menu item "Settings" which is called up by right-clicking systray icon. Here the PopMenu can be configured generally. ProxHTTPSPoxy's PopMenu has been pre-configured by me. The provided functions (items) corresponding to their labels are in most cases self-programmed executables and in a very few inserted commands. All items of ProxHTTPSPoxy's PopMenu are generally self-explanatory. Feel free to click on them and test them! If you click on item "Enable ProxHTTPSProxy system-wide", my program checks whether ProxHTTPSProxy is running or not. If not, it will be started immediately. This is necessary to set ProxHTTPSProxy to mode system-wide or setting process would fail. And one recommendation: Do not change or modify files in subfolder PopMenu and keep the file or folder structure inside main folder, otherwise the ProxHTTPSProxy's PopMenu won't work properly! If you want to modify the menu, do it in PopMenu's "Settings". But you have to know what you do otherwise ProxHTTPSPoxy's PopMenu won't work as expected. ProxHTTPSProxy's PopMenu itself has a very low usage of RAM. It's only about 2 MB. The download link of ProxHTTPSProxy's PopMenu 3V1 can be found in the section 11.2.1.1. Downloads related to ProxHTTPSProxy. 8. The TLS 1.3 proxy ProxyMII 8.1. Prerequisites: ProxyMII was created by Python 3.7.1 which requires Microsoft Visual C++ 2015 Redistributable or Microsoft Visual C++ 2015-2019 Redistributable (latest version 14.28.29213.0). Check if it is installed in your system! 8.2. General information about ProxyMII: ProxyMII is a proxy based on ProxHTTPSProxy which was originally created by whenever. It was enhanced in terms of the TLS 1.3 protocol and its cipher suites by @cmalex who recently created it using Python 3.7.1. Again, a big thanks for that to @cmalex! ProxyMII provides all TLS protocols from TLS 1.0 up to TLS 1.3 and its corresponding cipher suites. It differs from @heinoganda's ProxHTTPSProxy in its file structure and does not provide a comparable program like ProxHTTPSProxy_PSwitch.exe to activate or deactivate the proxy settings automatically, when the proxy is started or closed. This has to be done manually by the user. If you want to use ProxyMII as it is without any additional comfort, then read the following instructions to get it running. 8.3. Specific information about the different ProxyMII releases: 8.3.1 ProxyMII (20220717): Hardware requirements: A CPU with SSE2 instruction set is not required anymore, SSE only is sufficient. ProxyMII (20220717) is now based on OpenSSL 3.0.5, dated from 2022-07-05, and Cryptography 3.4.8, dated from 2021-08-24. 8.3.2. ProxyMII (20230813): Hardware requirements: A CPU with SSE2 instruction set is now required., SSE only is not sufficient anymore. ProxyMII (20230813) is now based on OpenSSL 3.1.2, dated from 2023-08-01, and Cryptography 40.0.2, dated from 2023-04-14. Here are the changelogs: Changes from OpenSSL 3.0.5 to OpenSSL 3.1.2: Changes from Cryptography 3.4.8 to Cryptography 40.0.2: 8.4. How to set up and use the TLS 1.3 proxy ProxyMII: Unpack the archive and copy the folder ProxyMII to a location of your choice. Install the file CA.crt to Trusted Root Certification Authority under the account local computer manually. I use the certificate generated by ProxHTTPSProxy REV3e, provided in my release of ProxHTTPSProxy's PopMenu 3V1. Or use my contained ProxHTTPSProxy CA Certificate Installer and Uninstaller to do that automatically. If so, you have to overwrite the already existing CA.crt in ProxyMII's program folder by the one of my release. Enable the proxy settings of IE in the Internet Options -> LAN settings, i.e., check mark "Use a proxy server for your LAN", and click on Advanced. Go to the entry Secure and enter the Proxy address 127.0.0.1 and the port 8079. Update the file cacert.pem to have the most recent one by using my cacert Updater Fixed (Recreated). Start the proxy by executing the file ProxHTTPSProxy.exe. Ensure that your firewall doesn't block this proxy. Add it to your exclusions list or allow its connection. Do not forget to disable the proxy settings of IE when ProxyMII has been closed. The download links of ProxyMII and cacert Updater Fixed can be found respectively in the sections 11.2.2. Downloads related to the TLS 1.3 proxies and 11.2.3. Downloads related to cacert.pem Certificate Update. ProxyMII is the TLS 1.3 proxy on which my program package ProxHTTPSProxy's PopMenu TLS 1.3 is based from now on. 9. The TLS 1.3 proxy ProxHTTPSProxy's PopMenu TLS 1.3 9.1. Prerequisites: ProxHTTPSProxy's PopMenu TLS 1.3 is based on ProxyMII, which was created by Python 3.7.1, and requires Microsoft Visual C++ 2015 Redistributable or Microsoft Visual C++ 2015-2019 Redistributable (latest version 14.28.29213.0). Furthermore, Microsoft .NET Framework 4.0 is now additionally required to run the program package ProxHTTPSProxy's PopMenu TLS 1.3 under Windows XP. Check if both are installed in your system! A CPU with SSE2 instruction set is not required anymore, SSE only is sufficient. 9.2. General information about ProxHTTPSProxy's PopMenu TLS 1.3 The main feature of my program package ProxHTTPSProxy's PopMenu TLS 1.3 is @cmalex's ProxyMII, a TLS 1.3 proxy. I replaced @heinoganda's TLS 1.2 proxy from my last release of ProxHTTPSProxy's PopMenu REV3e 3V1 by @cmalex's TLS 1.3 proxy. This sounds simple, but, unfortunately, it wasn't. A lot of problems had to be solved to implement this proxy completely, enhance functionality, and get control of it as convenient as the old one. ProxHTTPSProxy's PopMenu TLS 1.3 is a one-click menu in systray to access and control the brand new TLS 1.3 proxy ProxyMII, better known as ProxHTTPSProxy, credits to @cmalex and its original creator whenever. @cmalex's ProxyMII, dated from 2022-07-17, is now based on OpenSSL 3.0.5 and Cryptography 3.4.8. It provides all TLS protocols from TLS 1.0 up to TLS 1.3 and its corresponding ciphers. 9.3. ProxHTTPSProxy's PopMenu TLS 1.3 3V3 ProxHTTPSProxy's PopMenu TLS 1.3 3V3 is the third release of ProxHTTPSProxy's PopMenu 3.0, now in version 3.0.0.0, shortened 3V3. It is a synthesis of the excellent, brand new TLS 1.3 proxy ProxyMII, dated from 2022-07-17, credits to @cmalex at MSFN, several self-programmed executables and a very few commands, credits to @AstroSkipper at MSFN, the freeware PopMenu 3.0, credits to Jochanan Agam at freeware.persoft.ch, the open source utility Min2Tray v1.7.9, credits to Junyx at junyx.breadfan.de, and the program Certificate Updater 1.6, credits to @heinoganda at MSFN. If you wonder when the second version was released, the answer is very simple: never. This version was unofficial. ProxHTTPSProxy's PopMenu is not a classical launcher, it is rather a systray pop-up menu. It can be totally customized and continuously extended according to the user's needs due to its modular structure, therefore, much more flexible than a classical, compiled launcher. More features can be added easily without touching the existent code. Due to ProxHTTPSProxy's PopMenu's modular structure, the user can change, add, delete and reorder features. Even the icons in the menu can be changed easily by the user. Here is a screenshot: 9.3.1 Features of ProxHTTPSProxy's PopMenu TLS 1.3 3V3: Here is the complete list of features implemented in ProxHTTPSProxy's PopMenu TLS 1.3 3V3 and a short explanation of them: Start ProxHTTPSPoxy – Activates the proxy's settings in IE LAN Settings, starts the proxy, and deactivates and cleans its settings after closing, all automatically. Stop ProxHTTPSPoxy – Stops the proxy and closes its status window. Minimize ProxHTTPSProxy to systray – Minimizes ProxHTTPSProxy's status window to systray and shows its icon there. Restore ProxHTTPSProxy from systray – Restores ProxHTTPSProxy's minimized status window from systray. Hide ProxHTTPSPoxy – Hides ProxHTTPSProxy's status window completely. Show ProxHTTPSPoxy – Shows ProxHTTPSProxy's hidden status window again. Check if ProxHTTPSPoxy is running (in RAM) – Checks if ProxHTTPSPoxy is running in the background. cacert.pem Update – Performs an update of the file cacert.pem. Root Certificates Update – Performs an update of the system's Root Certificates. Open IE Proxy settings – Opens the tab LAN Settings in IE's Internet Options. Close IE Proxy settings – Closes the tab LAN Settings and IE's Internet Options completely. Check system proxy status – Checks whether the proxy is used system-wide or the system has direct access. Enable ProxHTTPSProxy system-wide – Permits the whole system to use this proxy. In this mode, services can route their traffic through the proxy, too. Disable ProxHTTPSProxy system-wide – The proxy can be used only locally if it is running, generally all have direct access to their servers or the internet. Edit config.ini – Opens the file config.ini with the editor Notepad to check or modify the proxy's configuration. Read documentation – Opens the documentation with the editor Notepad to get quickly information. In the screenshot above, you can see a red arrow which points to the icon of ProxHTTPSPoxy, minimized to systray. It's a new feature, and the green marked items have been added to the pop-up menu since last release. ProxHTTPSPoxy's PopMenu is provided together with ProxyMII from 2022-07-17, created by @cmalex and branded by me as ProxHTTPSProxy 1.5.220717. This new archive called ProxHTTPSProxy TLS 1.3 1.5.220717 PopMenu 3V3 has been additionally updated by me. These are the changes to the previous version of ProxHTTPSPoxy's PopMenu: 9.3.2 Changelog of ProxHTTPSProxy's PopMenu TLS 1.3 3V3: @heinoganda's ProxHTTPSProxy REV3e replaced by @cmalex's ProxHTTPSProxy 1.5.220717 with a brand new TLS 1.3 support. New starter program StartProxy.exe created to activate the proxy settings, start the proxy, and deactivate its settings after closing, all automatically. cacert.pem updated to the most recent one. Alternative cacert.pem from Mozilla, updated to the most recent version dated 2022-07-19. The open source utility Min2Tray has been fully implemented by the new configuration tools Configure PopMenu.exe and Setup Min2Tray.exe, all automatically. After the setup procedure, the programs PopMenu and Min2Tray are started automatically. All self-created files are not UPX-compressed. Therefore, the version is a noUPX only. Two new items added to the pop-up menu: Minimize ProxHTTPSProxy to systray and Restore ProxHTTPSProxy from systray. All unnecessarily embedded files have been removed from my self-created executables. Changes in calling up other programs. In all my affected programs, protection against code injection has been improved. This leads to preventing of future "space bugs", too! Different issues, which could have been noticed only in very rare cases, have been fixed. All unnecessary code has been removed. New bugs I additionally found have been fixed. Autostart entries of PopMenu and the new Min2Tray, automatically added to the registry by my configuration program, have been fixed in regard to the "space bug". All message windows of my programs have been resized and adjusted for a better visibility. All my self-created program files have been recompiled by using a different compiler. @cmalex's original ProxyMII wasn't modified by me, except a replacement of ProxHTTPSProxy.EXE's program icon, back to the old one and an update of the file config.ini to get access to the Microsoft Updates (MU) website with this proxy. 9.3.2 Installation and start of ProxHTTPSProxy's PopMenu TLS 1.3 3V3: Check if Microsoft Visual C++ 2015 Redistributable or Microsoft Visual C++ 2015-2019 Redistributable (latest version 14.28.29213.0) is installed in your system. Check if Microsoft .NET Framework 4.0 is installed in your system. Unpack the archive and copy either the complete folder ProxHTTPSProxy_TLS_1_3_1_5_220717_PopMenu_3V3 or its complete content to your desired location. Install the file CA.crt, located in the main program folder, to Trusted Root Certification Authority under the account local computer, or use the program ProxHTTPSProxy Cert Installer, provided in the archive. Go to the subfolder PopMenu and execute the program Configure PopMenu.exe. PopMenu and Min2Tray will be started automatically. A more detailed documentation, titled Documentation of ProxHTTPSProxy's PopMenu 3V3, can be found in the subfolder Docs of my program package and should be read before using ProxHTTPSProxy's PopMenu in any case. All features and more are described there. The programs PopMenu and Min2Tray have a very low usage of RAM. It's only about 2 MB and 4 MB respectively. The download link of ProxHTTPSProxy's PopMenu TLS 1.3 3V3 can be found in the section 11.2.2. Downloads related to the TLS 1.3 proxies. 10. Versions: 10.1. Versions of the TLS 1.2 proxies ProxHTTPSProxy, HTTPSProxy, and ProxHTTPSProxy's PopMenu: Last known version of ProxHTTPSProxyMII, created by @whenever and released in June of 2018: ProxHTTPSProxyMII 1.5 (20180616) ProxHTTPSProxyMII 1.3a (20150527) was released in May of 2015. Here are two links: https://prxbx.com/forums/showthread.php?tid=2172&pid=17686#pid17686 and https://prxbx.com/forums/showthread.php?tid=2172&pid=18454#pid18454 Due to support of SHA1 for signing certificates ProxHTTPSProxyMII 1.3a can be used in a Windows XP Professional x64 system to access MU successfully. More recent versions use SHA256 to sign certificates and fail while accessing MU. But that also means ProxHTTPSProxyMII 1.3a is not secure and should only be used if there is no other option. Here is a link to the post with necessary instructions and a screenshot of successful access to MU using ProxHTTPSProxyMII 1.3a in Windows XP Professional x64, credits to @maile3241: https://msfn.org/board/topic/178377-on-decommissioning-of-update-servers-for-2000-xp-and-vista-as-of-july-2019/?do=findComment&comment=1214098 Last known version of ProxHTTPSProxy released in November of 2019: ProxHTTPSProxy REV3e. Here is a link: https://msfn.org/board/topic/176344-problems-accessing-certain-sites-https-aka-tls/?do=findComment&comment=1173585 Last known version of HTTPSProxy released in November of 2018: HTTPSProxy_Launcher_v2_2018-11-06 Here are two links: https://msfn.org/board/topic/176344-problems-accessing-certain-sites-https-aka-tls/?do=findComment&comment=1155858 and https://msfn.org/board/topic/176344-problems-accessing-certain-sites-https-aka-tls/?do=findComment&comment=1156032 Last version of ProxHTTPSProxy's PopMenu released in May of 2022: ProxHTTPSProxy's PopMenu 3V1 (20220510) Here is the link to my post of this initial release: https://msfn.org/board/topic/183352-proxhttpsproxy-and-httpsproxy-in-windows-xp-for-future-use/?do=findComment&comment=1218622 10.2. Versions of the TLS 1.3 proxies ProxyMII and ProxHTTPSProxy's PopMenu TLS 1.3: ProxyMII released in July of 2022: ProxyMII (20220717). It was rebranded by me to ProxHTTPSProxy 1.5.220717. Here is the link to @cmalex's original post: https://msfn.org/board/topic/183684-looking-for-a-person-with-python-programming-skills-to-implement-tls-13-functionality-in-proxhttpsproxy-rev3e/?do=findComment&comment=1222235 Latest version of ProxyMII released in August of 2023: ProxyMII (20230813). Here is the link to @cmalex's original post: https://msfn.org/board/topic/183352-proxhttpsproxy-and-httpsproxy-in-windows-xp-for-future-use/?do=findComment&comment=1250552 Latest version of ProxHTTPSProxy's PopMenu TLS 1.3 3V3 released in August of 2022: ProxHTTPSProxy's PopMenu TLS 1.3 3V3 (20220817). Here is the link to the post of its official release: https://msfn.org/board/topic/183352-proxhttpsproxy-and-httpsproxy-in-windows-xp-for-future-use/?do=findComment&comment=1224184 11. Downloads: 11.1. Archived Downloads {obsolete}: ProxHTTPSProxyMII 1.3a can be downloaded here: http://www.proxfilter.net/proxhttpsproxy/ProxHTTPSProxyMII 1.3a.zip. Credits to @whenever. ProxHTTPSProxyMII 1.5 can be downloaded here: http://jjoe.proxfilter.net/ProxHTTPSProxyMII/files/ProxHTTPSProxyMII 1.5 advanced 34cx_freeze5.0.1urllib3v1.22Win32OpenSSL_Light-1_0_2o-1_1_0h.zip. Credits to @whenever. ProxHTTPSProxy REV3d can be downloaded here: https://www.mediafire.com/file/r23ct8jd2ypfjx5/ProxHTTPSProxyMII_REV3d_PY344.7z/file. Credits to @heinoganda. Root Certificate and Revoked Certificate Updater of 02/24/2022 created by @AstroSkipper: https://www.mediafire.com/file/n4ea8nbijox88o3/Roots_Certificate_Updater_24.02.22.7z/file Root Certificate and Revoked Certificate Updater (AIO version!) of 02/24/2022 created by @AstroSkipper: https://www.mediafire.com/file/8ler7d9z8aesz08/rootsupd.exe/file Root Certificate and Revoked Certificate Updater of 04/28/2022 created by @AstroSkipper: https://www.mediafire.com/file/7e6jw2mdp6bi3u0/Roots_Certificate_Updater_28.04.22.7z/file Root Certificate and Revoked Certificate Updater (AIO version!) of 04/28/2022 created by @AstroSkipper: https://www.mediafire.com/file/m6n7481wdq546ad/rootsupd.EXE/file Root Certificate and Revoked Certificate Updater of 05/24/2022 created by @AstroSkipper: https://www.mediafire.com/file/aob1fkpf6f3vyhd/Roots_Certificate_Updater_24.05.22.7z/file Root Certificate and Revoked Certificate Updater (AIO version!) of 05/24/2022 created by @AstroSkipper: https://www.mediafire.com/file/vkopcjfymnei5cn/rootsupd.exe/file Root Certificate and Revoked Certificate Updater of 06/28/2022 created by @AstroSkipper: https://www.mediafire.com/file/2eowvtl8r56q8tx/Roots_Certificate_Updater_28.06.22.7z/file Root Certificate and Revoked Certificate Updater (AIO version!) of 06/28/2022 created by @AstroSkipper: https://www.mediafire.com/file/h1460guuxqklkk5/rootsupd.exe/file Root Certificate and Revoked Certificate Updater of 08/23/2022 created by @AstroSkipper: https://www.mediafire.com/file/nxt11m8m39fnc1k/Roots_Certificate_Updater_23.08.22.7z/file Root Certificate and Revoked Certificate Updater (AIO version!) of 08/23/2022 created by @AstroSkipper: https://www.mediafire.com/file/0o2h3y16ekmtv2o/rootsupd.EXE/file Root Certificate and Revoked Certificate Updater of 09/27/2022 created by @AstroSkipper: https://www.mediafire.com/file/d4mtrexun8ao81l/Roots_Certificate_Updater_27.09.22.7z/file Root Certificate and Revoked Certificate Updater (AIO version!) of 09/27/2022 created by @AstroSkipper: https://www.mediafire.com/file/44suzv2x2fbrret/rootsupd.EXE/file Root Certificate and Revoked Certificate Updater of 10/25/2022 created by @AstroSkipper: https://www.mediafire.com/file/naxyauof6fs0p88/Roots_Certificate_Updater_25.10.22.7z/file Root Certificate and Revoked Certificate Updater (AIO version!) of 10/25/2022 created by @AstroSkipper: https://www.mediafire.com/file/nmzw6l4lzmxn8wx/rootsupd.EXE/file Root Certificate and Revoked Certificate Updater of 11/29/2022 created by @AstroSkipper: https://www.mediafire.com/file/cnlbxdffjq9beva/Roots_Certificate_Updater_29.11.22.7z/file Root Certificate and Revoked Certificate Updater (AIO version!) of 11/29/2022 created by @AstroSkipper: https://www.mediafire.com/file/pctxthjlcb6croc/rootsupd.EXE/file Root Certificate and Revoked Certificate Updater of 02/28/2023 created by @AstroSkipper: https://www.mediafire.com/file/6chiibdsdoh4i22/Roots_Certificate_Updater_28.02.23.7z/file Root Certificate and Revoked Certificate Updater (AIO version!) of 02/28/2023 created by @AstroSkipper: https://www.mediafire.com/file/rmjyq3pak60jayz/rootsupd.EXE/file Root Certificate and Revoked Certificate Updater of 04/25/2023 created by @AstroSkipper: https://www.mediafire.com/file/xgmi98u15ikerrn/Roots_Certificate_Updater_25.04.23.7z/file Root Certificate and Revoked Certificate Updater (AIO version!) of 04/25/2023 created by @AstroSkipper: https://www.mediafire.com/file/dxtxkgqdk6xlfb9/rootsupd.EXE/file Root Certificate and Revoked Certificate Updater of 08/22/2023 created by @AstroSkipper: https://www.mediafire.com/file/53fv86ouqgonm7f/Roots_Certificate_Updater_22.08.23.7z/file Root Certificate and Revoked Certificate Updater (AIO version!) of 08/22/2023 created by @AstroSkipper: https://www.mediafire.com/file/9xhsy3i2bphtf0i/rootsupd.EXE/file 11.2. Latest Downloads: 11.2.1. Downloads related to the TLS 1.2 proxies: 11.2.1.1. Downloads related to ProxHTTPSProxy: ProxHTTPSProxy REV3e can be downloaded here: https://www.mediafire.com/file/me5l9dydomgwa0h/2005536469_ProxHTTPSProxyMIIv1.5Rev3ePython3.44OriginalFiles.7z/file. Credits to @heinoganda. ProxHTTPSProxy's PopMenu 3V1 can be downloaded here: https://www.mediafire.com/file/h20kkuucurv2i2b/ProxHTTPSProxy_REV3e_PopMenu_3V1.7z/file. Credits to @AstroSkipper. ProxHTTPSProxy CA Certificate Installer and Uninstaller with a freshly pre-generated root certificate valid until 02/19/2032 modified and built by @AstroSkipper: https://www.mediafire.com/file/9tnonnlymrp98f8/ProxHTTPSProxy_Cert_Installer_%2B_Uninstaller_%2B_CA_valid_until_02-19-2032.7z/file ProxHTTPSProxy's config file to access MU website successfully, modified by @AstroSkipper: https://www.mediafire.com/file/vr1klatuzjh6v5c/ProxHTTPSProxy_-_config.ini/file 11.2.1.2. Downloads related to HTTPSProxy: HTTPSProxy in the version of HTTPSProxy_Launcher_v2_2018-11-06 can be downloaded here: https://www.mediafire.com/file/ku859ikt2t79cgl/HTTPSProxy_Launcher_v2_2018-11-06.7z/file. Credits to @Thomas S.. HTTPSProxy CA Certificate Installer and Uninstaller with a freshly pre-generated root certificate valid until 02/19/2032 created by @AstroSkipper: https://www.mediafire.com/file/sx1i6w2c6f1hvwm/HTTPSProxy_Cert_Installer_%2B_Uninstaller_%2B_CA_valid_until_02-19-2032.7z/file HTTPSProxy's config file to access MU website successfully, modified by @AstroSkipper: https://www.mediafire.com/file/6emtdvx2vmw4iz8/HTTPSProxy_-_config.ini/file 11.2.2. Downloads related to the TLS 1.3 proxies: ProxyMII (20220717) = ProxHTTPSProxy 1.5.220717 can be downloaded here: https://www.mediafire.com/file/pdy1cd8insmdq7g/ProxyMII_220717.7z/file. Credits to @cmalex. ProxyMII (20230813) can be downloaded here: https://www.mediafire.com/file/yb0xjos28l110xx/ProxyMII_230813.7z/file. Credits to @cmalex. ProxHTTPSProxy's PopMenu TLS 1.3 3V3 can be downloaded here: https://www.mediafire.com/file/1fd0ezzpuy7qctu/ProxHTTPSProxy_TLS_1_3_1_5_220717_PopMenu_3V3.7z/file. Credits to @AstroSkipper. ProxHTTPSProxy CA Certificate Installer and Uninstaller with a freshly pre-generated root certificate valid until 02/19/2032 modified and built by @AstroSkipper: https://www.mediafire.com/file/9tnonnlymrp98f8/ProxHTTPSProxy_Cert_Installer_%2B_Uninstaller_%2B_CA_valid_until_02-19-2032.7z/file ProxHTTPSProxy's config file to access MU website successfully, modified by @AstroSkipper: https://www.mediafire.com/file/vr1klatuzjh6v5c/ProxHTTPSProxy_-_config.ini/file 11.2.3. Downloads related to cacert.pem Certificate Update: cacert Updater Fixed, fixed and recreated by @AstroSkipper: https://www.mediafire.com/file/y98gtqf8ewr6zz4/cacert_Updater_Fixed_Recreated.7z/file. Credits to @heinoganda. 11.2.4. Downloads related to Root Certificate Updates: Root Certificate and Revoked Certificate Updater of 11/28/2023 created by @AstroSkipper: https://www.mediafire.com/file/361ux1ogvmokuhf/Roots_Certificate_Updater_28.11.23.7z/file Root Certificate and Revoked Certificate Updater (AIO version!) of 11/28/2023 created by @AstroSkipper: https://www.mediafire.com/file/6o1rfz4oqnh0din/rootsupd.EXE/file Certificate Updater 1.6: https://www.mediafire.com/file/nmoqrx8vwc8jr6l/jveWB2Qg1Lt9yT5m3CYpZ8b8N4rH.rar/file. Credits to @heinoganda. Archive password: S4QH5TIefi7m9n1XLyTIZ3V5hSv4se1XB6jJZpH5TfB6vkJ8hfRxU7DWB2p CAupdater 1.0.0.1: https://www.mediafire.com/file/z34fifg2a09fzxo/CAupdater.7z/file. Credits to @Thomas S.. The installers created by myself or built by me will be updated from time to time if necessary. All files in my offered archives are definitely virus-free and clean, although some AV scanners produce false positives. I recommend adding the complete folder to the exclusion list of your security program(s), only if you trust me, of course. Apart from that, you can also check positive reported files on VirusTotal, though. 12. Update notifications: 02/26/2022: Both versions of Root Certificate and Revoked Certificate Updater have been updated and are now of 02/24/2022. 03/16/2022: The functionality of @heinoganda's cacert Updater has been restored. cacert Updater Fixed can be downloaded in the section 11.2.3. Downloads related to cacert.pem Certificate Update. 04/23/2022: cacert Updater Fixed has been completely recreated due to false alarms of some virus scanners and can be downloaded in the section 11.2.3. Downloads related to cacert.pem Certificate Update. 05/10/2022: ProxHTTPSProxy's PopMenu 3V1 has been released. Here is the link to my post of the initial release with the download link: https://msfn.org/board/topic/183352-proxhttpsproxy-and-httpsproxy-in-windows-xp-for-future-use/?do=findComment&comment=1218622 05/16/2022: Both versions of Root Certificate and Revoked Certificate Updater have been updated and are now of 04/28/2022. 06/05/2022: Both versions of Root Certificate and Revoked Certificate Updater have been updated and are now of 05/24/2022. 06/30/2022: Both versions of Root Certificate and Revoked Certificate Updater have been updated and are now of 06/28/2022. 07/17/2022: ProxyMII has been released. Here is the link to the post of its official release: https://msfn.org/board/topic/183684-looking-for-a-person-with-python-programming-skills-to-implement-tls-13-functionality-in-proxhttpsproxy-rev3e/?do=findComment&comment=1222235. 08/17/2022: ProxHTTPSProxy's PopMenu TLS 1.3 3V3 has been released. Here is the link to the post of its official release: https://msfn.org/board/topic/183352-proxhttpsproxy-and-httpsproxy-in-windows-xp-for-future-use/?do=findComment&comment=1224184 09/05/2022: Both versions of Root Certificate and Revoked Certificate Updater have been updated and are now of 08/23/2022. 10/06/2022: Both versions of Root Certificate and Revoked Certificate Updater have been updated and are now of 09/27/2022. 11/06/2022: Both versions of Root Certificate and Revoked Certificate Updater have been updated and are now of 10/25/2022. 12/09/2022: Both versions of Root Certificate and Revoked Certificate Updater have been updated and are now of 11/29/2022. 03/04/2023: Both versions of Root Certificate and Revoked Certificate Updater have been updated and are now of 02/28/2023. 05/09/2023: Both versions of Root Certificate and Revoked Certificate Updater have been updated and are now of 04/25/2023. 08/13/2023: ProxyMII has been updated. Here is the link to the post of its official release: https://msfn.org/board/topic/183352-proxhttpsproxy-and-httpsproxy-in-windows-xp-for-future-use/?do=findComment&comment=1250552. 09/01/2023: Both versions of Root Certificate and Revoked Certificate Updater have been updated and are now of 08/22/2023. 12/11/2023: Both versions of Root Certificate and Revoked Certificate Updater have been updated and are now of 11/28/2023. 13. Conclusion: At the beginning of this post, I said we had to ask ourselves whether these proxies would continue doing their job in the future or not. After all these observations and explanations, the answer to this question is quite clear: Yes, of course. And especially since we have our new TLS 1.3 proxies. But we have to avoid misconfiguration of these proxies, and in addition, we know they won't work properly without updating and carrying out maintenance. Doing all these things leads to a general, positive side effect for those loving their Windows XP. If all is done correctly, we are now able to use a freshly generated 10 years valid root certificate of ProxHTTPSProxy or HTTPSProxy at any time as long as Windows XP, Internet Explorer access to WWW, TLS 1.2 or TLS 1.3 functionality, Microsoft Update for Windows XP, or the user himself still exist. 14. Disclaimer: All information that I spread here corresponds to my level of knowledge. Most of it has been carefully researched by me. I tested all programs of the section 11. Downloads extensively, and they worked properly in my system. Nevertheless, I do not assume any guarantee either for the correctness and completeness or for the implementation of my tips. The same applies to the application of my tools in the section 11. Downloads. Therefore, all at your own risk! You can use the commenting zone below to tell us about your experiences, problems and questions or to provide further tips and recommendations. Any discussions about these proxies are explicitly welcome. If this article has not been able to resolve any issues related to these proxies, and you need further assistance with configuring or running them, I will try to help you as much as I can. But one thing must be clear, everything should relate to the topic of this thread. That means please stay on-topic! If you enjoyed this article or maybe, you found it interesting and helpful, I would be pleased about any reaction by liking, upvoting, and of course, commenting. Kind regards, AstroSkipper
    20 points
  6. 360 Extreme Explorer Screenshot of the browser: (360 Extreme Explorer, Ver: 13.0.2250.0, "Chrome" Theme) Modified Version download links: v9 --> (Updated 22/03/23) Version: 9.5.0.138 Based on Chromium: 63.0.3239.132 v11 --> (Updated 22/03/23) Version: 11.0.2251.0 Based on Chromium: 69.0.3497.100 v12 --> (Updated 22/03/23) Version: 12.0.1592.0 Based on Chromium: 78.0.3904.108 v13 --> (Updated 22/03/23) Version: 13.0.2250.0 Based on Chromium: 86.0.4240.198 (Updated 22/03/23) Version: 13.0.2310.0 Based on Chromium: 86.0.4240.198 Archive with all versions --> https://archive.org/details/360EE_Modified_Version See: https://retrosystemsrevival.blogspot.com/2019/05/360-extreme-chrome-browser.html https://web.archive.org/web/20210925152949/https://xpforever.miraheze.org/wiki/360_Extreme_Explorer Note: The changes I made are so many that maybe some little errors related to translation and/or the building of the modification notes can be present so please tell me if you find any. Also, if you want to propose something else, please be aware that I do not have a lot of free time and that at any moment, I could be gone for a while for whatever reasons (I do not intend to be rude with this comment, feel free to speak yourself). If anyone wants to help, it will be truly appreciated. Kafan Mini-Browser Another Chinese Chromium-based browser that seems to be pretty much like a standard Chromium build. Official Page --> https://browser.kfsafe.cn/ Forum --> https://bbs.kafan.cn/forum-298-1.html Screenshot of the browser: Modified Version download link: v1 Version: 1.0.0.121 --> (22/03/23) Version: 1.0.0.127 --> (22/03/23) Based on Chromium: 87.0.4280.66 Folder --> https://archive.org/details/360EE_Modified_Version Observations: - On startup the browser will connect to the website of the search provider selected as default because of the search bar provided on the new tab. - Browser crashing when inserting a USB drive? --> Disable the "Enable new USB backend" flag in "chrome://flags/" (Thanks to @realisty). - Only natively compatible with XP-32bits. It can be used on XP-64bits thanks to @Matias Groen (see XP x64 folder). - Very heavy for old computers. - Doesn't have NPAPI support. Original download link (you can unzip the EXE file with 7zip): http://browser-download.kfsafe.cn/MiniBrowserSetup.exe (currently down) Internet Archive alternative link --> http://web.archive.org/web/20221201234530/http://browser-download.kfsafe.cn/MiniBrowserSetup.exe DC Browser A Chinese Chromium-based browser. The only version compatible with XP is v4 (Chromium 75). Official page --> http://dcbrowser.cqttech.com/home Screenshot of the browser: Modified Version download link: v4 --> (Updated 22/03/23) Version: 4.0.7.22 Based on Chromium: 75.0.3770.100 Folder --> https://archive.org/details/360EE_Modified_Version Observations: - On startup the browser will connect to the website of the search provider selected as default. Similar to Mini-Browser. - All default extensions were removed (the PDF Feature and Screen Capture will not work). You can get them out of the browser's interface through the settings. - Doesn't have NPAPI support. - Has DRM support (Win7+) --> https://bitmovin.com/demos/drm Original download link (you need to install to get the browser files, fortunately you can set the location of the installation): http://file.cdn.cqttech.com/dcbrowser/DCBrowser_1261_4.0.7.22.exe Patcher to retrieve the translation function for all browsers modified --> https://archive.org/details/360EE_Modified_Version Usage: - Inside the "trans_patch.7z" there is a "trans_patch" folder. Extract it. - Copy and paste the folder in the same place the browser executable file is. - After that, enter the folder and execute "trans-patch.bat". - A command-line interface will show up. Depending on the browser you are trying to apply the patches a small question will be promted on CMD. If everything goes correctly the program will show you at the end "Press any key to continue". Press any key, open the browser and check if the translation function was restored. After all that you can delete the "trans_patch" folder. It should work without errors. If anything else happens tell me. Thanks to all the following for the information I could gather for the modification of these browsers: @Windows 2000, @VistaLover, @Sampei.Nihira, @win32, @DragonSC7601, @redapple0204, @blackwingcat, @404notfound, @Cixert, @thebuildone, @ArcticFoxie, @Dixel, The Russian Repackers, @dmiranda, @we3fan, @athlonxpuser and @Greyfox77 I really hope this can help someone, Cheers. - Humming Owl
    19 points
  7. Game over I think, it doesn't get better than this! Neneh Cherry onstage at the Glastonbury Festival after the laptop running her background video apparently crashed!
    19 points
  8. Sad news for everyone here at MSFN. One of our forum supervisors, Dencorso, passed away on October 24th, after a long and courageous battle with cancer. Apparently he was still upbeat and optimistic about the future a few weeks before he passed. My memories of Den go back quite a few years. He was incredibly helpful to me with technical problems, which is what this board is all about of course, initially mainly with Windows 98, and latterly with Windows XP. He was immensely supportive too when I first became a moderator here, something I will always be grateful for. He was definitely one of the good guys, and will be sorely missed here. Please add your memories here of working with Den. Thanks, Dave.
    18 points
  9. Support for installing Chromium extensions, saving their settings, as well as keeping cookies and other settings has been implemented: The original objective was to fix the "CultureNotSupported"-related exceptions that prevented .NET Core 5 from working, but under the belief that the .NET and Chromium issues were connected, I worked on solving the issue using Chromium. It turns out that .NET's issues are unrelated.
    18 points
  10. Here, you will find a list of software compatible with Windows Vista, after installing the new extended kernel by Win32. As this project is very new, this list will remain quite short for the time being. List: BeamNG.Drive 0.16 and later Chromium versions 53-73 beta (later versions currently do not work) Firefox "classic" versions 53-56 Firefox Quantum version 57 and later GIMP 2.10.18 Google Earth 7.3.3 and later Interlink Mail client Logitech Gaming Software 9.02 Opera 44 (later versions currently do not work) Palemoon 28.x Rocket League Thunderbird versions 53 and later Waterfox Classic Waterfox Current Whatsapp I will continue to update this list as more software is made compatible. Feel free to contribute your own additions in the form of a reply to the topic, and I will add them ASAP.
    17 points
  11. I will not continue with this project, I have outgrown it. Thank you for all your kind comments, advice, etc. My modified versions are removed - they are unsafe due to sandbox bypass, embeded videos do not work.
    17 points
  12. This project make possible to compile ACPI 2.0 driver from leaked XP SP1 & W2003 RTM sources, has same functionality as existing acpi.sys v6666 (still missed integer/fields/memory 64 bit support/) Grab leaked XP SP1/W2003 RTM sources (google it) Use "XPSP1/NT" directory as basedir if you want to compile acpi.sys for Windows XP x32 Use "Win2K3/NT" directory as basedir for Windows 2003 x32 / Windows 2003 x64 / Windows XP x64 Download any GNU patch package for windows (gnuwin32.sourceforge.net, cygwin, mingw, msys2, ...) Open command console, change current dir to base\busdrv\acpi\ (Windows XP x32) Save text diff patch https://pastebin.com/C5NXwHbS (v7 update) to file base\busdrv\acpi\sp1_to_sp3(ACP2).patch (Windows 2003 x32 / Windows 2003 x64 / Windows XP x64) Save text diff patch https://pastebin.com/8QURrM49 (v7 update) to file base\busdrv\acpi\rtm_to_sp2(ACP2).patch (Windows 2003 x32 / Windows 2003 x64 / Windows XP x64) Rename Win2K3/NT/public to Win2K3/NT/public2 (Windows 2003 x32 / Windows 2003 x64 / Windows XP x64) Update compiler and headers to mix of W2003 DDK+WRK, unpack https://anonfiles.com/J1W9H1a8y1/W2003_tools_update_7z to basedir with overriding existing files Remove "read only" flag from base\busdrv\acpi directory including sub-dirs and files Apply patch to convert original SP1/RTM sources to SP3/SP2 with extended ACPi 2.0 syntax: patching file driver/amlinew/amlipriv.h patching file driver/amlinew/amlitest.c patching file driver/amlinew/data.c patching file driver/amlinew/misc.c patching file driver/amlinew/object.c patching file driver/amlinew/parser.c patching file driver/amlinew/proto.h patching file driver/amlinew/type1op.c patching file driver/amlinew/type2op.c patching file driver/inc/aml.h patching file driver/nt/debug.c patching file driver/nt/debug.h patching file driver/nt/devpower.c patching file driver/nt/internal.c patching file driver/nt/interupt.c patching file driver/nt/irqarb.c patching file driver/nt/osnotify.c patching file driver/nt/pciopregion.c patching file driver/nt/rangesup.c patching file driver/nt/root.c patching file driver/nt/wake.c Change current dir to basedir (Windows XP x32 / Windows 2003 x32) Run razzle environment setup: (Windows 2003 x64 / Windows XP x64) Run razzle environment setup Change current dir to base\busdrv\acpi\driver\ Complie ACPI driver: build /Dcegbw Compiled acpi.sys.sys will be in (x32) base\busdrv\acpi\driver\nt\obj\i386\ or (x64) base\busdrv\acpi\driver\nt\obj\amd64\ Project contains implementation of new ACPi 2.0 syntax: ToInteger ToString ToHexString Continue ConcatenateResTemplate ToDecimalString Mod ToBuffer CopyObject MidString QwordConst (inside ParseIntObj) Timer CreateQWordField(fake it as CreateDWordField) Know issues workarounds: BSOD 0xA5 (0x10006, ...) missing _DIS method for "PNP0C0F" (PCI Interrupt Link Devices) BSOD 0xA5 (0x02,xxx, 0x0, ...) ACPI vs E820 mem ranges conflict IOTRAPS I/O range 0xFF00-0xFFFF vs VGA (10-bit decode!) conflict BSOD 0xA5(0x03, ..., C0140008, ...) error in ValidateArgTypes() when reading 64-bit fields BSOD 0x7E(c0000005, ...) error in AcpiArbCrackPRT() when referencing null pointer BSOD 0xA5 (0x11, 0x08, ..., ...) error in _AMLILoadDDB() (zero lenght buffer) BSOD 0xA5 (0x11, 0x08, ..., ...) error in _AMLILoadDDB() (doubled device definition) BSOD 0xA5 (0x0000000D, ..., 0x4449555F, 0) absence _UID method BSOD 0xA5 (0x11, 0x08, ..., ...) error in _AMLILoadDDB() (Connection() opcode) CPU definition as Device with _HID=ACPI0007 BSOD 0xA5(0x03, ..., C0000034, ...) postponed SSDT loading on x64 platform (v8 update) Assertion Fail on loaddsdt.c, line 488 for x64 builds (v8 update) Unresolved issues: BSOD 0xA5 (0x0000000D, ..., ..., ...) duplicated/absence _HID/_UID method (AMD boards) BSOD 0xA5 (0x2001, 0x01, 0xC0000034, ...) failure to evaluate the _PIC method in NotifyHalWithMachineStates() Conflicted device names in Windows device manager (Code 42)
    16 points
  13. Hello everyone. I'm sorry for the very long period of inactivity lately. I've had a lot going on outside of MSFN in my personal life that has kept me busy. I also walked away from an unhealthy relationship and have been taking steps to rebuild my life since then, which has kept me from being able to update the list for the past several months. In light of the recent announcement that MSFN is going offline, I will be moving my list over to a forum hosted by my friend Ryan: http://forum.eclectic4un.me/ This will take a while as I need to manually re-add all of the links and formatting, but I will post the link here when it is finished. Feel free to join our forum if you're looking for a new home once MSFN is no longer available! We're still grassroots at the moment, but we will be building a new legacy software community over there and we'd love to have you join us (@Ximonite& @win32 are already there and have pertinent posts related to Vista Extended Kernel & Win2000's KernelXE!). Thank you so much everyone here for your contributions to the list over the past 6 years. It has been my pleasure to help provide this information to Vista users for the past several years, and I like to believe our efforts have helped many Vista (and even XP) users over the years. I'm sad to see MSFN go, but all good things do come to an end. Best regards
    16 points
  14. Yes, I would appreciate it too so it will be released when it is ready. Current status is that it does not work correctly yet. On the other side, I doubt that someone needs to upgrade to new builds immediately when it is released, especially when some needed software is not compatible with it.
    16 points
  15. WinNTSetup - a simple but powerful universal Windows Installer Features: Install (unattend) Windows 2k/XP/20??/Vista/7/8.x/10/11 x86/x64/arm64 Practically runs even on the most minimalistic WinPE selectable drive letter for the new Windows installation Fully automated with save/load setting in ini file and various command line options Install Windows also if nlite/vlite has remove winnt32.exe/setup.exe Integrate Drivers: normal PNP and Textmode Drivers Patch uxtheme to allow unsigned Themes Some common registry tweaks and *.reg file import DISM APPX removal, feature enable/disable Simple VHD creation and Installation Support "Windows to Go" for Windows 7 and later installs Supports WimBoot and CompactOS option for Windows 7 and later Supports all current WIM files: WIM/SWM/ESD and ISO files WinCapture - capture a Windows installation to WIM or ESD file MinWin - simple trimming WIM in memory before apply WinCopy - copy an existing Windows installation to another partition Offline Hotfix uninstall Offline password reset Not Supported: - No Windows embedded version (this includes WinFLP) - No upgrades of existing installations About driver installation: Every driver added in NT6.x windows will be added to the driver store. So it's not recommended to add countless driver, but rather more really required ones. NT5.x massstorage driver integration is possible thanks to Mr dUSHA powerful MSSTMake.exe tool To the Unattend option: It's possible to use an unattend.xml to run the Setup unattended. But as the actual WinPE Setup Phase isn't effective in that way of install, all Winpe related settings inside the unattend.xml won't be applied. Ini config file It's possible to save all GUI-settings to a ini file: push Ctrl + S to save all settings to an ini. push Ctrl + L to load all settings from an ini. A WinNTSetup.ini file in the same dir as the app itself will be loaded automatically at startup. It also can be selected via command line: WinNTSetup.exe /cfg:"C:\mysettings.ini" If you want to modify ini settings yourself, click-click has made a nice PDF for it. For advanced users there are also hidden settings described in the included WinNTSetup.ini.txt Command line: - Press F1 to get list of all options To install Windows in a VHD file: - requires Windows 7 as OS and Windows 7 Ultimate, Enterprise or Server 2008 R2 as Source - create a partitioned VHD and assign a drive letter (push Ctrl + Shift + V to use build in diskpart wrapper for this) - select the VHD drive as installation drive (make sure you boot drive ist a active primary partition on a physical disk) If you get an Antivirus warning from your AV software, please report it to them as a false positive and let them check it. Current Version: 5.3.4 Download: Mega - MediaFire
    15 points
  16. Hello Windows XP gaming community. I have what i believe are good news for you, if you are into emulation. I'm a developer and i've recently modified the latest version of the popular PCSX2 PlayStation 2 emulator to make it run again under the Windows XP operating system, since they removed that compatibility by 2016. The development to my modified version of PCSX2 started in May 2020, just when the latest stable official release was made public (v1.6.0), confirming it wasn't indeed compatible with XP. I wanted to do something about it, so i started peeking the code and considering the options i had. Well, after months of testing and patience, i got the latest v1.6.0 stable release from May 2020 running perfectly fine under XP. This project is called "PCSX2 XP" and is been made available from my website: http://neonfloppy.sytes.net/projects/pcsx2-xp/ and there is also a github repository: https://github.com/blueclouds8666/pcsx2_XP You may also join to my discord server, where you can find about my other projects and chat with other xp fans: https://discord.gg/KXKXcs4 I will be answering any questions you have regarding my project down below. I hope you all find this useful. Thanks for your attention.
    15 points
  17. they tried hard to make me laugh :) "unable to cherry-pick"? actually not, unless they never release any new source. since they're still releasing source with every new versions, I can still make a diff and figure out which part of changes should be in same part. yeah they did that do throw me back to pre-VCS "stone age", but it is NOT the end.
    15 points
  18. (Sorry, didn't have time to respond to this before.) I agree with your general point, but I'm not sure how much Google is to blame in this particular case. The thing is, programmers often tend to be pretty lazy when having to do maintenance tasks, because these aren't seen as "cool" and "innovative"... And this bug is a bit of a special case, because it takes almost 30 min to run a single test case, whether you're trying to track down where the regression originated, or trying to fix it. Let me give you a rough rundown of the process I went through with this (let's skip this long story for them normal people ; and this isn't about me looking for extra credit, honest! ) OK, so now consider that during virtually every step of this, you have to run a whole lot of 30 min (or longer) tests to make sure of your guesses or fixes. I am, of course, a great guy and all , but even with my highly vested hobbyist interest in solving this issue it took me several months to get through this all. Obviously not months of straight work on this alone, and obviously I didn't just sit around gaping at the screen every time I ran a test, but started the test and then did something else while it ran, but the whole thing still took time. Now, imagine I was an elite coder working at Mozilla , and generally supposed to work on some other stuff besides this. And, let's say you were my manager. Are you sure you'd let me spend all this time on this one, apparently (but really not) intermittent issue that seems to be affecting only a few people (really affecting all, but 99.99% of those people wouldn't put 2 and 2 together and notice the very specific interval and would instead write these freezes off as internet issues or whatever else) on a "legacy" OS that doesn't have that long to live anyway (or so you think, not knowing about POSReady, and MSFN )? And would I, an elite Mozilla engineer , want you to make me spend my precious time on something like this? I mean, even without the whole Windows driver dive and leak hunting thing they obviously wouldn't get into (the leak hadn't happened yet, either), it's a lot of work that isn't "cool", nor "innovative"! This is not to say that I excuse the fact that they don't even run tests for longer playback, etc., etc. We all know Mozilla has lots of problems with their attitude and policies, and there are many things they aren't doing that they should be doing (and vice versa). I definitely do blame them for letting this fall through the cracks and not doing more to fix this. But as far as Google goes, since they probably weren't using cubeb, maybe they themselves never ran into this bug (at least its more obvious, 2x:xx version), and since this isn't an issue specific to Youtube, I think I wouldn't blame them too much for this one. But there is Microsoft, who introduced this bug in the first place with that pretty dumb coding error...
    14 points
  19. I got some ideas for branding.. Pale Moon could be called Whistler after the Codename for Windows XP Basilisk could be called Freestyle the Codename for Windows XP Media Center Edition because of the extra media features and Australis UI Borealis could be called Neptune the Codename for a developmental predecessor of Windows XP Interlink could be called Lonestar the Codename for Windows XP TabletPC Edition (writing, email, get it?) These are all UXP based applications for Windows XP and there you go a theme for all your forks of them. OH just call Basilisk 55, call it the codename for the repo.. Moebius/Mobius. Good name at any rate. Again for the four UXP applications.. I am willing to do the work for you, get em all in one repo, do the branding (yes I will keep the appdata paths as they are to avoid profile issues) and gift wrap it for you for Christmas. What do you say? EDIT: Thank you for removing the official branding from the modified-uxp repository. ALSO, if you go forward with this I will list you on thereisonlyxul.org in a special section for Windows XP users.
    14 points
  20. I am glad that he had found friends here. I never really knew the extent of all of his Win9x work. My current desktop can still boot into Win9x because of him, although, I haven't in a while. I would like to try to provide some closure for others so I'll give a timeline of what happened. You may or may not have known that my father had heart issues. He had a mild heart attack in his 40s. August 19th: Goes in for angiogram, gets fast tracked for triple bypass surgery. He left me a message midday about it and I called him that evening. We discussed the options they gave him and he seemed settled on the bypass surgery. August 21st: Has the surgery. Gets out of surgery, doctor tells me take he handled it well. August 24th: First time I was able to contact him on the phone after the surgery. He seemed well but certainly worn-down after the surgery. August 25th: Had a heart attack (cardiac event). Survived, but apparently it was not a good situation. I was able to talk to him that evening (I think, it could have been the next day). Got the impression that his diabetes and insulin resistance played a major role in the incident. August 28th: Last night I get to talk to him. I made plans to come down to see him on the 30th. August 29th: Situation escalates, possible infection/sepsis. August 30th-September 2nd: He is heavily sedated for the pain. But things seem stable. Not good, but stable. I return home and hope for the best. September 3-7th: Situation goes back and forth, fluid buildup leads to treatment for infection. Ultimately, the infection is treatable but the sepsis is not. September 9th: Palliative care nurse contacts me and I go back down that afternoon. Situation is getting worse. September 10th: Responsiveness to questions during sedation vacation is lost except to pain stimulus. September 11th: Taken off of life support. Passes at 1:28pm. I hope that helps. I think it has helped me to write it out. I forgot I had the message from him in my voicemail about going to the hospital. My own personal take on it is that complications from diabetes played a major role in his inability to recover but I am not a doctor and it's just my own mind trying to justify the situation.
    14 points
  21. On behalf of xper, an explanation for MSFN being offline for the last few days. An ingress of water at the location of the server caused damage, fortunately not to the server itself, but to the room's UPS system batteries, which necessitated the removal of power and a physical move of the server to another location. This obviously took some time to do. Hopefully there will now be no further issues relating to this.
    13 points
  22. Hello everyone. I just finished re-adding GDI to Supermium. At first it would only work in --single-process mode, but I got it working in standard mode by ensuring that FontCache objects have the Skia GDI font manager when GDI is enabled. Then I want to fix TLS, readd D3D9 DXVA support, and link Supermium against a DLL with implementations of many newer functions. I have fixed my PMs if you are interested.
    13 points
  23. Off-Topic: so tomorrow is last day of my "sick leave" period caused by bicycle accident happened in 12 Nov 2022, I'll try to pick-up all upstream changes to my trees. Starting from 1 March I have to resume to my $DAYJOB and picking-up tasks that crated during the period that I was "missing" so it could be quite busy in following days/weeks. hope everything goes well and back to normal soon.
    13 points
  24. Off-topic: while testing my GreenPad on ReactOS, I found some bugs and fixed some of them. And ReactOS twitter account mentioned me. :)
    13 points
  25. I've attached RAR5 compressed files with lists of download links for all official updates for Vista 32-bit and 64-bit Post SP2 up to April 2017. Includes all language packs for Vista, IE9 and local Help update. Also included are Ultimate Extras, Optionals and .NET Framework 3.5 SP1 / 4.52 with updates. Superseded updates are not included except for a few ones just to satisfy Windows Update. Hotfixes are not included, unless available through Windows Update. Someone please mirror them on Web Archive. ASAP. EDIT: Updated files with .NET Framework 3.5 SP1 Language Packs. Installing System Updates: If you want to install a language pack, you must do it first, by downloading and running the language pack executable. 1) Download all files from Main_URLs.txt to the same folder. 2) Using WinRAR, sort files by type and unpack all .MSU files to the same folder, overwriting existing files. Then you may delete the .MSU files to save space. 3) Unpack the WindowsVistaSP2_x86_Installer.rar or WindowsVistaSP2_x64_Installer.rar (just batch files) to the same folder where you extracted the files. 4) Open a Command Prompt with Administrator privileges and switch to the folder where the update files are. 5) Run Main_Part1.bat, Main_Part2.bat and Main_Part3.bat. At the end of execution of every batch file, Windows will restart automatically. 6) Optionally you may install local copy of Help update (LangPacks_Help_URLs.txt) and the IE9 language pack (LangPacks_IE9_URLs.txt). PS: It'll take a while to install all 210+ updates. Installing .NET Framework 3.5 SP1 / 4.52 with updates: 1) Download all files from NDP35_45_URLs.txt to the same folder. 2) Unpack the WindowsVistaSP2_x86_Installer.rar or WindowsVistaSP2_x64_Installer.rar (just batch files) to the same folder where you extracted the files. 3) Open a Command Prompt with Administrator privileges and switch to the folder where the update files are. 4) Run NDP35_45_Install.bat, if needed Windows will restart automatically. 5) Optionally you may install a language pack (LangPacks_NDP35SP1_URLs.txt and LangPacks_NDP452_URLs.txt). Installing updates for optional features (only if you have installed IIS, IIS ASP, IIS FTP or Telnet from Program and Features Control Panel extension) Download all files from Features_URLs.txt and run the following .MSU packages if you have installed: IIS: KB4012373 IIS ASP: KB2124261 IIS FTP: KB975254 Telnet: KB960859 and KB3020393
    13 points
  26. I'd rather recommend than listening to the FBI but to upgrade your very unique Brain.exe instead. It's the best anti-virus out there. The only downside is, that Brain.exe can't be bought for money and downloading it is impossible, too. It must be fed proper knowledge to grow. And then one day, you will be capable of using the old operating systems online without running into a wall. Would I recommend to average users who use their brain on other things than computers to use Windows XP and Windows 7 for example? No, because that would put them easily in danger. But if you know, what you are doing, then you'll be able to avoid the problems. Use a hardware firewall, that you can configure. Block unwanted Javascripts. Block everything, you didn't ask for. Don't click on everything that sounds like a promising help to your problems. Learn to read links before clicking on them. These things. Also consider that something like Windows XP got more secure over time, as less and less people were using it. Windows 7 is still a very attractive target for mean hackers with circa 15% market share (2020).
    13 points
  27. Wow, that is quite a timeline you have provided here. Let me first start out by saying thank you ever so much for posting this and giving those that "knew" him some closure. I know @LoneCrusader will probably appreciate seeing this post as well because he and your dad kept in contact a lot and worked on projects together. I'm glad it also helped to get it off your chest as well, so it benefited all of us in the end. I still feel very sad over the loss and in time we will all heal but it sounds like he was quite a trooper through the whole thing but unfortunately just wasn't strong enough to come through. But some of us truly liked your father and he was always welcome here. As a small token of our gratitude, we promoted his account that you're using to the patrons group which is reserved for those who have had a special impact here or retired staff members. We know it's not much but it's all we can really offer along with our most sincere condolences. While you may or may not have much use being here, please be aware that you're certainly most welcome in the community, even if you just want to talk to some of us who were close to your dad. Not a lot of people would have done what you did but I know myself and others will be more at peace with your dad's untimely passing. Again, thank you ever so much for the update!
    13 points
  28. I found that there are ultimately four reasons why Chromium is broken on NT 6.x: 1. New imports in kernel32 and userenv. They can all be stubbed, not hard to fix. (Vista/7; 8.x has them) 2. Use of job object APIs in ways that are only supported on 8.x (without sandbox) and 10 (with sandbox) 3. Use of new NtQueryInformationProcess class for enumerating process handles; if it can't be used, the content process will be terminated (8.0 and below, sandbox only) 4. Use of new DirectWrite factories, like IDWriteFactory3, which was introduced in Windows 10 #1 is taken care of, I'm getting there with #2 and then I should be able to do #3. #4's solution is actually quite simple; copy over a Windows 10 DWrite.dll to use with Chromium using DLL redirection methods (I used 10.0.17763.1 and I think 10240 and up should work too). Then patch these DLL names in the import table with a hex editor or CFF explorer: api-ms-win-core-libraryloader-l1-2-0.dll -> kernel32.dll api-ms-win-core-localization-l1-2-2.dll -> kernel32.dll This is sufficient to run the latest Chromium browser snapshot on Windows 8: Right now there are truly missing functions on Windows Vista and 7, in api-ms-win-core-delayload-l1-1-0.dll and api-ms-win-core-delayload-l1-1-1.dll. Some of those return function pointers so they can't be stubbed.
    12 points
  29. Note regarding versions: The regular version will have a file name ending in _rebuild_#. Versions with a file name ending in _ungoogled disables embedded Google APIs in much the same way that "ungoogled-chromium" ( https://chromium.woolyss.com/ ) disables embedded Google APIs. The "ungoogled" version is recommended for those that prefer tighter control over a Google-based browser basically giving special treatment to Google cookies and violating user preference settings. A side effect to this approach (which also exists in "ungoogled-chromium") is that the Chrome Web Store is intentionally broken only in as far as the "Add to Chrome" button is concerned. This is great for those that prefer to manually install extensions as opposed to obtaining from the Chrome Web Store. A workaround to restore the "Add to" button (special thanks to @VistaLover for this solution) can be obtained from here -- https://github.com/NeverDecaf/chromium-web-store Mileage may vary, for me this only added the "Add to" button but clicking it only downloaded the extensions .crx (which I personally prefer anyway) as opposed to 'adding to' 360Chrome. I had similar results with official "ungoogled-chromium" on the official Chrome Web Store (restores "Add to" button but does not actually 'add to'). Special thanks to @Humming Owl for translated .png files. Special thanks to @Dixel for discussions leading towards the "ungoogled" versions. XP x86 SP2: v12, v13, and v13.5 work as-is in XP x86 SP2 but v11 requires special modifications - see this post by @we3fan Download links for starting from scratch with a NEW PROFILE: Regular: https://www.dropbox.com/s/mes4wez1v34w9k4/360ChromePortable_11.0.2031_rebuild_8.zip?dl=1 (last updated: Jan 9, 2022) https://www.dropbox.com/s/wol8va166au2p7j/360ChromePortable_12.0.1247_rebuild_12.zip?dl=1 (last updated: Jan 11, 2022) https://www.dropbox.com/s/6lnst7yp0dt34s5/360ChromePortable_13.0.2206_rebuild_9.zip?dl=1 (last updated: Jan 11, 2022) https://www.dropbox.com/s/8h4z346251wg7r8/360ChromePortable_13.5.1030_rebuild_6.zip?dl=1 (last updated: Jan 11, 2022) Ungoogled: https://www.dropbox.com/s/6z65t5yo08fr0ym/360ChromePortable_11.0.2031_rebuild_8_ungoogled.zip?dl=1 (last updated: Jan 9, 2022) https://www.dropbox.com/s/j5zxk7aqv9ljjjc/360ChromePortable_12.0.1247_rebuild_12_ungoogled.zip?dl=1 (last updated: Jan 11, 2022) https://www.dropbox.com/s/ld5dz2uwdowf1cz/360ChromePortable_13.0.2206_rebuild_9_ungoogled.zip?dl=1 (last updated: Jan 11, 2022) https://www.dropbox.com/s/glulv6r8sce6xpy/360ChromePortable_13.5.1030_rebuild_6_ungoogled.zip?dl=1 (last updated: Jan 11, 2022)
    12 points
  30. Hi Just made an account here, I have been following threads on this forums ‘anonymously’ for quite some time now, and wanted to share a few words about this. Nothing makes him special, really. For what is worth, I do not like that he did not open source the project. I mean, I don’t know, from my philosophy and point of view, you shouldn’t charge for projects like this, but whatever, that does not matter, I myself ‘donated’ (read: paid) for this software a good few years back as well. Thing is, it takes a lot of time to research these kinds of projects, and yeah, it teaches you a lot, but there is no financial incentive to doing it. Not short term, not long term. So you need to have some spare time which a lot of people do not have much. Like, take security researchers, that do a similar thing, they play around looking with whatever tools they have available to the inner workings of various pieces of software. BigMuscle here did the same for DWM. Yet, security researchers have the incentive that if they find some critical vulnerability, they get paid by Google etc. Hacking DWM serves no one’s business interest, so... you get what I mean. Anyway, developing this kind of software is pretty hard and becomes tedious and boring easily. You work only with closed source code, you have access only to binaries you can disassemble to various degrees and fortunately, for Windows files, Microsoft offers you symbols, which are little pieces of information that augment the binary ‘code’. That’s it, from there on, you have to look and understand all their architecture, how things piece together and so on. This is tremendous work, and even with financial incentives, it takes time, sometimes you get it wrong etc. Also, the appeal to doing this gets even lower because once you publish it, you have to support it, people will like it and demand it gets ‘updated’ with every release of the Windows OS, and in a timely manner of course. And this complicates the initial problem: you have to find ways to patch it in a way that is less likely to break on newer versions, so that you minimize your work when a new update comes. That again, it consumes a few resources, and especially a lot of time. And also, what programmers try to do when they encounter projects like this, is try to reuse old dormant code that’s still in the binary from previous versions, by maybe also looking on binaries from older versions of the software that had what they wanted. It is pretty hard to develop new stuff for a closed source binary with hardly any public interfaces... Now, regarding DWM, it changed quite a bit in Windows 10 2004. A good couple of the methods BigMuscle hooked in pre-2004 are simply not there in the new DWM. Microsoft actually changed a lot of the underlying architecture. What exactly, for what purpose, what is the high level meaning behind it? I did not have time to look enough at it to figure it out. Also, I had a try at this myself as well. I disassembled BM’s Aero Glass a while ago and looked a bit on it a while ago and gathering a few ideas from there, I coded a utility that changed the title bar text in Windows 10 to be centered. “Version 1” was pretty future proof, but had some edge cases which were still problematic, plus it did not do it quite like Windows 8 did it. I researched a lot more and was able to now fix my main issue with it, namely centering the text between the window borders, not the icon and minimize button. But it took considerably more time and effort and hooking to achieve this minor effect. I looked on DWM a bit more (BigMuscle did the same, but probably on way more of it then I did until now) and could ‘easily’ do a lot of stuff. You know acrylic (aka blur behind)? I enabled that on all title bars via DWM, it looks pretty awesome, I’d daily drive that. Imo it looks even better than Aero Glass, but that’s not the point. Point is it can be done, I relatively easily have done it myself, there were some rough edges of course, but I played with it. Some other stuff came up, did not really had time to work on it anymore, at least for the moment. But maintaining the kind of hacks required for releasing a public version of this is insane. People want UIs, configuration etc, for a niche and specialized thing like this, even command line arguments are too much, I’d rather DEFINE some stuff and compile it for each user’s taste. And there also is not a community keen on developing this. A one man army on this is not feasible, but maybe a team, on a public Git could each member write small bits and get somewhere. That’s why I believe, for e.g., that BM better open sourced it. Even in its now broken state with a lot of the code not that useful on newer Windows builds, still, it is a starting point. In a closed binary, without even symbols, it is uselessly lost knowledge, unfortunately, as no one has the time and incentive, as I said, to take a look at it. There are brilliant programmers out there, but this does not pay off that much. Anyway, I write this on mobile. Maybe when I open the PC I could upload a screenshot of my ‘Aero Glass’, but I don’t want to needlessly tease. Because this probably will never ship. An optimistic plan is to integrate this with my previously mentioned tool, but in the state of mess (coding wise) it is at the moment, it may take a while, especially not having a lot of time to work on this. What I can do in the mean time, is leave you a link to WinCenterTitle (https://github.com/valinet/WinCenterTitle), this software I mentioned that centers your title bar text. If you go to releases to download binaries, the latest modifications are in a pre releas version situated there. So that’s the story of it, at least how I see it. Edit: Yeah, also, forgot to say, what is pathetic here is that DWM is closed source, especially considering that third parties cannot really do compositors for Windows. I mean, I blame Microsoft here, it would be so cool to have official, powerful mechanisms to hook into it and do cool stuff. With that, I tell you, in 2 weeks someone will implement, for e.g., the genie effect when minimizing windows and all sorts of crazy stuff. It is pretty much a shame they also have this mess lately (some stuff that should be in DWM is in Explorer for some reason, like Win Tab, Alt Tab, Snap Assist etc) and also do not realistically look forward to collaborating with the enthusiasts; DWM is actually a pretty decent compositor and window manager.
    12 points
  31. Please, be patient, of course, there is going to be the new version soon, bit I'm a bit busy in the current situation.
    12 points
  32. Throughout time, the number of processes to support my empty desktop, with my favorite tweaks and "to work" software: XP: High teens. 100 MB. Vista: 30 or so. 800 MB. Win 7: 34. 1 GB. Win 8.1: 42. 1.2 GB. Win 10: 120. 4 GB. 3x the processes prior versions had to rock, just to get anything done. Says it all right there. No wonder it really doesn't seem to run any better on modern hardware than prior versions did on the best hardware of 7 years ago. And you can't really trim it down any more, for several reasons. Back when we thought Vista, Win 7, and Win 8.1 were bloated, we simply didn't know what True Bloat was. -Noel
    12 points
  33. Thank you, I've been in touch with @LoneCrusader regarding his cotnact with my father. I appreciate what you've done with my dad's account. I have found some source code, lots of it, so I know some of it isn't related to his patches. I'm going to make that stuff available too once I actually have some free time (my life was already busy before all of this). @LoneCrusader mentioned to me that he might have been using a custom compiler which I am unaware of at the moment so it may not just compile nicely. But, I've attached a few of the TRIM named files (and what look like dependencies he had) that I have. I don't know if these are the most recent or even if they are the right ones! BLK13EX.C TRIMCHK.C TRIMCMD.C DISKPORT.C TRIM.C DRIVE.C IDENTIFY.C GETNUM.C
    12 points
  34. ... And I'm so tired reading that same ol' mantra there: As if they (third party software developers) would give one nickel whether someone's setup is secure or not; what is the underlying truth inside this PR talk is that Microsoft themselves make it gradually impossible for third party software developers to target older OSes with their (M$'s) updated Windows SDKs! ... and it always comes down to that! Win7 will soon reach End of Extended Support, hence it'll also be "outdated and unsupported by Microsoft", with no more "security patches"; what is their stance on Win7? Security reasons my... behind!
    12 points
  35. You actually expect anyone here to take you seriously while you continue to maintain a condescending attitude toward roytam1 and everyone else in this community? You can't even speak of these things without lacing it with some ignorant derogatory language or FUD. Emphasis mine. I assume once again that users are intended to believe that "poor modification" is an acceptable definition of "restoring the pre-existing functionality that you intentionally chose to break?" Not one of us here cares one iota whether or not roytam1 has some useless eye-candy website or some fancy branding for his browser builds. What we care about is that they work and that he is very responsive to bug reports and quick to address other issues that may arise on the target platform(s). Yourself and "Moonchild Productions" could do with some lessons from what you find here. When the rest of the world leaves your precious Windows 7 and your "outdated" Mozilla forks, along with their "outdated" addons behind, where will you be? In the same boat with the rest of us. If you expect anyone here to take you seriously, you'd better learn to treat people here with respect whether you agree with them or not.
    12 points
  36. The staff is aware that there are currently spambots sending out private messages to random members here on the forum. We are actively dealing with the situation but if you happen to get one of those spam messages, please do not simply ignore or delete it but use the report system so that we can permaban every account responsible for these messages. Thank you for your patience!
    11 points
  37. Solving BSODs 0xA5(..., ..., ..., ...): Windows XP/2003 supports only ACPI 1.0b syntax, last generation bioses uses ACPI 2.0+ To support ACPI 2.0 syntax need replace acpi.sys and apply additional patches to avoid known BSODs : - 0xA5 (0x03, ..., C0140001, ...) missing ACPI 2.0 syntax, 95% solved, solutions: 1) acpi.sys v.5048, sha1:a09c0d9f6b5cb63192e2cebada56db38d3870b29) from Vista Beta/Longhorn v.5048 Pro: - Has most of ACPI 2.0 syntax opcodes - All integers are 64-bit regarding ACPI 2.0 specification Cons: - beta, compiled for next generation of windows - failed implementation of some internal data types, _ValidateArgTypes generates BSOD 0xA5(0x03, xxx, C0140008, yyy) Patches: - Add pointer to _atDataObj struct for QWord Opcode (_OpcodeTable start at .data:00039848, _atDataObj struct at .data:000397A8, missing pointer at .data:00039880, dont forget add additional relocs) 2) acpi.sys v.6666 based on original Windows XP SP3 v.5512 with integrated acpi 2.0 syntax support Pro: - based on original v.5512, match binary/offsets Cons: - All integers are still 32-bit, any operations on 64-bit fields/variables will drop high part of QuadWord 3) acpi.sys compiled from leaked "XP SP1+W2003 RTM" sources Pro: - allow compile x64 build based on W2003 sources Cons: - same as v.6666 - 0xA5 (0x11, 0x08, ..., ...) unknow error in _AMLILoadDDB, probably fail after parsing DSDT/SSDT table, solved Patch (by Diderius): - Ignore status of _AMLILoadDDB in _ACPIInitializeDDB (v5512 jl short .text:00036214 => nop, nop) - 0xA5(0x03, ..., C0140008, ...) DSDT code have operation with unexpected type of arguments, partially solved This BSOD probably means some argument has datatype, allowed only in ACPI 2.0 v6666 & v5048 support only argument datatypes allowed in ACPI 1.0b specification Patch: - _ValidateArgTypes must always return "OK", even on realy wrong types (mov edi, 0xC0140008=>mov edi, 0x00000000 at head of _ValidateArgTypes) - 0xA5 (0x10006, ..., ..., ...), missing _DIS method for "PNP0C0F"s (PCI Interrupt Link Devices) in DSDT/SSDT table Patch (by Daniel_k): - Skip looking for PNP0C0F in _DisableLinkNodesAsyncWorker, (v5512 call strstr, ..., jz .text:0001BBBD => jmp .text:0001BBBD ) Intel Motherboards specific issues: 1) ACPI BSOD 0xA5 (0x02, ..., ..., ...), error in ACPIRangeValidatePciResources, ACPI vs E820 conflict, solved BSOD is generated by DSDT code like this: DWordMemory (ResourceProducer, PosDecode, MinFixed, MaxFixed, NonCacheable, ReadWrite, 0x00000000, // Granularity 0x00000000, // Range Minimum 0xDFFFFFFF, // Range Maximum 0x00000000, // Translation Offset 0xE0000000, // Length ,, _Y0E, AddressRangeMemory, TypeStatic) ... CreateDWordField (BUF0, \_SB.PCI0._Y0E._MIN, M1MN) // _MIN: Minimum Base Address CreateDWordField (BUF0, \_SB.PCI0._Y0E._MAX, M1MX) // _MAX: Maximum Base Address CreateDWordField (BUF0, \_SB.PCI0._Y0E._LEN, M1LN) // _LEN: Length M1LN = M32L /* External reference */ M1MN = M32B /* External reference */ M1MX = ((M1MN + M1LN) - One) Sometimes M1LN, M1MN, M1MX cannot be calculated properly and this code claim most of memory (E0000000 = 3.7Gb) as motherboard resource, this brings to conflict with E820 memory ranges list Patch: - memory check in ACPIRangeValidatePciResources must always return "OK" (v5512 jz short .text:0001E0BB => jmp short .text:0001E0BB) 2) Device Manager show conflict between Video Card and Motherboard resources Device IOTR(PNP0C02) claim 255 I/O adresses in range 0xFF00-0xFFFE, this range conflict with Video Card I/O range because vga has limitation to 10Bit I/O decoding. solved, two solutions: 1) Manual patching DSDT table, remove this lines inside method _CRS of IOTR device, so _CRS will return empty Local0: If ((ITS0 == One)) { ConcatenateResTemplate (Local0, BUF0, Local1) Local0 = Local1 } If ((ITS1 == One)) { ConcatenateResTemplate (Local0, BUF1, Local1) Local0 = Local1 } If ((ITS2 == One)) { ConcatenateResTemplate (Local0, BUF2, Local1) Local0 = Local1 } If ((ITS3 == One)) { ConcatenateResTemplate (Local0, BUF3, Local1) Local0 = Local1 } 2) Patch acpi.sys with injecting special code to override IOTR template buffer: In _Buffer opcode handler replace: mov eax, [ebx+14h] mov ecx, [ebp+arg_0] to call Check_IOTR_Buffer ... Check_IOTR_Buffer: cmp eax, 0Ah ; eax - size of buffer jnz short Skip mov eax, [ebx+30h] mov eax, [eax+10h] ; eax - buffer cmp dword ptr [eax], 00000147h ; need matching all 10 bytes jnz short Skip cmp dword ptr [eax+4], 0FF010000h jnz short Skip cmp word ptr [eax+8], 0079h jnz short Skip mov byte ptr [eax+7], 0 ; MAIN ACTION, set i/o range to 0 instead 255 Skip: mov eax, [ebx+14h] mov ecx, [ebp+arg_0] ret IOTR template defined as: Name (BUF0, ResourceTemplate () { IO (Decode16, 0x0000, // Range Minimum 0x0000, // Range Maximum 0x01, // Alignment 0xFF, // Length _Y21) }) in bytecode: 11 0D 0A 47 01 00 00 00 00 01 FF 79 00 3) No CPU power saving, most time CPU in C0 state even without cpu load Some part of acpi hardware is disabled, so CPU should not use nonexistent ACPI C2/C3 power savings, solved, two solutions (intelppm.sys): 1) C2/C3 States => C1 State : - in _InitializeAcpi2IoSpaceCstates replace offsets AcpiC2Idle and AcpiC3ArbdisIdle to offset AcpiC1Idle 2) C2/C3 States => C7+ States (default Windows 7 power saving mode, DPC Latency Checker shows significal increased latency in this mode): Replace Acpi2C3ArbdisIdle to: push ebx mov ebx, ecx push esi push 0 call _KeQueryPerformanceCounter mov [ebx], eax mov [ebx+4], edx mov eax, offset DummyMon xor ecx, ecx xor edx, edx monitor mov ecx, 1 mov eax, 60h mwait push 0 call _KeQueryPerformanceCounter mov [ebx+8], eax mov [ebx+0Ch], edx xor eax, eax pop esi pop ebx retn DummyMon - any unused 4 byes in .data segment Replace Acpi2C2Idle: push ecx push 0 call _KeQueryPerformanceCounter mov ecx, [esp+4+var_4] mov [ecx], eax mov [ecx+4], edx mov eax, offset DummyMon xor ecx, ecx xor edx, edx monitor mov ecx, 1 mov eax, 33h mwait push 0 call _KeQueryPerformanceCounter pop ecx mov [ecx+8], eax mov [ecx+0Ch], edx xor eax, eax retn 4) Programs show wrong timing results/works only first 3.5 sec Windows XP SP2+ uses disabled acpi timer, solved Skylake+ bioses by default disable ACPI hardware timer (register "ACPI Timer Control (ACPI_TMR_CTL)" in southbridge, see PDF), but WinXP SP2+ still uses disabled acpi timer for getting incremental time counter (acpi spec declare this counter as part of specification). WinXP detect existing this timer by checking special bit USE_PLATFORM_CLOCK in FACP ACPI table, modern bioses still set USE_PLATFORM_CLOCK=1 in acpi (mistake by programmers / inform Win7+ about existing HPET timer (not acpi timer!)) Patch (by Diderius) "HAL_acpitimer_fix" to use CPU TSC counter as performance timer/counter: - in HaliAcpiTimerInit force to ignore USE_PLATFORM_CLOCK and receive it always =0 (v.5512 jns short PAGE:8002934B => jmp short PAGE:8002934B) Compatibility fix ("HAL TSC frequency divider") Some programms do wrong calculation with high values of PerformanceCounter/PerformanceFrequency (HAL_acpitimer_fix set values to cpu freq), to avoid this problem values need to divide to much lesser value, Windows 7 just divide it to 1024, so timer frequency on 3600Mhz cpu is only 3.51Mhz Patch: - divide to 1024 values of PerformanceCounter/PerformanceFrequency, replace _HalpAcpiTimerQueryPerfCount to: 5) No driver for Intel SATA Controller - BSOD 0x7B(..,..,..,..) Windows XP/2003 support SATA controllers only in Legacy IDE mode, modern Intel chipsets has only AHCI mode, solved, many solutions: 1) Intel RST AHCI/RAID 11.2.0.1006 (iaStor.sys) 2) Intel RSTe AHCI/RAID 4.7.0.1098 backport by daniel_k (iaStorA.sys+iaStorF.sys) 3) StorAHCI by skulltera/OneCore (storahci.sys), compiled from Microsoft Windows 8.x DDK Samples, (require storport.sys from Windows 2003) 4) UniATA (opensource) 5) Intel RSTe AHCI/RAID 4.0.2.1019, for Windows 2003 only, enterprise controllers only(??) (iaStorA.sys+iaStorF.sys)) 6) StorAHCI from Windows 8 (require backported storport.sys from Windows 8) 7) StorAhci for Windows 2003, based on Microsoft Windows 8.x DDK Samples source code, https://sourceforge.net/projects/storahci-for-windows-2003/ Tip: Add PCI\VEN_8086&CC_0106 or PCI\VEN_8086&CC_010601 to *.inf as universal DEV_ID for any Intel AHCI Sata Controller AMD Motherboards Issues ACPI BSOD 0xA5 (0x0000000D, ..., ..., ...) duplicated _HID method Patch: - Skip DetectDuplicateHID processing (v5512 .text:00013F6C => jmp .text:00013F6C) BSOD 0x7E (..., ..., C0000005, ...) unknow error in AcpiArbCrackPRT Patch: (v5512 jnz short .text:0001BD6D => jmp short .text:0001BD6D) Intel USB3 Controller Drivers Intel released USB3.x drivers only for Windows 7/8/10, so there were many attempts to use drivers of other usb chip manufacturers. Most of them do not work at Intel hardware, some works, but have problems with PAE or USB3 ports. Following drivers confirmed to work in normal and PAE environment, solved, three solutions: 1) Microsoft Generic v6.2.9200.16384/v6.2.9200.22453 from Windows 8.0, recommended driver 2) AMD v1.1.0.0145 (need amdxhci_adresscalc_fix) 3) Fresco Logic v3.6.9.0 (extended to 32 ports) AMD and Fresco drivers have ssues with recognizing devices after plug<->unplug, sometimes ports go to power saving modes and can't back UAS (Attached SCSI Mass Storage) drivers also available, solved, many solutions: 1) UAS Driver from Windows 8 + storport.sys from Windows 2003, beta 2) UAS Driver from Windows 8 + storport.sys from Windows 7, beta 3) UAS Driver from Windows 8 + storport.sys from Windows 8, beta 4) VIA UAS Driver 5) Etron UAS Driver VIA and Etron UAS Drivers doesn't support Safe Remove, require fixes, solved (via_uas_fix, etron_uas_fix) By default VIA and Etron UAS works only with genuine vendor USB3.0 Driver, but they are generic(?) and can work with any USB3 driver vusbstor.inf: change USB_VIA\Class_08&SubClass_06&Prot_62 to USB\Class_08&SubClass_06&Prot_62 EtronXHCI.inf: change ENUSB\Class_08&SubClass_06&Prot_62 to USB\Class_08&SubClass_06&Prot_62 Patches for Microsoft Generic USB3 driver Windows 8 USB3 driver always report USB2 speed on inserted USB3 devices, MS call it "compatibility", but vendors driver report proper USB3 speed and dont have compatibility issues(?) Fix to report proper USB3 speed, usbhub3.sys (v6.2.9200.21180): .text:19C58: jnz 00019C63 => jmp 00019C63 (75 09 => EB 09) Patch for AMD driver (amdxhci_adresscalc_fix) This driver is known to have issues with PAE environment, need fix: - replace in amdxhc.sys: mov ecx, [esi+458h] ; esi+458h = store of 64bit adress mov eax, [esi+28h] mov [eax], ecx ; low part mov [eax+4], ebx ; dropped high part, ebx=zeroes..... to mov ecx, [esi+458h] mov eax, [esi+28h] mov [eax], ecx mov ecx, [esi+45Ch] ; HIGH part of 64bit mov [eax+4], ecx ; no more zeroes Patch for VIA UASP driver (via_uas_fix) Restore "Safe Remove": - replace in vusbstor.sys (v6.1.7600.4002): page:000209B4: mov [ebp+SurpriseRemovalOK], ebx -> NOPs (89 9D 70 FF FF FF 89 9D 68 FF FF FF => 90 90 90 90 90 90 89 9D 68 FF FF FF) Patch for Etron UASP driver (etron_uas_fix) Restore "Safe Remove": - replace in EtronSTOR.SYS (any version): OR dword ptr [eax+4], 0300h -> OR dword ptr [eax+4], 0000h 4GB+ RAM Support - Windows 2003 supports more than 4Gb RAM without additional actions, limited to some value depending "Edition" - Windows XP ServicePack1 supports more than 4Gb RAM without additional actions, limited to some value (16Gb ?) - Windows XP ServicePack2/3 don't support RAM above 4Gb, need patching, solved, many solutions: 1) PatchPae(v2) by wj32, remove limits only in kernel, lack of HAL_DMA patch 2) fix128/PatchPae(v3) by Evgen_b, contains unfinished HAL_DMA patch, kernel patch is OK 3) WinXPPAE(v2+) by Daniel_k, contains proper HAL_DMA patch, kernel patch is OK UEFI Boot - Bootmgr from some Vista Betas/Longhorns allow boot Windows XP x64 from UEFI x64, alpha, there is issues with Video card, https://www.betaarchive.com/forum/viewtopic.php?f=61&t=20327 - Boot Windows x32 on UEFI 32 UEFI32 on real hardware is rare, confirmed only on emulated environment, alpha, Guide LINK by Gelip - Quibble bootloader (experimental, opensource), alpha, no NTFS support, booting possible only if Windows installed on FAT partition, project page - https://github.com/maharmstone/quibble NVMExpress Drivers Many solutions: - Modified OFA 1.3/1.5 driver + storport.sys from Windows 2003 - MS Windows 7 NVMe Driver by daniel_k + backported storport.sys from Windows 7 - MS Windows 7 NVMe Driver + storport.sys from Windows 7 + Emu_Extender - Samsung NVMe driver + storport.sys GPT partitions Windows 2003 already supports GPT Partitions for non-booting disks, no need additional software Windows XP doesn't support GPT Partitions, solved for non-booting disks, one solutions: - Paragon GPT Loader enable access to 3TB+ Disks/GPT partitions (commercial product, currently not available for sale) Booting from GPT disk partially solved, need convert pure GPT to HybridMBR, Guide LINK by Levvon Saving crash dumps through storport based disk controller drivers To enable saving crash dumps with storport-based disk drivers on Windows XP need patch kernel (scsi support will be disabled) Disk Controller drivers written for Windows 8 mostly will not save crash dumps on disk, they use new API to get information from kernel about dump context List of patches: 1) IopGetDumpStack: Replace unicode string "scsiport.sys" to "storport.sys" This string is 3rd argument of "call _IopLoadDumpDriver@12" 2) IopGetDumpStack: Original XP kernel will disable loading storport emulator(diskdump.sys) if storport/miniport return "Device Object" This is not problem for Windows 2003/7/.., newer OS still load diskdump.sys even if storport/miniport return anything Replace "mov [ebp+ScsiDump], 0" with NOPs Example for ntkrpamp.exe v5512: PAGE:004A0E0F mov byte ptr [ebp-29h],0 -> NOP, NOP, NOP, NOP ]3) IopGetDumpStack: Storport doesnt use SCSI ports names and dont need to search name of driver, need to skip this block Example for ntkrpamp.exe v5512: in range PAGE:004A0F49-004A1018 replace first opcode with "jmp 4A1019" 4) Use diskdump.sys from Windows 2003 or Wondows 7 (Windows 8 version not tested) 5) IoInitializeCrashDump: XP kernel allocate for diskdump.sys buffer of 32Kb (same size in Windows 2000), diskdump.sys from Windows 2003+ expect buffer of 64Kb. To be compatible with new diskdump.sys need to increase buffer Replace "push 8000h" with "push 10000h" as 3rd arg of ExAllocatePoolWithTag call Modded AVX/AVX2 kernel Currently Proof-Of-Concept, only one kernel version supported LINK Projects for Developers/Advanced Users - Remote kernel debug over LAN or USB3 cable, https://github.com/MovAX0xDEAD/KDNET - ACPI DSDT/SSDT Patcher at boot time for any windows, https://github.com/MovAX0xDEAD/ACPI-Patcher - WinXP/W2003 ntoskrnl.exe Emu_Extender, https://github.com/MovAX0xDEAD/NTOSKRNL_Emu, https://msfn.org/board/topic/181615-ntoskrnl-emu_extender-for-windows-xp2003/ Research & Experiments Running Windows XP with "new generation" ACPI.sys taken from many Vista Beta/Longhorn version Running existing USB3 vendor's drivers on Intel USB3.0 controller Implementation of ACPI Timer/HPET on different windows generations Switching between DMA32/DMA64 under PAE Environment, Windows XP Switching between DMA32/DMA64 under PAE Environment, Windows 7 Unresolved Problems/Requested Features: - ACPI.SYS v.6666 lack 64-bit integers - ACPI.SYS v.6666 limits possible datatypes in arguments only to ACPI 1.0b Specification - Boot Windows XP/2003 x32 from UEFI x64 - Generating TRIM command for SSD in filesystem (NTFS/???) - Internal GPT support for x32 Windows XP by replacing disk.sys/partmgr.sys/??? from Windows 2003 - Boot Windows x32 XP/2003 from pure GPT - Restore full Windows XP SP1 implementation of PAE/DMA for Windows XP SP3 - Generic/Universal HDA Audio driver - CSM Emulator for UEFI x64 - DirectX 10/11 kernel support - NDIS 6.x for Windows XP/2003
    11 points
  38. Finally got the time to create the much requested Update Repository for Vista. I've collected these updates a year ago, but only recently took the time to put them on my Mega account and organize them. It has roughly the same format as my post-EOL repositories, with x86 and amd64 versions. A few highlight points: Most updates come in ".cab" format, because at the time it was easier to manage bulk installations in this format (I was trying to update offline images) Includes hotfixes not distributed through Windows Update. These were collected through a mix of the now defunct MS Hotfix service and the website "hotfixshare". There's some interesting fixes in there. While most of the updates are language agnostic, some are specific to the language I use, Portuguese of Portugal (like the IE9 installer). If you'd like to provide a version for your language, please contact me. To install a ".cab" format update, just run the following command: start /w pkgmgr /ip /m:<path to updates> /s:<temp path for extraction> /l:<path for log files> /norestart To bulk install updates, I usually run the following set of commands: forfiles /p <path to update folder> /m *.cab /c "cmd /c mkdir @fname" forfiles /p <path to update folder> /m *.cab /c "cmd /c pkgmgr /ip /m:@file /s:@fname /norestart" The first command creates a folder for each individual update and the second one installs each update and extracts onto each created folder. Here's a practical example. Say, I have all of the updates from the repository located in my Downloads folder inside my user profile. In this case, I want to install every update in the "General" folder. I'd use the commands above like so: forfiles /p "C:\Users\greenhillmaniac\Downloads\General" /m *.cab /c "cmd /c mkdir @fname" forfiles /p "C:\Users\greenhillmaniac\Downloads\General" /m *.cab /c "cmd /c pkgmgr /ip /m:@file /s:@fname /norestart" I'd recommend you install no more than 200 updates at a time. This can also be used to create an updated Vista ISO for later use (tutorial coming soon™) Anyway, here's the link for the repository
    11 points
  39. New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20221203-3219d2d-uxp-74a139ee2-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20221203-3219d2d-uxp-74a139ee2-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20221203-3219d2d-uxp-74a139ee2-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20221203-d849524bd-uxp-74a139ee2-xpmod.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20221203-d849524bd-uxp-74a139ee2-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win64-git-20221203-d849524bd-uxp-74a139ee2-xpmod.7z Official UXP changes picked since my last build: - Issue #2036 - Prevent GTK color picker from being frozen when launched from a modal XUL window (6d6d149b6) - Issue #2030 - (chore) refactor event dispatch functions (4d310562d) - Issue #2030 - Allow child nodes of button to participate in mouse hit tests (4354c7a1b) - Issue #2030 - Pref-gate default button event dispatch logic (3f073056d) - Issue #2030 - Dispatch click on common interactive ancestor if mousdown/up are not on the same element (b4dd10626) - Issue #2022 Follow-Up - Add autorelease to our manual NSView to prevent potential leaks. Also move titlebar overrides from BaseWindow to ToolbarWindow... This caused problems in Waterfox Classic on Ventura, while this didn't seem to be necessary in UXP... There is no need for those overrides in BaseWindow, so why risk potential problems. https://bugzilla.mozilla.org/show_bug.cgi?id=1576387 https://github.com/WaterfoxCo/Waterfox-Classic/commit/d7f5814dc089f615385a00db4dfe187c6aefa1af (e10eeed77) - No Issue - Fix building ldap on MacOS. Discovered this problem building Epyrus on MacOS, based on this Mozilla Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1652906 (7354cde3e) No official Pale-Moon changes picked since my last build. No official Basilisk changes picked since my last build. Update Notice: - You may delete file named icudt58l.dat inside program folder when updating from old releases. * Notice: From now on, UXP rev will point to `custom` branch of my UXP repo instead of MCP UXP repo, while "official UXP changes" shows only `tracking` branch changes.
    11 points
  40. We are working with one of our friend from far East, Their soon gonna be a newer Chrome on XP , I will replace Boring SSL with OpenSSL [No need of Proxy for TLS1.3 and ECC] and port Angle Library to DirectX 9[ Smooth Scrolling] , He already got Chromium 92 working. Please Kindly have patience and i cannot reveal more as per my promise to him. Dont ask me when it is coming , but it is coming.
    11 points
  41. Hello everyone. Glad to see MSFN is still online! I'm happy to announce that the list has been migrated over to the Eclecboard forum. Huge thanks to my best friend @docR for migrating it for me to his forum and making sure all the formatting is correct. Here's the link to the sister thread on EclecBoard: https://forum.eclectic4un.me/viewtopic.php?f=27&t=113 Don't worry, I will continue to update the list on MSFN & EclecBoard for as long as both forums remain online. I am going to resume updating it again soon as I've been extremely busy in my personal life lately (and thankfully am now in a healthy, loving relationship ). After leaving the toxicity I was in before, I feel much better and have regained interest in Vista and the list again and hope to get everything squared away with it within the next couple of weeks, as there's going to be a LOT of new changes made since October 2020... Hope everyone is doing well!
    11 points
  42. - Windows NT 5.x family windowsupdate.com links for available languages, including all (any?) Custom Support Updates - The updates links are grouped for each build, slightly sorted, and ordered lexicographically per update number or file name as possible - Superseded (replaced) updates are not filtered or excluded - The dump is available as csv files containing updates name and url, or plain text files containing updates url - It's recommended to use CSVFileView to check the csv files https://www.nirsoft.net/utils/csv_file_view.html - You can filter or extract updates for certain language using findstr (Vista or 7) e.g. findstr /i \-enu NT_5.2.3790-x64-Custom.csv > NT_5.2.3790-x64-Custom-enu.csv however, few update have different language identifier or none, so it's best to review the whole file first - NT_5.1.2600-x86-SP2-Custom and NT_5.1.2600-x86-SP2-Custom-IE are ment for the EOS Windows XP SP2 x86 only - NT5-ia64 is for Itanium-based Server 2003 / Windows XP - .NET Framework packs and updates for NT 5.1/5.2 are in a separate list files, likewise Windows Media Player and some eXtra updates # P.S. Maybe it's best not to post the links explicitly in the forum replies or text sites (pastebin, txtuploader..), and share them in the txt/csv files # Download https://gitlab.com/stdout12/adns/uploads/9ca06a12dd08c06edd889e65afa637fa/NT5_WU_URLs_csv.7z https://gitlab.com/stdout12/adns/uploads/33fcfd0b0f6c1a0cb74472cb8407800d/NT5_WU_URLs_txt.7z
    11 points
  43. I think there is more to the old operating systems than just internet. These machines are resources of creativity with the tools, that run on them. Writing programs, graphic programs, music programs, programming tools... even if there would be no internet at all, the old computers are capable of plenty of things. I can work best with the tools that I know best, which are the old tools. Okay, the resolution may not be the highest. But as long as the hardware runs (whose spare parts cost 0 money on the scrapyard)... it would be an uneconomic choice to switch. Consider the time you need to learn new programs! Speaking of Linux? Fantastic for modern internet browsing, but not if you need special tools. Sometimes, the Linux counterparts are poorly designed, too. LibreOffice will never perform as good as Word 97. In fact it performs worse every year! On limited hardware we have to add. My decision is set in stone. Windows XP until repairing the hardware gets expensive. On to the future with Windows XP!
    11 points
  44. FWIW, there's nothing "standard" about NM27 here ; to add to what Mathwiz has posted: "Pale Moon" is an upstream browser application, which has a GUI from the pre-Australis Fx era; also, members here must understand the distinction between platform and application (Mozilla are the ones to blame for this confusion, because they had equated the Mozilla platform, not used solely by Fx, to their main browser, Firefox) ... When PM was at its major version 27 (did not support XP, Vista support was rudimentary), the platform it was built on was called Tycho, a fork of the Mozilla ESR 38 platform - the browser engine of PM27 was called Goanna version 3. The roytam1 fork derived from PM27 was/is New Moon 27 (NM27) ; as the web became more-and-more Googl-ised , PM27/Tycho started being crippled at loading many popular sites, so "upstream" (MCP) abandoned the Tycho platform and moved on, first to UXP Take 1 (aka Moebius), forked from a Mozilla 53.0a1 platform snapshot, and soon after to UXP Take 2 (just UXP now), forked from Mozilla ESR 52[.6] platform; PM27 became PM28; Pale Moon is currently at v33.0, but it's still built on UXP; both the paltform (UXP) and the browser application (PM) are being developed independently from Mozilla/Firefox... When upstream (MCP) abandoned Tycho (and PM27), roytam1 chose to keep his forked platform and browser (NM27) for the sake of Win2k/XP users on very old H/W, that doesn't support the SSE2+ instruction set ; as of this writing, NM27 and its browser engine, Goanna 3, is being "updated" based on a new "upstream", the developer (rmottola) behind the Artic-Fox project; this project aims to develop a (semi-)usable browser on old Macs, unsupported by Apple and the mainstream browser vendors; the project strives to "uplift" the browser from a Mozilla 38 platform snapshot (like in PM27/Tycho) to more recent versions, hence the large number of weekly updates (there's a lot of catching-up to do when you're still at a Fx mid-40s level) ... Also, Arctic-Fox isn't New Moon 27, hence several bugs that plague the latter are being reported by (the few?) NM27 users... To put it bluntly, I have now no need for this fork, because its web-compatibility is severely impaired in 2024; in addition to that, Roy is publishing SSE-compatible builds of NM28+St52, so if your old H/W can cope, it's advisable you use these instead of NM27... NM27 has inherited from PM27 a "status-4-ever" internal component, but as the platform is being updated by rmottola to Fx43+, this component has been partially BROKEN, breaking with it several download-related functions/extensions/userstyles/userscripts etc.; I have kept, for archival purposes, a NM27 build from 20220812, which seems to be the last with no such issues... As for NM28 (and St52), this is being updated mostly by backporting MCP code, especially in the platform aspect of it, and occasionally PM-specific (and Bk-specific) code is also being backported; and don't let the appVersion (28) confuse you ; Roy, for reasons he has explained in the past, decided to "freeze" the major version at 28, but latest NM28 embeds platform code to be found even in the latest PM33 "official" release ...
    10 points
  45. New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20230805-3219d2d-uxp-65de5a7185-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20230805-3219d2d-uxp-65de5a7185-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20230805-3219d2d-uxp-65de5a7185-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20230805-d849524bd-uxp-65de5a7185-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20230805-d849524bd-uxp-65de5a7185-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20230805-d849524bd-uxp-65de5a7185-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20230805-d849524bd-uxp-65de5a7185-xpmod.7z Official UXP changes picked since my last build: - Issue #2026 - Part 1 - Implement BigInt64 and BigUint64Array. https://bugzilla.mozilla.org/show_bug.cgi?id=1456569 (b64643e410) - Issue #2026 - Part 2a - Support BigInt in NumberFormat and toLocaleString. https://bugzilla.mozilla.org/show_bug.cgi?id=1543677 (d972016c23) - Issue #2026 - Part 2b - Format BigInts representable as int64_t without first converting them to strings. https://bugzilla.mozilla.org/show_bug.cgi?id=1543677 (3ce9cf4deb) - Issue #2026 - Part 3a - Add support for BigInt in devtools. (Server side) https://bugzilla.mozilla.org/show_bug.cgi?id=1527867 (e861cd3b3a) - Issue #2026 - Part 3b - Add BigInt Devtools support. (legacy frontend) (61efc86b21) - Issue #2026 - Part 3c - Add BigInt Devtools support. (new frontend) (9042881cea) - Issue #2026 - Part 4 - Fill in missing dense elements case and fix a comment. https://bugzilla.mozilla.org/show_bug.cgi?id=1456569 Skipped this during the initial implementation, not sure when or if this code path is used, but I figure it should be there just in case. Also fix debug builgs by removing an no longer valid MOZ_ASSERT. (b7e487bdf1) - Issue #1240 - Follow-up: Fix incorrect values in Number() constructor. https://bugzilla.mozilla.org/show_bug.cgi?id=1466893 Our code base was using the return value to create the Number object. However with the BigInt changes, it is no longer stored in rval, use args[0]. (df03810723) - Issue #1240 - Follow-up: Add missing JSVAL_TYPE_BIGINT cases in JitFrames.cpp. As pointed out by roytam1 during testing with Discord. (5c3cedb141) No official Pale-Moon changes picked since my last build. No official Basilisk changes picked since my last build. Update Notice: - You may delete file named icudt*.dat inside program folder when updating from old releases. * Notice: From now on, UXP rev will point to `custom` branch of my UXP repo instead of MCP UXP repo, while "official UXP changes" shows only `tracking` branch changes.
    10 points
  46. The fact that Feodor has been able to do as much as he has, given the circumstances, is truly incredible. I admire his dedication and enthusiasm for the projects he's worked on over the years...his 'old' MyPal (29.3.0) is still one of my primary daily-use browsers in XP, and it's been very exciting to see the progress that has been made so far on the newer 68. He's one talented coder, as his 'resurrected' MyPal 68 has proven...it's a shame to look back on that whole fiasco nearly one year later, because the Pale Moon developers had an opportunity to take the highest of high roads by inviting Feodor to work with them and even help them restore official compatibility to benefit XP/Vista users, but instead they fought and alienated him and many others. In a more ideal world, there would have been a mutual respect that could have led to a long-term partnership, maybe even a friendship. I'm genuinely praying for him, his family, and all of his friends...and of course, I'm keeping Roy in my thoughts too as he's in Hong Kong. They both come from places that have been through so much, especially in recent times. To Roy and Feodor: thank you both VERY much for everything you have done. Your efforts have never, ever been in vain.
    10 points
  47. GOOD NEWS EVERYONE! Thanks to @Osman Kovan for figuring out how to install Microsoft .NET Framework 4.8 on Windows Vista, I was able to use that same method to install Microsoft .NET Framework 4.6.2 Final on Windows Vista. I just extracted the setup .exe file with 7zip and ran the .MSI installation file contained within it, netfx_Full_x64.msi: After installing, I then tested ShareX Portable to see if it gave the same missing dependency errors that it does when running it with .NET Framework 4.8 Preview installed, and to my delight, it works just fine in Vista with 4.6.2 Final! Remembering what @VistaLover asked me to try with 4.6.2 Preview installed, I then decided to try the latest .NET Framework 4.6.x security rollup for Windows Server 2008 to see if it would patch .NET Framework 4.6.2 Final on Vista, and, lo and behold: It works! This means that .NET Framework 4.6.2 Final CAN be installed and patched on Windows Vista using @Osman Kovan's installation method, and then by downloading the .NET 4.6 patches for Server 2008 manually from the Microsoft Update Catalog. As such, Microsoft .NET Framework 4.6.2 Preview has been replaced with the final version on the list: Special thanks to @VistaLover, @Osman Kovan, and @artomberus for helping make this possible!
    10 points
  48. I have yet to see any evidence of these supposed "misguided people." We have only your word on the subject, which, given your general behavior and attitude, is not necessarily reputable. If one takes the source code for a given program (X) and re-compiles it targeting another platform (Y), how is it NOT "X for Y"? These programs are open source. If someone chooses to recompile them targeting a different platform, they have every right to do so, whether you like it or not. Good luck switching to "closed source," drop back by in a few years when you reach a closed-source state equivalent to the current open-source one you "leeched" from Mozilla. I've seen how you deal with these "poor ___ Linux builders" as you refer to them. You drop in, make demands and threats, create a general atmosphere of negativity that poisons the waters and turns everyone off, all the while hoping that no one stands up to your bullying. Most people eventually give in and give up, not willing to deal with your constant attacks. I'm afraid that modus operandi will not work here. I know for a fact that roytam's New Moon 27 builds are in fact named "New Moon" and not "Pale Moon" and do include a disclaimer on the About dialog that states the build is unofficial and specifically says not to request help on the official Pale Moon forum or otherwise. This thread is also mentioned. So what more do you expect? If the supposed "misguided people" you refer to are too ignorant to read and abide by these disclaimers then nothing else is going to stop them either. In the end all of these programs, including yours and those of Moonchild Productions, descend from Firefox or other Mozilla sources. The "chain of descent" is there, and it is not going away because someone changes a name or writes a disclaimer. Even if the name were changed, what happens when someone simply asks "what is this based on?" When the answer is given no one can control how others may use that piece of information to seek out the project's "upstreams." Even after all this ranting you still have not made any set of concrete "minimal acceptable changes" from your point of view. You keep changing them based on your level of annoyance each time you post. First it's change a name. Then it's full branding. Then "unofficial branding" is OK. Then it isn't. You noted at one point that mentions of the original names would be necessary for "profile compatibility reasons." Now, "ALL THE ORIGINAL NAMES MUST GO!" This is beyond ridiculous. Maybe roytam isn't a good graphics artist? I myself certainly wouldn't want to have to undertake the task of creating new "branding" that is worthy of the underlying code here. I'm no programmer, but I would take bets that changing the names and such would also create more headaches for roytam and his users in the fact that this could cause Addons and other associated applications to not recognize roy's builds, thereby forcing him or his users to manually modify every single Addon or associated application in order to get it working as it should. If my assumption of this is correct, what reasonable person with a life and better things to do who would choose this path? I'm sorry, but no truly serious user of these builds has any confusion whatsoever about what they are using. If the official installer(s) won't run on your non-supported platform and you had to get a build from here, that's self explanatory. And, if you're running on a supported platform where the official installer(s) work, that's self explanatory as well, and why would you come here in the first place? Covered this above, but once again - "If one takes the source code for a given program (X) and re-compiles it targeting another platform (Y), how is it NOT "X for Y"?" You "don't want to hear" these things because you don't like the fact that someone had the gall and took the time to compile your project for a different target platform that you disapprove of. That's the beauty of open source. Also once again - "Good luck switching to "closed source," drop back by in a few years when you reach a closed-source state equivalent to the current open-source one you "leeched" from Mozilla." See above about causing issues with Addons and associated applications. You claim that there is some "advantage" in the changes you are demanding when it seems more likely that this will only create more work for the developer. I see no advantage whatsoever to be gained by these projects from your suggestions, only that you just want things your way. I don't speak for roytam, but if I were in his shoes I would be all the less inclined to acquiesce to any of your demands simply based on your behavior. You have chosen to act in a condescending and demanding manner laced with threats to keep throwing roadblocks in the way of or create problems in any way possible for roytam's projects. On the other side, you create more annoyance for yourself by coming here and ranting about supposed "misguided users" who are troubling you, when it would be simpler (and probably better for your health) just to tell them off and go on about your day. You appear to thrive on creating a negative environment and beating dead horses. And, in the end, if you decide to try and make good on your threats then you will create more work for yourself in rewriting closed-source code to replace the open-source code you "borrowed" but don't like others "borrowing." Based on this and in the interest of civility I will state that I believe this "discussion" is never going anywhere. Please stop wasting everyone's time with your threats, condescension, and negative attitude. These will get you nothing here, except an end to OUR "diplomacy."
    10 points
  49. Hmm.. let's see. "Not doing a good job" could easily be defined as "breaking things that already work." For example existing code support for older operating systems. Nice and simple. I fail to see how roytam's software is "abused," give that he is actually fixing things you or Moonchild have broken, on purpose. See above. No one claimed they are official. In fact the About dialog in these builds clearly states they are not. "Not doing a good job" again..? See above. I'd like to see some proof of this supposed "massive confusion." If there is any confusion, it must come from those who are clueless in the first place. You cannot fault roytam for users who are too ignorant to read the About dialog or to deal with any issues here, where the builds are linked, rather than going to you or to the official PaleMoon forum. Also I'd love to see even one example where you or Moonchild or anyone else in your "group" has "cleaned up a mess when something goes wrong" that addressed the first single issue that affected these older operating systems or users of the unofficial builds on these systems. It sounds more to me like you're just a butthurt jerk who is having a tantrum because someone is making your toy work in places where you don't want it to. If you don't like it, write your own closed source program and stop "abusing" Mozilla's existing code. Without Mozilla's existing code, which once again I will remind you already provides compatibility for the systems roytam is targeting, and which you have intentionally broken, your pet projects would be nonexistent.
    10 points
×
×
  • Create New...