Re: Memory Limitations for WINE 1.1.33 under Mac OS Leopard

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> 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.



[Index of Archives]     [Gimp for Windows]     [Red Hat]     [Samba]     [Yosemite Camping]     [Graphics Cards]     [Wine Home]

  Powered by Linux