[comp.os.msdos.apps] Terminal program w/o Dos Shell.

shearer@cis.udel.edu (Rob Shearer) (09/27/90)

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?]

DSB100@psuvm.psu.edu (David Barr) (09/27/90)

(regarding disabling DOS shell and command.com access)

One other idea is to rename command.com to something else as well
as setting the COMSPEC variable to null.  Then even dumb programs
that are hard coded to run command.com can't

 / David Barr  |  Penn State CAC Student Consultant       \
| DSB100@psuvm.psu.edu     | dsbarr@endor.cs.psu.edu        \
| --- Trim that .sig!! --- | barr@barrstl.scol.pa.us          \
| "When a file is deleted, it actually still exists; it merely |
 \ has put Groucho glasses on so DOS no longer recognizes it" /