Wine 10.10 claimed that a 32bit #Delphi app was 16bit. After hunting down that issue(Wine source, WINEDEBUG=+all) I found a very old Delphi component pack that imported FreeLibrary16 from kernel32.dll via index 36. Wine redirects this to krnl386.exe16, in Windows=>wrong function
It took me almost 2h to realize that the newest Windows 11 update changes the color of the drive usage bar in Explorer. And I thought some program, I recently installed, was the culprit and I tried to get the lighter blue color (RGB 38,160,218) back. (New color: 0,112,203).
AMD's Chipset Driver installer still requires you to have the "VBScript" feature installed, otherwise it tells you that you don't have an "AMD system" and fails. Maybe somebody should tell @AMD that Microsoft has deprecated VBScript and is going to remove it from Windows 11.
Sometimes I really wonder what #Delphi "thinks" by generating such unnecessary push/pop code.
mov eax,[ebp+$08]
add eax,ebx
push eax ??????
pop eax ??????
xor edx,edx
div esi
or ecx,eax
While trying to apply that patch to the various Delphi versions, I found out that starting with Delphi 10.0, the IDE already can handle large (>2GB) addresses and also the 2 address-calc bugs in the compiler were fixed. Providing the patch only for old IDEs makes it much easier.
Will there ever be a 64bit Delphi IDE or at least a LargeAddressAware version. Our Projekt crashes the IDE between 14-18 compilations because it runs out of memory. Maybe I have to patch the IDE myself by moving all .NET and Compiler memory allocations above the 2 GB address.
Delphi compilers that are supported by IDEFixPack need an address calculation fix in IDEFixPack (only fails if LargeAddressAware is enabled). And newer Delphi compilers inherited that bug from IDEFixPack and need a new patch.
@dalijap That only helps for the compilation, but if you use code completion, ErrorInsight or the debugger, it still runs OOM. And in Delphi 2009 that option doesn't exist. I patches D2009 years ago to support it, but that had almost 0 effect. The project is simply to large for the IDE.
@TommiPrami That's why I only want to use the upper address space only for the .NET code (ErrorInsight), which certainly has no code that fails if it is above 2GB, and the Delphi compiler, which I may be able to patch to work above 2GB.
Eventually I found time to build the binary JCL and JVCL installers for #Delphi 11 Community Edition. Don't ask for Delphi 12, there is no Community Edition yet.
https://t.co/PLkiqeMGyP
Netflix's web page in Edge with an active fTPM (AMD) is unusable. Chrome doesn't have that problem. (different DRM). I hope AMD's next BIOS update really containts a fix. (https://t.co/fzrc25NHlT)
Three developers had to analyze why the database became slow as he** during a planed performance test. In the end it turned out that the data center moved the VM (that was marked as a "performance test environment") to the slowest HDD storage server they had without telling us.
Maybe I should allocate some (not available) spare time to making major changes to the #IndyComponents and create PRs. But they would be enormous and reviewing them would cost probably days. #Delphi