MoI discussion forum
MoI discussion forum

Full Version: Moi on Linux Wine problem

Show messages: All  1-9  10-20

From: Colin
12 Jun   [#10] In reply to [#9]
Hi Steve,

Thanks for those links & the extra details.
Given I'm tentative about venturing into the Terminal option, I'll try going with the installing Wine via the Software Manager...
If worst comes to worst & those Wine packages don't work for the trial MoI V4, then I've got your link directions.
Will report back to this thread on how things go.

regards Colin
From: sos (SAJURCAJU)
12 Jun   [#11] In reply to [#10]
The Software Manager frequently is not up to date, but in this case it will install Wine 9, which is what I had when I got Moi 4 working. So that should be fine.
From: Colin
13 Jun   [#12] In reply to [#11]
So I've tried installing Wive via the Software Manager using the "LM System Package"...
That gave me Wine 9.0~repack-4build3 but didn't seem to work, so removed it via the Software Manager option.
Tried doing same install but as the "Flatpak" which worked & gave me Wine.

Tried installing the MoI V4 Trial via the Terminal as per a video instruction but it wouldn't initiate...
I've no idea if it's the way I've installed Wine, whether I've not done something right by following the different Terminal commands..?
...but getting MoI to run is not happening.
I did a Timeshift back after doing each of the different failed Wine installs to be sure there was no "remnants".
At this point I've spent the best part of a day trying to fathom the different processes, codes/commands & info related to this...
Unfortunately that's about the limit of where I can go, it's all looking to be "way above my pay-grade".

Can't say I'd recommend a Windows user to try migrating over to Linux, with the idea of using MoI via Wine.

regards Colin
From: sos (SAJURCAJU)
13 Jun   [#13] In reply to [#12]
If you're up for one more attempt, I'm pretty sure this is what I did. I recommend using copy/paste, some of the lines are pretty long, but be sure to get the entire line :)

Taken from a Mint forum post:
make sure that the terminal command
dpkg --list *wine*
displays the following output:
dpkg-query: no packages found matching
If the response is different, post what you got here on Moi forum. I left the removal bits out to avoid clutter.

From WineHQ Debian/Ubuntu install:
sudo dpkg --add-architecture i386
cat /etc/os-release
From the cat output, you use UBUNTU_CODENAME or VERSION_CODENAME to select which code path (the first if both are present). Yours should be UBUNTU_CODENAME=noble for Mint 22. I've added that link below.

Before getting the actual code, get access to it (I may not be saying this just right):
sudo mkdir -pm755 /etc/apt/keyrings
wget -O - https://dl.winehq.org/wine-builds/winehq.key | sudo gpg --dearmor -o /etc/apt/keyrings/winehq-archive.key -
Do note there is a final - in the wget.

Now download the code for noble (Mint 22):
sudo wget -NP /etc/apt/sources.list.d/ https://dl.winehq.org/wine-builds/ubuntu/dists/noble/winehq-noble.sources

Update everything:
sudo apt update

Install Wine:
sudo apt install --install-recommends winehq-stable

Now, make sure Wine is set to Windows 10 (at least this is what works for me)
winecfg
At the bottom of the Applications tab you'll see Windows Version, make it Windows 10.

Here's hoping!
From: Colin
13 Jun   [#14] In reply to [#13]
Hi Steve,

Thanks for providing all of that, it's greatly appreciated.

I followed each of your directions but at the: "cat /etc/os-release" there was something like "nothing found" or "no file"...
Figured "that" response might've been correct so continued on following your directions.
Each following command did run & supposedly got to the end requiring the [Y/n] entry, to which I did "Y".
That was it for Terminal, nothing more happend...

At this point with my previous attempts, the Application Menu now had the "Wine" sub-menu.
In the last of those attempts, I needed to restart to get the sub-menu to populate with the "winecfg"

Following your directions, this time there was NO "Wine" sub-menu..?
Using the past experience, I rebooted & still no "Wine" sub-menu...
Did a Terminal command: dpkg --list *wine* ,resulting in: dpkg-query: no packages found matching

So at this point I appear to have done everything "by the book" yet it's failed to provide me with any results.
I might go back the the "Flatpak" install which at least gave me a full Wine 9 install & try installing MoI V4 again.

HTH, Colin
From: sos (SAJURCAJU)
13 Jun   [#15] In reply to [#14]
It's odd that you didn't get anything from the cat command, I copied/pasted the string you wrote and got exactly what I expected.
There isn't any reason to have Wine in your application list. This is not an issue.

When you install Moi (after Wine), a desktop icon should be created. In my desktop icon, If I right click and choose Properties, this is the command string:
env WINEPREFIX="/home/steve/.wine" wine C:\\Program\ Files\\MoI\ 4.0\\moi.exe
I'm pretty sure this was created when I installed Moi (after installing Wine).

You should have a desktop icon for the programs that will run under Wine, mine is labeled Wine-C representing the C drive on a Windows machine. Dig down to C:\Program Files\Moi 4.0\moi.exe
You should be able to right click moi.exe and choose Open With -> Wine and start the program.
From: Colin
13 Jun   [#16] In reply to [#15]
Hi Steve,

What you described about Wine & its C Drive was what I had previously with the Software Manager installed "Flatpak".
The "difference" was that mine had the Wine sub-folder in the LM Menu, as per the description on the LM Forum link you'd previously posted.

> "In the Linux Mint application menu, there should be a new submenu titled Wine. Inside the Wine sub-menu you will find among a few other items, the item "Configure Wine" (winecfg)."

Having purged everything once again & Timeshited back again to 3 days ago before I attempted any Wine istalls, I tried reinstalling the "Flatpak"...
This time the Software Manager refused to install a certain number of files & so it appears I've now manged to "break" something..?
Another Terminal purge, another Timeshift, another reboot & that's where I'm leaving it...

Linux Mint is working perfectly fine for all my other needs, I've installed VitualBox with W7 & that gives me an older Xara V9 to open my current Graphics files I'm working on via the VM.
Unfortunately even though I've installed my MoI V3 in that same VBox, the VM Graphics drivers wont allow MoI V3 to display anything within its Views...
Everything else related to MoI V3 at this point appears to be working except the View ports...
(I tried enabling "3D Acceleration" within VBox Display settings but it refuses to engage)
So the argument by various Linux Forum Users to "just use a VM for ANY Windows programs" doesn't seem valid or apply for MoI in this case..?

Having access to my old MoI files via either VirtualBox or Wine whilst on Linux Mint means I can walk away from Windows without any regrets...
Despite all of my researching prior to this migration over to Linux, it hasn't been as easy as the research suggested.

Image Attachments:
MoI in VBox.PNG 


From: Michael Gibson
14 Jun   [#17] In reply to [#16]
Hi Colin,

re:
> So the argument by various Linux Forum Users to "just use a VM for ANY Windows
> programs" doesn't seem valid or apply for MoI in this case..?

Well it gets more difficult with programs that need to access the GPU like MoI or many games.

It looks like there is some info here:
https://forums.virtualbox.org/viewtopic.php?t=99224

It looks like you need to include Direct3D support when you install VirtualBox not just set it as an runtime setting?

And it sounds like maybe you need to use an older version of VirtualBox because some GPU functionality was removed from current versions because of security holes?

- Michael
From: Colin
14 Jun   [#18] In reply to [#17]
Hi Micheal,

Thanks for the link & added info.
I'll go do more reading on including the Direct3D support part.
I'm running the VirtualBox package which is available via the Linux Mint Software Manager.

Everything I've done has been based on the following YouTube info from Christopher Barnatt's "ExplainingComputers" channel.
https://youtu.be/kN1MWBa3yiw?si=2qNoacS-wfN_Ec2d

In an effort to help minimise the chances of conflicts for myself, I tried installing only the stuff offered through the LM Software Manager...
Obviously that choice is now starting to present me with problems as I try to getting my preferred Windows programs into place.
Having now "broken" something related to the attempted Wine installs, I'm even more hesitant to start changing out Vbox...

The W7 within VBox has installed itself various Windows Updates, which I've allowed in the hope there's something needed for MoI...
That VBox W7 is running my old Xara PGD V9 just fine, so I just need the installed MoI V3 to run & my old "Graphics package" will be sorted

regards Colin
From: Colin
14 Jun   [#19]
Hi Michael,

After some research on the VitrualBox Forum I found a solution for MoI V3 display problem.
Please see attached screen capture of Display settings.

So with Linux Mint 22 running its own Software Manager installed VirtualBox & my "guest" VM W7 is running both MoI V3 & Xara V9

With that now solved & my W7 being x64, is MoI V4 able to run on W7 x64..?
If so then I can upgrade to it & thus avoid my current issues with installing Wine.

regards Colin

Image Attachments:
VM W7 x64 Display 3D [working] 14-06-2025.png 


From: Michael Gibson
14 Jun   [#20] In reply to [#19]
Hi Colin, that's great! Yes, MoI v4 will run on Windows 7, 64-bit only not 32-bit.

Moi v3 was able to run with extremely low amounts of video memory, v4 needs a little more (a byproduct of Direct3D11) for baseline so you may need to increase the amount in your VM settings.

- Michael

Show messages: All  1-9  10-20