Loading the Locking Module in System Memory

You must load at least one semaphore-locking module (either INMEMO.SYS or INMEMO.MLK) into system memory if you are going to allow concurrent editing of the same memo file. If you have many users and multiple memo files, you may want to define additional locking modules to reduce the chance of a significant delay if several users exit from memo editing in different files at the same instant. The modules are only 8 bytes long, so you shouldn't have much difficulty squeezing them in.

To make additional locking modules, simple copy the INMEMO.SYS file provided. The names of the additional modules must equal the names of the memo files with .MLK extensions. For example, to create a unique lock module for the memo file TSTMMO, execute this command:

.COPY TSTMMO.MLK = INMEMO.SYS

To load it/them into system memory, you must modify your AMOSxx.INI file as shown below. Note that you should always make a backup copy of the INI file and modify the backup copy, then use MONTST to test it before finally updating your live copy of AMOSL.INI.

Use VUE to edit the copy of the AMOSL.INI file, and insert the following line somewhere between the first and last SYSTEM commands:

SYSTEM INMEMO:INMEMO.SYS

Note that we specified the ersatz account where the lock module is. If you have additional lock modules, use additional SYSTEM commands to load them.