Hi Craig,

 CS> OS/2 shares executable code pages for both EXE and DLL files. If there is
 CS> a process running PROGRAM.EXE and you start a second process running
 CS> PROGRAM.EXE, additional memory for process and thread control blocks, file
 CS> handles, stacks, and read/write data areas will be allocated.  The actual
 CS> executable code in RAM will be shared between all processes running
 CS> PROGRAM.EXE.

Okay, that's clear speak. Good.
So I don't need to set anything special, OS/2 will share the code anyway.

 AL> under UNIX, you can even give it a 'sticky bit' attribute, forcing
 AL> it to stay in memory all the time, even if no processes use it at a
 AL> particular time (imagine a BBS program, called by getty).

 CS> There is no "sticky bit" in OS/2, but it is easy enough to simulate
 CS> this simply by blocking a thread on a named semaphore or some other
 CS> IPC object so that you can cause the process to terminate if you
 CS> want to release the memory.

Care to write me a sample?
I may want to have for instance Maximus stay in memory all the time, so the
BBS is started faster when a user is put through by the mailer....
Could do that by running the mailer and BBS in separate processes, but a
'sticky bit' equivalent would be just as effective, and easier to set up.
Cya! Agl.

--- Xenia Edit 1.17+ OS/2