LR>  
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. 

Huh?
I don't know why OS/2 would do that either... It doesn't do it. The
reason that it's a no-no to try to have a program write to it's own
.EXE file is that in low memory situations where paging is necessary,
OS/2, knowing that .EXE files are not data files, discards them in the
process of swapping out code and data to the swapfile to make room for
more stuff in memory. Conversely, it writes the unsaved information in
data files to disk. When the information in the swapfile is read back
in, it's the data, not the program's code that gets read. the program's
code is read from the program's .EXE or DLL file. I would imagine that
OS/2 might lock access to a program's .EXE file to ensure that it
doesn't get changed while it's running or something... Who knows? It's
either necessary to use a configuration file to store information in, or
use a separate configuration program to write to the .EXE file when the
program's not running.

Kelly

___
 X KWQ/2 1.2g NR X If at first you don't succeed, put out another version (KWQ 1.2g)
--- Maximus/2 2.01wb