On Thu, 2003-09-25 at 22:06, Alexandre Julliard wrote:
"Robert Shearman" <R.J.Shearman(a)warwick.ac.uk> writes:
This will break a lot of HOWTOs on various sites that describe how to get apps working with Wine.
I don't see why, the HOWTOs should explain how to set dll overrides in the config file, that has been the standard way for a long time now.
For doing things like InstallShields etc, it's common practice for people to be given canned command lines, such as wine --dll ole32,oleaut32,rpcrt4=n myprog.exe basically because this is more convenient than altering the config file for each combination. I guess WINEDLLOVERRIDES="ole32,oleaut32,rpcrt4=n" wine myprog.exe is only slightly longer. Why must wines command line options be removed though? They are often handy for testing things out. thanks -mike