On Thu, Apr 10, 2008 at 10:55 AM, Benjamin M. Schwartz <bmschwar@xxxxxxxxxxxxxxx> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Austin English wrote: > | You'd have to custom compile wine and edit those settings in > | tools/wine.inf before compiling. > > This can't be true. For example, as a matter of brute force, I could > start a copy of Wine, generate the .wine/, use winecfg to modify it, and > then carry that .wine/ around for future reference. Before starting > applications, I could just copy the entire contents of my customized > .wine/ into WINEPREFIX. This, however, is very ugly, because I'm moving > megabytes of junk around because I don't know where the settings are > stored. Where are the settings stored? > > - --Ben > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.7 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFH/jh9UJT6e6HFtqQRAof5AJoD5AtuaHOzsWGf03dBtBXDALnTVACfQ6Kf > 0x4+/ofRSsahH369ieFecYc= > =kRJ9 > -----END PGP SIGNATURE----- > You could run wineprefixcreate, then use a shell script to edit ~/.wine/user.reg & ~/.wine/system.reg. Actually, correct my mistake earlier. It seems you can edit /usr/share/wine/wine.inf as well (I haven't tested this though).
