Well I could sort of do that. We can put it to a vote.
If the HOME environment variable is set, should I use that instead of MOZILLA_HOME? what should I do if HOME points to a FAT drive? Mikus Grinbergs wrote: > On Wed, 25 Sep 2002 14:40:30 -0500 Michael Kaply <[EMAIL PROTECTED]> wrote: > >>Nicky Morrow wrote: >> >>>I do a lot of testing and reload the os often. I really really hate >>>apps that I have to reload in order to get them working again...it just >>>shouldn't be necessary to reload apps when you reload the os. >> >>You are definitely living in a theoretical dream world. If you format >>the boot drive, you are going to lose data. >> >>Reloading the OS is NOT something most people do all the time! >> >>The answer is to back up your CONFIG.SYS when you reinstall. >> >>And as far as apps that don't need change to CONFIG.SYS, that's Windows. >>Harder to do on OS/2 > > > In this instance I support an idea Nicky Morrow proposed (via email): > > | Have __all__ OS/2 applications use one environmental variable > | > | set USER_HOME=x:\home\base > | > | The applications would install __all__ their .INI or .DAT or > | whatever files into *that* directory (which is *not* on the > | OS/2 boot drive). Then, although the boot drive itself might > | get reformatted (for instance, to install MCP2 on a machine > | that had been running Warp), __all__ previously installed > | applications can be "re-identified" by simply adding the > | above environmental variable value to the new config.sys > > Of course, it is kinda late to have __all__ existing applications > do this. But that should not prevent putting in such an "easy-to- > allow-os-change" support facility into those applications which > *today* are still being worked on. > > > mikus (with thanks to Nicky Morrow) >
