tpatko
2010-Jan-12 04:45 UTC
[Wine] Re: Memory Limitations for WINE 1.1.33 under Mac OS Leopard
Dear Ryan Woodsmall: Thank you for the tip. Does the call to: wine winecfg then need to be run each time that a new WINE session is initiated to run my Windows program? I guess in the case that the wine configuration files are already present it will just not write them again I suppose. This should work just fine for me as the application is launched with a Bourne shell script. Setting the WINEPREFIX for each program call is thus very easy. Thanks, Thomas
ryan woodsmall
2010-Jan-12 04:50 UTC
[Wine] Memory Limitations for WINE 1.1.33 under Mac OS Leopard
> Thank you for the tip. Does the call to: > > wine winecfg > > then need to be run each time that a new WINE session is initiated to run my Windows program?The first call of "wine programname" will result in the custom WINEPREFIX, if set, being created on the fly. If it already exists, files will not be overwritten every time. If you start a newer version of Wine with a WINEPREFIX that contains older Wine files, some housekeeping will take place, but it shouldn't (generally) break anything.
doh123
2010-Jan-12 04:52 UTC
[Wine] Re: Memory Limitations for WINE 1.1.33 under Mac OS Leopard
wine winecfg was an example of running a program... it runs winecfg... you dont *have* to run it.... the export WINEPREFIX to wherever you want it is all you have to do before running the Wine command you want to run. You can right simple shell scripts to do this for you... and launch the program you want. If you want WINEPREFIX to always be in 1 other specific place all the time without typing it, you can add the export line to your ~/.bash_profile ... and every time a session starts.. or new terminal window... it will automatically set it for you.