LR> Hi, Kelly.  I don't know OS/2 but it seems to me that 
LR> denial to write to a exe file might be denied based on not 
LR> having it set up with proper acess.  Why should OS/2 or any 
LR> operating system presume what files are writeable or not. 
LR> Doesn't seem to make sense to me - unless OS/2 is marking 
LR> all .exe's as "Read Only" for some inexplicable reason.  
LR> Hmmmm.  Regards, -= Lou =-

Specifically, EXE files *that are currently running* can't be written
to.  This is because OS/2 is smart enough to load on demand only those
parts of the executable that are needed.  If you have a 2Mb .EXE file,
for example, you don't want the OS to immediately consume 2Mb of
physical memory and/or swap space when the program starts.  Also,
multiple running copies of the program would become confused if each
instance could change the program on the fly.  Sharing of code segments
would be impossible.  There is an unsupported API for loading all of a
module's contents into the swap area and then unlocking the file, but
it's better to keep this unsupported, since using it defeats the OS's
architecture.  (Lazy programmers want this kind of API to write
installation programs that can overwrite in-use EXEs and DLLs.)

John
--- Maximus/2 2.01wb