Riddle me this batman ... So I was playing around with an old doorgame I was writing back in 1995. Wanted to add lightbar arrow keys to it. Well, DDPLUS doesn't have that option. So I went looking for a new doorkit. Found XDOOR ... nice kit, one issue, after I compile with TP7.0 I get a RTE 003.


If I hit RUN from within Turbo Pascal the door works FINE ... but once it compiles, it shits the bed with a RTE 003. I have no idea why. Any takers? Compiles and runs fine under DDPLUS and ANGEL for TP7.

... Idiocy is an inbred genetic trait of all politicians.
--- Renegade v1.30r1/Exp
* Origin: The Titantic BBS Telnet - ttb.rgbbs.info (1:129/305)

If I hit RUN from within Turbo Pascal the door works FINE ... but once i compiles, it shits the bed with a RTE 003. I have no idea why. Any taker Compiles and runs fine under DDPLUS and ANGEL for TP7.

Update to this ... loaded DOSBOX and it ran just fine. Win10 32bit gives me the RTE003 on the exe with XDOOR kit. So, now I'm really puzzled where the erorr would be ... in the CRT unit or in the XDOOR source itself. I guess
the XDOOR source since DDPLUS and ANGEL work fine.

... Who is General Failure and why's he reading my hard disk?

--- Renegade v1.30r1/Exp
* Origin: The Titantic BBS Telnet - ttb.rgbbs.info (1:129/305)

On 2022 Jan 31 21:25:40, you wrote to All:

Update to this ... loaded DOSBOX and it ran just fine. Win10 32bit gives me the RTE003 on the exe with XDOOR kit.

Runtime Error 3 is "Path not found" so some directory or file is being looked for and failing to be found... XDOOR crashing with this problem indicates a code defect because XDOOR is not catching the error and handling it properly...


FWIW: i used to use an old TSR called iolog.exe to track things like this... i also used the mark and release tools so i could remove iolog from memory when i was finished with it... the following .bat snippets are 4DOS style...

eg:
if exist %FDSEMA\useiolog.sem (
REM take a snapshot current memory image
mark
REM make a semaphore so we know iolog is loaded
REM for this BBS node
rem>%FDSEMA\iolog%NODE.sem
REM execute the iolog TSR tool
iolog %RALOGS\raN%NODEio.log
)


and some place later we had this to unload iolog when it was not needed any more...


if exist %FDSEMA\iolog%NODE.sem (
REM reset memory to marked snapshot
REM this unloads all TSRs loaded after the snapshot was taken
release
REM remove the semaphore indicating iolog is loaded
del %FDSEMA\iolog%NODE.sem
)


so when we wanted to use iolog, we would create the useiolog.sem file in the %FDSEMA directory and the .bat file would take care of loading and unloading it for us... when we did not need iolog any more, we just deleted the useiolog.sem file and we were done... this made it quite easy to use it in our BBS' controller .bat files so we could use or not iolog without having to stop the BBS... the existance of the semaphores was check at each recycle of the main loop in the .bat file...

then we looked in the (eg) raN10io.log file for all the IO actions that took place during our BBS' N10 execution time period... these files can grow quite large pretty quickly if one is not careful...

)\/(ark

"The soul of a small kitten in the body of a mighty dragon. Look on my majesty, ye mighty, and despair! Or bring me catnip. Your choice. Oooh, a shiny thing!"
... Thy Corona come, thy Chili be Con, on Cuervo it is El Jefe.
---
* Origin: (1:3634/12.73)

Runtime Error 3 is "Path not found" so some directory or file is being loo for and failing to be found... XDOOR crashing with this problem indicates code defect because XDOOR is not catching the error and handling it proper

Yeah I figured that much already. Funny thing is, if I load DOSBOX and run it, it runs fine. Just under the Win10 DOS Prompt I get the RTE003.

... Limit Congressmen to 2 terms - 1 in Congress, 1 in Jail!
--- Renegade v1.30r1/Exp
* Origin: The Titantic BBS Telnet - ttb.rgbbs.info (1:129/305)