RJT> Anyhow, you're saying that if I drop a dos program on
RJT> that disk and just try to run it from an OS/2 command
RJT> prompt, that what's needed just happens
RJT> automatically? That'd be seriously weird, if so.
That's what happens. If you issue a dos command, or run a dos program from an
os/2 window, os/2 will automatically open a dos window and execute the comand
or program, then close the window after the program/command ends, and return
you to the os/2 CLI.
RJT> My concern right now is that I've got a whole *bunch*
RJT> of stuff I run on a regular basis, and I've only
RJT> begun to hunt up OS/2 versions of some of it, and in
RJT> some cases I'm not even sure that OS/2 versions of
RJT> some of that software is available, hence my thoughts
RJT> about invoking dos versions of stuff.
When I switched the BBS to OS/2 several years ago, the only native OS/2
programs I was runnning at the intial cut was bnikley/2 and Max/2. All my
control files were still dos, Makenl, Squish, Areafix, Raid, Tick, Hlist,
etc. As I found OS/2 versions to replace them I did, but they ran perfectly
as dos apps. It's really kinda neat to watch the thing switching back and
forth from OS/2 windows to dos windows as the need arises.:-)
--- Maximus/2 3.01
---------------
* Origin: Wylie Connection 128K ISDN / V34+ 972-429-7005 (1:124/7028)
|