MSGID: 2:240/1120@fidonet 61a9c45c   
   REPLY: 2:240/1120.29 fef19982   
   PID: GEDW32 3.0.1   
   CHRS: IBMPC 2   
   TID: FastEcho 1.46.1 3756   
   moin Tim,   
      
   Thursday December 02 2021 20:31, you wrote to me:   
      
    TS> //Hello Ulrich,//   
      
    US>>>> setup exe ... all I get is a runtime error 216 any hints ?   
    TS>>> Not really. Works here in various Win10 x64 installations   
    TS>>> including my desktop with the latest patches and various VMs.   
    TS>>> Anything special about that VM?   
      
    US>> 2 fresh new Win10 Pro installations:   
      
    US>> a. Host  Win10 Pro 64bit, Build 17763.1577   
    US>> b. Guest Win10 Pro 32bit, Build 19042.1348   
      
    US>> on top of a lenovo l560, 64bit, 8gb ram   
    US>> vmguest:  1gb win10pro 32bit   
      
    US>> both installations, same error ...   
    US>> runtime error 216 at 004041BA   
    US>> with the wp2005b5 setup.exe   
      
   on the bare metal 64bit system I've did running the sfc /scannow and got an   
   unrecoverable error ...   
   at the same time an windows update waiting for the next reboot   
   so I still try to investigate first, if this runtime error relates into the   
   middle of the way of the long windows update party   
   by default you can running programs while the windows update is downloading   
   and installing updates in the background   
      
    US>> search for runtime error 216 results in 3 directions   
    US>> 1. virus    checked   
    US>> 2. Runtime Error 216 Delphi   
    US>> 3. Runtime Error 216 pascal   
      
    TS> Seems to be an access vioaltion -> not very helpful. I also dont have   
    TS> the exact build configuration I used back in the days, so I cannot   
    TS> reproduce the address layout of the binary on my machine to see whats   
    TS> happening.   
      
   one article by microsoft points to backdoor subseven but all virus scanners   
   that I've still scanned with did not report any infection   
   https://support.microsoft.com/en-us/topic/error-message-runtime-   
   rror-216-1d0db575-c9bf-94e9-c432-2315c5bab9d5   
      
    TS> May first guess is actually, that newer windows versions may have   
    TS> stopped including a component that the original setup relies on. I   
    TS> will try to build a binary installer for the latest version over the   
    TS> weekend that we can use for testing.   
      
   to be continued ...   
      
    TS> Regards,   
    TS> Tim   
    TS> -$- WinPoint 379.0   
    TS>  $ Origin: Original WinPoint Origin! (2:240/1120.29)   
      
   regards, uli   ;-)   
      
   ---   
    * Origin: AMBROSIA - Bad Ueberkingen - Germany (2:240/1120)   
   SEEN-BY: 30/0 221/1 6 229/426 428 664 700 240/1120 261/38 280/464   
   SEEN-BY: 282/464 1038 292/854 301/0 1 101 113 335/364 341/66 371/0   
   SEEN-BY: 920/1 2452/250 5020/1042 5058/104   
   PATH: 240/1120 301/1 229/426