How to install ED on Linux using Wine [EXPERIMENTAL, NOT OFFICIALLY SUPPORTED]

I have one that is 27 mb. But I may be installing over an old game folder from a different file. Although the other installers I found on my system are also 27mb. Note: I haven't gotten it to work yet. I'm not sure which one is better. I would assume the smaller as stuff I've read says normal DX gets in the way. But I could be completely mistaken.
 
Last edited:
OKay.

Can't get this working with my debian testing install, and it'll be too much hard work to move to a different distro, and I suspect the Q4 update will break everything again.

This debian testing install is decades old, been through many dist-upgrades, been through many different GPU makes, drivers, monitor configurations, and a whole load of tweaks and adjustments throughout the years. It's either a lot of cruft in my install, or just something inherent with debian Testing. I could pfaff about and try a different distro, but I've ran out of energy today, and due to how I've set up this system (/boot and encrypted LVM), it'll be a lot of trouble to reinstall Linux on it.
 
If you install without the normal path where does it install too? I seem to have installed it in a way that it keeps saying I have it on the system and can't reinstall it.

I used:
WINEPREFIX=~/ed-wine ./winetricks dotnet452


I uninstalled wine with:

sudo dnf remove wine


And it did not resolve this.

I even deleted my .wine folder and it still will not let me reinstall dotnet again...
Details

Same or higher version of .NET Framework 4 has already been installed on this computer.


They really need to stop screwing around with wine and make it transparent. I'm tired of it not displaying install paths. I can't find anywhere on their website about where it puts things. And you sure as hell can't remove things without it.


WINEPREFIX=~/ed-wine WINE=/usr/bin/wine ./winetricks dotnet452 corefonts quartz vcrun2012
------------------------------------------------------
You are using a 64-bit WINEPREFIX. Note that many verbs only install 32-bit versions of packages. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug.
------------------------------------------------------
Using winetricks 20171222-next - sha256sum: ddc58be9c16d70a1764982f8a8d65e13f8e0b2e4c408159951626226c9b14954 with wine-3.17 (Staging) and WINEARCH=win64
------------------------------------------------------
You are running winetricks-20171222-next, latest upstream is winetricks-20180815!
------------------------------------------------------
------------------------------------------------------
You should update using your distribution's package manager, --self-update, or manually.
------------------------------------------------------
Executing w_do_call dotnet452
------------------------------------------------------
error: dotnet452 conflicts with dotnet40, which is already installed.

I've already manually deleted the .wine folder to remove old entries beyond using uninstall. Can't get rid of dotnet...

Also can't get rid of winetricks completly either(it won't uninstall from the packager at all!). And can't completely remove wine. At which point is this consider malware or a virus and this stopped. I don't understand where they think they get off. They refuse to document it and will not tell you where it is. I'm sick and tired of this crap. The registry and every part of what is installed via wine is a part of their program and can be removed and should be uninstallable somehow.

Using winetricks and no path is the default. Where do they think they get off letting that destroy my system. There is no way to reverse that.
 
Last edited:
Managed to get game running but having weird problem with keyboard under ED. Normal keys (a-zA-Z0-9) do not seem to produce correct output. I tried to set 2 as comms panel but get something totally different as output.

https://elite.piiri.net/junk/ed_under_linux_problem1.png
https://elite.piiri.net/junk/ed_under_linux_problem2.png

Keybind works as long as I do not go to settings or restart the game.

Cursor keys and function keys do produce correct output.

On a Notepad.exe running under Wine keyboard works ok. I even tried two different keyboards with same results.

Running Fedora 28 with Wine 3.1.7.

Only part that does not recognise keys correctly is settings. If I set a key for comms and activate it in game I can write anything and all the keys work as expected.
 
Last edited:
Is that a figure that is produced in another keyset like wingings. Maybe it is attempting to use a different character set somehow. Identify the keyset and it might make it easier to find out what is happening. Assuming that is related to the problem.

It has to be getting the character from somewhere. I would assume it's that or some random character from some inner code in the game. That I would think is the other logical answer.

It's not likely to be the keyboard unless it has some onboard chips to hold data about the keys specific character references custom to the keyboard or similar. Or I would assume.

^C is a normal one that comes up in the command line when a command is in the middle of executing and you hit certain buttons. Maybe that is popping up instead of the actual key. Anyone know what that is normally? ^A is another common one. Maybe it's sending that instead of the normal key data.

On my command line Ctrl+c is ^C. Other key combos may produce this though. Maybe it is related.

The game might have been having problems with saving keybinds in older wine when I was playing in the demo. I know it was hard to save it initially because of crashes. I can't remember if it was also resetting the keybinds at any point.
 
Last edited:
Would totally want to share my findings but my posts are still being held by the moderators (probably should repost the stuff if the post is accepted, so it doesn't stay burried).
Thanks for figuring the stuff out. Performance-wise the game runs great (appart of the bindings situation)
 
If you install without the normal path where does it install too? I seem to have installed it in a way that it keeps saying I have it on the system and can't reinstall it.

I'm not a big Wine user, but I think your frustration stems from not understanding the distinction between the Wine installation itself (this can be a system installation as I have been using, or a local build in your Linux $HOME), and the local Wine configuration(s) in your $HOME, which are similar to a Windows installation.

Wine configurations, aka wineprefixes and 'bottles' are folders each containing config for Wine, the windows version it is pretending to be, and probably the folders containing windows drives. The default value for this folder is $HOME/.wine. If you set the WINEPREFIX environment variable, a different folder is used. Different winprefixes have no effect on each other. winecfg modifies the registry within the specified wineprefix. winetricks is a package manager which installs DLLs within the specified wineprefix.

More info here: https://wiki.winehq.org/FAQ#Wineprefixes
I used:
Code:
[COLOR=#FFFFFF]WINEPREFIX=~/ed-wine ./winetricks dotnet452[/COLOR]

The './' in front of winetricks here worries me; it looks like you're using a local installation.....

I uninstalled wine with:
Code:
sudo dnf remove wine

And it did not resolve this.
...and this is uninstalling the system Wine installation; not modifying your wineprefixes at all.

I even deleted my .wine folder and it still will not let me reinstall dotnet again...
Code:
Same or higher version of .NET Framework 4 has already been installed on this computer.

This is removing the '.wine' wineprefix, and so does not affect any of the commands prefixed with WINEPREFIX=~/ed-wine.

They really need to stop screwing around with wine and make it transparent. I'm tired of it not displaying install paths. I can't find anywhere on their website about where it puts things. And you sure as hell can't remove things without it.
Now you know that all commands are operating inside the directory given by $WINEPREFIX, or ~/.wine if not specified, do you see that these folders are the install locations? You can simply rm -rf the entire wineprefix if you want to remove stuff, and start over. If it's not clear, section 6.5 of the Wine FAQ linked above and the following 6.6 should clear things up.

Code:
[COLOR=#FFFFFF]WINEPREFIX=~/ed-wine WINE=/usr/bin/wine ./winetricks dotnet452 corefonts quartz vcrun2012[/COLOR]
[COLOR=#FFFFFF]------------------------------------------------------[/COLOR]
[COLOR=#FFFFFF]You are using a 64-bit WINEPREFIX. Note that many verbs only install 32-bit versions of packages. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug.[/COLOR]
[COLOR=#FFFFFF]------------------------------------------------------[/COLOR]
[COLOR=#FFFFFF]Using winetricks 20171222-next - sha256sum: ddc58be9c16d70a1764982f8a8d65e13f8e0b2e4c408159951626226c9b14954 with wine-3.17 (Staging) and WINEARCH=win64[/COLOR]
[COLOR=#FFFFFF]------------------------------------------------------[/COLOR]
[COLOR=#FFFFFF]You are running winetricks-20171222-next, latest upstream is winetricks-20180815![/COLOR]
[COLOR=#FFFFFF]------------------------------------------------------[/COLOR]
[COLOR=#FFFFFF]------------------------------------------------------[/COLOR]
[COLOR=#FFFFFF]You should update using your distribution's package manager, --self-update, or manually.[/COLOR]
[COLOR=#FFFFFF]------------------------------------------------------[/COLOR]
[COLOR=#FFFFFF]Executing w_do_call dotnet452[/COLOR]
[COLOR=#FFFFFF]------------------------------------------------------[/COLOR]
[COLOR=#FFFFFF]error: dotnet452 conflicts with dotnet40, which is already installed.[/COLOR]

So this is where that local winetricks I worried about upsets me. You're telling it to use system Wine 'WINE=/usr/bin/wine' but the script itself is in the current directory. I suggest using packaged newer winetricks, if your distro's wine 3.18 includes it. If not, I would take the advice in the output and update it yourself, as there have been bugfixes around this error.

AND we see you are running Wine 3.17 - I have no idea whether this runs ED now, as I jumped on this yesterday. 3.18 is working for me and others.

I've already manually deleted the .wine folder to remove old entries beyond using uninstall. Can't get rid of dotnet...

Hopefully why this doesn't work is clear now. You were deleting the wineprefix '.wine' which does not change the dotnet40 installed in the alternative wineprefix '~/ed-wine'.

HTH
 
I deleted both ed-wine and .wine and removed wine via, "sudo dnf remove wine" and then I reinstalled wine via, "sudo dnf install wine". it refused to make a new .wine folder during install and every aspect of teh wine install is messing up and not doing what it should.

It also won't remove winetricks via dnf remove.. But it will install it. And manually deleting winetricks messes everything up. I had to restore it from the trash folder along with .wine And it still thinks dotnet is installed for some reason. Even with a new ed-wine.

It has to be hiding something somewhere on the system outside of the ed-wine folder.

I used this:

WINEPREFIX=~/ed-wine ./winetricks dotnet452

It's normally this:

WINEPREFIX=~/ed-wine WINE=/usr/bin/wine ./winetricks dotnet452

I can't figure out where the first one installed the dotnet452 too. If it's in ed-wine I deleted that and it's preserving it's belief that dotnet is installed. I'm not sure why.

I tried to reinstall wine to solve this. using dnf remove then dnf install doesn't resolve this. I then deleted .wine manually and tried reinstalling wine. But then wine install refused to make a new .wine. This installation/removal is presuming it will never break and you don't need to delete .wine and start over.

Wine literally has stuff thrown around the entire system and it refuses to remove them in any fashion. It's a permanent unfixable installation. And manually removing breaks everything. It's a virus. I used, "sudo dnf remove wine*", and it removed none of those files or folders. Even though they were labeled wine something.
 
Last edited:
It has to be getting the character from somewhere. I would assume it's that or some random character from some inner code in the game. That I would think is the other logical answer.

^C is a normal one that comes up in the command line when a command is in the middle of executing and you hit certain buttons. Maybe that is popping up instead of the actual key. Anyone know what that is normally? ^A is another common one. Maybe it's sending that instead of the normal key data.

On my command line Ctrl+c is ^C. Other key combos may produce this though. Maybe it is related.

Hard to figure out since ED is the only application this is happening. Notepad, winecfg, regedit all work just fine.

Saving these keybindings may fail because they're really something the game does not expect them to be.
 
I deleted both ed-wine and .wine and removed wine via, "sudo dnf remove wine" and then I reinstalled wine via, "sudo dnf install wine". it refused to make a new .wine folder during install and every aspect of teh wine install is messing up and not doing what it should.

It also won't remove winetricks via dnf remove.. But it will install it. And manually deleting winetricks messes everything up. I had to restore it from the trash folder along with .wine And it still thinks dotnet is installed for some reason. Even with a new ed-wine.

It has to be hiding something somewhere on the system outside of the ed-wine folder.

I used this:



It's normally this:



I can't figure out where the first one installed the dotnet452 too. If it's in ed-wine I deleted that and it's preserving it's belief that dotnet is installed. I'm not sure why.

I tried to reinstall wine to solve this. using dnf remove then dnf install doesn't resolve this. I then deleted .wine manually and tried reinstalling wine. But then wine install refused to make a new .wine. This installation/removal is presuming it will never break and you don't need to delete .wine and start over.

Wine literally has stuff thrown around the entire system and it refuses to remove them in any fashion. It's a permanent unfixable installation. And manually removing breaks everything. It's a virus. I used, "sudo dnf remove wine*", and it removed none of those files or folders. Even though they were labeled wine something.

installing and uninstalling system packages (with eg dnf) never touches the configuration created by the software in those packages in users' homes.

In other words, 'sudo dnf remove wine' will not remove ~/.wine, nor will 'sudo dnf install wine' create that folder.

Both winetricks commands you quote will install dotnet452 to ~/ed-wine - that's what the WINEPREFIX environment variable at the beginning of the line is telling it to do. The only difference is the second version explicitly tells to use the wine binary in /usr/bin, whereas the first one leaves it to whatever is first on your PATH.
 
I might be missing what you are saying. I can't figure out where it installed it with the first command with no direct path given. I normally use the /usr/bin/whatever from the OP and if you delete ed-wine it deletes the install and you can reinstall dotnet with no problems. I'm trying to figure out the location of the no path version to delete it so it's not saying I have it installed. I can't find the location on the system. I thought that was the default for winetricks but can't find anything on where winetricks installs with no path given. It did install somewhere. And i thought sudo dnf install wine normally ceates the .wine folder. It's the initial folder for wine.
 
I might be missing what you are saying. I can't figure out where it installed it with the first command with no direct path given. I normally use the /usr/bin/whatever from the OP and if you delete ed-wine it deletes the install and you can reinstall dotnet with no problems. I'm trying to figure out the location of the no path version to delete it so it's not saying I have it installed. I can't find the location on the system. I thought that was the default for winetricks but can't find anything on where winetricks installs with no path given. It did install somewhere.

Yeah, I think we are talking past each other. Re-read my initial response to you, and if it doesn't stick, I think it will be quite painful to debug what's going wrong on your system remotely. Maybe try the Lutris suggestion by flyinspaghetti.

And i thought sudo dnf install wine normally ceates the .wine folder. It's the initial folder for wine.

Nope, system package management operations should never touch users' data. dnf calls rpm, which extracts the files in the package and runs any installation scripts in the package. You can see what they are with "rpm -q --scripts wine" (here, there are calls to ldconfig only). .wine is almost certainly being created on your system by running winecfg or winetricks.

You can learn more about how rpm works here: https://docs.fedoraproject.org/en-U...e/RPM_Guide-Using_RPM_DB-listing_scripts.html
and how dnf works here: https://fedoraproject.org/wiki/DNF?rd=Dnf
 
Except that now that is broken I can't use lutris either because the program is persistent now and lutris would rely on it. Not to mention lutris doesn't even work with proprietary drivers. It relys on x only so it's not going to go on my system. If it's so simple you should be able to tell me the default installation path. I'm not talking past you you are talking past me.

I already said that I normally install into the ed-wine directory and it normally can be deleted. That is not the point here. I've looked all over the system and can't find it or reference to it.

My system is no unrepairable because of their design. All the other software that would use wine now can't work properly. I now need to backup and reinstall my entire system.

https://wiki.winehq.org/Winetricks

Nothing on default locations or how it installs anything.

Using winetricks

Once you've obtained winetricks you can run it simply by typing sh winetricks at the console. You can also use ./winetricks if you chmod +x winetricks first. If run without parameters, winetricks displays a GUI with a list of available packages. If you know the names of the package(s) you wish to install, you can append them to the winetricks command and it will immediately start the installation process. For example,
sh winetricks corefonts vcrun6
will install both the corefonts and vcrun6 packages.

So, where would it normally put an install? There is nothing on how that works. That or it is holding onto some stupid reference somewhere and it doesn't have a way to remove it. This software is rediciously designed on a thought that it won't break down and hence only needs to do things in one direction. That is as lazy as you get.
 
Last edited:
Except that now that is broken I can't use lutris either because the program is persistent now and lutris would rely on it. Not to mention lutris doesn't even work with proprietary drivers. It relys on x only so it's not going to go on my system. If it's so simple you should be able to tell me the default installation path. I'm not talking past you you are talking past me.

Lutris uses it's own runtime and own sand boxed versions of wine independent of the system, if you're not even getting that working there's something probably wrong with your OS install, possibly you're missing important libraries or system files that both Lutris and system wine need.

If you're not doing this on an up to date distro then that's best place to start.
 
No, the problem with litrus is I use proprietary drivers for nvidia. It does not install if it does not detect and cant' use x. I had to remove x as normal install for proprietary on fedora.

sudo dnf install lutris
Error:
Problem: conflicting requests
- nothing provides xorg-x11-server-Xephyr needed by lutris-0.4.21-4.1.noarch

I was assuming it used wine. But it's good it doesn't use it raw.

I'm on fedora 28. I'm assuming it's a bit more up to date than most. But I could be wrong.

Any idea where and why winetricks and wine are holding onto dotnet as being installed?
 
No, the problem with litrus is I use proprietary drivers for nvidia. It does not install if it does not detect and cant' use x. I had to remove x as normal install for proprietary on fedora.



I was assuming it used wine. But it's good it doesn't use it raw.

I'm on fedora 28. I'm assuming it's a bit more up to date than most. But I could be wrong.

Any idea where and why winetricks and wine are holding onto dotnet as being installed?

Dotnet40 was uninstallable in 3.16 but was fixed in 3.17, there were also a few versions back it was also broke.

Also Lutris shouldn't need the x org display server, I'm running a Vulkan beta proprietary driver just fine.

Did you blacklist nouveau when you installed the proprietary driver? I'm not experienced with Fedora but I'm guessing that's why for lutris, it's probably expecting the open source driver to be running.
 
Except that now that is broken I can't use lutris either because the program is persistent now and lutris would rely on it. Not to mention lutris doesn't even work with proprietary drivers. It relys on x only so it's not going to go on my system. If it's so simple you should be able to tell me the default installation path. I'm not talking past you you are talking past me.

I already said that I normally install into the ed-wine directory and it normally can be deleted. That is not the point here. I've looked all over the system and can't find it or reference to it.

My system is no unrepairable because of their design. All the other software that would use wine now can't work properly. I now need to backup and reinstall my entire system.

https://wiki.winehq.org/Winetricks

Nothing on default locations or how it installs anything.



So, where would it normally put an install? There is nothing on how that works. That or it is holding onto some stupid reference somewhere and it doesn't have a way to remove it. This software is rediciously designed on a thought that it won't break down and hence only needs to do things in one direction. That is as lazy as you get.

i just did a runthrough of the install of winetricks, it doesn't appear to be operating outside of the WINEPREFIX at all..

One suggestion i had was, after the dnf uninstall wine, check the process tree for remnants of WINE running, this includes pgreping for things like "System" ".exe" "windows" and "wine".. just make sure no wine, winetricks, or windows-reimplementation processes are running at all before wiping out your WINEPREFIXes.. THEN try reinstalling it and going again.. it could be possible the "phantom copy" you're encountering is in RAM?

-m
 
Back
Top Bottom