On Tue, Aug 4, 2009 at 12:01 PM, ChristTrekker<wineforum-user@xxxxxxxxxx> wrote: > > austin987 wrote: >> On Tue, Aug 4, 2009 at 11:34 AM, ChristTrekker<wineforum-user@xxxxxxxxxx> wrote: >> >> > >> > I assume "corruption" refers to various config files. So use a different wineprefix - just put binaries in a common place, using symlinks if this "binary path" isn't separately configurable. (~/.wine/drive_c/Program\ Files -> /usr/local/share/wine/Program\ Files) Executables aren't written to, so how would they be corrupted? >> > >> >> Depends on the executable. Most programs come with other files that >> are written to, e.g., ini files and the like. > > Ahhh... And since Windows wasn't designed as a timesharing OS with concurrent users in mind, it has single ini files rather than per-user ini files. Is that what I'm hearing? That would make sense. Exactly. > But... If I knew the deployment environment would only ever have one user at a time, would it be possible (and safe) to set up users to share a single wineprefix? I can't help but think there's an alternative to installing the same app multiple times You'd have to patch the source code. Search the forum, it's been explained before several times. -- -Austin
