Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uwm.edu!psuvax1!psuvm!cunyvm!byuvax!taylorj
From: taylorj@yvax.byu.edu
Newsgroups: comp.sys.mac.hypercard
Subject: Changing userLevel
Message-ID: <1035taylorj@yvax.byu.edu>
Date: 20 Jan 90 04:02:34 GMT
Lines: 19

In article <51012@bbn.COM> seibel@bbn.com (Fred Seibel) asks how to protect
the stack to cut down on disk access.

As you've discovered, setting the userlevel has nothing to do with stack
protection or disk access.  You need the following two commands:

  set the cantModify of this stack to true
  set the userModify to true

This locks the stack but still allows you (or your scripts) to do anything they
want on the current card.  Note carefully the last four words of the previous
sentence!  Once you leave a card it reverts to the state it was in before you
locked the stack.  This can cause all kinds of unexpected problems if you're
not careful.  If you can live with this, however, locking the stack eliminates
all disk access and can make your stack run much faster.


Jim Taylor
Microcomputer Support for Curriculum
Brigham Young University
taylorj@yvax.byu.edu