-=> Quoting Jon Guthrie to Carl Forester <=-

 JG> 11 Aug 94, Carl Forester writes to All:

 > I'm writing a os/2 text mode full screen app.  I'm trying to get the
 > .EXE file to write to itself.  When I try this I get a "Permission
 > denied" error.  The same routine works great in dos.

 JG> OS/2 is not DOS.  When OS/2 loads an executable program, it opens it
 JG> in a sharing mode that prevents anyone from writing to it.  That means
 JG> that a program can't write to its own executable file.



 JG> Not only that, but writing programs that save configuration
 JG> information in their exe's hasn't been a good idea for a half-dozen
 JG> years.  How do you handle a LAN environment where multiple people want
 JG> to share the same executable, but want to configure it differently?
 JG> My advice is to use an external configuration file.

Thanx for the answer to my question, but!
This program will never be run on a LAN, so I don't see the problem with
it writing to itself.  Not all applications are made to or are run on a
LAN.  For that matter, there lots of programs with cfg files that won't
run properly on LAN's.  The world doesn't revolve around LAN's.


-Carl-



~~~ PGPBLUE 2.9 *BETA*

... ///\oo/\\\ There are no more bugs. ///\oo/\\\ ///\oo/\\\
--- Blue Wave/Max v2.20f Beta