home bbs files messages ]

Just a sample of the Echomail archive

<< oldest | < older | list | newer > | newest >> ]

 Message 192 
 Tim Schattkowsky to Ulrich Schroeter 
 Re: fresh new install runtime error 216 
 02 Dec 21 20:31:21 
 
MSGID: 2:240/1120.29 fef19982
CHRS: IBMPC 2
TZUTC: 0100
REPLY: 2:240/1120@fidonet 61a88251
//Hello Ulrich,//

on *02.12.21* at *7:48:43* You wrote in rea *WINPOINT*
to *Tim Schattkowsky* about *"fresh new install runtime error 216"*.

 US> moin Tim,

 US> Wednesday December 01 2021 20:16, you wrote to me:

 TS>> Hello Ulrich,
 TS>> on 01.12.21 at 7:38:13 You wrote in rea WINPOINT to All about "fresh new
 TS>> install runtime error 216".
 US>>> to install a fresh new winpoint installation I have to unpack wp2005b5
 US>>> and later replace the executable with the winpoint375 executable,
 US>>> correct?
 TS>> Yep.

 US>>> so I've tried ... extracted the wp2005b5 package and starting setup exe
 US>>> ... all I get is a runtime error 216 any hints ?
 TS>> Not really. Works here in various Win10 x64 installations including my
 TS>> desktop with the latest patches and various VMs. Anything special about
 TS>> 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

 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

Seems to be an access vioaltion -> not very helpful. I also dont have the
exact build configuration I used back in the days, so I cannot reproduce the
address layout of the binary on my machine to see whats happening.

May first guess is actually, that newer windows versions may have stopped
including a component that the original setup relies on. I will try to build a
binary installer for the latest version over the weekend that we can use for
testing.

Regards,
Tim
--- WinPoint 379.0
 * Origin: Original WinPoint Origin! (2:240/1120.29)
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


<< oldest | < older | list | newer > | newest >> ]

(c) 1994,  bbs@darkrealms.ca