Exchange string data between 4DOS 8.00 and TCC v35

[Joe Caverly]

Normally, I just use the Windows Clipboard for exchanging string data between 4DOS 8.00 and TCC v35.

Here's another method of how I am exchanging string data between 4DOS 8.00 and TCC v35,
using a volatile variable in the registry (HKCU\Volatile Environment).

I'm running 4DOS 8.00 under DOSBox-X version 0.83.21 (SDL1, 64-bit) on my Windows 10 Pro system.

From 4DOS 8.00, I use the DOSBox-X START command, located on Z:\SYSTEM\start.com

start _ tccrt /H set /v amount=20.25
Starting tccrt...

R>

Switching to TCC v35...

U:\>set /v amount
20.25

U:\>ver

TCC  35.00.21 x64   Windows 10 [Version 10.0.19045.6332]

Getting string data back from TCC v35 requires a few more steps...

C>start _ tccrt /H r:\test.btm
Starting tccrt...
C>type clip:
20.25

Drive R:\ is shared between DOSBox-X and Windows 10.

::test.btm
@echo off
set /v amount > clip:

So, I end up needing to use the clipboard, regardless.

NOTES:

R:\>which tccrt
tccrt is an alias : "C:\Program Files\JPSoft\TCC_RT_%_vermajor\tcc.exe" /Q /C %1 %2 %3 %4 %5 %6 %7 %8 %9

The START command is disabled by default for security reasons, but can be enabled by either the "startcmd" config option (in [dos] section).
The START command itself will wait for program,
so it will return to the DOSBox-X shell when the program ends,
but the user can press Ctrl+C in the DOSBox-X window to terminate the program right away of course (or by closing the DOSBox-X window).
At this time console I/O will be done in the Command Prompt rather than within DOSBox-X.

Posting for my future reference, but others may also be interested.

Joe