CARL FORESTER had something deep to write about Writing to .EXE's

CF> I've written a program that writes the configuration info to
CF> itself.  Is there any way I can get this program to
CF> write to itself, or do I have to go back to a .CFG file, or
CF> seperate config program?

I'm almost certain that you will have to do something other that
overwrite part of the program.  OS/2 locks access to a program when it
runs it.  It does this to insure that the code will not change during
operation.  When committed memory exceeds physical memory, OS/2 can
move data to the swapper.dat file (if swapping is enabled) or discard
code that is not in immediate use.  Whenever that code is needed again,
it can be read back from the program file.  You can only modify OS/2
program files when they aren't being run.

There are several possibilities for configuration storage:

 1) a .CFG or .INI file specific to that program
 2) Extended Attributes attached to the program
 3) a few bytes of data in the OS2.ini file
 4) a separate configuration program that modifies the program code.

 * KWQ/2 1.2f * All I want for Christmas is a box of Smurfs and a mallet.


--- QScan v1.11b / 01-0093