I don't see why mounting a /programs directory is necessary. Perhaps someone could explain the logic to me.

AFAIK, mounting doesn't survive a software upgrade without extra user interaction. I was thinking this through for a user application installer and it seems to me that /drive0/programs and /drive1/programs is a much better solution. That way (i think) you could upgrade your software without affecting your installed applications, except the need to reapply hijack. (I'm 90% sure your config.ini changes persist, yes?)

(EDIT: of course config.ini changes persist, they're on drive0...)

In any case, it'd be sort of nice to have a standard place to put things, if not just for the sake of writing easier to follow documentation.

John


Edited by johnmcd3 (27/01/2003 23:43)
_________________________
1998 BMW ///M3 30 GB Mk2a, Tuner, and 10 GB backup