@leyrer also usong #deprected bs is not an excuse to non-compliance.
IDGAF if a company or public intitution chose to use #Widows11 or #WindowsServer: They are inherently incapable of #GDPR & #BDSG compliamce andnthus should be illegal without any exceptions.
And yes, refusal to support diacritics and other "advanced latin" is just bad - espechally since it't not like with non-latin scripts where one could reasonanly argue the need for transcription.
Not to mention the issues re: #KYC this has.
NT 3.1 through Server 2003 was the sweet spot for me. Back when thr system did what you want and otherwise stayed out of the way. Windows has been all downhill from there...
Hate on #Oracle#VirtualBox all you want, but when it comes to installing old school versions of Windows server, it really can't be beat. In VMWare, if I want to install Windows Server 2003, I'd either need sighted assistance or a lot of help from OCR, because not only is the Windows audio service disabled, but VMWare doesn't include the drivers needed for audio to work anyway, even if you enabled the service. You'd need to install not only VMWare Tools, but you'd have to find the audio driver that VMWare uses as well. With VirtualBox, however, Shift + F10, sc config AudioSrv start= auto, net start AudioSrv, and boom! Audio works! Now you can enable Narrator and breeze through the installation. The Lord said: 'Let there be sound,' and there was sound! #accessibility#WindowsServer#RetroTech
Windows 10, release in July 2015, unregistered. "I see you have an Enterprise key, here let me upgrade you."
Windows Server 2019, released in Oct 2018, Unregistered eval ISO. "I see you have a standard version reg key. I'm sorry I can't do that dave." Meanwhile on the internet "Yeah if you do this secret dism incantation you can totally do that."
It's a struggle to even get the GD system registered much less operating! :AngeryCat: