Path: utzoo!attcan!uunet!mailrus!cs.utexas.edu!wuarchive!udel!cis.udel.edu
From: shearer@cis.udel.edu (Rob Shearer)
Newsgroups: comp.os.msdos.apps
Subject: Terminal program w/o Dos Shell.
Message-ID: <31646@nigel.ee.udel.edu>
Date: 27 Sep 90 02:09:45 GMT
Sender: usenet@ee.udel.edu
Organization: University of Delaware
Lines: 30
Nntp-Posting-Host: sol.cis.udel.edu
Originator: shearer@cis.udel.edu

Actually you CAN (propbably) use Qmodem...  (I do not have it to try..
to be 100% sure..)..

I was put in charge of writing a menu system for my school's Micro Computer
Lab...  The whole Idea was to keep the students from getting down to
DOS...  I not only accomplished this idea with the menu... I was 
able to disable the DOS shell in Lotus 1-2-3, Dbase, WP, GWBasic... and
one more package I think...  the easy way to do it, is do a
SET COMSPEC=

That will keep "well-behaved" programs from finding Command.com. (Don't
forget to set it back later!)

So create a BATCH file.. hmmm...limitqm.bat??? that looks something like:

set comspec=
qmodem
REM  qmodem above should NOT be another BATCH file ! or the next set 
REM  won't occur...  perhaps put a CD \qmodem between the set and qmodem?
set comspec=c:\command.com
REM  replace c:\command.com with your correct path...  some people at work
REM  set comspec to c:\dos\command.com...
CLS

Send me mail and let me know if it worked (if you get a chance...)

Robb Shearer
shearer@sol.cis.udel.edu

[I am new to the net... should I have sent this in email instead of posting?]