What does not
What was not tested
extensive longtime testing
gstreamer1.0-plugins-good:i386 need to be installed, or the game crashes in the main menu.
(The game crashed once when the "exit" button in the main menu was pressed.
This could not be reproduced and wouldn't have been noticed without the wine crash handling window popping up.)
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Current||Ubuntu 19.10 "Eoan" amd64 (+ variants like Kubuntu)||Oct 29 2019||4.18||Yes||Yes||No||Platinum||consolelogger|
|Show||Linux Mint 14 "Nadia"||Nov 22 2013||1.7.6||Yes||Yes||Platinum||Booman|
|Show||Ubuntu 12.04 "Precise" amd64 (+ variants like Kubuntu)||Oct 19 2013||1.7.4||Yes||Yes||Bronze||mx2|
|Show||Arch Linux x86_64||Feb 03 2013||1.5.22||Yes||Yes||Gold||P. Neidhardt|
|Show||Ubuntu 13.04 "Raring" amd64 (+ variants like Kubuntu)||Dec 24 2012||1.5.16||Yes||Yes||Platinum||Dale|
2014-11-14 Admin note: the following was extracted from a user comment made on November 9th 2013, and may not be relevant to current Wine.
About windows getting minimized, the workaround is pretty simple : the MenuStates of the .ini file is reset everytime you launch the game, which causes it to define minimized windows. What you need to do is chmod it to read-only (chmod 444 does the trick) after having changed the MenuStates parameters to suitable window sizes.
I got it to work with around 50 mods, the thing is the .ini file needs to update the modlist, so you first need to run Morrowind with a writable .ini file (chmod 644 works like a charm), then you can kill the process immediately afterwards (wineserver -k after Ctrl+Alt+F1 for instance), chmod the .ini to 444 after checking the MenuStates section is still well and about, and launch the game !