Wes Newell wrote in a message to Roy J. Tellason:
 RJT> It appears,  from what I'm reading in this command 
 RJT> reference,  that if I want to run a dos program from 
 RJT> an OS/2 command line,  all I need is something like
 RJT>    command /c"doscommand"
 RJT> and that'll do it,  exiting back to the OS/2 command 
 RJT> processor when it's done. At least that's what it 
 RJT> looks like it means.  Is this right?  If so,  it'll 
 RJT> make things a bit easier for me to get going here 
 RJT> under a completely OS/2 system before I find 
 RJT> equivalents to all of the stuff I'm using now...
 WN> All you need to do is run the dos program. OS/2 will open a dos 
 WN> box, run the program, and then return to the os/2 session all 
 WN> automatically. All this assumes that you loaded DOS support in 
 WN> the first place.
Sure did,  along with winos2 support and all sorts of other junk...
I figured I might as well play with it *all* before I started messing with 
the bbs machine that I *need* to have up and running properly.
 WN> Assuming you still have your dos files and you have a path for 
 WN> them, type "edit" in an os/2 window and you'll get the idea.
I don't have any dos files on that drive that I didn't explicitly put there,  
started out with a bare drive,  no nothing on it.
It's been something else,  trying to get used to a different way of doing 
things.  I've not yet begun to scratch the surface when it comes to the 
command-line side of things,  and the GUI side of it is very much different 
than anything I've used before (not that I was a big fan of windoze or 
anything like that).
I *am* "getting it",  though.  To the point where I have to wonder about the 
authors of some of the packages I'm trying out.  None of them is satisfactory 
so far,  or they're missing bits here and there.  I couldn't understand why 
some of the folks in here had a bit of a problem with so many of the 
utilities they were trying out,  and I have a better appreciation of it now.  

Anyhow,  you're saying that if I drop a dos program on that disk and just try 
to run it from an OS/2 command prompt,  that what's needed just happens 
automatically?  That'd be seriously weird,  if so.
My concern right now is that I've got a whole *bunch* of stuff I run on a 
regular basis,  and I've only begun to hunt up OS/2 versions of some of it,  
and in some cases I'm not even sure that OS/2 versions of some of that 
software is available,  hence my thoughts about invoking dos versions of 
stuff.
email: roy.j.tellason%tanstaaf@frackit.com 
--- 
---------------