[opensuse-support] Wine experts? How to reconfigure?
Hi list, I wonder if there's some wine experts around here? My issue: I have a wine setup here on my Tumbleweed system, slowly grown with various applications over three years. I'm now trying to run some new program (Maskulator, a fresnel propagation optics program). It crashes :( However, if I rename .wine to .wine.bak and then run the program, I get a notification it is doing some configurations - and now the program runs! But of course all my previously installed stuff is gone. Is there a way to merge old and new, or to enforce a reconfiguration of things? -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On Fri, Sep 06, 2019 at 01:41:46PM +0100, Peter Suetterlin wrote:
Hi list,
I wonder if there's some wine experts around here?
My issue: I have a wine setup here on my Tumbleweed system, slowly grown with various applications over three years. I'm now trying to run some new program (Maskulator, a fresnel propagation optics program). It crashes :(
However, if I rename .wine to .wine.bak and then run the program, I get a notification it is doing some configurations - and now the program runs! But of course all my previously installed stuff is gone.
Is there a way to merge old and new, or to enforce a reconfiguration of things?
You can use a seperate wine prefix for your case. mkdir ~/.wine-maskulator and before starting it do: export WINEPREFIX=~/.wine-maskulator then wine ~/.wine-maskulator/drive_c/Program\ Files/.../foo.exe Ciao, Marcus -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Marcus Meissner wrote:
You can use a seperate wine prefix for your case.
mkdir ~/.wine-maskulator
and before starting it do: export WINEPREFIX=~/.wine-maskulator then wine ~/.wine-maskulator/drive_c/Program\ Files/.../foo.exe
Ah thanks - didn't get that idea. But it does come at quite a cost, drive_c/windows is some 700MB :o So I guess I'll use it, but continue to look for a proper solution ;^> -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Am 06.09.19 um 15:02 schrieb Peter Suetterlin:
But it does come at quite a cost, drive_c/windows is some 700MB :o
use 32bit wine-prefix like in my other mail explained. its much smaller than 64bit (standard) -of course only if your app will work with 32 bit. simoN -- www.becherer.de -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Simon Becherer wrote:
Am 06.09.19 um 15:02 schrieb Peter Suetterlin:
But it does come at quite a cost, drive_c/windows is some 700MB :o
use 32bit wine-prefix like in my other mail explained. its much smaller than 64bit (standard) -of course only if your app will work with 32 bit.
Just reading through that other mail :) Maybe my issue is that I do have (and need) wine-mono which is already 260 of those 700MB. I'll see what 32bit helps -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Am 06.09.19 um 15:10 schrieb Peter Suetterlin:
Simon Becherer wrote:
Am 06.09.19 um 15:02 schrieb Peter Suetterlin:
But it does come at quite a cost, drive_c/windows is some 700MB :o
use 32bit wine-prefix like in my other mail explained. its much smaller than 64bit (standard) -of course only if your app will work with 32 bit.
Just reading through that other mail :) Maybe my issue is that I do have (and need) wine-mono which is already 260 of those 700MB. I'll see what 32bit helps
goto (if you use kde) ./cache/wine there are all old mono installation-files inside. you need only the newest one. all other you could delete. -- www.becherer.de -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Am 06.09.19 um 15:02 schrieb Peter Suetterlin:
So I guess I'll use it, but continue to look for a proper solution ;^>
start winecfg in each of your 2 wine installations. check what is all different. try to set your old installaton to the settings of the new one. check if your new app then works. i do not remember where to check if its an 32bit or a 64 bit installation. but maybe the old is 32bit. the new without parameters is 64 bit. simoN -- www.becherer.de -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Am 06.09.19 um 15:08 schrieb Simon Becherer:
Am 06.09.19 um 15:02 schrieb Peter Suetterlin:
So I guess I'll use it, but continue to look for a proper solution ;^>
start winecfg in each of your 2 wine installations. check what is all different. try to set your old installaton to the settings of the new one. check if your new app then works.
i do not remember where to check if its an 32bit or a 64 bit installation. but maybe the old is 32bit. the new without parameters is 64 bit.
simoN
goto ~/.wine/drive_c if there is a directory: "Programm Files (x86)" in addition to "Programm Files" you have 64 bit wine if there is only "Programm Files" its 32bit but there should be some other way to check this.... -- www.becherer.de -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Am 06.09.19 um 14:41 schrieb Peter Suetterlin:>
Hi list,
I wonder if there's some wine experts around here?
My issue: I have a wine setup here on my Tumbleweed system, slowly grown with various applications over three years. I'm now trying to run some new program (Maskulator, a fresnel propagation optics program). It crashes :(
However, if I rename .wine to .wine.bak and then run the program, I get a notification it is doing some configurations - and now the program runs! But of course all my previously installed stuff is gone.
Is there a way to merge old and new, or to enforce a reconfiguration of things?
Hi, not an "expert" but some apps running here: ==================================================================== i would use one wine installation for each application. if you start wine / or your application (installer) like this: env WINEPREFIX="/home/myhome/.wine-mywineapp" wine mywineappinstaller wine will generate a ".wine-mywineapp" winedirectory for you and your application will only use this directory. (if it generates a desktop file, it will be start automatically from there) if you remove this directory it will only delete this one application. =========================================================================== example: for installing svnetcomfort i need a wine32bit enviorement with direct x9 in a seperate winedirectory and i do not like that wine-mimetypes will automatically integrated in linux. the steps would be like this: env WINEPREFIX="/home/simon/.wine-svnetcomfort" env WINEARCH=win32 winecfg exit (this will generate the wine directory) installing directx9: env WINEPREFIX="/home/simon/.wine-svnetcomfort" env WINEARCH=win32 winetricks directx9 exit settings for this application to work: env WINEPREFIX="/home/simon/.wine-svnetcomfort" env WINEARCH=win32 winecfg set windows-version to windows 7 set "MIMETYPE" do not manage fileassociations set dll: d3d8 nativ d3d9 nativ (all others do not touch) install svnet: env WINEPREFIX="/home/simon/.wine-svnetcomfort" env WINEARCH=win32 wine setup_sv.net-comfort_18.0.1.16.exe start it with env WINEPREFIX="/home/simon/.wine-svnetcomfort" wine C:\\windows\\command\\start.exe /Unix /home/simon/.wine-svnetcomfort/dosdevices/c:/users/Public/Desktop/sv.net\ comfort\ .lnk (or via desktop symbol) ======================================================================================== with one wine-directory for each applications its easy to use winetricks or some other special settings for one application and some other settings for other applications. hope this will help you simoN -- www.becherer.de -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
participants (3)
-
Marcus Meissner -
Peter Suetterlin -
Simon Becherer