I posted this on another thread, but I see the thread is 5 years old, so I figured I'd put it over her. Basically, I was wondering about passing data between an application in VBDOS (running under DOSBox) and a Windows application. I was thinking about putting a trapdoor in DOSBox that could transfer control to a WIndows application. In the DOSBox source code, I think I see where it intercepts internal commands. In "dos_programs.cpp" they have them all in a row, with lines like:

PROGRAMS_MakeFile("IMGMOUNT.COM", IMGMOUNT_ProgramStart);

It seems to be intercepting the command "IMGMOUNT.COM" from the command line and then transferring control to the function "IMGMOUNT_ProgramStart ()". So seems like I could drop in an extra command there, which could transfer control to another Windows app. Not sure what kind of side effects it would have, but seems like that would work.

I think it would be cool to be able to make a .Net Class of DOSBox, so that I could instantiate it as an object. Like:

DIM MyDOSBOX AS DOSBox
MyDOSBOX = new DOSBOX ("config.txt")

The constructor would run DOSBox, and then the trapdoor would suspend DOSBox and return control to the calling application. And then the application could transfer control back to DOSBox, and back and fortth.

That way, a .Net application could have subroutines that were written in VBDOS.

I'm wondering if this sort of thing already exists, or if anybody else has any opinion on the subject